Hi folks...

I run a unattended install where the unatten.txt contains references to the OEMPnPDriversPath entry. For example;

OEMPnPDriversPath = "Drv\Vid\Video1;Drv\Vid\Video2"

When checking the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion - DevicePath entry, it contains references to the above mentioned OEM drivers supplied.

Once the unattended installation reaches the end of the install sequence, it will shutdown using sysprep.exe.

The machine is then booted up on capture image from RIS, and saves the machine state to a .wim format on a UNC path from WinPE. So far so good..

When I want to deploy the .wim image, I boot into WinPE, apply the image to the machine, manually or by a .hta interface edit the sysprep.inf file to reference some new cool drivers, for example Drv\Vid\Video3 from the OEMPnPDriversPath entry. I then copy over the drivers locally so the entry and files/dirs correspond.

Once the machine has been installed, when checking the DevicePath entry in the registry it does NOT hold a reference to the Drv\Vid\Video3 driver added at the sysprep.inf "stage".

My question:

1. Is this correct? When adding entries in the OEMPnPDriversPath of the sysprep.inf file that was NOT a part of the unattend.txt OEMPnPDriversPath entry, should those not be visible from the DevicePath entry once the machine has been deployed???? If YES (they should), where am I going wrong?

Also, in my sysprep.inf file, I am using the UpdateInstalledDrivers = Yes to force a PnP enum. However, I am not running the -pnp switch when using sysprep.exe.

Best Regards

Tha Sausage Eater...

Oki, if one reads the deploy.chm file: for OEMPnPDriversPath entry

"If there is already a path in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\

CurrentVersion\DevicePath, Sysprep does not append the path to the registry key a second time."

I will never learn the term: RTFM

Summary:

The only way to get this working is to:

1. Install a machine using unattend.txt for example

2. Run sysprep.inf

3. Capture to .wim format from a WinPE

4. Apply .wim image to local machine from WinPE

5. From within WinPE, run a script that will mount the c:\windows\system32\config\software file to a TempHive using reg load.

6. Write the new paths to the key (for the external added paths to be included)

7. Unmount the TempHive

8. Exit WinPE and mini setup will process and include the new paths....

Cu...