OverFlow this post will be long.
Ideally, All that I am doing or want to do is the following which so far it is working. We have 3 different kinds of pc at our workplace so which means we hace 3 different images that were created by myself back in the days but now there are getting harder and harder to maintain with SMS and WSUS. Pc are --> P5B-VM DO, P5E-VM DO, P5LD2-VM
Never the less, I am starting from starch from a fresh image so taking one of the 3 pc listed above (example P5B-VM DO) I am doing the following.
1) Install Windows Pro SP2
2) Windows Update --> SP3
3) Installing MS Word 2003
Everything else will be done by SMS as I want to keep this universal image as basic as possible. So once the above is done, I do not install any drivers for that pc yet, so which mean everything in device manager is not installed.
4) Before I begin sysprep, I delete the processor information in the registry command --> "sc config intelppm start= disabled", Then I reboot then within device manager I delete the Processor, I DO not reboot and then delete the registry key "intelppm"
5) At this point on another computer I have prepared all the necessary files that I need to sysprep and integrate the driverpacks. This folder gets copied over to the root of C without the folder, so just the files.
What contains in this folder. (Imaging Folder)
- D folder --> Extracted all the driverpacks drivers. (C/G/L/M/S/W) Note, For the Chipset folder I only kept the Intel stuff as the AMD were giving me errors when it ran
- Sysprep Folder --> My sysprep.inf that I have modified and been using for years now. I have added the following entry in my sysprep.ini file for driverpacks according to the sticky in this section.
UpdateInstalledDrivers = Yes
DriverSigningPolicy = Ignore
- Sysprep Folder --> ROE.exe is also located in the sysprep folder also with all the other default sysprep files (setupcl.exe etc)
- Within the root of the Imaging folder I have the following files as well.
- DPsFnsher.ini file
Here is what my DPsFnsher.ini file looks like after I modified it:
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot = "%SystemDrive%"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = "paths:D\C;D\G;D\L;D\M;D\S;D\W"
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation = "%SystemRoot%\Options\Drivers"
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%"
; enables/disables debug mode (enabled by default)
debug = "true"
- All the DriverPack_*_wnt5_x86-32.ini files that are provided with the download.
- MassStorage.cmd --> This is a batch script that was made by someone on this forum to add all the chipset drivers I have within the d:\D folder to
my [SysprepMassStorage] section.
Now listed above are files that get transferred over to the pc that I will be running sysprep on.
Steps that I take to prepare before sysprep and up to sysprep.
Note* The following commands are being done on the pc that is being used to build the image*
Note, the below two steps are already down as part of the files/folder that gets transferred to the pc image.
1) sysprep.exe -bmsd --> As you know this will get all windows pci drivers and places them into the [SysprepMassStorage] section.
2) run masstorage.exe D\M --> This will print out to a file all of the Mass-storage within the driverpacks. After it spits it out into a file, I make sure there are no broken links aka gaps, I then insert then into the [SysprepMassStorage] section.
3) c:\devpath.exe c:\d
4) c:\makePNF.exe c:\d --> I was running this command, until you told me not to in the other post
5) sysprep\ROE.exe 937 (At this point I do not reboot as it will run this command)
And last but not least my sysprep command
6) c:\sysprep\sysprep.exe -reseal -activated -mini -pnp -quiet
At this point the sysprep will run for about 20-25 mins or so. However sometime the sysprep runs for only 1 mins and I know there is something wrong so I then let it finish and re-do the above steps again, not sure why this happens but oh well.
After sysprep takes its time the pc then turns off. At this point I will then insert my multibootdisk that I made to dump the image to the network but before that I want to make sure everything got installed and ran perfect. I know by letting it bootup and letting sysprep run again I will need to do the above steps again.
So sysprep runs it takes its time as its installing the drivers and then when login into windows the driverpack runs. Apparently it is claiming cleaning registry in the bottom left corner and then it moves my d folder to --> C:\windows\system32\options, which is what I want as the team that are deploying these images would like to have the drivers said in a folder rather then carrying there usb stick that have the drivers. Dont ask why they just want them stored on the pc just in case.
Note run the dbsfinsih runs, I get a prompted to Install Intel (R) Q35 (Graphics B). If I hit ok it looks for the driver in C:\windows\system32\options\g\i2 and all I have to do is hit next and it install with no problem. At this point everything in device manager is installed just nicely, but questions is which is why this thread started to begin with is why I’m I being prompted if it knows the driver is there. I personally dont really care about this, one prompt is better then a lot of prompts. As of now I have no problem leaving it like that and deploying the image like that. I am prompted when dbsfnshr is running for the driver install.
Anyhow OverFlow, the above is the exact step I do from start of the image to the end. Do you for see any problems on how I am doing this. I have read up many posts and I think I got it down pat. Answer to your questionYes then it is true KTD that I want to use.
If I leave it the way I am doing it, it should be good no? Honestly I didn’t even use DPs_BASE, I just extracted the drivers from the driverpacks.
Let me know what you think.
Sorry for the long post