Problem in sysprep

[iceangel89]

i am following "Art of OEM" guide here

doing the after gathering all drivers, building mass storage section with "sysprep -bmsd " and running sysprep i get something like cannot update regisry y is this so? i read on Microsoft that its likely to be problems with mass storage section but i didn't edit it. EDIT: see attached file

also after running setupmgr, the sysprep.inf i get is

;SetupMgrTag
 [Unattended]
	 OemSkipEula=Yes
	 InstallFilesPath=C:\sysprep\i386

 [GuiUnattended]
	 AdminPassword=*
	 EncryptedAdminPassword=NO
	 OEMSkipRegional=1
	 TimeZone=215
	 OemSkipWelcome=1

 [UserData]
	 ProductKey=XXX
	 FullName="XXX"
	 OrgName=""
	 ComputerName=*

 [RegionalSettings]
	 LanguageGroup=10,9

 [SetupMgr]
	 DistFolder=C:\sysprep\i386
	 DistShare=windist

 [GuiRunOnce]
	 Command0="cmd /c "rd %SystemDrive%\$WINDOWS.~BT /s /q""
	 Command1="cmd /c "rd %SystemDrive%\$WINDOWS.~LS /s /q"

 [Identification]
	 JoinWorkgroup=XXX

 [Networking]
	 InstallDefaultComponents=Yes

so is "InstallFilesPath=C:\sysprep\i386" not "InstallFilesPath="C:\WINDOWS\Driver Cache\i386"" as in the guide which is correct?

also the guide's

[SetupMgr]
 DistFolder="C:\WINDOWS\Driver Cache\i386"
 DistShare=windist

vs mine

[SetupMgr]
	 DistFolder=C:\sysprep\i386
	 DistShare=windist

Removed attachment - be sure to remove product keys before posting answer files.

Edited October 30, 2007 by IcemanND

[IcemanND]

Actually it is a problem with permissions in the registry where sysprep puts the critical device settings for the mass storage controllers.

Easiest way to get around it is as follows:

Open CMD window.

type: at 13:06 /interactive cmd.exe

where 13:06 is one minute ahead of the current system time.

A new CMD window will open which is running under the SYSTEM account header will be 'c:\windows\system32\svchost.exe'

run sysprep with your desired switches from the new CMD window.

[iceangel89]

thanks, but i still get cannot update registry? i am doing it in VMware doesn't make a difference right? i also have used Sysprep Driver Scanner to add tthe driver links to te registry successfully

sysprep -bmsd

shouldn't create any wrong things right? but if i delete the whole mass storage section it works

by the way, what switches should i use? i read that

sysprep -reseal -mini -reboot

is enough somewhere. but i ddn't use reboot, will reboot restart the comp or shutdown (which is what i would want)?

also what does -nosidgen -activated -pnp do? do i need them?

[IcemanND]

try this:

Add the following to the end of your sysprep.inf, having only blank lines after [sysprepMassStorage]

[Sysprep]
	BuildMassStorageSection=yes

[SysprepMassStorage]

Run sysprep from the system command prompt. using sysprep -reseal -mini -pnp

nosidgen - does not reset the SID (System ID)

activated - does not reset the 30 activation grace period

[iceangel89]

zzz... i still get the same error, that build mass storage section still makes the same list of stuff as "sysprep -bmsd" so guess it didn't help too much... u had this error b4? or any1 else? and how do i fix this? Microsoft says its becos of errors in MassStorage section but i didn't edit it myself!

http://support.microsoft.com/kb/249690

a little quote

To troubleshoot this issue, check the following:
1.	Check the PnpIDs left of the equal sign (=) to make sure they match the PnpIDs listed right of the corresponding equal sign.
2.	Check the spelling of each corresponding .inf file right of the equal sign.
3.	If the controller is supplied by an OEM, make sure the path to the .inf file is correct, the description field matches what is included in the Txtsetup.oem file, and the disk tag and ID match.

i got some drivers from http://www.driverpacks.net/DriverPacks/

should be ok right? does OEM drivers create this problem? i got mainly the LAN, MassStorage & Sound drivers so that the image can be as Universal as possible, i have also compiled drivers from my own PCs.

mmm...

a little of the mass storage section >

pci\ven_8086&dev_2662=c:\windows\inf\machine.inf
pci\ven_8086&dev_2664=c:\windows\inf\machine.inf
pci\ven_8086&dev_2666=c:\windows\inf\machine.inf
*int0800=c:\windows\inf\machine.inf
pci\ven_8086&dev_0008=c:\windows\inf\machine.inf
pci\ven_8086&dev_0326=c:\windows\inf\machine.inf
pci\ven_1033&dev_00a9&cc_0600=c:\windows\inf\machine.inf
pci\ven_1033&dev_00aa&cc_0500=c:\windows\inf\machine.inf
pci\ven_1033&dev_00ab&subsys_00ab1033=c:\windows\inf\machine.inf
pci\ven_1033&dev_00ac&cc_0600=c:\windows\inf\machine.inf
pci\ven_1033&dev_00ad&cc_0600=c:\windows\inf\machine.inf
pci\ven_1033&dev_00ae&cc_0600=c:\windows\inf\machine.inf
pci\ven_1033&dev_00af=c:\windows\inf\machine.inf
pci\ven_1033&dev_00b0=c:\windows\inf\machine.inf
pci\ven_1033&dev_00b1&cc_0600=c:\windows\inf\machine.inf
*pnp0a00=c:\windows\inf\machine.inf
*pnp0a01=c:\windows\inf\machine.inf
*pnp0a04=c:\windows\inf\machine.inf
*pnp0a03=c:\windows\inf\machine.inf
pci\cc_0604=c:\windows\inf\machine.inf
pci\cc_0601=c:\windows\inf\machine.inf
pci\cc_0602=c:\windows\inf\machine.inf
pci\cc_0600=c:\windows\inf\machine.inf
*pnp0c0e=c:\windows\inf\machine.inf
*pnp0c15=c:\windows\inf\machine.inf
acpi\dockdevice=c:\windows\inf\machine.inf
acpi\dockdevice&_sb_.pci_.oak_=c:\windows\inf\machine.inf
acpi\dockdevice&_sb_.pci_.isa_.slce=c:\windows\inf\machine.inf
acpi\fixedbutton=c:\windows\inf\machine.inf
acpi\thermalzone=c:\windows\inf\machine.inf
isapnp\readdataport=c:\windows\inf\machine.inf
pci\ven_10aa&dev_0000=c:\windows\inf\machine.inf
pci\ven_1025&dev_1435=c:\windows\inf\machine.inf
pci\ven_10b9&dev_1445=c:\windows\inf\machine.inf

looks ok right? but whats those with the "*" in front?

[iceangel89]

anyone knows why??

[iceangel89]

i think its something wrong with the drivers, how can i chk if drivers are OEM etc? drivers from http://www.driverpacks.net/DriverPacks/DriverPack.php?pag=m anyone tried with sysprep?

[IcemanND]

I haven't used the current massstorage driver packs but I have in the past, the last time was probably about 6 months ago. When I did I found a handful of the drivers were not properly arranged so they wouldn't add correctly.

Did you add the massstorage pack to your installation media or are you using it only at sysprep?

[iceangel89]

i have so far only tried on sysprep, maybe i try not adding them to see how. by the way the problem is caused by Mass Storage drivers only? or any other drivers can also cause the problem?

[IcemanND]

No, as far as I know only the massstorage drives will cause any issues. The other drivers are not used until mini-setup after deployment.

[iceangel89]

i am following Art of OEM and using BDD207 to organize my drivers, and noticed some drivers that are for x86, x64 and ia64 (2 or more from these 3) does it matter? i am testing if removing such drivers make a difference, FYI some are under System, SCSIAdapter others Net, etc.

[iceangel89]

can i just integrate the drivers with nLite and not do this? can't right?

[IcemanND]

I have never tried creating the image using an nLited install. The last time I did I had further problems post sysprep, those problems may have been resolved but I have just never tried it again.

[dexter.inside]

I have never tried creating the image using an nLited install. The last time I did I had further problems post sysprep, those problems may have been resolved but I have just never tried it again.

I did, and the problems are solved, nLite doesn't screw up sysprep functionality anymore

[iceangel89]

I have never tried creating the image using an nLited install. The last time I did I had further problems post sysprep, those problems may have been resolved but I have just never tried it again.

I did, and the problems are solved, nLite doesn't screw up sysprep functionality anymore

buyt does this mean i use a nLited install with Mass Storage drivers integrated means i do now have to use "sysprep -bmsd"? that could solve my problems