mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 02:43:43 +00:00
Acrolinx enhancement
This commit is contained in:
Siddarth Mandalika
@ -21,8 +21,8 @@ Operating system images are typically the production image used for deployment t
|
||||
|
||||
## Infrastructure
|
||||
|
||||
For the purposes of this guide, we will use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server.
|
||||
For the purposes of this guide, we'll use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server.
|
||||
- CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md).
|
||||
@ -46,7 +46,7 @@ An existing Configuration Manager infrastructure that is integrated with MDT is
|
||||
5. On the **General** page, assign the name Windows 10 Enterprise x64 RTM, click **Next** twice, and then click **Close**.
|
||||
6. Distribute the operating system image to the CM01 distribution point by right-clicking the **Windows 10 Enterprise x64 RTM** operating system image and then clicking **Distribute Content**.
|
||||
7. In the Distribute Content Wizard, add the CM01 distribution point, click **Next** and click **Close**.
|
||||
8. View the content status for the Windows 10 Enterprise x64 RTM package. Do not continue until the distribution is completed (it might take a few minutes). You also can review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for the **STATMSG: ID=2301** line.
|
||||
8. View the content status for the Windows 10 Enterprise x64 RTM package. Don't continue until the distribution is completed (it might take a few minutes). You also can review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for the **STATMSG: ID=2301** line.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -17,10 +17,10 @@ ms.custom: seo-marvel-apr2020
|
||||
|
||||
- Windows 10
|
||||
|
||||
In this topic, you will learn how to configure the Windows Preinstallation Environment (Windows PE) to include the network drivers required to connect to the deployment share and the storage drivers required to see the local storage on machines. Even though the Windows PE boot image and the Windows 10 operating system contain many out-of-the-box drivers, it is likely you will have to add new or updated drivers to support all your hardware. In this section, you import drivers for both Windows PE and the full Windows 10 operating system.
|
||||
In this topic, you'll learn how to configure the Windows Preinstallation Environment (Windows PE) to include the network drivers required to connect to the deployment share and the storage drivers required to see the local storage on machines. Even though the Windows PE boot image and the Windows 10 operating system contain many out-of-the-box drivers, it's likely you'll have to add new or updated drivers to support all your hardware. In this section, you import drivers for both Windows PE and the full Windows 10 operating system.
|
||||
|
||||
For the purposes of this guide, we will use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
For the purposes of this guide, we'll use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md).
|
||||
|
||||
@ -29,9 +29,9 @@ For the purposes of this guide, we will use one server computer: CM01.
|
||||
This section will show you how to import some network and storage drivers for Windows PE.
|
||||
|
||||
>[!NOTE]
|
||||
>Windows PE usually has a fairly comprehensive set of drivers out of the box, assuming that you are using a recent version of the Windows ADK. This is different than the full Windows OS which will often require drivers. You shouldn't add drivers to Windows PE unless you have an issue or are missing functionality, and in these cases you should only add the driver that you need. An example of a common driver that is added is the Intel I217 driver. Adding too many drivers can cause conflicts and lead to driver bloat in the Config Mgr database. This section shows you how to add drivers, but typically you can just skip this procedure.
|
||||
>Windows PE usually has a fairly comprehensive set of drivers out of the box, assuming that you are using a recent version of the Windows ADK. This is different than the full Windows OS which will often require drivers. You shouldn't add drivers to Windows PE unless you've an issue or are missing functionality, and in these cases you should only add the driver that you need. An example of a common driver that is added is the Intel I217 driver. Adding too many drivers can cause conflicts and lead to driver bloat in the Config Mgr database. This section shows you how to add drivers, but typically you can just skip this procedure.
|
||||
|
||||
This section assumes you have downloaded some drivers to the **D:\\Sources\\OSD\\DriverSources\\WinPE x64** folder on CM01.
|
||||
This section assumes you've downloaded some drivers to the **D:\\Sources\\OSD\\DriverSources\\WinPE x64** folder on CM01.
|
||||
|
||||
|
||||
|
||||
@ -58,7 +58,7 @@ On **CM01**:
|
||||
|
||||
This section illustrates how to add drivers for Windows 10 using the HP EliteBook 8560w as an example. Use the HP Image Assistant from the [HP Client Management Solutions site](https://hp.com/go/clientmanagement).
|
||||
|
||||
For the purposes of this section, we assume that you have downloaded the Windows 10 drivers for the HP EliteBook 8560w model and copied them to the **D:\Sources$\OSD\DriverSources\Windows 10 x64\Hewlett-Packard\HP EliteBook 8560w** folder on CM01.
|
||||
For the purposes of this section, we assume that you've downloaded the Windows 10 drivers for the HP EliteBook 8560w model and copied them to the **D:\Sources$\OSD\DriverSources\Windows 10 x64\Hewlett-Packard\HP EliteBook 8560w** folder on CM01.
|
||||
|
||||
|
||||
|
||||
@ -81,9 +81,9 @@ On **CM01**:
|
||||
* Path: \\\\CM01\\Sources$\\OSD\\DriverPackages\\Windows 10 x64\\Hewlett-Packard\\HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
>The package path does not yet exist, so you have to type it in. The wizard will create the new package using the path you specify.
|
||||
>The package path does not yet exist, so you've to type it in. The wizard will create the new package using the path you specify.
|
||||
|
||||
5. On the **Select drivers to include in the boot image** page, do not select anything, and click **Next** twice. After the package has been created, click **Close**.
|
||||
5. On the **Select drivers to include in the boot image** page, don't select anything, and click **Next** twice. After the package has been created, click **Close**.
|
||||
|
||||
>[!NOTE]
|
||||
>If you want to monitor the driver import process more closely, you can open the SMSProv.log file during driver import.
|
||||
|
||||
@ -20,16 +20,16 @@ ms.custom: seo-marvel-apr2020
|
||||
In Microsoft Endpoint Configuration Manager, you can create custom Windows Preinstallation Environment (Windows PE) boot images that include extra components and features. This topic shows you how to create a custom Windows PE 5.0 boot image with the Microsoft Deployment Toolkit (MDT) wizard. You can also add the Microsoft Diagnostics and Recovery Toolset (DaRT) 10 to the boot image as part of the boot image creation process.
|
||||
- The boot image that is created is based on the version of ADK that is installed.
|
||||
|
||||
For the purposes of this guide, we will use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
For the purposes of this guide, we'll use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md).
|
||||
|
||||
## Add DaRT 10 files and prepare to brand the boot image
|
||||
|
||||
The steps below outline the process for adding DaRT 10 installation files to the MDT installation directory. You also copy a custom background image to be used later. These steps are optional. If you do not wish to add DaRT, skip the steps below to copy DaRT tools and later skip adding the DaRT component to the boot image.
|
||||
The steps below outline the process for adding DaRT 10 installation files to the MDT installation directory. You also copy a custom background image to be used later. These steps are optional. If you don't wish to add DaRT, skip the steps below to copy DaRT tools and later skip adding the DaRT component to the boot image.
|
||||
|
||||
We assume you have downloaded [Microsoft Desktop Optimization Pack (MDOP) 2015](https://my.visualstudio.com/Downloads?q=Desktop%20Optimization%20Pack%202015) and copied the x64 version of MSDaRT100.msi to the **C:\\Setup\\DaRT 10** folder on CM01. We also assume you have created a custom background image and saved it in **C:\\Setup\\Branding** on CM01. In this section, we use a custom background image named <a href="../images/ContosoBackground.png">ContosoBackground.bmp</a>.
|
||||
We assume you've downloaded [Microsoft Desktop Optimization Pack (MDOP) 2015](https://my.visualstudio.com/Downloads?q=Desktop%20Optimization%20Pack%202015) and copied the x64 version of MSDaRT100.msi to the **C:\\Setup\\DaRT 10** folder on CM01. We also assume you've created a custom background image and saved it in **C:\\Setup\\Branding** on CM01. In this section, we use a custom background image named <a href="../images/ContosoBackground.png">ContosoBackground.bmp</a>.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
@ -42,7 +42,7 @@ On **CM01**:
|
||||
|
||||
## Create a boot image for Configuration Manager using the MDT wizard
|
||||
|
||||
By using the MDT wizard to create the boot image in Configuration Manager, you gain additional options for adding components and features to the boot image. In this section, you create a boot image for Configuration Manager using the MDT wizard.
|
||||
By using the MDT wizard to create the boot image in Configuration Manager, you gain more options for adding components and features to the boot image. In this section, you create a boot image for Configuration Manager using the MDT wizard.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
@ -65,7 +65,7 @@ On **CM01**:
|
||||
6. On the **Customization** page, select the **Use a custom background bitmap file** check box, and in the **UNC path:** text box, browse to **\\\\CM01\\Sources$\\OSD\\Branding\\ContosoBackground.bmp** and then click **Next** twice. Wait a few minutes while the boot image is generated, and then click **Finish**.
|
||||
7. Distribute the boot image to the CM01 distribution point by selecting the **Boot images** node, right-clicking the **Zero Touch WinPE x64** boot image, and selecting **Distribute Content**.
|
||||
8. In the Distribute Content Wizard, add the CM01 distribution point, and complete the wizard.
|
||||
9. Using Configuration Manager Trace, review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Do not continue until you can see that the boot image is distributed. Look for the line that reads **STATMSG: ID=2301**. You also can monitor Content Status in the Configuration Manager Console at **\Monitoring\Overview\Distribution Status\Content Status\Zero Touch WinPE x64**. See the following examples:
|
||||
9. Using Configuration Manager Trace, review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Don't continue until you can see that the boot image is distributed. Look for the line that reads **STATMSG: ID=2301**. You also can monitor Content Status in the Configuration Manager Console at **\Monitoring\Overview\Distribution Status\Content Status\Zero Touch WinPE x64**. See the following examples:
|
||||
|
||||
<br>
|
||||
|
||||
|
||||
@ -16,10 +16,10 @@ ms.topic: article
|
||||
|
||||
- Windows 10
|
||||
|
||||
In this article, you will learn how to create a Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard. Creating task sequences in Configuration Manager requires many more steps than creating task sequences for MDT Lite Touch installation. Luckily, the MDT wizard helps you through the process and also guides you through creating the needed packages.
|
||||
In this article, you'll learn how to create a Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard. Creating task sequences in Configuration Manager requires many more steps than creating task sequences for MDT Lite Touch installation. Luckily, the MDT wizard helps you through the process and also guides you through creating the needed packages.
|
||||
|
||||
For the purposes of this guide, we will use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
For the purposes of this guide, we'll use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md). Note: Active Directory [permissions](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md#configure-active-directory-permissions) for the **CM_JD** account are required for the task sequence to work properly.
|
||||
|
||||
@ -93,9 +93,9 @@ On **CM01**:
|
||||
Add an application to the Configuration Manager task sequence
|
||||
|
||||
>[!NOTE]
|
||||
>In recent versions of Configuration Manager the Request State Store and Release State Store actions described below are present by default. These actions are used for common computer replace scenarios. There is also the additional condition on the options tab: USMTOfflineMigration not equals TRUE. If these actions are not present, try updating to the Config Mgr current branch release.
|
||||
>In recent versions of Configuration Manager the Request State Store and Release State Store actions described below are present by default. These actions are used for common computer replace scenarios. There's also the additional condition on the options tab: USMTOfflineMigration not equals TRUE. If these actions are not present, try updating to the Config Mgr current branch release.
|
||||
|
||||
9. In the **State Restore** group, after the **Set Status 5** action, verify there is a **User State \ Request State Store** action with the following settings:
|
||||
9. In the **State Restore** group, after the **Set Status 5** action, verify there's a **User State \ Request State Store** action with the following settings:
|
||||
* Request state storage location to: Restore state from another computer
|
||||
* If computer account fails to connect to state store, use the Network Access account: selected
|
||||
* Options: Continue on error
|
||||
@ -103,7 +103,7 @@ On **CM01**:
|
||||
* Task Sequence Variable
|
||||
* USMTLOCAL not equals True
|
||||
|
||||
10. In the **State Restore** group, after the **Restore User State** action, verify there is a **Release State Store** action with the following settings:
|
||||
10. In the **State Restore** group, after the **Restore User State** action, verify there's a **Release State Store** action with the following settings:
|
||||
* Options: Continue on error
|
||||
* Options / Condition:
|
||||
* Task Sequence Variable
|
||||
@ -113,14 +113,14 @@ On **CM01**:
|
||||
|
||||
## Organize your packages (optional)
|
||||
|
||||
If desired, you can create a folder structure for packages. This is purely for organizational purposes and is useful if you need to manage a large number of packages.
|
||||
If desired, you can create a folder structure for packages. This folder structure is purely for organizational purposes and is useful if you need to manage a large number of packages.
|
||||
|
||||
To create a folder for packages:
|
||||
|
||||
On **CM01**:
|
||||
|
||||
1. Using the Configuration Manager Console, in the Software Library workspace, expand **Application Management**, and then select **Packages**.
|
||||
2. Right-click **Packages**, point to **Folder**, click **Create Folder** and create the OSD folder. This will create the Root \ OSD folder structure.
|
||||
2. Right-click **Packages**, point to **Folder**, click **Create Folder** and create the OSD folder. This process will create the Root \ OSD folder structure.
|
||||
3. Select the **MDT**, **User State Migration Tool for Windows**, and **Windows 10 x64 Settings** packages, right-click and select **Move**.
|
||||
4. In the **Move Selected Items** dialog box, select the **OSD** folder, and click **OK**.
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Create an app to deploy with Windows 10 using Configuration Manager
|
||||
description: Microsoft Microsoft Endpoint Manager supports deploying applications as part of the Windows 10 deployment process.
|
||||
description: Microsoft Endpoint Manager supports deploying applications as part of the Windows 10 deployment process.
|
||||
ms.assetid: 2dfb2f39-1597-4999-b4ec-b063e8a8c90c
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
@ -19,8 +20,8 @@ ms.topic: article
|
||||
|
||||
Microsoft Endpoint Manager supports deploying applications as part of the Windows 10 deployment process. In this section, you create an application in Microsoft Endpoint Manager that you later configure the task sequence to use.
|
||||
|
||||
For the purposes of this guide, we will use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
For the purposes of this guide, we'll use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
>[!NOTE]
|
||||
>The [reference image](add-a-windows-10-operating-system-image-using-configuration-manager.md) used in this lab already contains some applications, such as Microsoft Office 365 Pro Plus x64. The procedure demonstrated in this article enables you to add some additional custom applications beyond those included in the reference image.
|
||||
@ -29,9 +30,9 @@ For the purposes of this guide, we will use one server computer: CM01.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
1. Create the **D:\Setup** folder if it does not already exist.
|
||||
1. Create the **D:\Setup** folder if it doesn't already exist.
|
||||
1. Download the Enterprise distribution version of [Adobe Acrobat Reader DC](https://get.adobe.com/reader/enterprise/) (ex: AcroRdrDC2000620034_en_US.exe) to **D:\\Setup\\Adobe** on CM01. The filename will differ depending on the version of Acrobat Reader.
|
||||
2. Extract the .exe file that you downloaded to an .msi. The source folder will differ depending on where you downloaded the file. See the following example:
|
||||
2. Extract the .exe file that you downloaded to a .msi. The source folder will differ depending on where you downloaded the file. See the following example:
|
||||
|
||||
```powershell
|
||||
Set-Location C:\Users\administrator.CONTOSO\Downloads
|
||||
@ -64,7 +65,7 @@ On **CM01**:
|
||||
|
||||
Add the "OSD Install" suffix to the application name
|
||||
|
||||
11. In the **Applications** node, select the Adobe Reader - OSD Install application, and click **Properties** on the ribbon bar (this is another place to view properties, you can also right-click and select properties).
|
||||
11. In the **Applications** node, select the Adobe Reader - OSD Install application, and click **Properties** on the ribbon bar (this path is another place to view properties, you can also right-click and select properties).
|
||||
12. On the **General Information** tab, select the **Allow this application to be installed from the Install Application task sequence action without being deployed** check box, and click **OK**.
|
||||
|
||||
Next, see [Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md).
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Deploy Windows 10 using PXE and Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to deploy Windows 10 using Microsoft Endpoint Manager deployment packages and task sequences.
|
||||
description: In this topic, you'll learn how to deploy Windows 10 using Microsoft Endpoint Manager deployment packages and task sequences.
|
||||
ms.assetid: fb93f514-5b30-4f4b-99dc-58e6860009fa
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
ms.prod: w10
|
||||
@ -16,9 +17,9 @@ ms.collection: highpri
|
||||
|
||||
- Windows 10
|
||||
|
||||
In this topic, you will learn how to deploy Windows 10 using Microsoft Endpoint Manager deployment packages and task sequences. This topic will walk you through the process of deploying the Windows 10 Enterprise image to a Unified Extensible Firmware Interface (UEFI) computer named PC0001. An existing Configuration Manager infrastructure that is integrated with MDT is used for the procedures in this topic.
|
||||
In this topic, you'll learn how to deploy Windows 10 using Microsoft Endpoint Manager deployment packages and task sequences. This topic will walk you through the process of deploying the Windows 10 Enterprise image to a Unified Extensible Firmware Interface (UEFI) computer named PC0001. An existing Configuration Manager infrastructure that is integrated with MDT is used for the procedures in this topic.
|
||||
|
||||
This topic assumes that you have completed the following prerequisite procedures:
|
||||
This topic assumes that you've completed the following prerequisite procedures:
|
||||
- [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
- [Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
- [Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
@ -27,10 +28,10 @@ This topic assumes that you have completed the following prerequisite procedures
|
||||
- [Create a task sequence with Configuration Manager and MDT](create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
- [Finalize the operating system configuration for Windows 10 deployment with Configuration Manager](finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md)
|
||||
|
||||
For the purposes of this guide, we will use a minimum of two server computers (DC01 and CM01) and one client computer (PC0001).
|
||||
For the purposes of this guide, we'll use a minimum of two server computers (DC01 and CM01) and one client computer (PC0001).
|
||||
- DC01 is a domain controller and DNS server for the contoso.com domain. DHCP services are also available and optionally installed on DC01 or another server. Note: DHCP services are required for the client (PC0001) to connect to the Windows Deployment Service (WDS).
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server.
|
||||
- CM01 is also running WDS which will be required to start PC0001 via PXE. **Note**: Ensure that only CM01 is running WDS.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server.
|
||||
- CM01 is also running WDS that will be required to start PC0001 via PXE. **Note**: Ensure that only CM01 is running WDS.
|
||||
- PC0001 is a client computer that is blank, or has an operating system that will be erased and replaced with Windows 10. The device must be configured to boot from the network.
|
||||
|
||||
>[!NOTE]
|
||||
@ -38,7 +39,7 @@ For the purposes of this guide, we will use a minimum of two server computers (D
|
||||
|
||||
All servers are running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
All server and client computers referenced in this guide are on the same subnet. This is not required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
All server and client computers referenced in this guide are on the same subnet. This connection isn't required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
|
||||
>[!NOTE]
|
||||
>No WDS console configuration is required for PXE to work. Everything is done with the Configuration Manager console.
|
||||
@ -50,7 +51,7 @@ All server and client computers referenced in this guide are on the same subnet.
|
||||
3. On the **Select a task sequence to run** page, select **Windows 10 Enterprise x64 RTM** and click **Next**.
|
||||
4. On the **Edit Task Sequence Variables** page, double-click the **OSDComputerName** variable, and in the **Value** field, type **PC0001** and click **OK**. Then click **Next**.
|
||||
5. The operating system deployment will take several minutes to complete.
|
||||
6. You can monitor the deployment on CM01 using the MDT Deployment Workbench. When you see the PC0001 entry, double-click **PC0001**, and then click **DaRT Remote Control** and review the **Remote Control** option. The task sequence will run and do the following:
|
||||
6. You can monitor the deployment on CM01 using the MDT Deployment Workbench. When you see the PC0001 entry, double-click **PC0001**, and then click **DaRT Remote Control** and review the **Remote Control** option. The task sequence will run and do the following steps:
|
||||
|
||||
* Install the Windows 10 operating system.
|
||||
* Install the Configuration Manager client and the client hotfix.
|
||||
@ -64,7 +65,7 @@ All server and client computers referenced in this guide are on the same subnet.
|
||||
|
||||
Monitoring the deployment with MDT.
|
||||
|
||||
7. When the deployment is finished you will have a domain-joined Windows 10 computer with the Adobe Reader application installed as well as the applications that were included in the reference image, such as Office 365 Pro Plus.
|
||||
7. When the deployment is finished you'll have a domain-joined Windows 10 computer with the Adobe Reader application installed as well as the applications that were included in the reference image, such as Office 365 Pro Plus.
|
||||
|
||||
Examples are provided below of various stages of deployment:
|
||||
|
||||
|
||||
@ -19,8 +19,8 @@ ms.custom: seo-marvel-apr2020
|
||||
|
||||
This topic walks you through the steps to finalize the configuration of your Windows 10 operating deployment, which includes enabling optional MDT monitoring for Configuration Manager, logs folder settings, rules configuration, content distribution, and deployment of the previously created task sequence.
|
||||
|
||||
For the purposes of this guide, we will use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
For the purposes of this guide, we'll use one server computer: CM01.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server. CM01 is running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md).
|
||||
|
||||
@ -45,11 +45,11 @@ On **CM01**:
|
||||
|
||||
## Configure the Logs folder
|
||||
|
||||
The D:\Logs folder was [created previously](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md?#review-the-sources-folder-structure) and SMB permissions were added. Next, we will add NTFS folder permissions for the Configuration Manager Network Access Account (CM_NAA), and enable server-side logging by modifying the CustomSettings.ini file used by the Configuration Manager task sequence.
|
||||
The D:\Logs folder was [created previously](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md?#review-the-sources-folder-structure) and SMB permissions were added. Next, we'll add NTFS folder permissions for the Configuration Manager Network Access Account (CM_NAA), and enable server-side logging by modifying the CustomSettings.ini file used by the Configuration Manager task sequence.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
1. To configure NTFS permissions using icacls.exe, type the following at an elevated Windows PowerShell prompt:
|
||||
1. To configure NTFS permissions using icacls.exe, type the following command at an elevated Windows PowerShell prompt:
|
||||
|
||||
```
|
||||
icacls D:\Logs /grant '"CM_NAA":(OI)(CI)(M)'
|
||||
@ -82,17 +82,17 @@ On **CM01**:
|
||||
3. In the Configuration Manager console, update the distribution point for the **Windows 10 x64 Settings** package by right-clicking the **Windows 10 x64 Settings** package and selecting **Update Distribution Points**. Click **OK** in the popup dialog box.
|
||||
|
||||
>[!NOTE]
|
||||
>Although you have not yet added a distribution point, you still need to select Update Distribution Points. This process also updates the Configuration Manager content library with changes.
|
||||
>Although you haven't yet added a distribution point, you still need to select Update Distribution Points. This process also updates the Configuration Manager content library with changes.
|
||||
|
||||
## Distribute content to the CM01 distribution portal
|
||||
|
||||
In Configuration Manager, you can distribute all packages needed by a task sequence in a single task. In this section, you distribute packages that have not yet been distributed to the CM01 distribution point.
|
||||
In Configuration Manager, you can distribute all packages needed by a task sequence in a single task. In this section, you distribute packages that haven't yet been distributed to the CM01 distribution point.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
1. Using the Configuration Manager console, in the Software Library workspace, expand **Operating Systems** and select **Task Sequences**. Right-click the **Windows 10 Enterprise x64 RTM** task sequence, and select **Distribute Content**.
|
||||
2. In the Distribute Content Wizard, click **Next** twice then on the **Specify the content destination** page add the Distribution Point: **CM01.CONTOSO.COM**, and then complete the wizard.
|
||||
3. Using the CMTrace tool, verify the distribution to the CM01 distribution point by reviewing the distmgr.log file, or use the Distribution Status / Content Status option in the Monitoring workspace. Do not continue until you see all the new packages being distributed successfully.
|
||||
3. Using the CMTrace tool, verify the distribution to the CM01 distribution point by reviewing the distmgr.log file, or use the Distribution Status / Content Status option in the Monitoring workspace. Don't continue until you see all the new packages being distributed successfully.
|
||||
|
||||
|
||||
|
||||
@ -100,7 +100,7 @@ On **CM01**:
|
||||
|
||||
## Create a deployment for the task sequence
|
||||
|
||||
This sections provides steps to help you create a deployment for the task sequence.
|
||||
This section provides steps to help you create a deployment for the task sequence.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
@ -126,7 +126,7 @@ On **CM01**:
|
||||
|
||||
## Configure Configuration Manager to prompt for the computer name during deployment (optional)
|
||||
|
||||
You can have Configuration Manager prompt you for a computer name or you can use rules to generate a computer name. For more details on how to do this, see [Configure MDT settings](../deploy-windows-mdt/configure-mdt-settings.md).
|
||||
You can have Configuration Manager prompt you for a computer name or you can use rules to generate a computer name. For more information on how to do this step, see [Configure MDT settings](../deploy-windows-mdt/configure-mdt-settings.md).
|
||||
|
||||
This section provides steps to help you configure the All Unknown Computers collection to have Configuration Manager prompt for computer names.
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ This article walks you through the Zero Touch Installation (ZTI) process of Wind
|
||||
|
||||
## Prerequisites
|
||||
|
||||
In this article, you'll use [components](#components-of-configuration-manager-operating-system-deployment) of an existing Configuration Manager infrastructure to prepare for Windows 10 OSD. In addition to the base setup, the following configurations should be made in the Configuration Manager environment:
|
||||
In this topic, you'll use [components](#components-of-configuration-manager-operating-system-deployment) of an existing Configuration Manager infrastructure to prepare for Windows 10 OSD. In addition to the base setup, the following configurations should be made in the Configuration Manager environment:
|
||||
|
||||
- Configuration Manager current branch + all security and critical updates are installed.
|
||||
|
||||
@ -32,19 +32,18 @@ In this article, you'll use [components](#components-of-configuration-manager-op
|
||||
- The Configuration Manager [reporting services](/mem/configmgr/core/servers/manage/configuring-reporting) point role has been added and configured.
|
||||
- A file system folder structure and Configuration Manager console folder structure for packages has been created. Steps to verify or create this folder structure are [provided below](#review-the-sources-folder-structure).
|
||||
- The [Windows ADK](/windows-hardware/get-started/adk-install) (including USMT) version 1903, Windows PE add-on, WSIM 1903 update, [MDT](https://www.microsoft.com/download/details.aspx?id=54259) version 8456, and DaRT 10 (part of [MDOP 2015](https://my.visualstudio.com/Downloads?q=Desktop%20Optimization%20Pack%202015)) are installed.
|
||||
- The [CMTrace tool](/mem/configmgr/core/support/cmtrace) (cmtrace.exe) is installed on the distribution point.
|
||||
|
||||
> [!NOTE]
|
||||
> CMTrace is automatically installed with the current branch of Configuration Manager.
|
||||
- The [CMTrace tool](/configmgr/core/support/cmtrace) (cmtrace.exe) is installed on the distribution point.
|
||||
> [!NOTE]
|
||||
> CMTrace is automatically installed with the current branch of Configuration Manager at **Program Files\Microsoft Configuration Manager\tools\cmtrace.exe**. In previous releases of ConfigMgr, it was necessary to install the [Configuration Manager Toolkit](https://www.microsoft.com/download/details.aspx?id=50012) separately to get the CMTrace tool, but this separate installation is no longer needed. Configuration Manager version 1910 installs version 5.0.8913.1000 of the CMTrace tool.
|
||||
|
||||
For the purposes of this guide, we'll use three server computers: DC01, CM01 and HV01.
|
||||
- DC01 is a domain controller and DNS server for the contoso.com domain. DHCP services are also available and optionally installed on DC01 or another server.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server.
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server.
|
||||
- HV01 is a Hyper-V host computer that is used to build a Windows 10 reference image. This computer doesn't need to be a domain member.
|
||||
|
||||
All servers are running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
All server and client computers referenced in this guide are on the same subnet. This configuration isn't required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
All server and client computers referenced in this guide are on the same subnet. This interrelation isn't required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
|
||||
### Domain credentials
|
||||
|
||||
@ -57,13 +56,13 @@ The following generic credentials are used in this guide. You should replace the
|
||||
## Create the OU structure
|
||||
|
||||
>[!NOTE]
|
||||
>If you have already [created the OU structure](../deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md#create-the-ou-structure) that was used in the OSD guide for MDT, the same structure is used here and you can skip this section.
|
||||
>If you've already [created the OU structure](../deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md#create-the-ou-structure) that was used in the OSD guide for MDT, the same structure is used here and you can skip this section.
|
||||
|
||||
On **DC01**:
|
||||
|
||||
To create the OU structure, you can use the Active Directory Users and Computers console (dsa.msc), or you can use Windows PowerShell. The procedure below uses Windows PowerShell.
|
||||
|
||||
To use Windows PowerShell, copy the following commands into a text file and save it as **C:\Setup\Scripts\ou.ps1**. Be sure that you're viewing file extensions and that you save the file with the `.ps1` extension.
|
||||
To use Windows PowerShell, copy the following commands into a text file and save it as <b>C:\Setup\Scripts\ou.ps1</b>. Ensure that you're viewing file extensions and that you save the file with the .ps1 extension.
|
||||
|
||||
```powershell
|
||||
$oulist = Import-csv -Path c:\oulist.txt
|
||||
@ -123,11 +122,11 @@ On **DC01**:
|
||||
|
||||
## Configure Active Directory permissions
|
||||
|
||||
In order for the Configuration Manager Join Domain Account (CM\_JD) to join machines into the contoso.com domain you need to configure permissions in Active Directory. These steps assume you've downloaded the sample [Set-OUPermissions.ps1 script](https://github.com/DeploymentArtist/SWP1/tree/master/Scripts) and copied it to C:\\Setup\\Scripts on DC01.
|
||||
In order for the Configuration Manager Join Domain Account (CM\_JD) to join machines into the contoso.com domain, you need to configure permissions in Active Directory. These steps assume you've downloaded the sample [Set-OUPermissions.ps1 script](https://go.microsoft.com/fwlink/p/?LinkId=619362) and copied it to C:\\Setup\\Scripts on DC01.
|
||||
|
||||
On **DC01**:
|
||||
|
||||
1. Sign in as contoso\administrator and enter the following at an elevated Windows PowerShell prompt:
|
||||
1. Sign in as contoso\administrator and enter the following commands at an elevated Windows PowerShell prompt:
|
||||
|
||||
```powershell
|
||||
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force
|
||||
@ -135,7 +134,7 @@ On **DC01**:
|
||||
.\Set-OUPermissions.ps1 -Account CM_JD -TargetOU "OU=Workstations,OU=Computers,OU=Contoso"
|
||||
```
|
||||
|
||||
2. The Set-OUPermissions.ps1 script allows the CM\_JD user account permissions to manage computer accounts in the Contoso / Computers / Workstations OU. The following is a list of the permissions being granted:
|
||||
2. The Set-OUPermissions.ps1 script allows the CM\_JD user account permissions to manage computer accounts in the Contoso / Computers / Workstations OU. The following list is that of permissions being granted:
|
||||
|
||||
* Scope: This object and all descendant objects
|
||||
* Create Computer objects
|
||||
@ -174,7 +173,7 @@ To support the packages you create in this article, the following folder structu
|
||||
|
||||
You can run the following commands from an elevated Windows PowerShell prompt to create this folder structure:
|
||||
|
||||
>We will also create the D:\Logs folder here which will be used later to support server-side logging.
|
||||
>We'll also create the D:\Logs folder here which will be used later to support server-side logging.
|
||||
|
||||
```powershell
|
||||
New-Item -ItemType Directory -Path "D:\Sources"
|
||||
@ -196,7 +195,7 @@ New-SmbShare -Name Logs$ -Path D:\Logs -ChangeAccess EVERYONE
|
||||
|
||||
## Integrate Configuration Manager with MDT
|
||||
|
||||
To extend the Configuration Manager console with MDT wizards and templates, install MDT with the default settings and run the **Configure ConfigManager Integration** desktop app. In these steps, we assume you have already [downloaded MDT](https://www.microsoft.com/download/details.aspx?id=54259) and installed it with default settings.
|
||||
To extend the Configuration Manager console with MDT wizards and templates, install MDT with the default settings and run the **Configure ConfigManager Integration** desktop app. In these steps, we assume you've already [downloaded MDT](https://www.microsoft.com/download/details.aspx?id=54259) and installed it with default settings.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
@ -264,7 +263,7 @@ On **CM01**:
|
||||
Configure the CM01 distribution point for PXE.
|
||||
|
||||
>[!NOTE]
|
||||
>If you select **Enable a PXE responder without Windows Deployment Service**, then WDS will not be installed, or if it is already installed it will be suspended, and the **ConfigMgr PXE Responder Service** (SccmPxe) will be used instead of WDS. The ConfigMgr PXE Responder does not support multicast. For more information, see [Install and configure distribution points](/mem/configmgr/core/servers/deploy/configure/install-and-configure-distribution-points#bkmk_config-pxe).
|
||||
>If you select **Enable a PXE responder without Windows Deployment Service**, then WDS won't be installed, or if it's already installed it will be suspended, and the **ConfigMgr PXE Responder Service** (SccmPxe) will be used instead of WDS. The ConfigMgr PXE Responder doesn't support multicast. For more information, see [Install and configure distribution points](/configmgr/core/servers/deploy/configure/install-and-configure-distribution-points#bkmk_config-pxe).
|
||||
|
||||
4. Using the CMTrace tool, review the C:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file. Look for ConfigurePXE and CcmInstallPXE lines.
|
||||
|
||||
@ -272,7 +271,7 @@ On **CM01**:
|
||||
|
||||
The distmgr.log displays a successful configuration of PXE on the distribution point.
|
||||
|
||||
5. Verify that you have seven files in each of the folders **D:\\RemoteInstall\\SMSBoot\\x86** and **D:\\RemoteInstall\\SMSBoot\\x64**.
|
||||
5. Verify that you've seven files in each of the folders **D:\\RemoteInstall\\SMSBoot\\x86** and **D:\\RemoteInstall\\SMSBoot\\x64**.
|
||||
|
||||
|
||||
|
||||
@ -284,18 +283,17 @@ Next, see [Create a custom Windows PE boot image with Configuration Manager](cre
|
||||
|
||||
## Components of Configuration Manager operating system deployment
|
||||
|
||||
Operating system deployment with Configuration Manager is part of the normal software distribution infrastructure, but there are other components. For example, operating system deployment in Configuration Manager may use the State Migration Point role, which isn't used by normal application deployment in Configuration Manager. This section describes the Configuration Manager components involved with the deployment of an operating system, such as Windows 10.
|
||||
Operating system deployment with Configuration Manager is part of the normal software distribution infrastructure, but there are more components. For example, operating system deployment in Configuration Manager may use the State Migration Point role, which isn't used by normal application deployment in Configuration Manager. This section describes the Configuration Manager components involved with the deployment of an operating system, such as Windows 10.
|
||||
|
||||
- **State migration point (SMP).** The state migration point is used to store user state migration data during computer replace scenarios.
|
||||
- **Distribution point (DP).** The distribution point is used to store all packages in Configuration Manager, including the operating system deployment-related packages.
|
||||
- **Software update point (SUP).** The software update point, which is normally used to deploy updates to existing machines, also can be used to update an operating system as part of the deployment process. You also can use offline servicing to update the image directly on the Configuration Manager server.
|
||||
- **Reporting services point.** The reporting services point can be used to monitor the operating system deployment process.
|
||||
- **Boot images.** Boot images are the Windows Preinstallation Environment (Windows PE) images Configuration Manager uses to start the deployment.
|
||||
- **Operating system images.** The operating system image package contains only one file, the custom .wim image. This is typically the production deployment image.
|
||||
- **Operating system images.** The operating system image package contains only one file, the custom .wim image. This image is typically the production deployment image.
|
||||
- **Operating system installers.** The operating system installers were originally added to create reference images using Configuration Manager. Instead, we recommend that you use MDT Lite Touch to create your reference images. For more information on how to create a reference image, see [Create a Windows 10 reference image](../deploy-windows-mdt/create-a-windows-10-reference-image.md).
|
||||
- **Drivers.** Like MDT Lite Touch, Configuration Manager also provides a repository (catalog) of managed device drivers.
|
||||
- **Task sequences.** The task sequences in Configuration Manager look and feel much like the sequences in MDT Lite Touch, and they're used for the same purpose. However, in Configuration Manager the task sequence is delivered to the clients as a policy via the Management Point (MP). MDT provides extra task sequence templates to Configuration Manager.
|
||||
|
||||
- **Task sequences.** The task sequences in Configuration Manager look and feel much like the sequences in MDT Lite Touch, and they're used for the same purpose. However, in Configuration Manager, the task sequence is delivered to the clients as a policy via the Management Point (MP). MDT provides more task sequence templates to Configuration Manager.
|
||||
> [!NOTE]
|
||||
> The Windows Assessment and Deployment Kit (ADK) for Windows 10 is also required to support management and deployment of Windows 10.
|
||||
|
||||
@ -303,12 +301,17 @@ Operating system deployment with Configuration Manager is part of the normal sof
|
||||
|
||||
As noted above, MDT adds many enhancements to Configuration Manager. While these enhancements are called Zero Touch, that name doesn't reflect how deployment is conducted. The following sections provide a few samples of the 280 enhancements that MDT adds to Configuration Manager.
|
||||
|
||||
>[!NOTE]
|
||||
>MDT installation requires the following:
|
||||
>- The Windows ADK for Windows 10 (installed in the previous procedure)
|
||||
>- Windows PowerShell ([version 5.1](https://www.microsoft.com/download/details.aspx?id=54616) is recommended; type **$host** to check)
|
||||
>- Microsoft .NET Framework
|
||||
|
||||
### MDT enables dynamic deployment
|
||||
|
||||
When MDT is integrated with Configuration Manager, the task sequence takes other instructions from the MDT rules. In its most simple form, these settings are stored in a text file, the CustomSettings.ini file, but you can store the settings in Microsoft SQL Server databases, or have a script or web services provide the settings used.
|
||||
When MDT is integrated with Configuration Manager, the task sequence takes more instructions from the MDT rules. In its most simple form, these settings are stored in a text file, the CustomSettings.ini file, but you can store the settings in Microsoft SQL Server databases, or have Microsoft Visual Basic Scripting Edition (VBScripts) or web services provide the settings used.
|
||||
|
||||
The task sequence uses instructions that allow you to reduce the number of task sequences in Configuration Manager and instead store settings outside the task sequence. Here are a few examples:
|
||||
|
||||
- The following settings instruct the task sequence to install the HP Hotkeys package, but only if the hardware is an HP EliteBook 8570w. You don't have to add the package to the task sequence.
|
||||
|
||||
``` syntax
|
||||
@ -349,7 +352,7 @@ The folder that contains the rules, a few scripts from MDT, and a custom script
|
||||
|
||||
### MDT adds real-time monitoring
|
||||
|
||||
With MDT integration, you can follow your deployments in real time, and if you have access to Microsoft Diagnostics and Recovery Toolkit (DaRT), you can even remote into Windows Preinstallation Environment (Windows PE) during deployment. The real-time monitoring data can be viewed from within the MDT Deployment Workbench, via a web browser, Windows PowerShell, the Event Viewer, or Microsoft Excel 2013. In fact, any script or app that can read an Open Data (OData) feed can read the information.
|
||||
With MDT integration, you can follow your deployments in real time, and if you've access to Microsoft Diagnostics and Recovery Toolkit (DaRT), you can even remote into Windows Preinstallation Environment (Windows PE) during deployment. The real-time monitoring data can be viewed from within the MDT Deployment Workbench, via a web browser, Windows PowerShell, the Event Viewer, or Microsoft Excel 2013. In fact, any script or app that can read an Open Data (OData) feed can read the information.
|
||||
|
||||
|
||||
|
||||
@ -370,25 +373,18 @@ MDT Zero Touch simply extends Configuration Manager with many useful built-in op
|
||||
You can create reference images for Configuration Manager in Configuration Manager, but in general we recommend creating them in MDT Lite Touch for the following reasons:
|
||||
|
||||
- You can use the same image for every type of operating system deployment - Microsoft Virtual Desktop Infrastructure (VDI), Microsoft System Center Virtual Machine Manager (VMM), MDT, Configuration Manager, Windows Deployment Services (WDS), and more.
|
||||
- Configuration Manager performs deployment in the LocalSystem context. This means that you can't configure the Administrator account with all of the settings that you would like to be included in the image. MDT runs in the context of the Local Administrator, which means you can configure the look and feel of the configuration and then use the CopyProfile functionality to copy these changes to the default user during deployment.
|
||||
- Configuration Manager performs deployment in the LocalSystem context, which means that you can't configure the Administrator account with all of the settings that you would like to be included in the image. MDT runs in the context of the Local Administrator, which means you can configure the look and feel of the configuration and then use the CopyProfile functionality to copy these changes to the default user during deployment.
|
||||
- The Configuration Manager task sequence doesn't suppress user interface interaction.
|
||||
- MDT Lite Touch supports a Suspend action that allows for reboots, which is useful when you need to perform a manual installation or check the reference image before it's automatically captured.
|
||||
- MDT Lite Touch doesn't require any infrastructure and is easy to delegate.
|
||||
|
||||
## Related articles
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](./create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
## Related topics
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)<br>
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)<br>
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)<br>
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)<br>
|
||||
[Create a task sequence with Configuration Manager and MDT](./create-a-task-sequence-with-configuration-manager-and-mdt.md)<br>
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)<br>
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)<br>
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
@ -17,7 +17,7 @@ ms.custom: seo-marvel-apr2020
|
||||
|
||||
- Windows 10
|
||||
|
||||
This topic will show you how to refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager and Microsoft Deployment Toolkit (MDT). A computer refresh is not the same as an in-place upgrade. A computer refresh involves storing user data and settings from the old installation, wiping the hard drives, installing a new OS, and then restoring the user data at the end of the installation. Also see the MDT refesh procedure: [Refresh a Windows 7 computer with Windows 10](../deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10.md).
|
||||
This topic will show you how to refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager and Microsoft Deployment Toolkit (MDT). A computer refresh isn't the same as an in-place upgrade. A computer refresh involves storing user data and settings from the old installation, wiping the hard drives, installing a new OS, and then restoring the user data at the end of the installation. Also see the MDT refresh procedure: [Refresh a Windows 7 computer with Windows 10](../deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10.md).
|
||||
|
||||
A computer refresh with Configuration Manager works the same as it does with MDT Lite Touch installation. Configuration Manager also uses the User State Migration Tool (USMT) from the Windows Assessment and Deployment Kit (Windows ADK) 10 in the background. A computer refresh with Configuration Manager has the following steps:
|
||||
|
||||
@ -31,8 +31,8 @@ A computer refresh with Configuration Manager works the same as it does with MDT
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md).
|
||||
|
||||
For the purposes of this article, we will use one server computer (CM01) and one client computer (PC0003).
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server.
|
||||
For the purposes of this article, we'll use one server computer (CM01) and one client computer (PC0003).
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server.
|
||||
- PC0003 is a domain member client computer running Windows 7 SP1, or a later version of Windows, with the Configuration Manager client installed, that will be refreshed to Windows 10.
|
||||
|
||||
>[!NOTE]
|
||||
@ -40,7 +40,7 @@ For the purposes of this article, we will use one server computer (CM01) and one
|
||||
|
||||
All servers are running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
All server and client computers referenced in this guide are on the same subnet. This is not required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
All server and client computers referenced in this guide are on the same subnet. This interrelation isn't required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>This article assumes that you have [configured Active Directory permissions](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md#configure-active-directory-permissions) in the specified OU for the **CM_JD** account, and the client's Active Directory computer account is in the **Contoso > Computers > Workstations** OU. Use the Active Directory Users and Computers console to review the location of computer objects and move them if needed.
|
||||
@ -76,7 +76,7 @@ On **CM01**:
|
||||
|
||||
Use the default settings to complete the remaining wizard pages and click **Close**.
|
||||
|
||||
2. Review the Install Windows 10 Enterprise x64 collection. Do not continue until you see the PC0003 machine in the collection.
|
||||
2. Review the Install Windows 10 Enterprise x64 collection. Don't continue until you see the PC0003 machine in the collection.
|
||||
|
||||
>[!NOTE]
|
||||
>It may take a short while for the collection to refresh; you can view progress via the Colleval.log file. If you want to speed up the process, you can manually update membership on the Install Windows 10 Enterprise x64 collection by right-clicking the collection and selecting Update Membership.
|
||||
@ -94,7 +94,7 @@ Using the Configuration Manager console, in the Software Library workspace, expa
|
||||
- Make available to the following: Configuration Manager clients, media and PXE
|
||||
|
||||
>[!NOTE]
|
||||
>It is not necessary to make the deployment available to media and Pre-Boot Execution Environment (PXE) for a computer refresh, but you will use the same deployment for bare-metal deployments later on and you will need it at that point.
|
||||
>It's not necessary to make the deployment available to media and Pre-Boot Execution Environment (PXE) for a computer refresh, but you will use the same deployment for bare-metal deployments later on and you will need it at that point.
|
||||
|
||||
- Scheduling
|
||||
- <default>
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
description: In this topic, you will learn how to replacing a Windows 7 SP1 computer using Microsoft Endpoint Configuration Manager.
|
||||
description: In this topic, you'll learn how to replace a Windows 7 SP1 computer using Microsoft Endpoint Configuration Manager.
|
||||
ms.assetid: 3c8a2d53-8f08-475f-923a-bca79ca8ac36
|
||||
ms.reviewer:
|
||||
manager: dougeby
|
||||
ms.author: aaroncz
|
||||
@ -17,16 +18,16 @@ ms.custom: seo-marvel-apr2020
|
||||
|
||||
- Windows 10
|
||||
|
||||
In this topic, you will learn how to replace a Windows 7 SP1 computer using Microsoft Endpoint Configuration Manager. This process is similar to refreshing a computer, but since you are replacing the device, you have to run the backup job separately from the deployment of Windows 10.
|
||||
In this topic, you'll learn how to replace a Windows 7 SP1 computer using Microsoft Endpoint Configuration Manager. This process is similar to refreshing a computer, but since you're replacing the device, you have to run the backup job separately from the deployment of Windows 10.
|
||||
|
||||
In this topic, you will create a backup-only task sequence that you run on PC0004 (the device you are replacing), deploy the PC0006 computer running Windows 10, and then restore this backup of PC0004 onto PC006. This is similar to the MDT replace process: [Replace a Windows 7 computer with a Windows 10 computer](../deploy-windows-mdt/replace-a-windows-7-computer-with-a-windows-10-computer.md).
|
||||
In this topic, you'll create a backup-only task sequence that you run on PC0004 (the device you're replacing), deploy the PC0006 computer running Windows 10, and then restore this backup of PC0004 onto PC006. This process is similar to the MDT replace process: [Replace a Windows 7 computer with a Windows 10 computer](../deploy-windows-mdt/replace-a-windows-7-computer-with-a-windows-10-computer.md).
|
||||
|
||||
## Infrastructure
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md).
|
||||
|
||||
For the purposes of this article, we will use one server computer (CM01) and two client computers (PC0004, PC0006).
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server.
|
||||
For the purposes of this article, we'll use one server computer (CM01) and two client computers (PC0004, PC0006).
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server.
|
||||
- Important: CM01 must include the **[State migration point](/configmgr/osd/get-started/manage-user-state#BKMK_StateMigrationPoint)** role for the replace task sequence used in this article to work.
|
||||
- PC0004 is a domain member client computer running Windows 7 SP1, or a later version of Windows, with the Configuration Manager client installed, that will be replaced.
|
||||
- PC0006 is a domain member client computer running Windows 10, with the Configuration Manager client installed, that will replace PC0004.
|
||||
@ -36,7 +37,7 @@ For the purposes of this article, we will use one server computer (CM01) and two
|
||||
|
||||
All servers are running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
All server and client computers referenced in this guide are on the same subnet. This is not required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
All server and client computers referenced in this guide are on the same subnet. This interrelation isn't required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>This article assumes that you have [configured Active Directory permissions](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md#configure-active-directory-permissions) in the specified OU for the **CM_JD** account, and the client's Active Directory computer account is in the **Contoso > Computers > Workstations** OU. Use the Active Directory Users and Computers console to review the location of computer objects and move them if needed.
|
||||
@ -70,15 +71,15 @@ The backup-only task sequence (named Replace Task Sequence).
|
||||
|
||||
## Associate the new device with the old computer
|
||||
|
||||
This section walks you through the process of associating a new, blank device (PC0006), with an existing computer (PC0004), for the purpose of replacing PC0004 with PC0006. PC0006 can be either a physical or virtual machine.
|
||||
This section walks you through the process of associating a new, blank device (PC0006), with an existing computer (PC0004), for replacing PC0004 with PC0006. PC0006 can be either a physical or virtual machine.
|
||||
|
||||
On **HV01** (if PC0006 is a VM) or in the PC0006 BIOS:
|
||||
|
||||
1. Make a note of the MAC address for PC0006. (If PC0006 is a virtual machine, you can see the MAC Address in the virtual machine settings.) In our example, the PC0006 MAC Address is 00:15:5D:0A:6A:96. Do not attempt to PXE boot PC0006 yet.
|
||||
1. Make a note of the MAC address for PC0006. (If PC0006 is a virtual machine, you can see the MAC Address in the virtual machine settings.) In our example, the PC0006 MAC Address is 00:15:5D:0A:6A:96. Don't attempt to PXE boot PC0006 yet.
|
||||
|
||||
On **CM01**:
|
||||
|
||||
2. Using the Configuration Manager console, in the Assets and Compliance workspace, right-click **Devices**, and then click **Import Computer Information**.
|
||||
2. When you're using the Configuration Manager console, in the Assets and Compliance workspace, right-click **Devices**, and then click **Import Computer Information**.
|
||||
3. On the **Select Source** page, select **Import single computer** and click **Next**.
|
||||
4. On the **Single Computer** page, use the following settings and then click **Next**:
|
||||
|
||||
@ -95,14 +96,14 @@ On **CM01**:
|
||||
7. On the **Choose additional collections** page, click **Add** and then select the **Install Windows 10 Enterprise x64** collection. Now, select the checkbox next to the Install Windows 10 Enterprise x64 collection you just added, and then click **Next**.
|
||||
8. On the **Summary** page, click **Next**, and then click **Close**.
|
||||
9. Select the **User State Migration** node and review the computer association in the right hand pane.
|
||||
10. Right-click the **PC0004/PC0006** association and click **View Recovery Information**. Note that a recovery key has been assigned already, but a user state store location has not.
|
||||
11. Review the **Install Windows 10 Enterprise x64** collection. Do not continue until you see the **PC0006** computer in the collection. You might have to update membership and refresh the collection again.
|
||||
10. Right-click the **PC0004/PC0006** association and click **View Recovery Information**. A recovery key has been assigned already, but a user state store location hasn't.
|
||||
11. Review the **Install Windows 10 Enterprise x64** collection. Don't continue until you see the **PC0006** computer in the collection. You might have to update membership and refresh the collection again.
|
||||
|
||||
## Create a device collection and add the PC0004 computer
|
||||
|
||||
On **CM01**:
|
||||
|
||||
1. Using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
1. When you're using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
|
||||
* General
|
||||
* Name: USMT Backup (Replace)
|
||||
@ -117,7 +118,7 @@ On **CM01**:
|
||||
|
||||
Use default settings for the remaining wizard pages, then click **Close**.
|
||||
|
||||
2. Review the **USMT Backup (Replace)** collection. Do not continue until you see the **PC0004** computer in the collection.
|
||||
2. Review the **USMT Backup (Replace)** collection. Don't continue until you see the **PC0004** computer in the collection.
|
||||
|
||||
## Create a new deployment
|
||||
|
||||
@ -145,7 +146,7 @@ This section assumes that you have a computer named PC0004 with the Configuratio
|
||||
|
||||
On **PC0004**:
|
||||
|
||||
1. If it is not already started, start the PC0004 computer and open the Configuration Manager control panel (control smscfgrc).
|
||||
1. If it's not already started, start the PC0004 computer and open the Configuration Manager control panel (control smscfgrc).
|
||||
2. On the **Actions** tab, select **Machine Policy Retrieval & Evaluation Cycle**, click **Run Now**, and then click **OK** in the popup dialog box that appears.
|
||||
|
||||
>[!NOTE]
|
||||
@ -161,8 +162,8 @@ Capturing the user state
|
||||
|
||||
On **CM01**:
|
||||
|
||||
6. Open the state migration point storage folder (ex: D:\Migdata) and verify that a sub-folder was created containing the USMT backup.
|
||||
7. Using the Configuration Manager console, in the Assets and Compliance workspace, select the **User State Migration** node, right-click the **PC0004/PC0006** association, and select **View Recovery Information**. Note that the object now also has a user state store location.
|
||||
6. Open the state migration point storage folder (ex: D:\Migdata) and verify that a subfolder was created containing the USMT backup.
|
||||
7. Using the Configuration Manager console, in the Assets and Compliance workspace, select the **User State Migration** node, right-click the **PC0004/PC0006** association, and select **View Recovery Information**. The object now also has a user state store location.
|
||||
|
||||
>[!NOTE]
|
||||
>It may take a few minutes for the user state store location to be populated.
|
||||
@ -176,7 +177,7 @@ On **PC0006**:
|
||||
* Password: pass@word1
|
||||
* Select a task sequence to execute on this computer: Windows 10 Enterprise x64 RTM
|
||||
|
||||
2. The setup now starts and does the following:
|
||||
2. The setup now starts and does the following steps:
|
||||
|
||||
* Installs the Windows 10 operating system
|
||||
* Installs the Configuration Manager client
|
||||
@ -184,7 +185,7 @@ On **PC0006**:
|
||||
* Installs the applications
|
||||
* Restores the PC0004 backup
|
||||
|
||||
When the process is complete, you will have a new Windows 10 computer in your domain with user data and settings restored. See the following examples:
|
||||
When the process is complete, you'll have a new Windows 10 computer in your domain with user data and settings restored. See the following examples:
|
||||
|
||||
<br>
|
||||
<br>
|
||||
|
||||
@ -27,28 +27,28 @@ The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Wi
|
||||
|
||||
An existing Configuration Manager infrastructure that is integrated with MDT is used for the following procedures. For more information about the setup for this article, see [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md).
|
||||
|
||||
For the purposes of this article, we will use one server computer (CM01) and one client computers (PC0004).
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide CM01 is a standalone primary site server.
|
||||
For the purposes of this article, we'll use one server computer (CM01) and one client computer (PC0004).
|
||||
- CM01 is a domain member server and Configuration Manager software distribution point. In this guide, CM01 is a standalone primary site server.
|
||||
- PC0004 is a domain member client computer running Windows 7 SP1, or a later version of Windows, with the Configuration Manager client installed, that will be upgraded to Windows 10.
|
||||
|
||||
All servers are running Windows Server 2019. However, an earlier, supported version of Windows Server can also be used.
|
||||
|
||||
All server and client computers referenced in this guide are on the same subnet. This is not required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
All server and client computers referenced in this guide are on the same subnet. This interrelation isn't required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso.com domain. Internet connectivity is also required to download OS and application updates.
|
||||
|
||||
## Add an OS upgrade package
|
||||
|
||||
Configuration Manager Current Branch includes a native in-place upgrade task. This task sequence differs from the MDT in-place upgrade task sequence in that it does not use a default OS image, but rather uses an [OS upgrade package](/configmgr/osd/get-started/manage-operating-system-upgrade-packages).
|
||||
Configuration Manager Current Branch includes a native in-place upgrade task. This task sequence differs from the MDT in-place upgrade task sequence in that it doesn't use a default OS image, but rather uses an [OS upgrade package](/configmgr/osd/get-started/manage-operating-system-upgrade-packages).
|
||||
|
||||
On **CM01**:
|
||||
|
||||
1. Using the Configuration Manager console, in the Software Library workspace, expand **Operating Systems**, right-click **Operating System Upgrade Packages**, and click **Add Operating System Upgrade Package**.
|
||||
2. On the **Data Source** page, under **Path**, click **Browse** and enter the UNC path to your media source. In this example, we have extracted the Windows 10 installation media to **\\\\cm01\\Sources$\\OSD\\UpgradePackages\\Windows 10**.
|
||||
3. If you have multiple image indexes in the installation media, select **Extract a specific image index from install.wim...** and choose the image index you want from the dropdown menu. In this example, we have chosen **Windows 10 Enterprise**.
|
||||
2. On the **Data Source** page, under **Path**, click **Browse** and enter the UNC path to your media source. In this example, we've extracted the Windows 10 installation media to **\\\\cm01\\Sources$\\OSD\\UpgradePackages\\Windows 10**.
|
||||
3. If you have multiple image indexes in the installation media, select **Extract a specific image index from install.wim...** and choose the image index you want from the dropdown menu. In this example, we've chosen **Windows 10 Enterprise**.
|
||||
4. Next to **Architecture**, select **x64**, choose a language from the dropdown menu next to **Language**, and then click **Next**.
|
||||
5. Next to **Name**, enter **Windows 10 x64 RTM** and then complete the wizard by clicking **Next** and **Close**.
|
||||
6. Distribute the OS upgrade package to the CM01 distribution point by right-clicking the **Windows 10 x64 RTM** OS upgrade package and then clicking **Distribute Content**.
|
||||
7. In the Distribute Content Wizard, add the CM01 distribution point, click **Next** and click **Close**.
|
||||
8. View the content status for the Windows 10 x64 RTM upgrade package. Do not continue until the distribution is completed (it might take a few minutes). You also can review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for the **STATMSG: ID=2301** line.
|
||||
8. View the content status for the Windows 10 x64 RTM upgrade package. Don't continue until the distribution is completed (it might take a few minutes). You also can review the D:\\Program Files\\Microsoft Configuration Manager\\Logs\\distmgr.log file and look for the **STATMSG: ID=2301** line.
|
||||
|
||||
## Create an in-place upgrade task sequence
|
||||
|
||||
@ -77,7 +77,7 @@ After you create the upgrade task sequence, you can create a collection to test
|
||||
|
||||
On **CM01**:
|
||||
|
||||
1. Using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
1. When you're using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
- General
|
||||
- Name: Windows 10 x64 in-place upgrade
|
||||
- Limited Collection: All Systems
|
||||
@ -89,7 +89,7 @@ On **CM01**:
|
||||
- Select Resources
|
||||
- Select PC0004
|
||||
|
||||
2. Review the Windows 10 x64 in-place upgrade collection. Do not continue until you see PC0004 in the collection.
|
||||
2. Review the Windows 10 x64 in-place upgrade collection. Don't continue until you see PC0004 in the collection.
|
||||
|
||||
## Deploy the Windows 10 upgrade
|
||||
|
||||
|
||||
Reference in New Issue
Block a user