In this topic
Step 1: Configure Active Directory permissions
Step 2: Set up the MDT production deployment share
Step 3: Add a custom image
Step 4: Add an application
Step 5: Prepare the drivers repository
Step 6: Create the deployment task sequence
Step 7: Configure the MDT production deployment share
Step 8: Deploy the Windows 8.1 client image
Multicast deployments
Use offline media to deploy Windows 8.1
Unified Extensible Firmware Interface (UEFI)-based deployments
See also
Get Started with the Microsoft Deployment Toolkit (MDT)
Create a Windows 8.1 Reference Image
Build a Distributed Environment for Windows 8.1 Deployment
Refresh a Windows 7 Computer with Windows 8.1
Replace a Windows 7 Computer with a Windows 8.1 Computer
Configure MDT 2013 Settings
Upgrade Windows 8 to Windows 8.1
2/18/2015
Page 2 of 21
Windows Preinstallation Environment (Windows PE) to connect to MDT01.In order for MDT 2013 to join machines into the contoso.com domain you need to
create an account and configure permissions in Active Directory.
1. On DC01, using Active Directory User and Computers, browse to contoso.com / Contoso / Service Accounts.
2. Select the Service Accounts organizational unit (OU) and create the MDT_JD account using the following settings:
a. Name: MDT_JD
b. User logon name: MDT_JD
c. Password: P@ssw0rd
d. User must change password at next logon: Clear
e. User cannot change password: Select
f. Password never expires: Select
3. In an elevated Windows PowerShell prompt (run as Administrator), run the following commands and press Enter after each command:
4. The Set-OUPermissions.ps1 script allows the MDT_JD user account permissions to manage computer accounts in the Contoso / Computers OU. Below you
find a list of the permissions being granted:
a. Scope: This object and all descendant objects
i. Create Computer objects
ii. Delete Computer objects
b. Scope: Descendant Computer objects
i. Read All Properties
ii. Write All Properties
iii. Read Permissions
iv. Modify Permissions
v. Change Password
vi. Reset Password
vii. Validated write to DNS host name
viii. Validated write to service principal name
2/18/2015
Page 3 of 21
3. On the Path page, in the Deployment share path text box, type E:\MDTProduction and click Next.
4. On the Share page, in the Share name text box, type MDTProduction$ and click Next.
5. On the Descriptive Name page, in the Deployment share description text box, type MDT Production and click Next.
6. On the Options page, accept the default settings and click Next twice, and then click Finish.
7. Using File Explorer, verify that you can access the \\MDT01\MDTProduction$ share.
1. Using the Deployment Workbench, expand the Deployment Shares node, and then expand MDT Production; select the Operating Systems node, and
create a folder named Windows 8.1.
2. Right-click the Windows 8.1 folder and select Import Operating System.
3. On the OS Type page, select Custom image file and click Next.
4. On the Image page, in the Source file text box, browse to E:\MDTBuildLab\Captures\REFW81X64-001.wim and click Next.
5. On the Setup page, select the Copy Windows 7, Windows Server 2008 R2, or later setup files from the specified path option; in the Setup source
directory text box, browse to E:\MDTBuildLab\Operating Systems\W81EX64RTM and click Next.
6. On the Destination page, in the Destination directory name text box, type W81EX64RTM, click Next twice, and then click Finish.
7. After adding the operating system, double-click the added operating system name in the Operating Systems / Windows 8.1 node and change the
name to match the following: Windows 8.1 Enterprise x64 RTM Custom Image.
Note
The reason for adding the setup files has changed since earlier versions of MDT. MDT 2010 used the setup files to install Windows. MDT 2013 uses ImageX
to apply the image; however, you still need the setup files because some components in roles and features are stored outside the main image.
2/18/2015
Page 4 of 21
1. Using the Deployment Workbench, expand the MDT Production node and navigate to the Applications node.
2. Right-click the Applications node, and create a new folder named Adobe.
3. In the Applications node, right-click the Adobe folder and select New Application.
4. On the Application Type page, select the Application with source files option and click Next.
5. On the Details page, in the Application name text box, type Install - Adobe Reader XI - x86 and click Next.
6. On the Source page, in the Source Directory text box, browse to E:\Setup\Adobe Reader XI and click Next.
7. On the Destination page, in the Specify the name of the directory that should be created text box, type Install - Adobe Reader XI - x86 and click
Next.
8. On the Command Details page, in the Command Line text box, type msiexec /i AdbeRdr11000_eu_ES.msi /q, click Next twice, and then click Finish.
For boot images, you need to have storage and network drivers; for the operating system, you need to have the full suite of drivers.
Note
2/18/2015
Page 5 of 21
You should only add drivers to the Windows PE images if the default drivers dont work. Adding drivers that are not necessary will only make the boot image
larger and potentially delay the download time.
Note
Even if you are not going to use both x86 and x64 boot images, we still recommend that you add the support structure for future use.
2/18/2015
Page 6 of 21
c. Lenovo
i. 4178
d. Microsoft
i. Surface with Windows 8 Pro
The preceding folder names are selected because they match the actual make and model values that MDT reads from the machines during deployment. You
can find out the model values for your machines via the following command in Windows PowerShell:
Get-WmiObject
-Class:Win32_ComputerSystem
If you want a more standardized naming convention, try the ModelAliasExit.vbs script from the Deployment Guys blog post entitled Using and Extending Model
Aliases for Hardware Specific Application Installation.
1. On MDT01, using the Deployment Workbench, in the MDT Production node, expand the Advanced Configuration node, right-click the Selection
Profiles node, and select New Selection Profile.
2. In the New Selection Profile Wizard, create a selection profile with the following settings:
a. Selection Profile name: WinPE x86
b. Folders: Select the WinPE x86 folder in Out-of-Box Drivers.
2/18/2015
Page 7 of 21
3. Again, right-click the Selection Profiles node, and select New Selection Profile.
4. In the New Selection Profile Wizard, create a selection profile with the following settings:
a. Selection Profile name: WinPE x64
b. Folders: Select the WinPE x64 folder in Out-of-Box Drivers.
2/18/2015
Page 8 of 21
1. On MDT01, using the Deployment Workbench, in the MDT Production node, expand the Out-Of-Box Drivers node, and expand the Lenovo node.
2. Right-click the 4178 folder and select Import Drivers; use the following setting for the Import Drivers Wizard:
a. Driver source directory: E:\Drivers\Windows 8.1 x64\Lenovo\ThinkPad T420 (4178)
1. On MDT01, using the Deployment Workbench, in the MDT Production node, expand the Out-Of-Box Drivers node, and expand the Dell node.
2. Right-click the Latitude E6440 folder and select Import Drivers; use the following setting for the Import Drivers Wizard:
a. Driver source directory: E:\Drivers\Windows 8.1 x64\Dell\Latitude E6440
2/18/2015
Page 9 of 21
1. On MDT01, using the Deployment Workbench, in the MDT Production node, expand the Out-Of-Box Drivers node, and expand the HewlettPackard node.
2. Right-click the HP EliteBook 8560w folder and select Import Drivers; use the following setting for the Import Drivers Wizard:
a. Driver source directory: E:\Drivers\Windows 8.1 x64\HP\HP EliteBook 8560w
1. On MDT01, using the Deployment Workbench, in the MDT Production node, expand the Out-Of-Box Drivers node, and expand the Microsoft
node.
2. Right-click the Surface with Windows 8 Pro folder and select Import Drivers; use the following setting for the Import Drivers Wizard:
a. Driver source directory: E:\Drivers\Windows 8.1 x64\Microsoft\Surface with Windows 8 Pro
2/18/2015
Page 10 of 21
Note
The configuration above indicates that MDT should only use drivers from the folder specified by the DriverGroup001 property, which is
defined by the Choose a selection profile: Nothing setting, and that MDT should not use plug and play to determine which drivers to
copy, which is defined by the Install all drivers from the selection profile setting.
Note
In Windows PE 5.0, which MDT 2013 uses, you dont need to set the scratch space size like you did in previous versions. Scratch space in Windows PE 5.0 is
dynamic. For example, if you have 1 GB of RAM or more on the machine you are deploying, Windows PE 5.0 will automatically set 512 MB scratch space.
2/18/2015
Page 11 of 21
[Settings]
Priority=Default
[Default]
_SMSTSORGNAME=Contoso
OSInstall=YES
UserDataLocation=AUTO
TimeZoneName=Pacific Standard Time
AdminPassword=P@ssw0rd
JoinDomain=contoso.com
DomainAdmin=CONTOSO\MDT_JD
DomainAdminPassword=P@ssw0rd
MachineObjectOU=OU=Workstations,OU=Computers,OU=Contoso,DC=contoso,DC=com
SLShare=\\MDT01\Logs$
ScanStateArgs=/ue:*\* /ui:CONTOSO\*
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
HideShell=YES
ApplyGPOPack=NO
WSUSServer=mdt01.contoso.com:8530
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=NO
SkipBitLocker=YES
SkipSummary=YES
SkipCapture=YES
SkipFinalSummary=NO
[Settings]
Priority=Default
[Default]
DeployRoot=\\MDT01\MDTProduction$
UserDomain=CONTOSO
UserID=MDT_BA
SkipBDDWelcome=YES
5. In the Windows PE tab, in the Platform drop-down list, make sure x86 is selected.
6. In the General sub tab, configure the following settings:
a. In the Lite Touch Boot Image Settings area:
i. Image description: MDT Production x86
ii. ISO file name: MDT Production x86.iso
2/18/2015
Page 12 of 21
Note
Because you are going to use Pre-Boot Execution Environment (PXE) later to deploy the machines, you dont need the ISO file; however, we
recommend creating ISO files because they are useful when troubleshooting deployments and for quick tests.
7. In the Drivers and Patches sub tab, select the WinPE x86 selection profile and select the Include all drivers from the selection profile option.
8. In the Windows PE tab, in the Platform drop-down list, select x64.
9. In the General sub tab, configure the following settings:
a. In the Lite Touch Boot Image Settings area:
i. Image description: MDT Production x64
ii. ISO file name: MDT Production x64.iso
10. In the Drivers and Patches sub tab, select the WinPE x64 selection profile and select the Include all drivers from the selection profile option.
11. In the Monitoring tab, select the Enable monitoring for this deployment share check box.
12. Click OK.
Note
It will take a while for the Deployment Workbench to create the monitoring database and web service.
2/18/2015
Page 13 of 21
This is the MDT Production Bootstrap.ini without the user credentials (except domain information):
[Settings]
Priority=Default
[Default]
DeployRoot=\\MDT01\MDTProduction$
UserDomain=CONTOSO
UserID=MDT_BA
SkipBDDWelcome=YES
[Settings]
Priority=Default
[Default]
_SMSTSORGNAME=Contoso
OSInstall=Y
UserDataLocation=AUTO
TimeZoneName=Pacific Standard Time
AdminPassword=P@ssw0rd
JoinDomain=contoso.com
DomainAdmin=CONTOSO\MDT_JD
DomainAdminPassword=P@ssw0rd
MachineObjectOU=OU=Workstations,OU=Computers,OU=Contoso,DC=contoso,DC=com
SLShare=\\MDT01\Logs$
ScanStateArgs=/ue:*\* /ui:CONTOSO\*
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
HideShell=YES
ApplyGPOPack=NO
WSUSServer=http://mdt01.contoso.com:8530
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=NO
SkipBitLocker=YES
SkipSummary=YES
SkipCapture=YES
SkipFinalSummary=NO
EventService=http://MDT01:9800
The additional properties to use in the MDT Production rules file are as follows:
2/18/2015
Page 14 of 21
In these steps, we assume that you downloaded MDOP 2013 R2 and copied DaRT 8.1 to the E:\Setup\DaRT 8.1 folder on MDT01.
2/18/2015
Page 15 of 21
1. Right-click the MDT Production deployment share and select Update Deployment Share.
2. Use the default options for the Update Deployment Share Wizard.
Note
The update process will take 5 to 10 minutes.
1. Using the WDS console, right-click Boot Images and select Add Boot Image.
2. Browse to the E:\MDTProduction\Boot\LiteTouchPE_x64.wim file and add the image with the default settings.
2/18/2015
Page 16 of 21
2/18/2015
Page 17 of 21
1. On MDT01, using Deployment Workbench, expand the MDT Production deployment share folder.
2. Select the Monitoring node, and wait until you see PC0005.
3. Double-click PC0005, and review the information.
Figure 13. The Monitoring node, showing the deployment progress of PC0005.
2/18/2015
Page 18 of 21
Multicast deployments
Multicast deployment allows for image deployment with reduced network load during simultaneous deployments. Multicast is a useful operating system
deployment feature in Microsoft Deployment Toolkit (MDT) 2013 deployments, however it is important to ensure that your network supports it and is designed
for it.
Requirements
Multicast requires that Windows Deployment Services (WDS) is running on Windows Server 2008 or later. In addition to the core MDT 2013 setup for multicast,
the network needs to be configured to support multicast. In general, this means involving the organization networking team to make sure that Internet Group
Management Protocol (IGMP) snooping is turned on and that the network is designed for multicast traffic. The multicast solution uses IGMPv3.
1. On MDT01, right-click the MDT Production deployment share folder and select Properties.
2. In the General tab, select the Enable multicast for this deployment share (requires Windows Server 2008 R2 Windows Deployment Services)
check box, and click OK.
3. Right-click the MDT Production deployment share folder and select Update Deployment Share.
4. After updating the deployment share, use the Windows Deployment Services console to, verify that the multicast namespace was created.
2/18/2015
Page 19 of 21
1. On MDT01, using Deployment Workbench, in the MDT Production / Advanced Configuration node, right-click Selection Profile, and select New
Selection Profile.
2. Use the following settings for the New Selection Profile Wizard:
a. General Settings
i. Selection profile name: Windows 8.1 Offline Media
b. Folders
i. Applications / Adobe
ii. Operating Systems / Windows 8.1
iii. Out-Of-Box Drivers / WinPE x64
iv. Out-Of-Box Drivers / Windows 8.1 x64
v. Task Sequences / Windows 8.1
Note
2/18/2015
Page 20 of 21
When creating offline media, you need to create the target folder first. It is crucial that you do not create a subfolder inside the deployment share
folder because it will break the offline media.
2. Using Deployment Workbench, in the MDT Production / Advanced Configuration node, right-click the Media node, and select New Media.
3. Use the following settings for the New Media Wizard:
a. General Settings
i. Media path: E:\MDTOfflineMedia
ii. Selection profile: Windows 8.1 Offline Media
1. On MDT01, using File Explorer, copy the CustomSettings.ini file from the E:\MDTBuildLab\Control folder to
E:\MDTOfflineMedia\Content\Deploy\Control. Overwrite the existing files.
2. Using Deployment Workbench, in the MDT Production / Advanced Configuration / Media node, right-click the MEDIA001 media, and select
Properties.
3. In the General tab, configure the following:
a. Clear the Generate x86 boot image check box.
b. ISO file name: Windows 8.1 Offline Media.iso
4. Still in the Windows PE tab, in the Platform drop-down list, select x64.
5. In the General sub tab, configure the following settings:
a. In the Lite Touch Boot Image Settings area:
i. Image description: MDT Production x64
b. In the Windows PE Customizations area, set the Scratch space size to 128.
6. In the Drivers and Patches sub tab, select the WinPE x64 selection profile and select the Include all drivers from the selection profile option.
7. Click OK.
1. On MDT01, using Deployment Workbench, navigate to the MDT Production / Advanced Configuration / Media node.
2. Right-click the MEDIA001 media, and select Update Media Content. The Update Media Content process now generates the offline media in the
E:\MDTOfflineMedia\Content folder.
1. On a physical machine running Windows 8.1 (or Windows 7), insert the USB stick you want to use.
2/18/2015
Page 21 of 21
2. Copy the content of the MDTOfflineMedia\Content folder to the root of the USB stick.
3. Start an elevated command prompt (run as Administrator), and start the Diskpart utility by typing Diskpart and pressing Enter.
4. In the Diskpart utility, you can type list volume (or the shorter list vol) to list the volumes, but you really only need to remember the drive letter of the
USB stick to which you copied the content. In our example, the USB stick had the drive letter F.
5. In the Diskpart utility, type select volume F (replace F with your USB stick drive letter).
6. In the Diskpart utility, type active, and then type exit.
Community Additions
2015 Microsoft
2/18/2015