To automate the setup of MDT I've created all these scripts and configuration files to setup MDT as fast as possible.

Setup a Windows Server OS as you normally do. Add a hard disk D: and format it with NTFS. I recommend about 100GB, but this also depends on the needed capabilities.

Run the Download and Install.ps1 script. This script will download ADK, WinPE, MDT and will install WDS on the D: disk. This will also download the needed scripts that can be found in the Scripts.zip and ISOs.zip

The Scripts.zip is downloaded and extracted to the D:\MDT\Scripts folder and contains several scripts:

• Download and import OS.ps1 = This script will download and import the Operating Systems that you want to deploy with MDT. If you want the latest Windows 11 or Windows Server 2025 Insider Builts in MDT, just remove the Insider ISO's from the D:\MDT\ISOs folder and run this script again. All others ISO's only need to be downloaded once and will not be updated.
• Import Drivers.ps1 = This script can be used to import drivers for specific hardware. Create a folder structure in the Drivers folder the way you like and run this script to import all drivers in MDT. Don't forget to run the Update bootfiles.ps1 is you have added NIC or storage drivers needed for WinPE.
• MDT Apps.ps1 = This script is used to import applications into you Deployment share.
• MDTExitNameToGuid.vbs = Script from Microsoft to make app deployment easier.
• Media.ps1 = This script can be used to create an ISO that you can use in combination with Rufus to create USB media. With this you can install the chosen Windows version and Apps from your USB drive. The media will be created in the folder D:\MDT\Media
• Update bootfiles.ps1 = script to update the bootfiles in WDS after adding drivers for optional NIC's or storage devices needed for WinPE.
• WDS prompt.bat = Turn F12 prompt in WDS on or off
• WDS_F12.bat = Turn F12 option on (only boot from WDS after pressing F12)
• WDS_no_F12.bat = Turn F12 option off (always boot to WDS)

The CustomSettings.zip contains example files that can be used for the CustomSettings.ini in the MDT Share. This makes switching between configurations in MDT really easy. You can run the CustomSetting.hta on the server to update the CustomSettings.ini in the Deploymentshare with just a few clicks. The files with Media in the name are used to import them when you create specific media. If you select Windows 11 or Windows all, the user will be asked to input data during deployment like domain, applications etc. If you want predefined options, you can select other files. You can add your own examplename.ini in the D:\MDT\CustomSettings folder for future use. The hta script will find them all.

The Apps.zip is downloaded and extracted to D:\MDT\Apps. This folder contains a subfolder for each application. All applications can be installed by running the install.ps1, install.vbs or install.bat file. Most application installs are based on WINGET, so the last version available will be downloaded and installed on the fly. Some old apps need to be downloaded first. To download the latest versions, you can easily run the D:\MDT\Apps\Update all subfolders.vbs file. To update a specific app, you can run the Update.ps1 file in each application folder.

Adding your own apps requires you to create a folder in D:\MDT\Apps with an install.ps1 file. Please use the included scripts as examples for your own install scripts.

After you have downloaded all the latest versions of the apps and added your own apps, make sure you run the D:\MDT\Scripts\MDT App.ps1 script to update the MDT Deploymentshare.

These scripts customize Windows components and will install of remove the following components:

• .Net Framework 3.5 and TelnetClient will be installed
• Faxing and Printing features are removed
• All Appx packages are removed, except Calculator, Photos, ScreenSketch, Stickynotes and Microsoft Store
• All Store Apps will be updated
• All Powershell help files will be updated
• Recovery Agent is disabled
• WinRM is configured
• Winsat is run
• Firewall is set to Private Profile
• Firewall rules are configured
• Default file extentions are configured (which can easily be updated with your own preferences by running the "export DefaultApps.bat" script on a configured system)
• Default start menu layout for all users (which can easily be updated with your own preferences by running the "export Start Menu.bat" script on a configured system)
• If you place a "Background.jpg" in this folder, the desktop background will be set for all new user profiles
• If you place a "UserLogo.bmp" in this folder, the user picture will be changed for the all users
• Hibernation and Sleep will be turned off
• No password is required after screensaver
• Screenbrightness is set to 100%
• If you use WSUS during deployment, this will be removed at the next startup

All Fonts that you want to deploy can be places in the folder Fonts and will be installed during deployment.

If you need to import specific WLAN SSID's during deployment of an MDT client, you can run the D:\MDT\Apps\ConnectWLAN\export.bat script to export the needed settings for an SSID. This will create a "SSID.xml" file in the folder and will be imported when a Task Sequence is run.

Numerous registry settings will be set. Look in the Regfiles folder for all settings. If you add your own .reg file to this folder, this will be included during deployment.

Runs Windows and Office activation to Public KMS servers.