Create a Windows x reference image

  • Article
  • 31 minutes to read

Applies to

  • Windows 10

Creating a reference epitome is of import considering that image serves as the foundation for the devices in your arrangement. In this topic, you will learn how to create a Windows 10 reference image using the Microsoft Deployment Toolkit (MDT). Yous will create a deployment share, configure rules and settings, and import all the applications and operating arrangement files required to build a Windows 10 reference prototype. Later completing the steps outlined in this topic, you will have a Windows 10 reference image that can be used in your deployment solution.

For the purposes of this topic, nosotros will use three computers: DC01, MDT01, and HV01.

  • DC01 is a domain controller for the contoso.com domain.
  • MDT01 is a contoso.com domain member server.
  • HV01 is a Hyper-V server that volition exist used to build the reference image.

devices.

Computers used in this topic.

The reference epitome

The reference image described in this guide is designed primarily for deployment to concrete devices. However, the reference image is typically created on a virtual platform, earlier being automatically run through the System Training (Sysprep) tool process and captured to a Windows Imaging (WIM) file. The reasons for creating the reference image on a virtual platform are the following:

  • To reduce development time and can use snapshots to test different configurations quickly.
  • To rule out hardware issues. Yous simply go the best possible paradigm, and if y'all accept a problem, it's not likely to be hardware related.
  • To ensures that you won't have unwanted applications that could exist installed equally part of a commuter install but not removed by the Sysprep process.
  • The image is easy to move between lab, examination, and product.

With Windows x, there is no difficult requirement to create reference images. However, to reduce the time needed for deployment, yous might want to create a reference image that contains a few base applications as well as all of the latest updates. This department will bear witness you lot how to create and configure the MDT Build Lab deployment share to create a Windows 10 reference image. Because reference images will be deployed just to virtual machines during the creation process and accept specific settings (rules), you should always create a separate deployment share specifically for this procedure.

On MDT01:

  • Sign in equally contoso\administrator using a password of pass@word1 (credentials from the ready for deployment topic).

  • Start the MDT deployment workbench, and pin this to the taskbar for easy access.

  • Using the Deployment Workbench, right-click Deployment Shares and select New Deployment Share.

  • Use the following settings for the New Deployment Share Magician:

    • Deployment share path: D:\MDTBuildLab
    • Share name: MDTBuildLab$
    • Deployment share description: MDT Build Lab

  • Accept the default selections on the Options folio and click Next.

  • Review the Summary page, click Adjacent, wait for the deployment share to be created, so click Stop.

  • Verify that you can access the \\MDT01\MDTBuildLab$ share.

    figure 2.

    The Deployment Workbench with the MDT Build Lab deployment share.

Enable monitoring

To monitor the task sequence equally it happens, right-click the MDT Build Lab deployment share, click Properties, click the Monitoring tab, and select Enable monitoring for this deployment share. This step is optional.

In gild to read files in the deployment share and write the reference image back to it, you need to assign NTFS and SMB permissions to the MDT Build Business relationship (MDT_BA) for the D:\MDTBuildLab folder

On MDT01:

  1. Ensure you lot are signed in as contoso\ambassador.

  2. Change the NTFS permissions for the D:\MDTBuildLab folder past running the following control in an elevated Windows PowerShell prompt:

                      icacls "D:\MDTBuildLab" /grant '"CONTOSO\MDT_BA":(OI)(CI)(M)' grant-smbshareaccess -Name MDTBuildLab$ -AccountName "Contoso\MDT_BA" -AccessRight Total -forcefulness

Add setup files

This section will evidence you lot how to populate the MDT deployment share with the Windows 10 operating system source files, commonly referred to equally setup files, which will be used to create a reference image. Setup files are used during the reference prototype cosmos process and are the foundation for the reference paradigm.

Add the Windows x installation files

MDT supports adding both total source Windows 10 DVDs (ISOs) and custom images that you lot have created. In this example, y'all create a reference image, so you add the full source setup files from Microsoft.

Note

Due to the Windows limits on path length, nosotros are purposely keeping the operating organization destination directory short, using the folder proper noun W10EX64RTM rather than a more descriptive proper name like Windows 10 Enterprise x64 RTM.

Add Windows x Enterprise x64 (full source)

On MDT01:

  1. Sign in every bit contoso\ambassador and copy the content of a Windows 10 Enterprise x64 DVD/ISO to the D:\Downloads\Windows 10 Enterprise x64 folder on MDT01, or just insert the DVD or mount an ISO on MDT01. The following example shows the files copied to the D:\Downloads folder, but y'all can also choose to import the OS straight from an ISO or DVD.

    ISO.

  2. Using the Deployment Workbench, expand the Deployment Shares node, and then expand MDT Build Lab.

  3. Right-click the Operating Systems node, and create a new folder named Windows 10.

  4. Expand the Operating Systems node, right-click the Windows 10 binder, and select Import Operating Arrangement. Apply the following settings for the Import Operating System Sorcerer:

    • Full set of source files
    • Source directory: (location of your source files)
    • Destination directory name: W10EX64RTM

  5. Afterwards calculation the operating system, in the Operating Systems / Windows 10 folder, double-click information technology and alter the name to: Windows ten Enterprise x64 RTM Default Image. See the following case.

    Default image.

Depending on the DVD you used, there might be multiple editions available. For the purposes of this guide, we are using the Windows x Enterprise image, but other images will also work.

Add applications

Before you create an MDT job sequence, you need to add together any applications and scripts yous wish to install to the MDT Build Lab share.

On MDT01:

First, create an MDT folder to store the Microsoft applications that will be installed:

  1. In the MDT Deployment Workbench, aggrandize Deployment Shares \ MDT Build Lab \ Applications
  2. Right-click Applications and then click New Folder.
  3. Under Folder name, type Microsoft.
  4. Click Next twice, and then click Finish.

The steps in this section use a strict naming standard for your MDT applications.

  • Utilise the "Install - " prefix for typical application installations that run a setup installer of some kind,
  • Employ the "Configure - " prefix when an application configures a setting in the operating arrangement.
  • Y'all likewise add an " - x86", " - x64", or "- x86-x64" suffix to indicate the application's architecture (some applications accept installers for both architectures).

Using a script naming standard is always recommended when using MDT as information technology helps maintain order and consistency.

Past storing configuration items as MDT applications, it is easy to move these objects between various solutions, or between test and product environments.

In example sections, you will add the post-obit applications:

  • Install - Microsoft Function 365 Pro Plus - x64
  • Install - Microsoft Visual C++ Redistributable 2019 - x86
  • Install - Microsoft Visual C++ Redistributable 2019 - x64

The 64-fleck version of Microsoft Office 365 Pro Plus is recommended unless you need legacy app support. For more information, run into Choose betwixt the 64-bit or 32-bit version of Office

Download links:

  • Part Deployment Tool
  • Microsoft Visual C++ Redistributable 2019 - x86
  • Microsoft Visual C++ Redistributable 2019 - x64

Download all iii items in this list to the D:\Downloads folder on MDT01.

Annotation: For the purposes of this lab, we volition leave the MSVC files in the D:\Downloads folder and the Office365 files will be extracted to a child folder. If you prefer, you tin place each application in its own separate child folder and and then modify the $ApplicationSourcePath below as needed (instead of simply D:\Downloads).

Create configuration file: Microsoft Part 365 Professional Plus x64

  1. Afterward downloading the most current version of the Role Deployment tool from the Microsoft Download Centre using the link provided higher up, run the self-extracting executable file and extract the files to D:\Downloads\Office365. The Function Deployment Tool (setup.exe) and several sample configuration.xml files will be extracted.

  2. Using a text editor (such as Notepad), create an XML file in the D:\Downloads\Office365 directory with the installation settings for Microsoft 365 Apps for enterprise that are appropriate for your organization. The file uses an XML format, so the file you create must take an extension of .xml but the file can have any filename.

    For instance, you tin use the following configuration.xml file, which provides these configuration settings:

    • Install the 64-chip version of Microsoft 365 Apps for enterprise in English language directly from the Office Content Delivery Network (CDN) on the internet. Note: 64-bit is now the default and recommended edition.
    • Use the Full general Availability Channel and go updates directly from the Function CDN on the internet.
    • Perform a silent installation. You won't see anything that shows the progress of the installation and you won't come across any fault messages.
                      <Configuration>  <Add OfficeClientEdition="64" Channel="Wide">    <Production ID="O365ProPlusRetail">      <Language ID="en-us" />    </Product>  </Add>  <Display Level="None" AcceptEULA="Truthful" />  <Updates Enabled="Truthful" /> </Configuration>

    Past using these settings, whatever time you build the reference image yous'll be installing the most up-to-appointment General Availability Channel version of Microsoft 365 Apps for enterprise.

Tip

You tin as well apply the spider web-based interface of the Part Customization Tool to assist yous create your configuration.xml file.

Also see Configuration options for the Office Deployment Tool and Overview of the Office Deployment Tool for more information.

  1. Ensure the configuration.xml file is in the D:\Downloads\Office365 binder. See the following case of the extracted files plus the configuration.xml file in the Downloads\Office365 folder:

    folder.

Assuming yous take named the file "configuration.xml" every bit shown above, nosotros will utilise the control "setup.exe /configure configuration.xml" when we create the application in MDT. This will perform the installation of Microsoft 365 Apps for enterprise using the configuration settings in the configuration.xml file. Exercise not perform this pace yet.

Important

Subsequently Microsoft 365 Apps for enterprise is installed on the reference image, do NOT open any Office programs. if you open an Function program, you are prompted to sign-in, which activates the installation of Microsoft 365 Apps for enterprise. Even if you don't sign in and you lot close the Sign in to prepare up Office dialog box, a temporary production key is installed. You don't want any kind of product central for Microsoft 365 Apps for enterprise installed as part of your reference image.

Additional information

  • Microsoft 365 Apps for enterprise is usually updated on a monthly ground with security updates and other quality updates (bug fixes), and perhaps new features (depending on which update channel y'all're using). That means that once you've deployed your reference prototype, Microsoft 365 Apps for enterprise will nearly probable need to download and install the latest updates that have been released since you created your reference image.

  • Note: Past using installing Office Deployment Tool equally function of the reference prototype, Microsoft 365 Apps for enterprise is installed immediately later on the reference image is deployed to the user's device, rather than including Office apps office of the reference image. This manner the user will accept the virtually up-to-date version of Microsoft 365 Apps for enterprise right abroad and won't have to download any new updates (which is well-nigh probable what would happen if Microsoft 365 Apps for enterprise was installed equally office of the reference image.)

  • When you are creating your reference image, instead of installing Microsoft 365 Apps for enterprise direct from the Office CDN on the internet, y'all tin can install Microsoft 365 Apps for enterprise from a location on your local network, such as a file share. To do that, yous would use the Role Deployment Tool in /download way to download the installation files to that file share. Then yous could utilise the Office Deployment Tool in /configure style to install Microsoft 365 Apps for enterprise from that location on to your reference image. Equally function of that, you'll need to bespeak to that location in your configuration.xml file so that the Office Deployment Tool knows where to get the Microsoft 365 Apps for enterprise files. If you decide to practice this, the next time you create a new reference image, y'all'll desire to exist sure to use the Office Deployment Tool to download the most up-to-date installation files for Microsoft 365 Apps for enterprise to that location on your internal network. That way your new reference epitome will have a more up-to-engagement installation of Microsoft 365 Apps for enterprise.

If yous need to add together many applications, you can take advantage of the PowerShell support that MDT has. To starting time using PowerShell confronting the deployment share, y'all must kickoff load the MDT PowerShell snap-in and then brand the deployment share a PowerShell drive (PSDrive).

On MDT01:

  1. Ensure you are signed in as contoso\Administrator.

  2. Import the snap-in and create the PSDrive by running the following commands in an elevated PowerShell prompt:

                      Import-Module "C:\Programme Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1" New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "D:\MDTBuildLab"

Tip

Utilise "Get-Command -module MicrosoftDeploymentToolkit" to see a list of available cmdlets

Create the install: Microsoft Function 365 Pro Plus - x64

In these steps we presume that you accept downloaded the Function Deployment Tool. You might need to change the path to the source folder to reflect your current environment. In this example, the source path is set to D:\Downloads\Office365.

On MDT01:

  1. Ensure you are signed on every bit contoso\Administrator.

  2. Create the application by running the following commands in an elevated PowerShell prompt:

                      $ApplicationName = "Install - Office365 ProPlus - x64" $CommandLine = "setup.exe /configure configuration.xml" $ApplicationSourcePath = "D:\Downloads\Office365" Import-MDTApplication -Path "DS001:\Applications\Microsoft" -Enable "True" -Proper noun $ApplicationName -ShortName $ApplicationName -CommandLine $CommandLine -WorkingDirectory ".\Applications\$ApplicationName" -ApplicationSourcePath $ApplicationSourcePath -DestinationFolder $ApplicationName -Verbose

    Upon successful installation the post-obit text is displayed:

                      VERBOSE: Performing the functioning "import" on target "Application". VERBOSE: Beginning application import VERBOSE: Copying awarding source files from D:\Downloads\Office365 to D:\MDTBuildLab\Applications\Install - Office365 ProPlus - x64 VERBOSE: Creating new item named Install - Office365 ProPlus - x64 at DS001:\Applications\Microsoft.  Name ---- Install - Office365 ProPlus - x64 VERBOSE: Import processing finished.

Create the install: Microsoft Visual C++ Redistributable 2019 - x86

Annotation

We accept abbreviated "Microsoft Visual C++ Redistributable" in the $ApplicationName below as "MSVC" to avoid the path name exceeding the maxiumum allowed length of 248 characters.

In these steps we presume that you take downloaded Microsoft Visual C++ Redistributable 2019 - x86. You might demand to modify the path to the source folder to reflect your current environment. In this case, the source path is set to D:\Downloads.

On MDT01:

  1. Ensure y'all are signed on as contoso\Administrator.

  2. Create the awarding by running the post-obit commands in an elevated PowerShell prompt:

                      $ApplicationName = "Install - MSVC 2019 - x86" $CommandLine = "vc_redist.x86.exe /Q" $ApplicationSourcePath = "D:\Downloads" Import-MDTApplication -Path "DS001:\Applications\Microsoft" -Enable "Truthful" -Name $ApplicationName -ShortName $ApplicationName -CommandLine $CommandLine -WorkingDirectory ".\Applications\$ApplicationName" -ApplicationSourcePath $ApplicationSourcePath -DestinationFolder $ApplicationName -Verbose

    Upon successful installation the following text is displayed:

                      VERBOSE: Performing the operation "import" on target "Application". VERBOSE: Beginning application import VERBOSE: Copying awarding source files from D:\Downloads to D:\MDTBuildLab\Applications\Install - MSVC 2019 - x86 VERBOSE: Creating new detail named Install - MSVC 2019 - x86 at DS001:\Applications\Microsoft.  Name ---- Install - MSVC 2019 - x86 VERBOSE: Import processing finished.

Create the install: Microsoft Visual C++ Redistributable 2019 - x64

In these steps nosotros assume that you have downloaded Microsoft Visual C++ Redistributable 2019 - x64. Y'all might need to modify the path to the source folder to reverberate your current environs. In this instance, the source path is set to D:\Downloads.

On MDT01:

  1. Ensure yous are signed on equally contoso\Administrator.

  2. Create the application by running the post-obit commands in an elevated PowerShell prompt:

                      $ApplicationName = "Install - MSVC 2019 - x64" $CommandLine = "vc_redist.x64.exe /Q" $ApplicationSourcePath = "D:\Downloads" Import-MDTApplication -Path "DS001:\Applications\Microsoft" -Enable "True" -Name $ApplicationName -ShortName $ApplicationName -CommandLine $CommandLine -WorkingDirectory ".\Applications\$ApplicationName" -ApplicationSourcePath $ApplicationSourcePath -DestinationFolder $ApplicationName -Verbose

Create the reference epitome task sequence

In order to build and capture your Windows 10 reference epitome for deployment using MDT, yous will create a task sequence. The task sequence volition reference the operating system and applications that you previously imported into the MDT Build Lab deployment share to build a Windows 10 reference prototype. After creating the task sequence, you configure it to enable patching against the Windows Server Update Services (WSUS) server. The Task Sequence Windows Update activity supports getting updates directly from Microsoft Update, but you get more stable patching if you utilize a local WSUS server. WSUS also allows for an piece of cake process of approving the patches that you are deploying.

Drivers and the reference image

Because we use modern virtual platforms for creating our reference images, nosotros don't demand to worry about drivers when creating reference images for Windows x. Nosotros utilize Hyper-V in our environment, and Windows Preinstallation Surround (Windows PE) already has all the needed drivers congenital-in for Hyper-V.

Create a chore sequence for Windows 10 Enterprise

To create a Windows 10 reference image task sequence, the process is as follows:

On MDT01:

  1. Using the Deployment Workbench, nether Deployment Shares > MDT Build Lab right-click Task Sequences, and create a New Binder named Windows ten.
  2. Right-click the new Windows 10 folder and select New Task Sequence. Apply the following settings for the New Task Sequence Wizard:
    1. Job sequence ID: REFW10X64-001
    2. Task sequence proper name: Windows 10 Enterprise x64 RTM Default Image
    3. Task sequence comments: Reference Build
    4. Template: Standard Client Task Sequence
    5. Select OS: Windows 10 Enterprise x64 RTM Default Image
    6. Specify Product Key: Do not specify a product key at this time
    7. Full Name: Contoso
    8. Organization: Contoso
    9. Internet Explorer home folio: http://world wide web.contoso.com
    10. Admin Password: Exercise non specify an Administrator Password at this time

Edit the Windows 10 chore sequence

The steps below walk you through the process of editing the Windows ten reference image task sequence to include the deportment required to update the reference image with the latest updates from WSUS, install roles and features, and utilities, and install Microsoft Office365 ProPlus x64.

On MDT01:

  1. In the Chore Sequences / Windows x folder, correct-click the Windows x Enterprise x64 RTM Default Image job sequence, and select Backdrop.
  2. On the Task Sequence tab, configure the Windows x Enterprise x64 RTM Default Image chore sequence with the following settings:

    1. Country Restore > Windows Update (Pre-Application Installation) action: Enable this action by clicking the Options tab and immigration the Disable this step check box.

    2. Land Restore > Windows Update (Post-Application Installation) activeness: Too enable this action.

    3. State Restore: Later on the Tattoo action, add a new Group activity (click Add then click New Group) with the following setting:

      • Proper name: Custom Tasks (Pre-Windows Update)

    4. Country Restore: Subsequently Windows Update (Post-Application Installation) action, rename Custom Tasks to Custom Tasks (Post-Windows Update).

      • Note: The reason for adding the applications later on the Tattoo activeness but before running Windows Update is simply to save time during the deployment. This way we can add all applications that will upgrade some of the congenital-in components and avert unnecessary updating.

    5. State Restore > Custom Tasks (Pre-Windows Update): Add a new Install Roles and Features action with the post-obit settings:

      1. Name: Install - Microsoft NET Framework 3.5.1
      2. Select the operating system for which roles are to be installed: Windows ten
      3. Select the roles and features that should be installed: .Cyberspace Framework iii.v (includes .NET two.0 and 3.0)

      Of import

      This is probably the nearly important step when creating a reference image. Many applications demand the .NET Framework, and we strongly recommend having it available in the image. The 1 thing that makes this different from other components is that .NET Framework three.5.1 is non included in the WIM file. Information technology is installed from the Sources\SxS folder on the media, and that makes it more than difficult to add afterward the image has been deployed.

      task sequence.

      The task sequence after creating the Custom Tasks (Pre-Windows Update) group and adding the Install - Microsoft Net Framework iii.v.1 action.

    6. Country Restore > Custom Tasks (Pre-Windows Update): Afterwards the Install - Microsoft Internet Framework three.5.1 action, add together a new Install Awarding action (selected from the Full general group) with the following settings:

      1. Name: Microsoft Visual C++ Redistributable 2019 - x86
      2. Install a Single Application: browse to Install - MSVC 2019 - x86

    7. Repeat these steps (add a new Install Application) to add together Microsoft Visual C++ Redistributable 2019 - x64 and Microsoft 365 Apps for enterprise as well.

  3. Click OK.

apps.

Optional configuration: Add together a suspend action

The goal when creating a reference prototype is of course to automate everything. But sometimes y'all have a special configuration or application setup that is likewise time-consuming to automate. If you lot need to do some manual configuration, you tin can add together a piddling-known characteristic called Lite Touch Installation (LTI) Suspend. If you lot add the LTISuspend.wsf script every bit a custom action in the chore sequence, information technology will suspend the task sequence until you click the Resume Chore Sequence shortcut icon on the desktop. In addition to using the LTI Suspend feature for manual configuration or installation, you can also utilise it only for verifying a reference prototype before you allow the task sequence to continue and use Sysprep and capture the virtual motorcar.

figure 8.

A task sequence with optional Suspend action (LTISuspend.wsf) added.

figure 9.

The Windows 10 desktop with the Resume Task Sequence shortcut.

Edit the Unattend.xml file for Windows 10 Enterprise

When using MDT, you don't demand to edit the Unattend.xml file very frequently considering almost configurations are taken intendance of by MDT. Notwithstanding if, for case, you lot want to configure Internet Explorer behavior, then you lot can edit the Unattend.xml for this. Editing the Unattend.xml for bones Internet Explorer settings is piece of cake, but for more advanced settings, you volition want to use the Cyberspace Explorer Administration Kit (IEAK).

Alert

Do not use SkipMachineOOBE or SkipUserOOBE in your Unattend.xml file. These settings are deprecated and tin can have unintended effects if used.

Note

You lot also can use the Unattend.xml to enable components in Windows 10, like the Telnet Customer or Hyper-V customer. Normally nosotros prefer to do this via the Install Roles and Features action, or using Deployment Paradigm Servicing and Management (DISM) command-line tools, because then we can add that equally an application, existence dynamic, having weather, and so along. Too, if you are adding packages via Unattend.xml, it is version specific, so Unattend.xml must match the exact version of the operating system you lot are servicing.

Follow these steps to configure Net Explorer settings in Unattend.xml for the Windows 10 Enterprise x64 RTM Default Prototype task sequence:

On MDT01:

  1. Using the Deployment Workbench, under Deployment Shares > MDT Build Lab > Task Sequences right-click the Windows 10 Enterprise x64 RTM Default Image task sequence and select Backdrop.
  2. In the Os Info tab, click Edit Unattend.xml. MDT now generates a catalog file. This will accept a few minutes, and then Windows Organization Image Manager (Windows SIM) volition start.

Of import

The ADK version 1903 has a known issue generating a itemize file for Windows 10, version 1903 or 1909 X64 install.wim. You might see the mistake "Could not load file or assembly" in in the console output. To avoid this issue, install the ADK, version 2004 or a later on version. A workaround is also available for the ADK version 1903:

  • Shut the Deployment Workbench and install the WSIM 1903 update. This volition update imagecat.exe and imgmgr.exe to version 10.0.18362.144.
  • Manually run imgmgr.exe (C:\Plan Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM\imgmgr.exe).
  • Generate a catalog (Tools/Create Itemize) for the selected install.wim (ex: D:\MDTBuildLab\Operating Systems\W10EX64RTM\sources\install.wim).
  • Subsequently manually creating the catalog file (ex: D:\MDTBuildLab\Operating Systems\W10EX64RTM\sources\install_Windows 10 Enterprise.clg), open the Deployment Workbench and proceed to edit unattend.xml.
  1. In Windows SIM, aggrandize the 4 specialize node in the Reply File pane and select the amd64_Microsoft-Windows-IE-InternetExplorer_neutral entry.
  2. In the amd64_Microsoft-Windows-IE-InternetExplorer_neutral properties window (right-hand window), set up the following values:
  • DisableDevTools: true

  1. Salve the Unattend.xml file, and close Windows SIM.

    • Note: If errors are reported that sure display values are wrong, you can ignore this or browse to 7oobeSystem\amd64_Microsoft-Windows-Beat out-Setup__neutral\Display and enter the following: ColorDepth 32, HorizontalResolution 1, RefreshRate 60, VerticalResolution 1.

  2. On the Windows 10 Enterprise x64 RTM Default Image Properties, click OK.

    figure 10.

    Windows System Image Manager with the Windows 10 Unattend.xml.

Agreement rules is critical to successfully using MDT. Rules are configured using the Rules tab of the deployment share's properties. The Rules tab is substantially a shortcut to edit the CustomSettings.ini file that exists in the D:\MDTBuildLab\Command folder. This section discusses how to configure the MDT deployment share rules as part of your Windows 10 Enterprise deployment.

In MDT, at that place are ever 2 rule files: the CustomSettings.ini file and the Bootstrap.ini file. You can add almost any rule to either. Still, the Bootstrap.ini file is copied from the Control folder to the boot paradigm, so the kicking image needs to be updated every fourth dimension you modify that file. For this reason, add only a minimal set of rules to Bootstrap.ini, such every bit which deployment server and share to connect to - the DEPLOYROOT value. Put the other rules in CustomSettings.ini because that file is updated immediately when you click OK.

To configure the rules for the MDT Build Lab deployment share:

On MDT01:

  1. Using the Deployment Workbench, correct-click the MDT Build Lab deployment share and select Properties.

  2. Select the Rules tab and supplant the existing content with the following information (edit the settings as needed to match your deployment). For example, If you do not have a WSUS server in your environment, delete the WSUSServer line from the configuration:

                      [Settings] Priority=Default  [Default] _SMSTSORGNAME=Contoso UserDataLocation=NONE DoCapture=Aye OSInstall=Y AdminPassword=laissez passer@word1 TimeZoneName=Pacific Standard Fourth dimension  JoinWorkgroup=WORKGROUP HideShell=YES FinishAction=SHUTDOWN DoNotCreateExtraPartition=YES WSUSServer=http://mdt01.contoso.com:8530 ApplyGPOPack=NO SLSHARE=\\MDT01\Logs$ SkipAdminPassword=Yeah SkipProductKey=YES SkipComputerName=YES SkipDomainMembership=YES SkipUserData=YES SkipLocaleSelection=YES SkipTaskSequence=NO SkipTimeZone=Yep SkipApplications=YES SkipBitLocker=Aye SkipSummary=YES SkipRoles=YES SkipCapture=NO SkipFinalSummary=YES

    figure 11.

    The server-side rules for the MDT Build Lab deployment share.

  3. Click Edit Bootstrap.ini and modify using the following information:

                      [Settings] Priority=Default  [Default] DeployRoot=\\MDT01\MDTBuildLab$ UserDomain=CONTOSO UserID=MDT_BA UserPassword=pass@word1  SkipBDDWelcome=YES

    Notation

    For security reasons, yous normally don't add the password to the Bootstrap.ini file; nonetheless, considering this deployment share is for creating reference epitome builds only, and should non be published to the product network, it is acceptable to do so in this state of affairs. Plainly if you are not using the same password (pass@word3) that is provided in this lab, you must enter your own custom password on the Rules tab and in Bootstrap.ini.

  4. On the Windows PE tab, in the Platform drib-down listing, select x86.

  5. In the Calorie-free Impact Kick Image Settings area, configure the following settings:

    1. Prototype clarification: MDT Build Lab x86
    2. ISO file name: MDT Build Lab x86.iso

  6. On the Windows PE tab, in the Platform drop-down listing, select x64.

  7. In the Lite Touch on Kicking Image Settings area, configure the following settings:

    1. Image clarification: MDT Build Lab x64
    2. ISO file proper name: MDT Build Lab x64.iso

  8. Click OK.

Note

In MDT, the x86 kick image can deploy both x86 and x64 operating systems (except on computers based on Unified Extensible Firmware Interface).

Later on the deployment share has been configured, it needs to exist updated. This is the process when the Windows PE boot images are created.

  1. In the Deployment Workbench, correct-click the MDT Build Lab deployment share and select Update Deployment Share.
  2. Utilise the default options for the Update Deployment Share Sorcerer.

Note

The update process volition have 5 to 10 minutes.

The rules explained

At present that the MDT Build Lab deployment share (the share used to create the reference images) has been configured, it is time to explain the various settings used in the Bootstrap.ini and CustomSettings.ini files.

The Bootstrap.ini and CustomSettings.ini files work together. The Bootstrap.ini file is always present on the kick image and is read first. The basic purpose for Bootstrap.ini is to provide just plenty information for MDT to detect the CustomSettings.ini.

The CustomSettings.ini file is normally stored on the server, in the Deployment share\Command binder, but also can be stored on the media (when using offline media).

Note

The settings, or properties, that are used in the rules (CustomSettings.ini and Bootstrap.ini) are listed in the MDT documentation, in the Microsoft Deployment Toolkit Reference / Properties / Holding Definition section.

The Bootstrap.ini file

The Bootstrap.ini file is available via the deployment share'south Properties dialog box, or via the D:\MDTBuildLab\Control binder on MDT01.

              [Settings] Priority=Default [Default] DeployRoot=\\MDT01\MDTBuildLab$ UserDomain=CONTOSO UserID=MDT_BA UserPassword=laissez passer@word1 SkipBDDWelcome=Aye

Then, what are these settings?

  • Priority. This determines the order in which different sections are read. This Bootstrap.ini has simply i section, named [Default].

  • DeployRoot. This is the location of the deployment share. Commonly, this value is set past MDT, but you need to update the DeployRoot value if you move to another server or other share. If you don't specify a value, the Windows Deployment Wizard prompts you for a location.

  • UserDomain, UserID, and UserPassword. These values are used for automatic log on to the deployment share. Again, if they are non specified, the wizard prompts you.

    Warning

    Circumspection is brash. These values are stored in clear text on the boot image. Apply them only for the MDT Build Lab deployment share and not for the MDT Production deployment share that you lot learn to create in the next topic.

  • SkipBDDWelcome. Even if it is nice to exist welcomed every time we commencement a deployment, we prefer to skip the initial welcome page of the Windows Deployment Wizard.

Annotation

All backdrop beginning with "Skip" control only whether to display that pane in the Windows Deployment Wizard. Most of the panes also crave yous to actually fix one or more than values.

The CustomSettings.ini file

The CustomSettings.ini file, whose content you come across on the Rules tab of the deployment share Properties dialog box, contains most of the properties used in the configuration.

              [Settings] Priority=Default [Default] _SMSTSORGNAME=Contoso UserDataLocation=NONE DoCapture=Aye OSInstall=Y AdminPassword=pass@word1 TimeZoneName=Pacific Standard Fourth dimension  JoinWorkgroup=WORKGROUP HideShell=YES FinishAction=SHUTDOWN DoNotCreateExtraPartition=Yes WSUSServer=http://mdt01.contoso.com:8530 ApplyGPOPack=NO SLSHARE=\\MDT01\Logs$ SkipAdminPassword=Aye SkipProductKey=Yes SkipComputerName=Yes SkipDomainMembership=Aye SkipUserData=YES SkipLocaleSelection=YES SkipTaskSequence=NO SkipTimeZone=YES SkipApplications=Yeah SkipBitLocker=YES SkipSummary=YES SkipRoles=YES SkipCapture=NO SkipFinalSummary=Yep

  • Priority. Has the same function as in Bootstrap.ini. Priority determines the order in which different sections are read. This CustomSettings.ini has but one section, named [Default]. In general, if you take multiple sections that gear up the aforementioned value, the value from the first section (higher priority) wins. The rare exceptions are listed in the ZTIGather.xml file.

  • _SMSTSORGNAME. The arrangement name displayed in the chore sequence progress bar window during deployment.

  • UserDataLocation. Controls the settings for user state backup. You do not demand to utilise when building and capturing a reference image.

  • DoCapture. Configures the task sequence to run the Organization Training (Sysprep) tool and capture the image to a file when the operating system is installed.

  • OSInstall. Must be prepare to Y or YES (the code actually just looks for the Y graphic symbol) for the setup to continue.

  • AdminPassword. Sets the local Ambassador account password.

  • TimeZoneName. Establishes the fourth dimension zone to use. Don't confuse this value with TimeZone, which is only for legacy operating systems (Windows 7 and Windows Server 2003).

    Annotation: The easiest way to find the current time zone name on a Windows 10 machine is to run tzutil /g in a command prompt. You can also run tzutil /l to get a listing of all available time zone names.

  • JoinWorkgroup. Configures Windows to bring together a workgroup.

  • HideShell. Hides the Windows Shell during deployment. This is especially useful for Windows 10 deployments in which the deployment wizard will otherwise appear behind the tiles.

  • FinishAction. Instructs MDT what to do when the task sequence is consummate.

  • DoNotCreateExtraPartition. Configures the task sequence not to create the extra sectionalisation for BitLocker. There is no need to do this for your reference image.

  • WSUSServer. Specifies which Windows Server Update Services (WSUS) server (and port, if needed) to use during the deployment. Without this option MDT will use Microsoft Update directly, which will increase deployment fourth dimension and limit your options of decision-making which updates are applied.

  • SLSHARE. Instructs MDT to re-create the log files to a server share if something goes wrong during deployment, or when a deployment is successfully completed.

  • ApplyGPOPack. Allows y'all to deploy local group policies created by Microsoft Security Compliance Managing director (SCM).

  • SkipAdminPassword. Skips the pane that asks for the Administrator password.

  • SkipProductKey. Skips the pane that asks for the product key.

  • SkipComputerName. Skips the Computer Proper noun pane.

  • SkipDomainMemberShip. Skips the Domain Membership pane. If set to Aye, you need to configure either the JoinWorkgroup value or the JoinDomain, DomainAdmin, DomainAdminDomain, and DomainAdminPassword backdrop.

  • SkipUserData. Skips the pane for user state migration.

  • SkipLocaleSelection. Skips the pane for selecting language and keyboard settings.

  • SkipTimeZone. Skips the pane for setting the time zone.

  • SkipApplications. Skips the Applications pane.

  • SkipBitLocker. Skips the BitLocker pane.

  • SkipSummary. Skips the initial Windows Deployment Wizard summary pane.

  • SkipRoles. Skips the Install Roles and Features pane.

  • SkipCapture. Skips the Capture pane.

  • SkipFinalSummary. Skips the final Windows Deployment Sorcerer summary. Because you use FinishAction=Shutdown, you don't desire the sorcerer to terminate in the end then that you demand to click OK earlier the machine shuts down.

Build the Windows x reference image

Equally previously described, this section requires a Hyper-Five host. See Hyper-V requirements for more than information.

Once you have created your task sequence, yous are gear up to create the Windows ten reference prototype. This will exist performed by launching the task sequence from a virtual machine which will then automatically perform the reference epitome creation and capture process.

The steps below outline the procedure used to kicking a virtual automobile using an ISO boot image created by MDT, and so run the reference epitome task sequence image to create and capture the Windows x reference image.

  1. Copy D:\MDTBuildLab\Boot\MDT Build Lab x86.iso on MDT01 to C:\ISO on your Hyper-Five host (HV01).

    Note: Call up, in MDT yous tin use the x86 boot image to deploy both x86 and x64 operating system images. That's why you can use the x86 boot image instead of the x64 kicking image.

On HV01:

  1. Create a new virtual machine with the post-obit settings:

    1. Proper name: REFW10X64-001
    2. Store the virtual machine in a different location: C:\VM
    3. Generation 1
    4. Memory: 1024 MB
    5. Network: Must be able to connect to \MDT01\MDTBuildLab$
    6. Hd: 60 GB (dynamic deejay)
    7. Install Bone with image file: C:\ISO\MDT Build Lab x86.iso

  2. Before you start the VM, add a checkpoint for REFW10X64-001, and name it Clean with MDT Build Lab x86 ISO.

    Notation: Checkpoints are useful if you need to restart the procedure and want to brand sure you can start clean.

  3. Start the REFW10X64-001 virtual machine and connect to it.

    Annotation: Up to this point we have not discussed IP addressing or DHCP. In the initial setup for this guide, DC01 was provisioned as a DHCP server to provide IP address leases to customer computers. You might have a different DHCP server on your network that you wish to employ. The REFW10X64-001 virtual machine requires an IP accost lease that provides it with connectivity to MDT01 so that it tin connect to the \MDT01\MDTBuildLab$ share. In the current scenario this is accomplished with a DHCP scope that provides IP addresses in the 10.10.10.100 - 10.10.ten.200 range, as part of a /24 subnet so that the customer tin can connect to MDT01 at 10.10.10.11.

    Subsequently booting into Windows PE, complete the Windows Deployment Wizard with the following settings:

    1. Select a job sequence to execute on this computer: Windows 10 Enterprise x64 RTM Default Image

    2. Specify whether to capture an image: Capture an image of this reference reckoner

      • Location: \\MDT01\MDTBuildLab$\Captures

    3. File name: REFW10X64-001.wim

      capture image.

      The Windows Deployment Wizard for the Windows 10 reference paradigm.

  4. The setup now starts and does the post-obit:

    1. Installs the Windows x Enterprise operating system.
    2. Installs the added applications, roles, and features.
    3. Updates the operating organisation via your local Windows Server Update Services (WSUS) server.
    4. Stages Windows PE on the local disk.
    5. Runs Arrangement Training (Sysprep) and reboots into Windows PE.
    6. Captures the installation to a Windows Imaging (WIM) file.
    7. Turns off the virtual machine.

After some fourth dimension, yous will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep, located in the D:\MDTBuildLab\Captures folder on your deployment server. The file name is REFW10X64-001.wim.

image.

Troubleshooting

If you enabled monitoring, y'all tin can check the progress of the job sequence.

monitoring.

If at that place are problems with your task sequence, you tin troubleshoot in Windows PE by pressing F8 to open a command prompt. There are several MDT log files created that can be helpful determining the origin of an fault, such as BDD.log. From the command line in Windows PE y'all tin copy these logs from the client to your MDT server for viewing with CMTrace. For case: copy BDD.log \\mdt01\logs$.

Later some time, you will accept a Windows 10 Enterprise x64 prototype that is fully patched and has run through Sysprep, located in the D:\MDTBuildLab\Captures folder on your deployment server. The file name is REFW10X64-001.wim.

Get started with the Microsoft Deployment Toolkit (MDT)
Deploy a Windows x image using MDT
Build a distributed surroundings for Windows 10 deployment
Refresh a Windows vii computer with Windows 10
Replace a Windows 7 computer with a Windows x computer
Configure MDT settings