Take the 2-minute tour ×

e.g. I have a master PC, install drivers and sysprep and take image. On PC 2 I installed that image, update any drivers, sysprep and take image. Move to PC 3, install the image, update drivers, sysprep and take image.

Now will this final image contain drivers for all 3 PC types?

share|improve this question
add comment

3 Answers

Yes this will work, but it is a bad idea. Sysprep maintains a count of how many times it's been run. If you do this, you'll max out that count and make a lot of work for yourself.

Install all of your drivers on the first machine, then sysprep it.

If you're using WDS, you can push drivers with the image. Also, you can use dism to add drivers to an offline image before you push it down.


Since you're running XP, there is a Microsoft approved way of adding drivers to the image. This might work out much better for you. Check out this KB article:

share|improve this answer
Thanks for the reply. I don't think there is a limit if you are on Volume Licence? –  Hax Jan 31 '11 at 15:19
Even with a volume license there is a 3 sysprep limit. VL still needs activation and the limit was imposed to prevent people from trying to circumvent activation with sysprep. –  Jason Berg Jan 31 '11 at 15:27
I'm doing XP SP3 sysprep, if that makes a difference? –  Hax Feb 1 '11 at 10:28
That does make a difference. VL versions of XP do not require activation. There is no sysprep limit. There is a way to have sysprep install drivers for you though. –  Jason Berg Feb 1 '11 at 14:54
Resetting Windows Activation - technet.microsoft.com/en-us/library/cc766514(WS.10).aspx. "If you anticipate running Sysprep multiple times on a single computer, you must use the SkipRearm setting" –  thing2k Feb 1 '11 at 15:08
add comment

For Win XP If you have Volume Licence AND VL media, you can do it as many times as you want! See the MS link : http://support.microsoft.com/kb/299840

share|improve this answer
add comment

You would end up with all drivers installed, but you may also end up with some issues due to driver utilities (say NVidia control panel) attempting to launch on systems not containing the driver. This is a really bad way to do this.

You'd be much better served by exporting all non-Microsoft drivers off each PC with a tool like Double Driver, and then using Sysprep Driver Scanner prior to a sysprep on your master image.

share|improve this answer
add comment

Your Answer


