r/MDT

Hey everyone! I’m working on a Windows deployment setup using Microsoft Deployment Toolkit, and I’m hitting a bit of a wall on how to structure my driver folders, specifically for WinPE and model specific drivers. I’m deploying Windows 11 (though I’m considering using Windows 10 drivers if necessary) onto HP Z840 workstations and Dell Precision 5920 towers.

Right now, I have a “Drivers” folder, with a “WinPE” subfolder for the core boot drivers, and then a “Windows 11” folder that branches into specific models (HP Z840 and Dell Precision 5920). But I’m unsure if this is the best structure, especially for the WinPE drivers. How do you all organize your driver sets? Do you keep all model specific drivers inside the Windows 11 folders, or do you have a separate driver structure for WinPE that all models share? Also, any advice on using Windows 10 or Server 2019 drivers if Windows 11 ones are missing?

I’m getting a specific error during deployment: “A connection to deployment share cannot be made. The following network device did not have a hard drive installed: PCI\\VEN\_8086&DEV\_15A0.”

Hi everyone,

I've created a PowerShell script to collect hardware hashes using a task sequence during PXE boot. I created a custom task sequence that currently only contains the PowerShell script.

The script works fine when I run it from the full OS, and the hashes are successfully saved to a network share. However, I would like to collect the hardware hashes during PXE boot so I don't have to fully set up the device before gathering the hashes.

I can also run the script manually from a USB drive during OOBE, and the hashes are saved successfully. Ideally though, I’d like this to run automatically through the task sequence.

Has anyone successfully collected hardware hashes while in PXE/WinPE using a task sequence?

Hello MDT friends!
We have roughly 20 different Dell desktops and laptops. What is the best approach to update BIOS at time of imaging?
HP makes a great guide below where the power shell script reaches out to HP servers, downloads bin file, checks for bitlocker and applies update with password.

https://hp.service-now.com/workforceexperience?id=kb\_article&sysparm\_article=KB0011905&sys\_id=953c08be47a1ed1064affae5536d43f8

I don’t want to keep a repository of bios models. Any help here?

I can't seem to get the Windows Deployment Services Server service started after adding the Windows Deployment Services role.

• Installed on a member server (no DHCP server services)
• Windows 2019 (1809)
• Logs show Event IDs:
  • 1811: BINLSVC: An error occurred while checking for the existence or creation of a Service Control Point for BINLSVC Provider.
  • 261: WDSPXE: An error occurred while trying to initialize provider WDSDCPXE loaded from C:\Windows\system32\wdsdcpxe.dll. If the provider is marked as critical, the Windows Deployment Services server will shut down.
  • 264: WDSPXE: An error occurred while trying to initialize provider WDSDCPXE. Because the provider is not marked as critical, the Windows Deployment Services server will continue to run.
  • 268: WDSPXE: All registered providers failed to initialize. Review the Event Log for specific error messages for each provider. Windows Deployment Services will shut down.
  • 513: WDSServer: An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown. Error Information: 0xC107010C

I've gone through:

• Removing and re-adding the role
• Uninitialized and Reinitalized
• Installed all the Visual C++ Redistributables
• Confirmed there are no port conflicts with 67, 69, 4011, 5040, 5041 (compared from working MDT/WDS server)
• Checked the Do not listen on DHCP ports (even though DHCP Server is not running)

I seem to keep coming across the same information over and over without any changes. Hopefully someone here can provide some guidance.