Answered by:
Server 2008, WDS and Sysprep drivers will not install

Question
-
I'm going to make this as clear as I possibly can. I am trying to build 1 image for many computers. This means I cannot include the drivers pre-installed in the image. So far I have gotten my server to not only deploy images and capture images, but I'm also to the point where it is entering in the License key and going through the nitty gritty setup pieces automatically. What I am having issues with is the Drivers. So, my current setup for the the server is as follows:C:\RemoteInstall\Images\Test Image Group\Master3\$OEM$\$1\sysprepin this folder is my sysprep.inf which so far seems to be working except for the driver installation.I guess I'm a little confused where to store the drivers for an image as well as how to tell sysprep to use those drivers. I've tried to put them in the $1 folder as well as the $OEM$ folder. Then I resorted to storing them on the target computer thinking that sysprep may tell the computer to pull them from a local source.On the target computer (Dell D620) :my sysprep folder is in c:\windows\system32\sysprepdrivers are stored in C:\drivers\1\2\3... etcIn each folder (1,2,3, 4,5) there are inf's that came from Dell, I've extracted from their .exe. My thoughts are if I can get this to work with the D620 then I can get it work with the rest of the different laptops we have here. I've already had to find and inject specific drivers into the boot.wim for our E6400's to boot in the windows PE 2.0 environment.My sysprep.inf file looks like this:as I said so far it works except for the drivers._________________________________________________________________________________________________________________________________________;SetupMgrTag[Unattended]OemPnPDriversPath="\Drivers\1;\Drivers\2;\Drivers\3;\Drivers\4;\Drivers\5;\Drivers\6;\Drivers\7;\Drivers\8;\Drivers\9"InstallFilesPath=C:\Windows\system32\sysprep\i386TargetPath = \WindowsKeepPagefile=0OemSkipEula=YesUpdateInstalledDrivers=YesNonDriversSigningPolicy=IgnoreDriverSigningPolicy=IgnoreUpdateServerProfileDirectory=1[Sysprep]BuildMassStorageSection=Yes[GuiUnattended]AdminPassword="Password"EncryptedAdminPassword=NOOEMSkipRegional=1TimeZone=35OemSkipWelcome=1AutoLogon=YesAutoLogonCount=1[UserData]ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"FullName="Default User"OrgName="Default"ComputerName=Dpt-Typ-LastFi[TapiLocation]CountryCode=1AreaCode=860[SetupMgr]DistFolder=C:\Windows\system32\sysprep\i386DistShare=windist[Identification]JoinWorkgroup=WORKGROUP[Networking]InstallDefaultComponents=Yes[Sysprep]BuildMassStorageSection=yes[SysprepMassStorage]_________________________________________________________________________________________________________________________________________Quick Summary.WDS is working and deploying imagesLicense key is auto loadedTarget machine is receiving imageTarget machine reboots and auto logs in.Issue:Target machine does not have drivers installed like I had thought I had specified to do in the sysprep.infThanks for your help
- Edited by SchucoIT Wednesday, April 14, 2010 8:51 PM change title
Wednesday, April 14, 2010 8:46 PM
Answers
-
Well, after 200 views and nobody responding I managed to solve this myself.
1- Remove the OemPnpDriversPath from the sysprep.inf file
2- go to this site http://blog.remyservices.net/2007/09/ and go to step 1, you will be following these instructions, they are very good.
3- Use doubledriver http://www.boozet.org/dd.htm and sysprepdriver scanner http://www.vernalex.com/tools/spdrvscn/index.shtml to change the registry key
keep following http://blog.remyservices.net/2007/09/28/sysprep-in-depth-part-1-adding-drivers-to-our-image-pc/ and keep following it. I skipped the HAL section because I was not changing the hardware at all.
- Marked as answer by SchucoIT Wednesday, April 28, 2010 9:13 PM
Wednesday, April 28, 2010 9:13 PM
All replies
-
Well, after 200 views and nobody responding I managed to solve this myself.
1- Remove the OemPnpDriversPath from the sysprep.inf file
2- go to this site http://blog.remyservices.net/2007/09/ and go to step 1, you will be following these instructions, they are very good.
3- Use doubledriver http://www.boozet.org/dd.htm and sysprepdriver scanner http://www.vernalex.com/tools/spdrvscn/index.shtml to change the registry key
keep following http://blog.remyservices.net/2007/09/28/sysprep-in-depth-part-1-adding-drivers-to-our-image-pc/ and keep following it. I skipped the HAL section because I was not changing the hardware at all.
- Marked as answer by SchucoIT Wednesday, April 28, 2010 9:13 PM
Wednesday, April 28, 2010 9:13 PM -
Hi!
I Have the exact same problem, but the page http://blog.remyservices.net/2007/09/ does not seems to work anymore :(
Do you remember what you did, or anyone else have any ideas?
Thursday, June 3, 2010 11:42 AM