View Full Version : Making a master ghost image
kleptophobiac
07-27-2005, 11:58 AM
I've prepared a ghost image to go on some 400 computers, but they have varying hardware. I would use the sysprep tool, but that means I have to reenter the license key on each machine. This is unnacceptable, considering we have volume licensing with a single key. I also don't want to have to go through the bloody mini setup, and the inf file that microsoft's sysprep answer file maker makes is ignored.
Is there a better way? Is there a way to use sysprep to reset the drivers without pwning other things?
Roach
07-27-2005, 12:24 PM
How much do the systems vary in hardware? Perhaps using nlite and making an install cd with multiple drivers might work? I've never tried loading more than one display adapter or anything so I'm not entirely sure.
djnes
07-27-2005, 12:30 PM
You need to reread the sections on unattended over again to find the error somewhere. The VLK key should be read in and re-used. That's the only way your going to be able to do it, as far as I know. Nlite isn't a solution to your problem, because it still would involve installing the OS manually on each machine.
Phoenix86
07-27-2005, 02:23 PM
I would use the sysprep tool, but that means I have to reenter the license key on each machine.
Sysprep is the solution, learn it, live it, love it.
Longhorn uses syspreped images as the base installer as opposed to a traditional setup routine.
Edit sysprep.inf to include the key.
[UserData]
ProductID=<Insert VLA Key here>
FullName=<Insert User>
OrgName=<Insert orginization's name>
kleptophobiac
07-27-2005, 07:00 PM
I finally got it to work. I never knew windows systems cared about case. I couldn't get sysprep to recognize the inf until I made it with an uppercase S. Go figure!
Anyway, it worked great once I got past that niggle.
Phoenix86
07-28-2005, 01:11 PM
I finally got it to work. I never knew windows systems cared about case. I couldn't get sysprep to recognize the inf until I made it with an uppercase S. Go figure!
Anyway, it worked great once I got past that niggle.
:confused:
Mine is lower case. It shouldn't matter...
vBulletin® v3.8.2, Copyright ©2000-2009, Jelsoft Enterprises Ltd.