Skip navigation

I've written a custom action in my Microsoft Systems Management Server (SMS) OS Deployment Feature Pack deployment that modifies the sysprep.inf file with an updated OemPnPDriversPath. Why is the action having no effect?

A. Normally, you can use the OemPnPDriversPath value to instruct the Setup Wizard to check other locations for drivers for detected hardware. However, if you set this value in the post-installation phase of an SMS OS Deployment Feature Pack deployment, in some circumstances this is too late and will have no effect. Instead, you need to edit the DevicePath registry key on the deployed OS and set the full list of driver path folders. The following code performs this action:

reg load HKLM\sw %OSDTARGETDRIVE%windows\system32\config\software 
reg add HKLM\sw\microsoft\windows\currentversion /v DevicePath /t REG_EXPAND_SZ /f /d "c:\windows\inf;c:\drivers\network;c:\drivers\storage;c:\drivers\Video" 
reg unload HKLM\sw 

The second line performs the actual modification to the DevicePath variable and sets it to search the default c:\windows\inf folder and any additional driver folders. You'd add this code as a post-installation phase action.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.