Creating and managing MDT Bundles manually

Use the Fixlets and tasks in the MDT Bundle Creator Setup node to manually prepare your environment for creating MDT Bundles.

You can download and run the MDT Bundle Creator tool on an BigFix client, or on any other computer of your choice, providing it connects to the external network, and meets specific system requirements and prerequisites. If you run the tool on a client, there are Fixlets and tasks that install the required prerequisites and components for you.

If your designated computer is not an Endpoint Management client, then you must download the MDT Bundle Creator tool manually and install the needed prerequisites , by following the process described in MDT Bundle creation process.

If you are setting up the MDT Bundle on an BigFix client, from the Setup node, expand MDT Bundle Creator Setup to display the required Fixlets and tasks.

To prepare your client system to run the MDT Bundle Creator Tool, run the required Fixlets and tasks in the order shown, then launch the MDT Bundle Creator tool to create your MDT Bundle, and finally upload the bundle to the BigFix server.

Note that some Fixlets might not be relevant if the selected client already has the corresponding prerequisites at the required level. The computer on which you run the WADK installation Fixlets must be connected to the external network.
Important: At least Powershell 2.0 is required as a prerequisite to install the MDT Bundle Creator tool.
  1. Deploy 7-Zip - Fixlet 40

    Downloads the 7-zip compression and decompression tool to the selected computer.

  2. Deploy Windows Assessment and Deployment Kit 10 - Fixlet 62
    To download and install one of the following on the selected computer:
    • WADK for Windows 11 22H2 (build 22621) to use with MDT build 8456
    • WADK for Windows 11 (build 22000) to use with MDT build 8456
    • WADK 10 release id 2004 to use with MDT build 8456
    • WADK 10 release id 1903 to use with MDT build 8456
    • WADK 10 release id 1809 to use with MDT build 8450 or build 8456
    • WADK 10 release id 1803 to use with MDT build 8450
    • WADK 10 release id 1709 to use with MDT build 8443 or build 8450
    • WADK 10 release id 1703 to use with MDT build 8443
    • WADK 10 release id 1607 to use with MDT build 8443
    Important:
    • WADK for Windows 11 (build 22621) supersedes all previous x64 versions.
    • WADK for Windows 10 2004 supersedes all previous x86 versions.
    • Using WADK 10 release id 1703 or later, when you create an MDT Bundle with a parameters.ini file pointing to an .iso containing install.esd or to a folder containing an install.esd image, and not install.wim, the creation of the bundle is successful.
    • On Windows 7, Windows 2008, or Windows 2008 R2 systems, Microsoft .NET Framework 4.5 must already be installed before you run this Fixlet.
    Note: The choice of which kit to download depends on the operating systems you are planning to deploy. See MDT Bundle Creators and valid component combinations. WAIK and WADK cannot coexist on the same computer.
  3. Deploy MDT build 8456 - Fixlet 137

    Run this Fixlet on the selected computer if you installed WADK 10 version 1809, version 1903, version 2004, version 21H2 (build 22000), version 22H2 (build 22621) in the previous step.

    Note: MDT build 8443 and build 8450 are no longer available.
  4. Deploy MDT Bundle Creator - Task 46

    When you run the MDT Bundle Creator task from the OS Deployment and Bare Metal Imaging site, a folder containing all the MDT Bundle Creator tool programs is created. The folder is located in the path %Drive of IEM Client%\OSDSETUP . You can also download the MDT Bundle tool manually to your computer. In this case, a compressed file is downloaded to the specified path and you must extract its contents.

  5. Follow the steps described in MDT Bundle creation process to launch the MDT Bundle Creator tool on the selected computer.
  6. Upload the MDT Bundle to the BigFix server from the MDT Resources tab of the Bundle and Media Manager Dashboard.
You can find further Fixlets to deploy the old tools at Superseded and Deprecated Fixlets.