Anyone share a working Unattend.xml?
- FOG Version: 1.4.4
- OS: Ubuntu
- Service Version: Whatever is current, it’s a fresh install
- OS: Win10 1703
Could anyone share a sanitized version of a working Win10 Unattend.xml file that will pull from a specific folder for drivers?
I’ve been reusing my same one from Win 7, and thought I had changed the offline settings pass appropriately to find the drivers, but I’m wrong. So would anyone be able to post one I can use as a comparission to fix mine?
@george1421 Thanks George. I understand about the IP reasons.
That site makes sense, now that I can see where the offline service bit had to be put. I had it in the wrong spot on mind, which meant drivers weren’t being picked up. Moved it, and it’s working great.
@Bob-Henderson I can’t share a working example of our Win10 unattend.xml file because of IP reasons. But I think I can get you pretty close.
If you go to any of the online unattend.xml builders to construct your unattend.xml file, such as this one: http://windowsafg.no-ip.org/win10x86_x64.html
Even without entering any values (btw: this is an excellent unattend.xml builder if you are not using MDT or other deployment tool), down at the bottom there is an output section. If you search there for
settings pass="offlineServicing"you will see two sections. Just insert the following from this article: https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/4 just below the existing offlineServicing section or just insert another component section inside an existing offlineServicing section.
<settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>C:\Windows\DRV</Path> </PathAndCredentials> </DriverPaths> </component> </settings>
Since the driver store is located ON the target computer there is no need to supply any credentials to make this work.