Understanding the MDT Lite Touch Driver Repository

Earlier this week I was asked to help out with an MDT Lite Touch Driver Repository that was missing most of its drivers. After some research it turned out that the drivers.xml had been truncated, something that can happen if multiple admin are working with drivers at the same time (MDT uses a last-writer-wins approach). Here is how you can troubleshoot that:

Importing Drivers to MDT Lite Touch

When importing drivers to MDT Lite Touch, there are two XML files being updated. The DriverGroups.xml file which contains a list of your virtual folder structure inside Out-of-Box Drivers, together with the GUID of each driver that is linked to each folder, and the Drivers.xml file which contains details about each driver.

Here is an example of a DriverGroups.xml file with a single folder (Windows 10 x64 22H2\HP ZBook Firefly 14 G7 Mobile Workstation) having a few drivers in it.

<group guid="{dc62b51a-5e1d-4c17-a2dd-a1ec41a4d3e4}" enable="True">
    <Name>Windows 10 x64 22H2\HP ZBook Firefly 14 G7 Mobile Workstation</Name>
    <CreatedTime>2/26/2023 6:14:54 AM</CreatedTime>
    <LastModifiedTime>2/26/2023 6:19:07 AM</LastModifiedTime>
Drivers listed in the DriverGroups.xml file

If we take a look at the corresponding Drivers.xml file, you find the following info for one of the drivers. Please note the 749ff0d6-dca2-4a6b-a94e-370905fdfd40 guid that is also showing in the DriverGroups.xml file.

<driver guid="{749ff0d6-dca2-4a6b-a94e-370905fdfd40}" enable="True">
    <Name>Intel Corporation Extension HdBusExt.inf</Name>
    <CreatedTime>2/26/2023 6:16:45 AM</CreatedTime>
    <LastModifiedTime>2/26/2023 6:16:45 AM</LastModifiedTime>
    <Manufacturer>Intel Corporation</Manufacturer>
    <Source>.\Out-of-box Drivers\SoftwareComponent\cui_dch_27.20.100.8853_3246FC52CEAE4B6C3A2F7F64ABC3DFBBB8B495ABE4415326C6769AFAF26592D3\HdBusExt.inf</Source>
Details for one of the drivers in Drivers.xml

Using PowerShell to Troubleshoot

If you want to make sure the DriverGroups.xml file is matching the Drivers.xml file, you can use some basic XML parsing in PowerShell. Here are some examplesÖ

# Using PowerShell to Parse XML Attributes with Select-Xml
$Drivers = "C:\DeploymentShare\Control\Drivers.xml"
Select-Xml -Path $Drivers -XPath '/drivers/driver' | ForEach-Object { $_.Node.guid }
(Select-Xml -Path $Drivers -XPath '/drivers/driver' | ForEach-Object { $_.Node.guid }).count

# Using PowerShell to Parse XML Attributes with Select-Xml
$DriverGroups = "C:\DeploymentShare\Control\DriverGroups.xml"
Select-Xml -Path $DriverGroups -XPath '/groups/group/Member' | ForEach-Object { $_.Node.InnerXML }
(Select-Xml -Path $DriverGroups -XPath '/groups/group/Member' | ForEach-Object { $_.Node.InnerXML }).count

Restoring from Backup

If the XML files for drivers gets in a mismatch, simply restore the from your backup. In the very event you don't have a daily backup of your deployment share (which you should have), please note that you may be lucky and find a working copy of your drivers*xml files in the <DeploymentShare>\Backup\Automatic folder.

Example of the <DeploymentShare>\Backup\Automatic folder
About the author

Johan Arwidmark

5 1 vote
Article Rating
Notify of
Inline Feedbacks
View all comments