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]
----------------------------------------------------------------------------
:
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]
----------------------------------------------------------------------------