How to build a common Windows image
Hi there.
I have recently posted a "how to" article refering to building a common windows image for multiple hardware platforms.
Hopefully you can get something out of it.
Thanks.
http://www.oneforthelittleguy.com/2006/03/30/how-to-build-a-common-windows-image/
I have recently posted a "how to" article refering to building a common windows image for multiple hardware platforms.
Hopefully you can get something out of it.
Thanks.
http://www.oneforthelittleguy.com/2006/03/30/how-to-build-a-common-windows-image/
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
williamwbishop
18 years ago
We are supporting about IBM,DELL,HP and a couple other platforms, with support for notebooks as well, and loading 40 apps on a single image that is 2.5 gigs in size.
This is a for a company of 5000 users, and so far we've been exceedingly lucky, and built everything as we go. Everything we use is opensource, therefore free. We saved a few hundred thousand by not purchasing ghost or altiris. And no telling how much we saved by migrating to openoffice from MSoffice.
The things we've learned:
1. Stay away from sysprep v2, it blows.
2. Build your universal image in vmware, but do not install vmtools. We can add to the image in minutes and have a new revision in about an hour.
3. You can deploy the image with G4U/MIDS in around 4 minutes.
4. Pare down the drivers list, and be aware of any gotchas(The TPM security chipset on IBM's comes to mind).
We're actually moving back to less applications on the image and having our post run script call menus to install anything else. We use autohotkey to build mini menus and they are very quick on the network.
This is a for a company of 5000 users, and so far we've been exceedingly lucky, and built everything as we go. Everything we use is opensource, therefore free. We saved a few hundred thousand by not purchasing ghost or altiris. And no telling how much we saved by migrating to openoffice from MSoffice.
The things we've learned:
1. Stay away from sysprep v2, it blows.
2. Build your universal image in vmware, but do not install vmtools. We can add to the image in minutes and have a new revision in about an hour.
3. You can deploy the image with G4U/MIDS in around 4 minutes.
4. Pare down the drivers list, and be aware of any gotchas(The TPM security chipset on IBM's comes to mind).
We're actually moving back to less applications on the image and having our post run script call menus to install anything else. We use autohotkey to build mini menus and they are very quick on the network.
Posted by:
DeployTech
15 years ago
Posted by:
dubzaddict
15 years ago
Hi DT
thanx for the response
Yes I am in need of any material that can educate/assist me with packaging/imaging applications.
I have downloaded all your videos and the a great help..any formal education is not an option at the moment as the finances is nonexitant if i could say that...
BTW..awesome site[:D]
thanx for the response
Yes I am in need of any material that can educate/assist me with packaging/imaging applications.
I have downloaded all your videos and the a great help..any formal education is not an option at the moment as the finances is nonexitant if i could say that...
BTW..awesome site[:D]
Posted by:
DeployTech
15 years ago
Posted by:
Imaster
18 years ago
Posted by:
TNguyen81
18 years ago
Posted by:
Imaster
18 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.