VMware image creation/hal/domains

[axelseaa]

Greetings!

I am attempting to build a windows image on a VMware Virtual Machine.

I have been using the sysprep file below, and have been running "sysprep -mini -reseal".

Here is the problem. When the mini setup runs, it does not have the network drivers installed so it is not able to join the domain. The weird thing however, is that after the first login, windows detects and installs all the drivers successfully without asking for locations of drivers, which leads me to believe its not an issues with mini setup finding the drivers.

Does the OemPNPDriversPath directory structure have to be anything specific?

Is there any reason for this behavior?

Any info is appreciated, thanks!

-- Aaron

Sysprep.inf:

;SetupMgrTag

[unattended]InstallFilesPath=C:\sysprep\i386

ExtendOEMPartition=1

KeepPageFile=0

DriverSigningPolicy=ignore

UpdateUPHAL=ACPIPIC_UP,%systemroot%\inf\hal.inf

UpdateInstalledDrivers=Yes

OemSkipEula=Yes

TargetPath=\WINDOWS

OemPnPDriversPath=sysprep\drivers\gx260\audio;sysprep\drivers\gx260\network;sysprep\drivers\gx260\system;sysprep\drivers\gx270\audio;sysprep\drivers\gx270\mainboard;sysprep\drivers\gx270\network;sysprep\drivers\gx270\video;sysprep\drivers\gx280\audio;sysprep\drivers\gx280\mainboard;sysprep\drivers\gx280\nic;sysprep\drivers\gx280\video;sysprep\drivers\p670\audio;sysprep\drivers\p670\chipset;sysprep\drivers\p670\monitor;sysprep\drivers\p670\nic;sysprep\drivers\p670\video;sysprep\drivers\i8200\chipset;sysprep\drivers\i8200\network;sysprep\drivers\i8200\sound;sysprep\drivers\i8200\video;sysprep\drivers\i8200\wifi;sysprep\drivers\i8200\;sysprep\drivers\gx620\audio;sysprep\drivers\gx620\system;sysprep\drivers\gx620\nic

[GuiUnattended]

AdminPassword=*

EncryptedAdminPassword=NO

OEMSkipRegional=1

OEMDuplicatorstring="LTC // Built from WinXP SP2 - May 2nd 2006"

TimeZone=20

OemSkipWelcome=1

[userData]

ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

FullName="Example User"

OrgName="Example Org"

[Display]

BitsPerPel=32

Xresolution=1280

YResolution=1024

Vrefresh=60

[identification]

JoinDomain=EXAMPLE.COM

DomainAdmin=EXAMPLE\Installer

DomainAdminPassword="password"

MachineObjectOU="OU=Workstations,DC=example,DC=com"

[TapiLocation]

CountryCode=1

Dialing=Tone

AreaCode=262

LongDistanceAccess="1"

[RegionalSettings]

LanguageGroup=2,7,13

[setupMgr]

DistFolder=C:\sysprep\i386

DistShare=windist

[Networking]

InstallDefaultComponents=Yes

[sysprep]

BuildMassStorageSection=yes

[sysPrepMassStorage]

[branding]

BrandIEUsingUnattended=Yes

Home_Page=http://www.uww.edu

[Proxy]

Proxy_Enable=0

Use_Same_Proxy=0

[Components]

IEAccess = Off

OEAccess = Off

WMAccess = Off

Msnexplr = Off

WMPOCM = Off

[flite]

I cant say for certain, but I think the oempnpdrivers line isnt correct. i believe it needs a \ at the beginning of each line. although since i found this little handy utility (http://www.vernalex.com/tools/spdrvscn/index.shtml). i havent had to know.

[axelseaa]

That definetly looks like a handy program, i'll give that a shot and see what happens.

The way the image is setup, it is in a VM Virtual machine, and the HAL is set to Standard PC. Could the UpdateUPHal line of the sysprep be causing the drivers to not work at mini-setup?

[flite]

have you tried running sysprep with the -pnp switch?

[axelseaa]

have you tried running sysprep with the -pnp switch?

I did before, but the sysprep documentation says that the UpdateInstalledDrivers line and the -pnp switch should not be used together. This also appeared to be the issue before as well though

[IcemanND]

check the windows\inf directory and delete and oemxx.inf oemxx.pnf files there. (where xx is 00..99+)

When I had a similar problem it was trying to use these files instead of the infs in my drivers directory.

[axelseaa]

check the windows\inf directory and delete and oemxx.inf oemxx.pnf files there. (where xx is 00..99+)

When I had a similar problem it was trying to use these files instead of the infs in my drivers directory.

Tried that, still similiar behavior. I also tried the program posted above to detect the drivers. When i used that, the drivers were not installed at all, and nothing worked.