XP SP2 Sysprep - drivers not installed during mini-setup wizard?


B

Barkley Bees

I am updating an existing Windows XP SP2 image with the below goals
:
1. Adding new drivers to support new hardware.
2. Updating existing application versions and installing latest the security
patches.

As a first test step I took our existing image and updated the local
C:\Drivers dir with the necessary drivers for our new hardware models.
I then used Vernalex's handy sysprep driver scanner
(http://www.vernalex.com/tools/spdrvscn/index.shtml) to update the registry
here:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath

I, of course, had my sysprep.inf prepared and then ran
"sysprep.exe -reseal -mini -quiet". The system then rebooted and everything
came up roses. The new image worked fine on the new systems and detected all
the hardware during the mini-setup wizard.

After this intial test I went back to the original image and updated the
versions of existing apps, made some updates to the IE settings and
installed the most recent security patches (not SP3 though as we have a
compatibility issue with some internal apps at this time).

I then add the updated drivers as I did in my testing and did a sysprep
"sysprep.exe -reseal -mini -quiet". The system reboots and the does not
detect any drivers during the mini-setup wizard. This is on the same system
I performed the testing. I am now scratching my head to figure out what may
be the issue?

I did have to install the nic drivers on this system before I did the
sysprep in order to install the the updates from Microsoft though. Could
this be a potential cause?

Here is my sysprep answer file for reference. Note that the
"OemPnPDriversPath" line is not there as the drivers have already written to
the registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath)
just before sysprep-ing. Appreciate any help/advice:
----------------------------------------------------------------------------
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS
UpdateUPHAL = ACPIAPIC_UP,WINDOWS\Inf\Hal.inf

[GuiUnattended]
AdminPassword=xxxxxxxxx
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=xxx
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1

[UserData]
ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName="xxxxxxxxxxxxxxxxxxxx"
OrgName="xxxxxxxxxxxxxxxxxxxx"


[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=75

[RegionalSettings]
LanguageGroup=x
UserLocale=00000xxx
SystemLocale=00000xxx
InputLocale=0xxx:e0200xxx
UserLocale_DefaultUser=00000xxx
InputLocale_DefaultUser=0xxx:e0200xxx


[Identification]
JoinDomain=xxx

[Networking]
InstallDefaultComponents=Yes

[NetOptionalComponents]
SNMP=1

[GuiRunOnce]
Command0="netsh firewall reset"
Command1="C:\setup\custom.bat"
[sysprepcleanup]

----------------------------------------------------------------------------
 
Ad

Advertisements

B

Barkley Bees

So I went back and added the following two lines to my [unattended] portion
of the sysprep.inf (assuming this is the correct thing to do):

DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes


I then did a "sysprep -reseal -mini -quiet". Upon rebooting, the drivers are
properly detected during the mini-setup phase. There is one issue though,
during the mini-setup phase the "New Hardware Wizard" pops up multiple times
as it detects the new hardware. Is there anyway to hide this from the end
users as there is no need for them to see this. Much appreciate any
feedback.


Barkley Bees said:
I am updating an existing Windows XP SP2 image with the below goals
:
1. Adding new drivers to support new hardware.
2. Updating existing application versions and installing latest the
security patches.

As a first test step I took our existing image and updated the local
C:\Drivers dir with the necessary drivers for our new hardware models.
I then used Vernalex's handy sysprep driver scanner
(http://www.vernalex.com/tools/spdrvscn/index.shtml) to update the
registry here:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath

I, of course, had my sysprep.inf prepared and then ran
"sysprep.exe -reseal -mini -quiet". The system then rebooted and
everything came up roses. The new image worked fine on the new systems and
detected all the hardware during the mini-setup wizard.

After this intial test I went back to the original image and updated the
versions of existing apps, made some updates to the IE settings and
installed the most recent security patches (not SP3 though as we have a
compatibility issue with some internal apps at this time).

I then add the updated drivers as I did in my testing and did a sysprep
"sysprep.exe -reseal -mini -quiet". The system reboots and the does not
detect any drivers during the mini-setup wizard. This is on the same
system I performed the testing. I am now scratching my head to figure out
what may be the issue?

I did have to install the nic drivers on this system before I did the
sysprep in order to install the the updates from Microsoft though. Could
this be a potential cause?

Here is my sysprep answer file for reference. Note that the
"OemPnPDriversPath" line is not there as the drivers have already written
to the registry
(HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath) just before
sysprep-ing. Appreciate any help/advice:
----------------------------------------------------------------------------
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS
UpdateUPHAL = ACPIAPIC_UP,WINDOWS\Inf\Hal.inf

[GuiUnattended]
AdminPassword=xxxxxxxxx
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=xxx
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1

[UserData]
ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName="xxxxxxxxxxxxxxxxxxxx"
OrgName="xxxxxxxxxxxxxxxxxxxx"


[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=75

[RegionalSettings]
LanguageGroup=x
UserLocale=00000xxx
SystemLocale=00000xxx
InputLocale=0xxx:e0200xxx
UserLocale_DefaultUser=00000xxx
InputLocale_DefaultUser=0xxx:e0200xxx


[Identification]
JoinDomain=xxx

[Networking]
InstallDefaultComponents=Yes

[NetOptionalComponents]
SNMP=1

[GuiRunOnce]
Command0="netsh firewall reset"
Command1="C:\setup\custom.bat"
[sysprepcleanup]
 
B

Barkley Bees

So I have gone the route of removing the below from my sysprep.inf:

DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes

I have 4 target hardware (Dell Latitude E4200, E4300, E6400 and Optiplex
760) for my image. So, I used the E6400 as my reference PC and configured
the OS the way it needed to be. I only installed the nic (Intel 82567LM
Gigabit Network Adapter) driver as I needed network connectivity to download
the latest patches, etc

All of the sysmtesm install fine with my new image and drivers get loaded
accordingly except for the E6400 (reference PC). I think that this may be
cause of my problem as I left the nic drivers installed. When the image is
loaded on to the E6400 the nic shows up but nothing else gets loaded. Is it
possible that the minisetup wizard simply ignores the other devices
(chipset, audio, etc) since the nic drivers were already installed?

If so, I will go back to my pre-sysprep image and attempt to fully uninstall
the nic drivers I foolishly installed and then sysprep that image. Can
anyone advise if this may be the contributing factor?

Also, for completely unisntalling all traces of the installed nic drivers I
have found the following (does this seem like the way to go?):

http://remyservices.wordpress.com/2007/09/28/sysprep-in-depth-part-4-cleaning-up-unneeded-drivers/

Thanks again all and appreciate your help.


Barkley Bees said:
So I went back and added the following two lines to my [unattended]
portion of the sysprep.inf (assuming this is the correct thing to do):

DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes


I then did a "sysprep -reseal -mini -quiet". Upon rebooting, the drivers
are properly detected during the mini-setup phase. There is one issue
though, during the mini-setup phase the "New Hardware Wizard" pops up
multiple times as it detects the new hardware. Is there anyway to hide
this from the end users as there is no need for them to see this. Much
appreciate any feedback.


Barkley Bees said:
I am updating an existing Windows XP SP2 image with the below goals
:
1. Adding new drivers to support new hardware.
2. Updating existing application versions and installing latest the
security patches.

As a first test step I took our existing image and updated the local
C:\Drivers dir with the necessary drivers for our new hardware models.
I then used Vernalex's handy sysprep driver scanner
(http://www.vernalex.com/tools/spdrvscn/index.shtml) to update the
registry here:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath

I, of course, had my sysprep.inf prepared and then ran
"sysprep.exe -reseal -mini -quiet". The system then rebooted and
everything came up roses. The new image worked fine on the new systems
and detected all the hardware during the mini-setup wizard.

After this intial test I went back to the original image and updated the
versions of existing apps, made some updates to the IE settings and
installed the most recent security patches (not SP3 though as we have a
compatibility issue with some internal apps at this time).

I then add the updated drivers as I did in my testing and did a sysprep
"sysprep.exe -reseal -mini -quiet". The system reboots and the does not
detect any drivers during the mini-setup wizard. This is on the same
system I performed the testing. I am now scratching my head to figure out
what may be the issue?

I did have to install the nic drivers on this system before I did the
sysprep in order to install the the updates from Microsoft though. Could
this be a potential cause?

Here is my sysprep answer file for reference. Note that the
"OemPnPDriversPath" line is not there as the drivers have already written
to the registry
(HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath) just before
sysprep-ing. Appreciate any help/advice:
----------------------------------------------------------------------------
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS
UpdateUPHAL = ACPIAPIC_UP,WINDOWS\Inf\Hal.inf

[GuiUnattended]
AdminPassword=xxxxxxxxx
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=xxx
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1

[UserData]
ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName="xxxxxxxxxxxxxxxxxxxx"
OrgName="xxxxxxxxxxxxxxxxxxxx"


[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=75

[RegionalSettings]
LanguageGroup=x
UserLocale=00000xxx
SystemLocale=00000xxx
InputLocale=0xxx:e0200xxx
UserLocale_DefaultUser=00000xxx
InputLocale_DefaultUser=0xxx:e0200xxx


[Identification]
JoinDomain=xxx

[Networking]
InstallDefaultComponents=Yes

[NetOptionalComponents]
SNMP=1

[GuiRunOnce]
Command0="netsh firewall reset"
Command1="C:\setup\custom.bat"
[sysprepcleanup]
 
Ad

Advertisements

B

Barkley Bees

Well I have found the embarassingly simple cause of my problem where the
drivers will get not installed to the system I used as a reference PC when
building my image. Ugh...egg on face:

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

I was not uninstalling the devices (devices without drivers installed) from
device manager right before doing my sysprep. As such they would not get
picked up during the pnp scan during the mini-setup wizard. Glad I got that
simple one out of the way...and it only took me a few days to figure it
out...eek.

Barkley Bees said:
So I have gone the route of removing the below from my sysprep.inf:

DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes

I have 4 target hardware (Dell Latitude E4200, E4300, E6400 and Optiplex
760) for my image. So, I used the E6400 as my reference PC and configured
the OS the way it needed to be. I only installed the nic (Intel 82567LM
Gigabit Network Adapter) driver as I needed network connectivity to
download the latest patches, etc

All of the sysmtesm install fine with my new image and drivers get loaded
accordingly except for the E6400 (reference PC). I think that this may be
cause of my problem as I left the nic drivers installed. When the image is
loaded on to the E6400 the nic shows up but nothing else gets loaded. Is
it possible that the minisetup wizard simply ignores the other devices
(chipset, audio, etc) since the nic drivers were already installed?

If so, I will go back to my pre-sysprep image and attempt to fully
uninstall the nic drivers I foolishly installed and then sysprep that
image. Can anyone advise if this may be the contributing factor?

Also, for completely unisntalling all traces of the installed nic drivers
I have found the following (does this seem like the way to go?):

http://remyservices.wordpress.com/2007/09/28/sysprep-in-depth-part-4-cleaning-up-unneeded-drivers/

Thanks again all and appreciate your help.


Barkley Bees said:
So I went back and added the following two lines to my [unattended]
portion of the sysprep.inf (assuming this is the correct thing to do):

DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes


I then did a "sysprep -reseal -mini -quiet". Upon rebooting, the drivers
are properly detected during the mini-setup phase. There is one issue
though, during the mini-setup phase the "New Hardware Wizard" pops up
multiple times as it detects the new hardware. Is there anyway to hide
this from the end users as there is no need for them to see this. Much
appreciate any feedback.


Barkley Bees said:
I am updating an existing Windows XP SP2 image with the below goals
:
1. Adding new drivers to support new hardware.
2. Updating existing application versions and installing latest the
security patches.

As a first test step I took our existing image and updated the local
C:\Drivers dir with the necessary drivers for our new hardware models.
I then used Vernalex's handy sysprep driver scanner
(http://www.vernalex.com/tools/spdrvscn/index.shtml) to update the
registry here:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath

I, of course, had my sysprep.inf prepared and then ran
"sysprep.exe -reseal -mini -quiet". The system then rebooted and
everything came up roses. The new image worked fine on the new systems
and detected all the hardware during the mini-setup wizard.

After this intial test I went back to the original image and updated the
versions of existing apps, made some updates to the IE settings and
installed the most recent security patches (not SP3 though as we have a
compatibility issue with some internal apps at this time).

I then add the updated drivers as I did in my testing and did a sysprep
"sysprep.exe -reseal -mini -quiet". The system reboots and the does not
detect any drivers during the mini-setup wizard. This is on the same
system I performed the testing. I am now scratching my head to figure
out what may be the issue?

I did have to install the nic drivers on this system before I did the
sysprep in order to install the the updates from Microsoft though. Could
this be a potential cause?

Here is my sysprep answer file for reference. Note that the
"OemPnPDriversPath" line is not there as the drivers have already
written to the registry
(HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath) just before
sysprep-ing. Appreciate any help/advice:
----------------------------------------------------------------------------
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS
UpdateUPHAL = ACPIAPIC_UP,WINDOWS\Inf\Hal.inf

[GuiUnattended]
AdminPassword=xxxxxxxxx
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=xxx
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1

[UserData]
ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName="xxxxxxxxxxxxxxxxxxxx"
OrgName="xxxxxxxxxxxxxxxxxxxx"


[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=75

[RegionalSettings]
LanguageGroup=x
UserLocale=00000xxx
SystemLocale=00000xxx
InputLocale=0xxx:e0200xxx
UserLocale_DefaultUser=00000xxx
InputLocale_DefaultUser=0xxx:e0200xxx


[Identification]
JoinDomain=xxx

[Networking]
InstallDefaultComponents=Yes

[NetOptionalComponents]
SNMP=1

[GuiRunOnce]
Command0="netsh firewall reset"
Command1="C:\setup\custom.bat"
[sysprepcleanup]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top