Sysprep woes

[techleet]

Hi all!

I'm having issues with Sysprep for Windows 2000. I'm using Sysprep v1.1

I'm trying to create a master ghost image for all machines in my company. The target machines all have the same HAL, and the Mass Storage Controllers are taken care of by Sysprep.

I have put all the drivers for all the hardware on all the systems under a directory called C:\Sysprep\$OEM$\$1\Drivers, for example:

C:\Sysprep\$OEM$\$1\Drivers\Sp27103\SMAXWDM\W2K_XP
C:\Sysprep\$OEM$\$1\Drivers\3CC8-10\Drivers\Modem\W2K



I have included the following section in SYSPREP.INF:

[unattended]
OemPnPDriversPath=sysprep\$oem$\$1\drivers\sp27103 \smaxwdm\w2k_xp;sysprep\$oem$\$1\drivers\3cc8-10\drivers\modem\w2k

I have over 50 driver directories, and entries to match.

Some drivers get loaded during the mini setup and some don't.

My questions:

- Why do some get loaded and some don't? LOL!

- Does the mini-setup search all subdirectories under C:\sysprep\$oem$\$1\Drivers for drivers, or do you have to specify the full path to each and every INF file in the OemPnPDriversPath?


By the way, I use the -pnp switch when running sysprep. Do I have to?

Thank you for any and all input!

[techleet]

Any ideas? Thanks!

[capcomind]

Hi all!

I'm having issues with Sysprep for Windows 2000. I'm using Sysprep v1.1

I'm trying to create a master ghost image for all machines in my company. The target machines all have the same HAL, and the Mass Storage Controllers are taken care of by Sysprep.

I have put all the drivers for all the hardware on all the systems under a directory called C:\Sysprep\$OEM$\$1\Drivers, for example:

C:\Sysprep\$OEM$\$1\Drivers\Sp27103\SMAXWDM\W2K_XP
C:\Sysprep\$OEM$\$1\Drivers\3CC8-10\Drivers\Modem\W2K



I have included the following section in SYSPREP.INF:

[unattended]
OemPnPDriversPath=sysprep\$oem$\$1\drivers\sp27103 \smaxwdm\w2k_xp;sysprep\$oem$\$1\drivers\3cc8-10\drivers\modem\w2k

I have over 50 driver directories, and entries to match.

Some drivers get loaded during the mini setup and some don't.

My questions:

- Why do some get loaded and some don't? LOL!

- Does the mini-setup search all subdirectories under C:\sysprep\$oem$\$1\Drivers for drivers, or do you have to specify the full path to each and every INF file in the OemPnPDriversPath?


By the way, I use the -pnp switch when running sysprep. Do I have to?

Thank you for any and all input!

[FONT=Courier New][SIZE=7][COLOR=Navy]

I believe the problem lies with the number of drivers you are trying to keep in the file. There is a limit to the number of characters allowed, I think its about 250. After experiencing a similar issue I took a sysprepped image and installed it on every variant of machine which we have, installing any missing drivers, then I sysprepped the disc it before moving it onto the next machine. It seems to work ;-). Its long winded but it gets round the text file limitation. Also if you are using later intel chipsets if you sysprep a machine you will need to run the latest inf update to enable correct driver detection. The /pnp switch isn't necessary unless you are using non pnp drivers, however, it does seem to make for a much cleaner installation.

[Saerdna]

I wrote up a possible answer to your question on another forum where I was working on the same concept.

http://forums.windrivers.com/showthr...306#post617306

My last post on the second page might help.