mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Add periods to alt text
No other changes
This commit is contained in:
Gary Moore
@ -28,7 +28,7 @@ This topic will show you how to add applications to a role in the MDT database a
|
||||
2. Applications / Lite Touch Applications:
|
||||
3. Install - Adobe Reader XI - x86
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 12. The Standard PC role with the application added
|
||||
|
||||
@ -39,7 +39,7 @@ After creating the role, you can associate it with one or more computer entries.
|
||||
2. In the **Computers** node, double-click the **PC00075** entry, and add the following setting:
|
||||
- Roles: Standard PC
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 13. The Standard PC role added to PC00075 (having ID 1 in the database).
|
||||
|
||||
@ -120,7 +120,7 @@ When the database is populated, you can use the MDT simulation environment to si
|
||||
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 14. ZTIGather.log displaying the application GUID belonging to the Adobe Reader XI application that would have been installed if you deployed this machine.
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ Four computers are used in this topic: DC01, MDT01, MDT02, and PC0006. DC01 is a
|
||||
|
||||
For the purposes of this article, we assume that MDT02 is prepared with the same network and storage capabilities that were specified for MDT01, except that MDT02 is located on a different subnet than MDT01. For more details on the infrastructure setup for this topic, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
|
||||
|
||||
|
||||
Computers used in this topic.
|
||||
|
||||
@ -149,7 +149,7 @@ On **MDT01**:
|
||||
4. After the update is complete, use the Windows Deployment Services console on MDT01. In the **Boot Images** node, right-click the **MDT Production x64** boot image and select **Replace Image**.
|
||||
5. Browse and select the **D:\\MDTProduction\\Boot\\LiteTouchPE\_x64.wim** boot image, and then complete Replace Boot Image Wizard using the default settings.
|
||||
|
||||
|
||||
|
||||
|
||||
Replacing the updated boot image in WDS.
|
||||
|
||||
@ -167,7 +167,7 @@ On **MDT01**:
|
||||
8. On the **Name and Domain** page, assign the **MDTProduction** name, and click **Next**.
|
||||
9. On the **Replication Group Members** page, click **Add**, add **MDT01** and **MDT02**, and then click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
Adding the Replication Group Members.
|
||||
|
||||
@ -223,7 +223,7 @@ On **MDT02**:
|
||||
7. On the **Review Settings and Create Report** page, click **Create**.
|
||||
8. Open the report in Internet Explorer, and if necessary, select the **Allow blocked content** option.
|
||||
|
||||
|
||||
|
||||
|
||||
The DFS Replication Health Report.
|
||||
|
||||
@ -258,7 +258,7 @@ Now you should have a solution ready for deploying the Windows 10 client to the
|
||||
2. Install applications.
|
||||
3. Update the operating system using your local Windows Server Update Services (WSUS) server.
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ ms.topic: article
|
||||
One of the most powerful features in Microsoft Deployment Toolkit (MDT) is its extension capabilities; there is virtually no limitation to what you can do in terms of customization. In this topic, you learn about configuring customizations for your environment.
|
||||
For the purposes of this topic, we will use four machines: DC01, MDT01, HV01, and PC0001. DC01 is a domain controller, MDT01 is a Windows Server 2012 R2 Standard server, and PC0001 is a Windows 10 Enterprise x64 client used for the MDT simulation environment. OR01 has Microsoft System Center 2012 R2 Orchestrator installed. MDT01, OR01, and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](./prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
|
||||
|
||||
|
||||
The computers used in this topic.
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ For the purposes of this topic, we will use three computers: DC01, MDT01, and HV
|
||||
- MDT01 is a contoso.com domain member server.
|
||||
- HV01 is a Hyper-V server that will be used to build the reference image.
|
||||
|
||||
|
||||
|
||||
|
||||
Computers used in this topic.
|
||||
|
||||
@ -62,7 +62,7 @@ On **MDT01**:
|
||||
- Review the Summary page, click **Next**, wait for the deployment share to be created, then click **Finish**.
|
||||
- Verify that you can access the <b>\\\\MDT01\\MDTBuildLab$</b> share.
|
||||
|
||||
|
||||
|
||||
|
||||
The Deployment Workbench with the MDT Build Lab deployment share.
|
||||
|
||||
@ -101,7 +101,7 @@ On **MDT01**:
|
||||
|
||||
1. Sign in as **contoso\\administrator** 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 you can also choose to import the OS directly from an ISO or DVD.
|
||||
|
||||
|
||||
|
||||
|
||||
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**.
|
||||
@ -111,7 +111,7 @@ On **MDT01**:
|
||||
- Destination directory name: <b>W10EX64RTM</b>
|
||||
5. After adding the operating system, in the **Operating Systems / Windows 10** folder, double-click it and change the name to: **Windows 10 Enterprise x64 RTM Default Image**. See the following example.
|
||||
|
||||
|
||||
|
||||
|
||||
>Depending on the DVD you used, there might be multiple editions available. For the purposes of this guide, we are using the Windows 10 Enterprise image, but other images will also work.
|
||||
|
||||
@ -188,7 +188,7 @@ Download all three items in this list to the D:\\Downloads folder on MDT01.
|
||||
|
||||
3. Ensure the configuration.xml file is in the D:\\Downloads\\Office365 folder. See the following example of the extracted files plus the configuration.xml file in the Downloads\\Office365 folder:
|
||||
|
||||
|
||||
|
||||
|
||||
Assuming you have named the file "configuration.xml" as shown above, we will use the command "**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. Do not perform this step yet.
|
||||
|
||||
@ -346,7 +346,7 @@ On **MDT01**:
|
||||
>[!IMPORTANT]
|
||||
>This is probably the most important step when creating a reference image. Many applications need the .NET Framework, and we strongly recommend having it available in the image. The one thing that makes this different from other components is that .NET Framework 3.5.1 is not included in the WIM file. It is installed from the **Sources\\SxS** folder on the media, and that makes it more difficult to add after the image has been deployed.
|
||||
|
||||
|
||||
|
||||
|
||||
The task sequence after creating the Custom Tasks (Pre-Windows Update) group and adding the Install - Microsoft NET Framework 3.5.1 action.
|
||||
|
||||
@ -356,18 +356,18 @@ On **MDT01**:
|
||||
7. Repeat these steps (add a new **Install Application**) to add Microsoft Visual C++ Redistributable 2019 - x64 and Microsoft 365 Apps for enterprise as well.
|
||||
3. Click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Optional configuration: Add a suspend action
|
||||
|
||||
The goal when creating a reference image is of course to automate everything. But sometimes you have a special configuration or application setup that is too time-consuming to automate. If you need to do some manual configuration, you can add a little-known feature called Lite Touch Installation (LTI) Suspend. If you add the LTISuspend.wsf script as a custom action in the task sequence, it will suspend the task sequence until you click the Resume Task Sequence shortcut icon on the desktop. In addition to using the LTI Suspend feature for manual configuration or installation, you can also use it simply for verifying a reference image before you allow the task sequence to continue and use Sysprep and capture the virtual machine.
|
||||
|
||||
|
||||
|
||||
|
||||
A task sequence with optional Suspend action (LTISuspend.wsf) added.
|
||||
|
||||
|
||||
|
||||
|
||||
The Windows 10 desktop with the Resume Task Sequence shortcut.
|
||||
|
||||
@ -402,7 +402,7 @@ On **MDT01**:
|
||||
- Note: If errors are reported that certain display values are incorrect, you can ignore this or browse to **7oobeSystem\\amd64_Microsoft-Windows-Shell-Setup__neutral\\Display** and enter the following: ColorDepth 32, HorizontalResolution 1, RefreshRate 60, VerticalResolution 1.
|
||||
6. On the Windows 10 Enterprise x64 RTM Default Image Properties, click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
Windows System Image Manager with the Windows 10 Unattend.xml.
|
||||
|
||||
@ -455,7 +455,7 @@ On **MDT01**:
|
||||
SkipFinalSummary=YES
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
The server-side rules for the MDT Build Lab deployment share.
|
||||
|
||||
@ -642,7 +642,7 @@ On **HV01**:
|
||||
- Location: \\\\MDT01\\MDTBuildLab$\\Captures
|
||||
3. File name: REFW10X64-001.wim
|
||||
|
||||
|
||||
|
||||
|
||||
The Windows Deployment Wizard for the Windows 10 reference image.
|
||||
|
||||
@ -657,7 +657,7 @@ On **HV01**:
|
||||
|
||||
After some time, you 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.
|
||||
|
||||
|
||||
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
@ -666,7 +666,7 @@ After some time, you will have a Windows 10 Enterprise x64 image that is fully
|
||||
|
||||
If you [enabled monitoring](#enable-monitoring), you can check the progress of the task sequence.
|
||||
|
||||
|
||||
|
||||
|
||||
If there are problems with your task sequence, you can troubleshoot in Windows PE by pressing F8 to open a command prompt. There are several [MDT log files](/configmgr/mdt/troubleshooting-reference#mdt-logs) created that can be helpful determining the origin of an error, such as BDD.log. From the command line in Windows PE you can copy these logs from the client to your MDT server for viewing with CMTrace. For example: copy BDD.log \\\\mdt01\\logs$.
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ For the purposes of this topic, we will use four computers: DC01, MDT01, HV01 an
|
||||
|
||||
MDT01 and PC0005 are members of the domain contoso.com for the fictitious Contoso Corporation. HV01 used to test deployment of PC0005 in a virtual environment.
|
||||
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>For details about the setup for the procedures in this article, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
@ -135,7 +135,7 @@ In these steps, we assume that you have completed the steps in the [Create a Win
|
||||
>The reason for adding the setup files has changed since earlier versions of MDT. MDT 2010 used the setup files to install Windows. MDT uses DISM to apply the image; however, you still need the setup files because some components in roles and features are stored outside the main image.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Step 4: Add an application
|
||||
|
||||
@ -162,7 +162,7 @@ On **MDT01**:
|
||||
|
||||
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.
|
||||
|
||||
@ -238,7 +238,7 @@ 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](/archive/blogs/deploymentguys/using-and-extending-model-aliases-for-hardware-specific-application-installation).
|
||||
|
||||
|
||||
|
||||
|
||||
The Out-of-Box Drivers structure in the Deployment Workbench.
|
||||
|
||||
@ -260,7 +260,7 @@ 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.
|
||||
|
||||
@ -284,7 +284,7 @@ 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).
|
||||
|
||||
@ -386,7 +386,7 @@ On **MDT01**:
|
||||
|
||||
3. Click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
The task sequence for production deployment.
|
||||
|
||||
@ -488,7 +488,7 @@ On **MDT01**:
|
||||
>[!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.
|
||||
|
||||
@ -586,7 +586,7 @@ On **MDT01**:
|
||||
|
||||
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.
|
||||
|
||||
@ -596,7 +596,7 @@ On **MDT01**:
|
||||
|
||||
5. On the **Features** sub tab, select the **Microsoft Diagnostics and Recovery Toolkit (DaRT)** checkbox.
|
||||
|
||||
|
||||
|
||||
|
||||
Selecting the DaRT 10 feature in the deployment share.
|
||||
|
||||
@ -633,7 +633,7 @@ On **MDT01**:
|
||||
|
||||
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.
|
||||
|
||||
@ -655,7 +655,7 @@ On **HV01**:
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
The initial PXE boot process of PC0005.
|
||||
|
||||
@ -671,13 +671,13 @@ On **HV01**:
|
||||
- Installs the added application.
|
||||
- Updates the operating system via your local Windows Server Update Services (WSUS) server.
|
||||
|
||||
|
||||
|
||||
|
||||
### Application installation
|
||||
|
||||
Following OS installation, Microsoft Office 365 Pro Plus - x64 is installed automatically.
|
||||
|
||||
|
||||
|
||||
|
||||
### Use the MDT monitoring feature
|
||||
|
||||
@ -691,7 +691,7 @@ On **MDT01**:
|
||||
|
||||
3. Double-click PC0005, and review the information.
|
||||
|
||||
|
||||
|
||||
|
||||
The Monitoring node, showing the deployment progress of PC0005.
|
||||
|
||||
@ -699,7 +699,7 @@ On **MDT01**:
|
||||
|
||||
When monitoring is enabled, MDT also writes information to the event viewer on MDT01. This information can be used to trigger notifications via scheduled tasks when deployment is completed. For example, you can configure scheduled tasks to send an email when a certain event is created in the event log.
|
||||
|
||||
|
||||
|
||||
|
||||
The Event Viewer showing a successful deployment of PC0005.
|
||||
|
||||
@ -723,7 +723,7 @@ 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.
|
||||
|
||||
@ -753,7 +753,7 @@ On **MDT01**:
|
||||
- Out-Of-Box Drivers / Windows 10 x64
|
||||
- Task Sequences / Windows 10
|
||||
|
||||
|
||||
|
||||
|
||||
### Create the offline media
|
||||
|
||||
@ -831,7 +831,7 @@ Follow these steps to create a bootable USB stick from the offline media content
|
||||
|
||||
As referenced in [Windows 10 deployment scenarios and tools](../windows-deployment-scenarios-and-tools.md), Unified Extensible Firmware Interface (UEFI)-based deployments are becoming more common. In fact, when you create a generation 2 virtual machine in Hyper-V, you get a UEFI-based computer. During deployment, MDT automatically detects that you have an UEFI-based machine and creates the partitions UEFI requires. You do not need to update or change your task sequences in any way to accommodate UEFI.
|
||||
|
||||
|
||||
|
||||
|
||||
The partitions when deploying an UEFI-based machine.
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ MDT has many useful features, such as:
|
||||
- **GPT support.** Supports deployment to machines that require the new GPT partition table format. This is related to UEFI.
|
||||
- **Enhanced Windows PowerShell support.** Provides support for running PowerShell scripts.
|
||||
|
||||
|
||||
|
||||
|
||||
The deployment share mounted as a standard PSDrive allows for administration using PowerShell.
|
||||
|
||||
@ -58,7 +58,7 @@ MDT has many useful features, such as:
|
||||
- **Offline BitLocker.** Provides the capability to have BitLocker enabled during the Windows Preinstallation Environment (Windows PE) phase, thus saving hours of encryption time.
|
||||
- **USMT offline user-state migration.** Provides support for running the User State Migration Tool (USMT) capture offline, during the Windows PE phase of the deployment.
|
||||
|
||||
|
||||
|
||||
|
||||
The offline USMT backup in action.
|
||||
|
||||
@ -76,7 +76,7 @@ Many features in MDT support Lite Touch Installation (LTI) for Windows 10. An L
|
||||
|
||||
When deploying the Windows operating system using MDT, most of the administration and configuration is done through the Deployment Workbench, but you also can perform many of the tasks using Windows PowerShell. The easiest way to find out how to use PowerShell in MDT is to use the Deployment Workbench to perform an operation and at the end of that task, click View Script. That will give you the PowerShell command.
|
||||
|
||||
|
||||
|
||||
|
||||
If you click **View Script** on the right side, you will get the PowerShell code that was used to perform the task.
|
||||
|
||||
@ -93,7 +93,7 @@ The rules (CustomSettings.ini and Bootstrap.ini) make up the brain of MDT. The r
|
||||
- Regional settings
|
||||
You can manage hundreds of settings in the rules. For more information, see the [Microsoft Deployment Toolkit resource center](/mem/configmgr/mdt/).
|
||||
|
||||
|
||||
|
||||
|
||||
Example of a MDT rule. In this example, the new computer name is being calculated based on PC- plus the first seven (Left) characters from the serial number
|
||||
|
||||
|
||||
@ -75,7 +75,7 @@ The following generic credentials are used in this guide. You should replace the
|
||||
|
||||
The following OU structure is used in this guide. Instructions are provided [below](#create-the-ou-structure) to help you create the required OUs.
|
||||
|
||||
|
||||
|
||||
|
||||
## Install the Windows ADK
|
||||
|
||||
@ -182,7 +182,7 @@ Set-Location $home\Setup\Scripts
|
||||
|
||||
This will create an OU structure as shown below.
|
||||
|
||||
|
||||
|
||||
|
||||
To use the Active Directory Users and Computers console (instead of PowerShell):
|
||||
|
||||
@ -233,18 +233,18 @@ On **MDT01**:
|
||||
|
||||
See the following example:
|
||||
|
||||
|
||||
|
||||
|
||||
## Use CMTrace to read log files (optional)
|
||||
|
||||
The log files in MDT Lite Touch are formatted to be read by Configuration Manager Trace ([CMTrace](/sccm/core/support/cmtrace)), which is available as part of the [Microsoft System 2012 R2 Center Configuration Manager Toolkit](https://go.microsoft.com/fwlink/p/?LinkId=734717). You should also download this tool.
|
||||
You can use Notepad (example below):
|
||||
|
||||
|
||||
|
||||
|
||||
Alternatively, CMTrace formatting makes the logs much easier to read. See the same log file below, opened in CMTrace:
|
||||
|
||||
|
||||
|
||||
|
||||
After installing the ConfigMgrTools.msi file, you can search for **cmtrace** and pin the tool to your taskbar for easy access.
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ For the purposes of this topic, we will use three computers: DC01, MDT01, and PC
|
||||
|
||||
Both DC01 and MDT01 are running Windows Server 2019; however any supported version of Windows Server can be used. For more details on the setup for this topic, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
|
||||
|
||||
|
||||
The computers used in this topic.
|
||||
|
||||
@ -93,7 +93,7 @@ It is also assumed that you have a domain member client computer named PC0001 in
|
||||
>Skip this optional full WIM backup that we are choosing not to perform. The USMT backup will still run.
|
||||
* Select one or more applications to install: Install - Adobe Reader
|
||||
|
||||
|
||||
|
||||
|
||||
4. Setup starts and does the following:
|
||||
|
||||
@ -105,7 +105,7 @@ It is also assumed that you have a domain member client computer named PC0001 in
|
||||
|
||||
5. You can monitor progress of the deployment using the deployment workbench on MDT01. See the following example:
|
||||
|
||||
|
||||
|
||||
|
||||
6. After the refresh process completes, sign in to the Windows 10 computer and verify that user accounts, data and settings were migrated.
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@ For the purposes of this topic, we will use four computers: DC01, MDT01, PC0002,
|
||||
|
||||
For more details on the setup for this topic, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
|
||||
|
||||
|
||||
|
||||
|
||||
The computers used in this topic.
|
||||
|
||||
@ -73,7 +73,7 @@ On **MDT01**:
|
||||
|
||||
4. In the **Other** folder, double-click **Backup Only Task Sequence**, and then in the **Task Sequence** tab, review the sequence. Notice that it only contains a subset of the normal client task sequence actions.
|
||||
|
||||
|
||||
|
||||
|
||||
The Backup Only Task Sequence action list.
|
||||
|
||||
@ -103,13 +103,13 @@ On **PC0002**:
|
||||
|
||||
The task sequence will now run USMT (Scanstate.exe) to capture user data and settings of the computer.
|
||||
|
||||
|
||||
|
||||
|
||||
The new task sequence running the Capture User State action on PC0002.
|
||||
|
||||
4. On **MDT01**, verify that you have an USMT.MIG compressed backup file in the **D:\\MigData\\PC0002\\USMT** folder.
|
||||
|
||||
|
||||
|
||||
|
||||
The USMT backup of PC0002.
|
||||
|
||||
@ -130,7 +130,7 @@ On **HV01**:
|
||||
|
||||
2. Start the PC0007 virtual machine, and press **Enter** to start the Pre-Boot Execution Environment (PXE) boot. The VM will now load the Windows PE boot image from MDT01 (or MDT02 if at a remote site).
|
||||
|
||||
|
||||
|
||||
|
||||
The initial PXE boot process of PC0007.
|
||||
|
||||
@ -153,7 +153,7 @@ On **HV01**:
|
||||
|
||||
You can view progress of the process by clicking the Monitoring node in the Deployment Workbrench on MDT01.
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -52,7 +52,7 @@ To enable BitLocker to store the recovery key and TPM information in Active Dire
|
||||
|
||||
In Windows Server version from 2008 R2 and later, you have access to the BitLocker Drive Encryption Administration Utilities features, which will help you manage BitLocker. When you install the features, the BitLocker Active Directory Recovery Password Viewer is included, and it extends Active Directory Users and Computers with BitLocker Recovery information.
|
||||
|
||||
|
||||
|
||||
|
||||
The BitLocker Recovery information on a computer object in the contoso.com domain.
|
||||
|
||||
@ -71,7 +71,7 @@ The BitLocker Drive Encryption Administration Utilities are added as features vi
|
||||
3. BitLocker Recovery Password Viewer
|
||||
7. On the **Confirm installation selections** page, click **Install**, and then click **Close**.
|
||||
|
||||
|
||||
|
||||
|
||||
Selecting the BitLocker Drive Encryption Administration Utilities.
|
||||
|
||||
@ -104,7 +104,7 @@ In addition to the Group Policy created previously, you need to configure permis
|
||||
cscript C:\Setup\Scripts\Add-TPMSelfWriteACE.vbs
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
Running the Add-TPMSelfWriteACE.vbs script on DC01.
|
||||
|
||||
|
||||
@ -46,7 +46,7 @@ On **PC0001**:
|
||||
8. In the **C:\\MDT** folder, create a subfolder named **X64**.
|
||||
9. From the **\\\\MDT01\\MDTProduction$\\Tools\\X64** folder, copy the Microsoft.BDD.Utility.dll file to **C:\\MDT\\X64**.
|
||||
|
||||
|
||||
|
||||
|
||||
The C:\\MDT folder with the files added for the simulation environment.
|
||||
|
||||
@ -62,7 +62,7 @@ On **PC0001**:
|
||||
**Note**
|
||||
Warnings or errors with regard to the Wizard.hta are expected. If the log file looks okay, you are ready to try a real deployment.
|
||||
|
||||
|
||||
|
||||
|
||||
The ZTIGather.log file from PC0001.
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ Three computers are used in this topic: DC01, MDT01, and PC0002.
|
||||
- MDT01 is a domain member server
|
||||
- PC0002 is a domain member computer running Windows 7 SP1, targeted for the Windows 10 upgrade
|
||||
|
||||
|
||||
|
||||
|
||||
The computers used in this topic.
|
||||
|
||||
@ -96,15 +96,15 @@ On **PC0002**:
|
||||
4. On the **Ready** tab, click **Begin** to start the task sequence.
|
||||
When the task sequence begins, it automatically initiates the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
|
||||
|
||||
After the task sequence completes, the computer will be fully upgraded to Windows 10.
|
||||
|
||||
|
||||
@ -47,13 +47,13 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
|
||||
**Note**
|
||||
Make sure File Explorer is configured to show known file extensions so the file is not named DeployLog.txt.txt.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 23. The DeployLog.txt file.
|
||||
|
||||
3. Using System Center 2012 R2 Orchestrator Runbook Designer, in the **Runbooks** node, create the **1.0 MDT** folder.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 24. Folder created in the Runbooks node.
|
||||
|
||||
@ -65,14 +65,14 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
|
||||
2. Text File Management / Append Line
|
||||
8. Connect **Initialize Data** to **Append Line**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 25. Activities added and connected.
|
||||
|
||||
9. Right-click the **Initialize Data** activity, and select **Properties**
|
||||
10. On **the Initialize Data Properties** page, click **Add**, change **Parameter 1** to **OSDComputerName**, and then click **Finish**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 26. The Initialize Data Properties window.
|
||||
|
||||
@ -81,13 +81,13 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
|
||||
13. In the **File** encoding drop-down list, select **ASCII**.
|
||||
14. In the **Append** area, right-click inside the **Text** text box and select **Expand**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 27. Expanding the Text area.
|
||||
|
||||
15. In the blank text box, right-click and select **Subscribe / Published Data**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 28. Subscribing to data.
|
||||
|
||||
@ -95,7 +95,7 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
|
||||
17. After the **{OSDComputerName from "Initialize Data"}** text, type in **has been deployed at** and, once again, right-click and select **Subscribe / Published Data**.
|
||||
18. In the **Published Data** window, select the **Show common Published Data** check box, select the **Activity end time** item, and click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 29. The expanded text box after all subscriptions have been added.
|
||||
|
||||
@ -109,7 +109,7 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
|
||||
23. Close the **Runbook Tester**.
|
||||
24. On the ribbon bar, click **Check In**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 30. All tests completed.
|
||||
|
||||
@ -133,7 +133,7 @@ Figure 30. All tests completed.
|
||||
2. Use Browse to select **1.0 MDT / MDT Sample**.
|
||||
8. Click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 31. The ready-made task sequence.
|
||||
|
||||
@ -157,7 +157,7 @@ Make sure the account you are using has permissions to run runbooks on the Orche
|
||||
3. Domain: CONTOSO
|
||||
4. Wait until the task sequence is completed and then verify that the DeployLog.txt file in the E:\\Logfile folder on OR01 was updated.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 32. The ready-made task sequence.
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ The MDT database is by default created and managed from the Deployment Workbench
|
||||
3. On the **Database** page, select **Create a new database**; in the **Database** field, type **MDT** and click **Next**.
|
||||
4. On the **SQL Share** page, in the **SQL Share** field, type **Logs$** and click **Next**. Click **Next** again and then click **Finish**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 8. The MDT database added to MDT01.
|
||||
|
||||
@ -54,7 +54,7 @@ After creating the database, you need to assign permissions to it. In MDT, the a
|
||||
2. In the **Connect to Server** dialog box, in the **Server name** list, select **MDT01\\SQLEXPRESS** and click **Connect**.
|
||||
3. In the **Object Explorer** pane, expand the top-level **Security** node, right-click **Logins**, and select **New Login**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 9. The top-level Security node.
|
||||
|
||||
@ -64,7 +64,7 @@ After creating the database, you need to assign permissions to it. In MDT, the a
|
||||
3. public (default)
|
||||
5. Click **OK**, and close SQL Server Management Studio.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 10. Creating the login and settings permissions to the MDT database.
|
||||
|
||||
@ -77,7 +77,7 @@ To start using the database, you add a computer entry and assign a description a
|
||||
2. MacAddress: <PC00075 MAC Address in the 00:00:00:00:00:00 format>
|
||||
3. Details Tab / OSDComputerName: PC00075
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 11. Adding the PC00075 computer to the database.
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ In these steps we assume you have installed Microsoft Visual Studio Express 2013
|
||||
1. Web.config
|
||||
2. mdtsample.asmx
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 15. The sample project in Microsoft Visual Studio Express 2013 for Web.
|
||||
|
||||
@ -49,7 +49,7 @@ This section assumes that you have enabled the Web Server (IIS) role on MDT01.
|
||||
4. Select the **Start application pool immediately** check box.
|
||||
5. Click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 16. The new MDTSample application.
|
||||
|
||||
@ -60,7 +60,7 @@ Figure 16. The new MDTSample application.
|
||||
2. Application pool: MDTSample
|
||||
3. Physical Path: E:\\MDTSample
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 17. Adding the MDTSample web application.
|
||||
|
||||
@ -68,7 +68,7 @@ Figure 16. The new MDTSample application.
|
||||
1. Anonymous Authentication: Enabled
|
||||
2. ASP.NET Impersonation: Disabled
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 18. Configuring Authentication for the MDTSample web service.
|
||||
|
||||
@ -77,14 +77,14 @@ Figure 18. Configuring Authentication for the MDTSample web service.
|
||||
1. On PC0001, using Internet Explorer, navigate to: **http://MDT01/MDTSample/mdtsample.asmx**.
|
||||
2. Click the **GetComputerName** link.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 19. The MDT Sample web service.
|
||||
3. On the **GetComputerName** page, type in the following settings, and click **Invoke**:
|
||||
1. Model: Hewlett-Packard
|
||||
2. SerialNumber: 123456789
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 20. The result from the MDT Sample web service.
|
||||
|
||||
@ -103,7 +103,7 @@ After verifying the web service using Internet Explorer, you are ready to do the
|
||||
Parameters=Model,SerialNumber
|
||||
OSDComputerName=string
|
||||
```
|
||||
|
||||
|
||||
|
||||
Figure 21. The updated CustomSettings.ini file.
|
||||
|
||||
@ -115,7 +115,7 @@ After verifying the web service using Internet Explorer, you are ready to do the
|
||||
```
|
||||
4. Review the ZTIGather.log in the **C:\\MININT\\SMSOSD\\OSDLOGS** folder.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 22. The OSDCOMPUTERNAME value obtained from the web service.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user