mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
fix conflicts
This commit is contained in:
greg-lindsay
@ -45,8 +45,9 @@ These steps will show you how to configure an Active Directory account with the
|
||||
|
||||
On **DC01**:
|
||||
|
||||
1. Download the [Set-OUPermissions.ps1 script](https://go.microsoft.com/fwlink/p/?LinkId=619362) and copy it to the **C:\\Setup\\Scripts** directory on DC01. This script configures permissions to allow the MDT_JD account to manage computer accounts in the contoso > Computers organizational unit.
|
||||
2. Create the MDT_JD service account by running the following command from an elevated Windows PowerShell prompt:
|
||||
1. Download the [Set-OUPermissions.ps1 script](https://go.microsoft.com/fwlink/p/?LinkId=619362) and copy it to the **C:\\Setup\\Scripts** directory on **DC01**. This script configures permissions to allow the **MDT_JD** account to manage computer accounts in the contoso > Computers organizational unit.
|
||||
|
||||
2. Create the **MDT_JD** service account by running the following command from an elevated **Windows PowerShell prompt**:
|
||||
|
||||
```powershell
|
||||
New-ADUser -Name MDT_JD -UserPrincipalName MDT_JD -path "OU=Service Accounts,OU=Accounts,OU=Contoso,DC=CONTOSO,DC=COM" -Description "MDT join domain account" -AccountPassword (ConvertTo-SecureString "pass@word1" -AsPlainText -Force) -ChangePasswordAtLogon $false -PasswordNeverExpires $true -Enabled $true
|
||||
@ -60,19 +61,20 @@ On **DC01**:
|
||||
.\Set-OUPermissions.ps1 -Account MDT_JD -TargetOU "OU=Workstations,OU=Computers,OU=Contoso"
|
||||
```
|
||||
|
||||
The following is a list of the permissions being granted:
|
||||
a. Scope: This object and all descendant objects
|
||||
b. Create Computer objects
|
||||
c. Delete Computer objects
|
||||
d. Scope: Descendant Computer objects
|
||||
e. Read All Properties
|
||||
f. Write All Properties
|
||||
g. Read Permissions
|
||||
h. Modify Permissions
|
||||
i. Change Password
|
||||
j. Reset Password
|
||||
k. Validated write to DNS host name
|
||||
l. Validated write to service principal name
|
||||
The following is a list of the permissions being granted:
|
||||
|
||||
- Scope: This object and all descendant objects
|
||||
- Create Computer objects
|
||||
- Delete Computer objects
|
||||
- Scope: Descendant Computer objects
|
||||
- Read All Properties
|
||||
- Write All Properties
|
||||
- Read Permissions
|
||||
- Modify Permissions
|
||||
- Change Password
|
||||
- Reset Password
|
||||
- Validated write to DNS host name
|
||||
- Validated write to service principal name
|
||||
|
||||
## Step 2: Set up the MDT production deployment share
|
||||
|
||||
@ -87,8 +89,11 @@ The steps for creating the deployment share for production are the same as when
|
||||
1. Ensure you are signed on as: contoso\administrator.
|
||||
2. In the Deployment Workbench console, right-click **Deployment Shares** and select **New Deployment Share**.
|
||||
3. On the **Path** page, in the **Deployment share path** text box, type **D:\\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.
|
||||
|
||||
@ -116,9 +121,13 @@ In these steps, we assume that you have completed the steps in the [Create a Win
|
||||
|
||||
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 10**.
|
||||
2. Right-click the **Windows 10** 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 **D:\\MDTBuildLab\\Captures\\REFW10X64-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 **D:\\MDTBuildLab\\Operating Systems\\W10EX64RTM** and click **Next**.
|
||||
|
||||
6. On the **Destination** page, in the **Destination directory name** text box, type **W10EX64RTM**, 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 10** node and change the name to **Windows 10 Enterprise x64 RTM Custom Image**.
|
||||
|
||||
@ -140,16 +149,22 @@ On **MDT01**:
|
||||
2. Extract the .exe file that you downloaded to an .msi (ex: .\AcroRdrDC1902120058_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
|
||||
3. In the Deployment Workbench, expand the **MDT Production** node and navigate to the **Applications** node.
|
||||
4. Right-click the **Applications** node, and create a new folder named **Adobe**.
|
||||
|
||||
5. In the **Applications** node, right-click the **Adobe** folder and select **New Application**.
|
||||
|
||||
6. On the **Application Type** page, select the **Application with source files** option and click **Next**.
|
||||
|
||||
7. On the **Details** page, in the **Application Name** text box, type **Install - Adobe Reader** and click *Next**.
|
||||
|
||||
8. On the **Source** page, in the **Source Directory** text box, browse to **D:\\setup\\adobe\\install** and click **Next**.
|
||||
|
||||
9. On the **Destination** page, in the **Specify the name of the directory that should be created** text box, type **Install - Adobe Reader** and click **Next**.
|
||||
|
||||
10. On the **Command Details** page, in the **Command Line** text box, type **msiexec /i AcroRead.msi /q**, click **Next** twice, and then click **Finish**.
|
||||
|
||||
|
||||
|
||||
|
||||
The Adobe Reader application added to the Deployment Workbench.
|
||||
The Adobe Reader application added to the Deployment Workbench.
|
||||
|
||||
## Step 5: Prepare the drivers repository
|
||||
|
||||
@ -211,16 +226,17 @@ When you import drivers to the MDT driver repository, MDT creates a single insta
|
||||
|
||||
The preceding folder names should match the actual make and model values that MDT reads from devices during deployment. You can find out the model values for your machines by using the following command in Windows PowerShell:
|
||||
|
||||
``` powershell
|
||||
```powershell
|
||||
Get-WmiObject -Class:Win32_ComputerSystem
|
||||
```
|
||||
|
||||
Or, you can use this command in a normal command prompt:
|
||||
|
||||
```
|
||||
```console
|
||||
wmic csproduct get name
|
||||
```
|
||||
|
||||
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](https://go.microsoft.com/fwlink/p/?LinkId=619536).
|
||||
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](https://go.microsoft.com/fwlink/p/?LinkId=619536).
|
||||
|
||||
|
||||
|
||||
@ -244,9 +260,9 @@ On **MDT01**:
|
||||
2. Folders: Select the WinPE x64 folder in Out-of-Box Drivers.
|
||||
3. Click **Next**, **Next** and **Finish**.
|
||||
|
||||
|
||||
|
||||
|
||||
Creating the WinPE x64 selection profile.
|
||||
Creating the WinPE x64 selection profile.
|
||||
|
||||
### Extract and import drivers for the x64 boot image
|
||||
|
||||
@ -267,7 +283,8 @@ On **MDT01**:
|
||||
|
||||
For the ThinkStation P500 model, you use the Lenovo ThinkVantage Update Retriever software to download the drivers. With Update Retriever, you need to specify the correct Lenovo Machine Type for the actual hardware (the first four characters of the model name). As an example, the Lenovo ThinkStation P500 model has the 30A6003TUS model name, meaning the Machine Type is 30A6.
|
||||
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
To get the updates, download the drivers from the Lenovo ThinkVantage Update Retriever using its export function. You can also download the drivers by searching PC Support on the [Lenovo website](https://go.microsoft.com/fwlink/p/?LinkId=619543).
|
||||
|
||||
@ -276,9 +293,12 @@ In this example, we assume you have downloaded and extracted the drivers using T
|
||||
On **MDT01**:
|
||||
|
||||
1. In the Deployment Workbench, in the **MDT Production** > **Out-Of-Box Drivers** > **Windows 10 x64** node, expand the **Lenovo** node.
|
||||
2. Right-click the **30A6003TUS** folder and select **Import Drivers** and use the following Driver source directory to import drivers: **D:\\Drivers\\Windows 10 x64\\Lenovo\\ThinkStation P500 (30A6003TUS)**
|
||||
|
||||
The folder you select and all sub-folders will be checked for drivers, expanding any .cab files that are present and searching for drivers.
|
||||
2. Right-click the **30A6003TUS** folder and select **Import Drivers** and use the following Driver source directory to import drivers:
|
||||
|
||||
**D:\\Drivers\\Windows 10 x64\\Lenovo\\ThinkStation P500 (30A6003TUS)**
|
||||
|
||||
The folder you select and all sub-folders will be checked for drivers, expanding any .cab files that are present and searching for drivers.
|
||||
|
||||
### For the Latitude E7450
|
||||
|
||||
@ -289,7 +309,10 @@ In these steps, we assume you have downloaded and extracted the CAB file for the
|
||||
On **MDT01**:
|
||||
|
||||
1. In the **Deployment Workbench**, in the **MDT Production** > **Out-Of-Box Drivers** > **Windows 10 x64** node, expand the **Dell Inc** node.
|
||||
2. Right-click the **Latitude E7450** folder and select **Import Drivers** and use the following Driver source directory to import drivers: **D:\\Drivers\\Windows 10 x64\\Dell Inc\\Latitude E7450**
|
||||
|
||||
2. Right-click the **Latitude E7450** folder and select **Import Drivers** and use the following Driver source directory to import drivers:
|
||||
|
||||
**D:\\Drivers\\Windows 10 x64\\Dell Inc\\Latitude E7450**
|
||||
|
||||
### For the HP EliteBook 8560w
|
||||
|
||||
@ -300,7 +323,10 @@ In these steps, we assume you have downloaded and extracted the drivers for the
|
||||
On **MDT01**:
|
||||
|
||||
1. In the **Deployment Workbench**, in the **MDT Production** > **Out-Of-Box Drivers** > **Windows 10 x64** node, expand the **Hewlett-Packard** node.
|
||||
2. Right-click the **HP EliteBook 8560w** folder and select **Import Drivers** and use the following Driver source directory to import drivers: **D:\\Drivers\\Windows 10 x64\\Hewlett-Packard\\HP EliteBook 8560w**
|
||||
|
||||
2. Right-click the **HP EliteBook 8560w** folder and select **Import Drivers** and use the following Driver source directory to import drivers:
|
||||
|
||||
**D:\\Drivers\\Windows 10 x64\\Hewlett-Packard\\HP EliteBook 8560w**
|
||||
|
||||
### For the Microsoft Surface Laptop
|
||||
|
||||
@ -309,7 +335,10 @@ For the Microsoft Surface Laptop model, you find the drivers on the Microsoft we
|
||||
On **MDT01**:
|
||||
|
||||
1. In the Deployment Workbench, in the **MDT Production** > **Out-Of-Box Drivers** > **Windows 10 x64** node, expand the **Microsoft** node.
|
||||
2. Right-click the **Surface Laptop** folder and select **Import Drivers**; and use the following Driver source directory to import drivers: **D:\\Drivers\\Windows 10 x64\\Microsoft\\Surface Laptop**
|
||||
|
||||
2. Right-click the **Surface Laptop** folder and select **Import Drivers**; and use the following Driver source directory to import drivers:
|
||||
|
||||
**D:\\Drivers\\Windows 10 x64\\Microsoft\\Surface Laptop**
|
||||
|
||||
## Step 6: Create the deployment task sequence
|
||||
|
||||
@ -320,40 +349,46 @@ This section will show you how to create the task sequence used to deploy your p
|
||||
On **MDT01**:
|
||||
|
||||
1. In the Deployment Workbench, under the **MDT Production** node, right-click **Task Sequences**, and create a folder named **Windows 10**.
|
||||
|
||||
2. Right-click the new **Windows 10** folder and select **New Task Sequence**. Use the following settings for the New Task Sequence Wizard:
|
||||
1. Task sequence ID: W10-X64-001
|
||||
2. Task sequence name: Windows 10 Enterprise x64 RTM Custom Image
|
||||
3. Task sequence comments: Production Image
|
||||
4. Template: Standard Client Task Sequence
|
||||
5. Select OS: Windows 10 Enterprise x64 RTM Custom 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 page: https://www.contoso.com
|
||||
10. Admin Password: Do not specify an Administrator Password at this time
|
||||
- Task sequence ID: W10-X64-001
|
||||
- Task sequence name: Windows 10 Enterprise x64 RTM Custom Image
|
||||
- Task sequence comments: Production Image
|
||||
- Template: Standard Client Task Sequence
|
||||
- Select OS: Windows 10 Enterprise x64 RTM Custom Image
|
||||
- Specify Product Key: Do not specify a product key at this time
|
||||
- Full Name: Contoso
|
||||
- Organization: Contoso
|
||||
- Internet Explorer home page: https://www.contoso.com
|
||||
- Admin Password: Do not specify an Administrator Password at this time
|
||||
|
||||
### Edit the Windows 10 task sequence
|
||||
|
||||
1. Continuing from the previous procedure, right-click the **Windows 10 Enterprise x64 RTM Custom Image** task sequence, and select **Properties**.
|
||||
2. On the **Task Sequence** tab, configure the **Windows 10 Enterprise x64 RTM Custom Image** task sequence with the following settings:
|
||||
1. Preinstall: After the **Enable BitLocker (Offline)** action, add a **Set Task Sequence Variable** action with the following settings:
|
||||
1. Name: Set DriverGroup001
|
||||
2. Task Sequence Variable: DriverGroup001
|
||||
3. Value: Windows 10 x64\\%Make%\\%Model%
|
||||
2. Configure the **Inject Drivers** action with the following settings:
|
||||
1. Choose a selection profile: Nothing
|
||||
2. Install all drivers from the selection profile
|
||||
|
||||
>[!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.
|
||||
2. On the **Task Sequence** tab, configure the **Windows 10 Enterprise x64 RTM Custom Image** task sequence with the following settings:
|
||||
|
||||
1. Preinstall: After the **Enable BitLocker (Offline)** action, add a **Set Task Sequence Variable** action with the following settings:
|
||||
- Name: Set DriverGroup001
|
||||
- Task Sequence Variable: DriverGroup001
|
||||
- Value: Windows 10 x64\\%Make%\\%Model%
|
||||
|
||||
2. Configure the **Inject Drivers** action with the following settings:
|
||||
- Choose a selection profile: Nothing
|
||||
- Install all drivers from the selection profile
|
||||
|
||||
> [!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.
|
||||
|
||||
3. State Restore. Enable the **Windows Update (Pre-Application Installation)** action.
|
||||
|
||||
4. State Restore. Enable the **Windows Update (Post-Application Installation)** action.
|
||||
|
||||
3. Click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
The task sequence for production deployment.
|
||||
The task sequence for production deployment.
|
||||
|
||||
## Step 7: Configure the MDT production deployment share
|
||||
|
||||
@ -369,95 +404,104 @@ On **MDT01**:
|
||||
1. Right-click the **MDT Production** deployment share and select **Properties**.
|
||||
2. Select the **Rules** tab and replace the existing rules with the following information (modify the domain name, WSUS server, and administrative credentials to match your environment):
|
||||
|
||||
```
|
||||
[Settings]
|
||||
Priority=Default
|
||||
|
||||
[Default]
|
||||
_SMSTSORGNAME=Contoso
|
||||
OSInstall=YES
|
||||
UserDataLocation=AUTO
|
||||
TimeZoneName=Pacific Standard Time
|
||||
AdminPassword=pass@word1
|
||||
JoinDomain=contoso.com
|
||||
DomainAdmin=CONTOSO\MDT_JD
|
||||
DomainAdminPassword=pass@word1
|
||||
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]
|
||||
_SMSTSORGNAME=Contoso
|
||||
OSInstall=YES
|
||||
UserDataLocation=AUTO
|
||||
TimeZoneName=Pacific Standard Time
|
||||
AdminPassword=pass@word1
|
||||
JoinDomain=contoso.com
|
||||
DomainAdmin=CONTOSO\MDT_JD
|
||||
DomainAdminPassword=pass@word1
|
||||
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
|
||||
```
|
||||
|
||||
3. Click **Edit Bootstrap.ini** and modify using the following information:
|
||||
|
||||
```
|
||||
[Settings]
|
||||
Priority=Default
|
||||
```
|
||||
[Settings]
|
||||
Priority=Default
|
||||
|
||||
[Default]
|
||||
DeployRoot=\\MDT01\MDTProduction$
|
||||
UserDomain=CONTOSO
|
||||
UserID=MDT_BA
|
||||
UserPassword=pass@word1
|
||||
SkipBDDWelcome=YES
|
||||
```
|
||||
[Default]
|
||||
DeployRoot=\\MDT01\MDTProduction$
|
||||
UserDomain=CONTOSO
|
||||
UserID=MDT_BA
|
||||
UserPassword=pass@word1
|
||||
SkipBDDWelcome=YES
|
||||
```
|
||||
|
||||
4. On the **Windows PE** tab, in the **Platform** drop-down list, make sure **x86** is selected.
|
||||
|
||||
5. On the **General** sub tab (still under the main Windows PE tab), configure the following settings:
|
||||
- In the **Lite Touch Boot Image Settings** area:
|
||||
1. Image description: MDT Production x86
|
||||
2. ISO file name: MDT Production x86.iso
|
||||
|
||||
In the **Lite Touch Boot Image Settings** area:
|
||||
|
||||
- Image description: MDT Production x86
|
||||
- ISO file name: MDT Production x86.iso
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
>Because you are going to use Pre-Boot Execution Environment (PXE) later to deploy the machines, you do not need the ISO file; however, we recommend creating ISO files because they are useful when troubleshooting deployments and for quick tests.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Because you are going to use Pre-Boot Execution Environment (PXE) later to deploy the machines, you do not need the ISO file; however, we recommend creating ISO files because they are useful when troubleshooting deployments and for quick tests.
|
||||
|
||||
6. On the **Drivers and Patches** sub tab, select the **WinPE x86** selection profile and select the **Include all drivers from the selection profile** option.
|
||||
|
||||
7. On the **Windows PE** tab, in the **Platform** drop-down list, select **x64**.
|
||||
|
||||
8. On the **General** sub tab, configure the following settings:
|
||||
- In the **Lite Touch Boot Image Settings** area:
|
||||
1. Image description: MDT Production x64
|
||||
2. ISO file name: MDT Production x64.iso
|
||||
|
||||
In the **Lite Touch Boot Image Settings** area:
|
||||
|
||||
- Image description: MDT Production x64
|
||||
- ISO file name: MDT Production x64.iso
|
||||
|
||||
9. In the **Drivers and Patches** sub tab, select the **WinPE x64** selection profile and select the **Include all drivers from the selection profile** option.
|
||||
|
||||
10. In the **Monitoring** tab, select the **Enable monitoring for this deployment share** check box.
|
||||
|
||||
11. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>It will take a while for the Deployment Workbench to create the monitoring database and web service.
|
||||
>[!NOTE]
|
||||
>It will take a while for the Deployment Workbench to create the monitoring database and web service.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The Windows PE tab for the x64 boot image.
|
||||
The Windows PE tab for the x64 boot image.
|
||||
|
||||
### The rules explained
|
||||
|
||||
The rules for the MDT Production deployment share are somewhat different from those for the MDT Build Lab deployment share. The biggest differences are that you deploy the machines into a domain instead of a workgroup.
|
||||
|
||||
>
|
||||
>You can optionally remove the **UserID** and **UserPassword** entries from Bootstrap.ini so that users performing PXE boot are prompted to provide credentials with permission to connect to the deployment share. Setting **SkipBDDWelcome=NO** enables the welcome screen that displays options to run the deployment wizard, run DaRT tools (if installed), exit to a Windows PE command prompt, set the keyboard layout, or configure a static IP address. In this example we are skipping the welcome screen and providing credentials.
|
||||
You can optionally remove the **UserID** and **UserPassword** entries from Bootstrap.ini so that users performing PXE boot are prompted to provide credentials with permission to connect to the deployment share. Setting **SkipBDDWelcome=NO** enables the welcome screen that displays options to run the deployment wizard, run DaRT tools (if installed), exit to a Windows PE command prompt, set the keyboard layout, or configure a static IP address. In this example we are skipping the welcome screen and providing credentials.
|
||||
|
||||
### The Bootstrap.ini file
|
||||
|
||||
This is the MDT Production Bootstrap.ini:
|
||||
|
||||
```
|
||||
[Settings]
|
||||
Priority=Default
|
||||
@ -473,6 +517,7 @@ SkipBDDWelcome=YES
|
||||
### The CustomSettings.ini file
|
||||
|
||||
This is the CustomSettings.ini file with the new join domain information:
|
||||
|
||||
```
|
||||
[Settings]
|
||||
Priority=Default
|
||||
@ -529,32 +574,44 @@ If your organization has a Microsoft Software Assurance agreement, you also can
|
||||
|
||||
If you have licensing for MDOP and DaRT, you can add DaRT to the boot images using the steps in this section. If you do not have DaRT licensing, or don't want to use it, simply skip to the next section, [Update the Deployment Share](#update-the-deployment-share). To enable the remote connection feature in MDT, you need to do the following:
|
||||
|
||||
>DaRT 10 is part of [MDOP 2015](https://docs.microsoft.com/microsoft-desktop-optimization-pack/#how-to-get-mdop). Note: MDOP might be available as a download from your [Visual Studio subscription](https://my.visualstudio.com/Downloads). When searching, be sure to look for **Desktop Optimization Pack**.
|
||||
|
||||
> [!NOTE]
|
||||
> DaRT 10 is part of [MDOP 2015](https://docs.microsoft.com/microsoft-desktop-optimization-pack/#how-to-get-mdop).
|
||||
>
|
||||
> MDOP might be available as a download from your [Visual Studio subscription](https://my.visualstudio.com/Downloads). When searching, be sure to look for **Desktop Optimization Pack**.
|
||||
|
||||
On **MDT01**:
|
||||
|
||||
1. Download MDOP 2015 and copy the DaRT 10 installer file to the D:\\Setup\\DaRT 10 folder on MDT01 (DaRT\\DaRT 10\\Installers\\\<lang\>\\x64\\MSDaRT100.msi).
|
||||
|
||||
2. Install DaRT 10 (MSDaRT10.msi) using the default settings.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Copy the two tools CAB files from **C:\\Program Files\\Microsoft DaRT\\v10** (**Toolsx86.cab** and **Toolsx64.cab**) to the production deployment share at **D:\\MDTProduction\\Tools\\x86** and **D:\\MDTProduction\\Tools\\x64**, respectively.
|
||||
|
||||
3. In the Deployment Workbench, right-click the **MDT Production** deployment share and select **Properties**.
|
||||
|
||||
4. On the **Windows PE** tab, in the **Platform** drop-down list, make sure **x86** is selected.
|
||||
|
||||
5. On the **Features** sub tab, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** checkbox.
|
||||
|
||||
|
||||
|
||||
|
||||
Selecting the DaRT 10 feature in the deployment share.
|
||||
Selecting the DaRT 10 feature in the deployment share.
|
||||
|
||||
8. In the **Windows PE** tab, in the **Platform** drop-down list, select **x64**.
|
||||
|
||||
9. In the **Features** sub tab, in addition to the default selected feature pack, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** check box.
|
||||
|
||||
10. Click **OK**.
|
||||
|
||||
### Update the deployment share
|
||||
|
||||
Like the MDT Build Lab deployment share, the MDT Production deployment share needs to be updated after it has been configured. This is the process during which the Windows PE boot images are created.
|
||||
|
||||
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]
|
||||
@ -571,12 +628,14 @@ You need to add the MDT Production Lite Touch x64 Boot image to WDS in preparati
|
||||
On **MDT01**:
|
||||
|
||||
1. Open the Windows Deployment Services console, expand the **Servers** node and then expand **MDT01.contoso.com**.
|
||||
|
||||
2. Right-click **Boot Images** and select **Add Boot Image**.
|
||||
|
||||
3. Browse to the **D:\\MDTProduction\\Boot\\LiteTouchPE\_x64.wim** file and add the image with the default settings.
|
||||
|
||||
|
||||
|
||||
|
||||
The boot image added to the WDS console.
|
||||
The boot image added to the WDS console.
|
||||
|
||||
### Deploy the Windows 10 client
|
||||
|
||||
@ -585,13 +644,15 @@ At this point, you should have a solution ready for deploying the Windows 10 cl
|
||||
On **HV01**:
|
||||
|
||||
1. Create a virtual machine with the following settings:
|
||||
1. Name: PC0005
|
||||
2. Store the virtual machine in a different location: C:\VM
|
||||
3. Generation: 2
|
||||
4. Memory: 2048 MB
|
||||
5. Network: Must be able to connect to \\MDT01\MDTProduction$
|
||||
6. Hard disk: 60 GB (dynamic disk)
|
||||
7. Installation Options: Install an operating system from a network-based installation server
|
||||
|
||||
- Name: PC0005
|
||||
- Store the virtual machine in a different location: C:\VM
|
||||
- Generation: 2
|
||||
- Memory: 2048 MB
|
||||
- Network: Must be able to connect to \\MDT01\MDTProduction$
|
||||
- Hard disk: 60 GB (dynamic disk)
|
||||
- Installation Options: Install an operating system from a network-based installation server
|
||||
|
||||
2. Start the PC0005 virtual machine, and press **Enter** to start the PXE boot. The VM will now load the Windows PE boot image from the WDS server.
|
||||
|
||||
|
||||
@ -599,15 +660,18 @@ On **HV01**:
|
||||
The initial PXE boot process of PC0005.
|
||||
|
||||
3. After Windows PE has booted, complete the Windows Deployment Wizard using the following setting:
|
||||
1. Select a task sequence to execute on this computer: Windows 10 Enterprise x64 RTM Custom Image
|
||||
2. Computer Name: **PC0005**
|
||||
3. Applications: Select the **Install - Adobe Reader** checkbox.
|
||||
4. Setup now begins and does the following:
|
||||
1. Installs the Windows 10 Enterprise operating system.
|
||||
2. Installs the added application.
|
||||
3. Updates the operating system via your local Windows Server Update Services (WSUS) server.
|
||||
|
||||
|
||||
- Select a task sequence to execute on this computer: Windows 10 Enterprise x64 RTM Custom Image
|
||||
- Computer Name: **PC0005**
|
||||
- Applications: Select the **Install - Adobe Reader** checkbox.
|
||||
|
||||
4. Setup now begins and does the following:
|
||||
|
||||
- Installs the Windows 10 Enterprise operating system.
|
||||
- Installs the added application.
|
||||
- Updates the operating system via your local Windows Server Update Services (WSUS) server.
|
||||
|
||||
|
||||
|
||||
### Application installation
|
||||
|
||||
@ -622,12 +686,14 @@ Since you have enabled the monitoring on the MDT Production deployment share, yo
|
||||
On **MDT01**:
|
||||
|
||||
1. In the 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.
|
||||
|
||||
|
||||
|
||||
|
||||
The Monitoring node, showing the deployment progress of PC0005.
|
||||
The Monitoring node, showing the deployment progress of PC0005.
|
||||
|
||||
### Use information in the Event Viewer
|
||||
|
||||
@ -657,9 +723,9 @@ On **MDT01**:
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
The newly created multicast namespace.
|
||||
The newly created multicast namespace.
|
||||
|
||||
## Use offline media to deploy Windows 10
|
||||
|
||||
@ -674,15 +740,18 @@ To filter what is being added to the media, you create a selection profile. When
|
||||
On **MDT01**:
|
||||
|
||||
1. In the Deployment Workbench, under the **MDT Production / Advanced Configuration** node, right-click **Selection Profiles**, and select **New Selection Profile**.
|
||||
|
||||
2. Use the following settings for the New Selection Profile Wizard:
|
||||
1. General Settings
|
||||
- Selection profile name: Windows 10 Offline Media
|
||||
2. Folders
|
||||
1. Applications / Adobe
|
||||
2. Operating Systems / Windows 10
|
||||
3. Out-Of-Box Drivers / WinPE x64
|
||||
4. Out-Of-Box Drivers / Windows 10 x64
|
||||
5. Task Sequences / Windows 10
|
||||
|
||||
- General Settings
|
||||
- Selection profile name: Windows 10 Offline Media
|
||||
|
||||
- Folders
|
||||
- Applications / Adobe
|
||||
- Operating Systems / Windows 10
|
||||
- Out-Of-Box Drivers / WinPE x64
|
||||
- Out-Of-Box Drivers / Windows 10 x64
|
||||
- Task Sequences / Windows 10
|
||||
|
||||
|
||||
|
||||
@ -696,10 +765,11 @@ In these steps, you generate offline media from the MDT Production deployment sh
|
||||
>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. In the Deployment Workbench, under 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:
|
||||
- General Settings
|
||||
1. Media path: **D:\\MDTOfflineMedia**
|
||||
2. Selection profile: **Windows 10 Offline Media**
|
||||
- Media path: **D:\\MDTOfflineMedia**
|
||||
- Selection profile: **Windows 10 Offline Media**
|
||||
|
||||
### Configure the offline media
|
||||
|
||||
@ -708,16 +778,22 @@ Offline media has its own rules, its own Bootstrap.ini and CustomSettings.ini fi
|
||||
On **MDT01**:
|
||||
|
||||
1. Copy the CustomSettings.ini file from the **D:\MDTProduction\Control** folder to **D:\\MDTOfflineMedia\\Content\\Deploy\\Control**. Overwrite the existing files.
|
||||
|
||||
2. In the Deployment Workbench, under the **MDT Production / Advanced Configuration / Media** node, right-click the **MEDIA001** media, and select **Properties**.
|
||||
|
||||
3. In the **General** tab, configure the following:
|
||||
1. Clear the Generate x86 boot image check box.
|
||||
2. ISO file name: Windows 10 Offline Media.iso
|
||||
- Clear the Generate x86 boot image check box.
|
||||
- ISO file name: Windows 10 Offline Media.iso
|
||||
|
||||
4. On the **Windows PE** tab, in the **Platform** drop-down list, select **x64**.
|
||||
|
||||
5. On the **General** sub tab, configure the following settings:
|
||||
1. In the **Lite Touch Boot Image Settings** area:
|
||||
- Image description: MDT Production x64
|
||||
2. In the **Windows PE Customizations** area, set the Scratch space size to 128.
|
||||
- In the **Lite Touch Boot Image Settings** area:
|
||||
- Image description: MDT Production x64
|
||||
- In the **Windows PE Customizations** area, set the Scratch space size to 128.
|
||||
|
||||
6. On 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**.
|
||||
|
||||
### Generate the offline media
|
||||
@ -727,6 +803,7 @@ You have now configured the offline media deployment share, however the share ha
|
||||
On **MDT01**:
|
||||
|
||||
1. In the 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 **D:\\MDTOfflineMedia\\Content** folder. The process might require several minutes.
|
||||
|
||||
### Create a bootable USB stick
|
||||
@ -734,15 +811,20 @@ On **MDT01**:
|
||||
The ISO that you got when updating the offline media item can be burned to a DVD and used directly (it will be bootable), but it is often more efficient to use USB sticks instead since they are faster and can hold more data. (A dual-layer DVD is limited to 8.5 GB.)
|
||||
|
||||
>[!TIP]
|
||||
>In this example, the .wim file is 5.5 GB in size. However, bootable USB sticks are formatted with the FAT32 file system which limits file size to 4.0 GB. You can place the image on a different drive (ex: E:\Deploy\Operating Systems\W10EX64RTM\REFW10X64-001.swm) and then modify E:\Deploy\Control\OperatingSystems.xml to point to it. Alternatively to keep using the USB you must split the .wim file, which can be done using DISM: <br> <br>Dism /Split-Image /ImageFile:D:\MDTOfflinemedia\Content\Deploy\Operating Systems\W10EX64RTM\REFW10X64-001.wim /SWMFile:E:\sources\install.swm /FileSize:3800. <br> <br>Windows Setup automatically installs from this file, provided you name it install.swm. The file names for the next files include numbers, for example: install2.swm, install3.swm. <br> <br>To enable split image in MDT, the Settings.xml file in your deployment share (ex: D:\MDTProduction\Control\Settings.xml) must have the **SkipWimSplit** value set to **False**. By default this value is set to True (\<SkipWimSplit\>True\</SkipWimSplit\>), so this must be changed and the offline media content updated.
|
||||
>In this example, the .wim file is 5.5 GB in size. However, bootable USB sticks are formatted with the FAT32 file system which limits file size to 4.0 GB. You can place the image on a different drive (ex: E:\Deploy\Operating Systems\W10EX64RTM\REFW10X64-001.swm) and then modify E:\Deploy\Control\OperatingSystems.xml to point to it. Alternatively to keep using the USB you must split the .wim file, which can be done using DISM: <br> <br>Dism /Split-Image /ImageFile:D:\MDTOfflinemedia\Content\Deploy\Operating Systems\W10EX64RTM\REFW10X64-001.wim /SWMFile:E:\sources\install.swm /FileSize:3800. <br> <br>Windows Setup automatically installs from this file, provided you name it install.swm. The file names for the next files include numbers, for example: install2.swm, install3.swm. <br> <br>To enable split image in MDT, the Settings.xml file in your deployment share (ex: D:\MDTProduction\Control\Settings.xml) must have the **SkipWimSplit** value set to **False**. By default this value is set to True (`<SkipWimSplit>True</SkipWimSplit>`), so this must be changed and the offline media content updated.
|
||||
|
||||
Follow these steps to create a bootable USB stick from the offline media content:
|
||||
|
||||
1. On a physical machine running Windows 7 or later, insert the USB stick you want to use.
|
||||
|
||||
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**.
|
||||
|
||||
## Unified Extensible Firmware Interface (UEFI)-based deployments
|
||||
|
||||
Reference in New Issue
Block a user