I need help with sysprep 2.0

[hrp2171]

H E L P!!! S. M. S.!!! Save My Ship!!!

Here it goes:

Whenever we order new computer systems, I install the OS and all the apps we need from scratch. We also customize the settings and create a default user profile. After that's done, we run sysprep and use Norton Ghost to create an image to use on the rest of the systems. With Windows 2000 Professional, that process works great but I'm running into problems with Windows XP Professional.

Mainly, Windows 2000 would just prompt for a computer name and the admin password because that's the way we setup the sysprep.inf file. After mini-setup, Windows 2000 would just come up ready for production. On the other hand, Windows XP keeps losing the network card drivers. It prompts me to install the network card drivers after mini-setup is done. It's so annoying to see that after a successful sysprep configuration. Windows 2000 does not change anything in the hardware configuration whatsoever.

Why is Windows XP losing the network card configuration? Is it sysprep that's mucking up the network card configuration?

Here is the line I use for sysprep 2.0 in XP:

sysprep.exe -mini -reseal -quiet -reboot

Here is the sysprep.inf:

;SetupMgrTag

[unattended]

InstallFilesPath=C:\sysprep\i386

OEMSkipEula=Yes

[GuiUnattended]

EncryptedAdminPassword=NO

OEMSkipRegional=1

TimeZone=4

[userData]

ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

FullName="IT Department"

OrgName="IT Department"

[TapiLocation]

CountryCode=1

Dialing=Tone

AreaCode=831

LongDistanceAccess="9"

[setupMgr]

DistFolder=C:\sysprep\i386

DistShare=windist

[identification]

JoinWorkgroup=workgroup

[Networking]

InstallDefaultComponents=Yes

Thanks,

Hector

[hrp2171]

I'm getting close to Windows XP mini-setup nirvana.

The last 3 lines in the [unattended] section are part of the solution.

I'm still running into another wall, but will soon find out how to get around it.

Here is my newly modified sysprep.inf based on some tips found on the 'net:

;SetupMgrTag

[unattended]

InstallFilesPath=C:\sysprep\i386

OEMSkipEula=Yes

DriverSigningPolicy=Ignore

OEMPNPDriversPath=c:\sysprep\i386\$oem$\$1\drivers\nic

UpdateInstalledDrivers=Yes

[GuiUnattended]

EncryptedAdminPassword=NO

OEMSkipRegional=1

OEMSkipWelcome=1

TimeZone=4

AdminPassword="adminpasshere"

[userData]

ProductKey=product-key-here

FullName="IT Dept"

OrgName="IT Dept"

[TapiLocation]

CountryCode=1

Dialing=Tone

AreaCode=831

LongDistanceAccess="9"

[identification]

JoinDomain=domain

[Networking]

InstallDefaultComponents=Yes

[hrp2171]

This is an FYI. Hopefully this information will be helpful to others.

I posted the same question about sysprep 2.0 and XP at the Microsoft's OEM System Builders newgroup. I was told that sysprep 2.0 removes all network interfaces when it runs and you have to have Signed drivers for your network card if you want it to work after mini-setup is done. There is a workaround by adding the 3 lines mentioned on my previous post. However, it's still not working as prescribed and I'm always being prompted for the location of the unsigned drivers for my network card.

I will master the process no matter what.

[yourtech]

You might want to check these links out:

http://unattended.msfn.org/xp/oemfolders.htm

http://unattended.msfn.org/xp/drivers.htm

OEMPNPDriversPath=c:\sysprep\i386\$oem$\$1\drivers\nic

looks like it could be your path

[hrp2171]

Hmm, I've already tried using "Drivers\NIC" for my OEM drivers path.

I'll try it again. It seems though, that it doesnt matter which path I use it ignores my OEM drivers path and it wants to use the one in the registry.

Thanks for the links. I'll keep this thread updated.

[Jazkal]

It is a known problem of Sysprep.

Sysprep will NOT install unsigned drivers.

DriverSigningPolicy=Ignore

This entry does nothing at all for sysprep, it ignores it totally.

The only work around is to use the -pnp switch with sysprep, but it has lots of drawbacks. Try it out and see if you can deal with the side effects.

[rdalling]

Add this a run command before you execute the other applications to build and they will install...

regedit.exe /s D:\MSI\RemoveZen\DriverSignOff.reg

DriverSignOff.reg

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Non-Driver Signing]

"Policy"=hex:00

Roger