Sysprep help for Windows 7

[stevec59]

Hi,
We have created a Syspreped image of windows 7 with all the drivers that we need, I have some questions:-

1) When we install the image on a new PC, it doesn't keep the Video driver, I have got around that by putting the install files in C:\temp and then running, is there a way to keep the video driver, so That I don't need to install?

2) We might want to Strip out the Licence code,
a) Is that possible
b) What effect will it have, will it just ask for licenec code or will you have to go through a lot of the setup again?


Thanks

Steve

 

[pparks1]

Are you doing "Generalized" when you do sysprep? This would take out the drivers so that you could install it on other hardware.

 

[Duzzy]

I think you use something along these lines,

sysprep.exe /generalize /unattend:answerfile

and in the answer file under the generalize configuration pass use the Microsoft-Windows-PnPSysprep\PersistAllDeviceInstalls

More info
Sysprep Command-Line Syntax
Prepare to Capture an Image for Deployment (Generalize)

 

[stevec59]

Thanks Guys, I am using:-

"In sysprep dialog that opens, choose System Cleanup Action as Enter System Out-of-Box-Experience (OOBE), select Generalize, select Shutdown Options Shutdown. Click OK"

But it keeps all the other drivers that I have added to the Basic Windows 7, x32 (NIC and a few others), which is good, it looses the Video, Is there a way around it?

What about the licence question?

Thanks

Steve

 

[Duzzy]

I've never used Sysprep myself only read a little when I created a Unattended setup so I've had a little play and a bit more of a read.

About the drivers and the info I gave previously.
I came to the conclusion that using Sysprep with Generalize will uninstall the driver but not remove the driver files. The next time that image is booted you will see a mini setup and part of that will display "Configuring Device Drivers" or something like that and during this stage (specialize pass) any previously installed 3rd-Party drivers will be installed. Now if that doesn't make much sense I found another thread that seems to confirm this but explains it differently (maybe better) - http://www.sevenforums.com/installation-setup/69246-deployment-sysprep-answer-files.html

Using PersistAllDeviceInstalls I think keeps the driver installed so during the mini setup it probably skips the "Configuring Device Drivers" stage but would cause errors if installed to a system with different hardware. I have not tried this yet so this is only a guess.

Your video driver
Now with your video driver and considering the above I would try installing Windows then your video driver. Next open Device Manager select your Display Adaptor and search automatically for a updated driver.

If Windows chooses a different driver then I would think this is your problem. During the "Configuring Device Drivers" stage it would be choosing the driver it thinks is best. Let us know what happens and maybe we can find a way around this.

If this image will only be installed to systems with identical hardware then you could also try the PersistAllDeviceInstalls. Sysprep GUI will need to be closed and run from the command line and include the /unattend switch. eg. sysprep.exe /oobe /generalize /shutdown /quiet /unattend:answerfile

Product Key.
I have read conflicting threads about Sysprep removing this so I can not say if it can be removed by Sysprep but I guessing your key remains after using Sysprep with Generalize which also happened with me, although my test may not be correct.

I can confirm that if you do not enter a Product Key during setup then you will be prompted for one when booting OOBE, so I would suggest if you can customise everything for your image without it and in less than 30 days then don't enter it. When you Sysprep with Generalize the Activation clock will rearm but if you plan on generalizing the image more than once then beware

If you do not use KMS, you can generalize the image to rearm the activation clock. However, you can rearm the clock only a limited number of times, determined by the Windows edition. After you reach this limit, you can still generalize the image, but the activation clock is not rearmed.

 

[kegobeer]

I think you use something along these lines,

sysprep.exe /generalize /unattend:answerfile

and in the answer file under the generalize configuration pass use the Microsoft-Windows-PnPSysprep\PersistAllDeviceInstalls

More info
Sysprep Command-Line Syntax
Prepare to Capture an Image for Deployment (Generalize)

To piggyback on this: if you don't know how to make an answerfile, check out this post:

Video Drivers Stripped Out during Sysprep

Also, watch this video that explains how to make one.

http://www.youtube.com/watch?v=PWnPWoQ1jqI

 

[stevec59]

Thanks for that

Things have been a bit hectic at work this week, so I haven't had a chance to look at this yet, but if I have any more questions, I will update this topic.

Thanks again

Steve