From f933f6a1615f6f4ad52003405d5eafa8af15d0f9 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Fri, 6 Mar 2020 08:42:07 -0800 Subject: [PATCH] edits --- .../configuration-manager-components-osd.md | 25 ++----------------- ...ntegrate-configuration-manager-with-mdt.md | 16 +++++++----- 2 files changed, 12 insertions(+), 29 deletions(-) diff --git a/windows/deployment/deploy-windows-cm/configuration-manager-components-osd.md b/windows/deployment/deploy-windows-cm/configuration-manager-components-osd.md index bc6ac0c2d3..b54c267cd8 100644 --- a/windows/deployment/deploy-windows-cm/configuration-manager-components-osd.md +++ b/windows/deployment/deploy-windows-cm/configuration-manager-components-osd.md @@ -15,29 +15,11 @@ author: greg-lindsay ms.topic: article --- -# Get started deploying Windows 10 with Configuration Manager +## Components of Configuration Manager operating system deployment (OSD) **Applies to** - Windows 10 -If you have Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT). - ->[!NOTE] ->See [Scenarios to deploy enterprise operating systems with Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems) for general guidance on all available options for OS deployment with Configuration Manager. The articles presented here provide step by step guidance for common Windows 10-specific deployment scenarios. - -For the purposes of this topic, we will use four computers: DC01, CM01, PC0003, and PC0004. -- DC01 is a domain controller for the contoso.com domain running Windows Server 2019. -- CM01 is a domain member server unning Windows Server 2019. -- PC0003 and PC0004 are computers running Windows 7 SP1 to which Windows 10 will be deployed via refresh and replace scenarios, respectively. - -All servers and clients are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Prepare for deployment with MDT](../deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md). - -![figure 1](../images/mdt-06-fig01.png) - -The computers used in this topic. - -## Components of Configuration Manager operating system deployment - Operating system deployment with Configuration Manager is part of the normal software distribution infrastructure, but there are additional components. For example, operating system deployment in Configuration Manager may use the State Migration Point role, which is not 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. @@ -50,9 +32,7 @@ Operating system deployment with Configuration Manager is part of the normal sof - **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 pretty much like the sequences in MDT Lite Touch, and they are 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 additional task sequence templates to Configuration Manager. - **Note**  Configuration Manager SP1 along with the Windows Assessment and Deployment Kit (ADK) for Windows 10 are required to support management and deployment of Windows 10. - -   + **Note**  The Windows Assessment and Deployment Kit (ADK) for Windows 10 is also required to support management and deployment of Windows 10. ## See also @@ -60,6 +40,5 @@ Operating system deployment with Configuration Manager is part of the normal sof - [Windows deployment tools](../windows-deployment-scenarios-and-tools.md)
- [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md)
- [Upgrade to Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md)
-- [Deploy Windows To Go in your organization](../deploy-windows-to-go.md)
- [Sideload Windows Store apps](https://technet.microsoft.com/library/dn613831.aspx)
- [Windows ADK for Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=526803) diff --git a/windows/deployment/deploy-windows-cm/integrate-configuration-manager-with-mdt.md b/windows/deployment/deploy-windows-cm/integrate-configuration-manager-with-mdt.md index 225b30822a..03529bad04 100644 --- a/windows/deployment/deploy-windows-cm/integrate-configuration-manager-with-mdt.md +++ b/windows/deployment/deploy-windows-cm/integrate-configuration-manager-with-mdt.md @@ -21,15 +21,19 @@ ms.topic: article **Applies to** - Windows 10 -This topic will help you understand the benefits of integrating the Microsoft Deployment Toolkit with Microsoft System Center 2012 R2 Configuration Manager SP1 when you deploy a new or updated version of the Windows operating system. -MDT is a free, supported download from Microsoft that adds approximately 280 enhancements to Windows operating system deployment with System Center 2012 R2 Configuration Manager SP1. It is, therefore, recommended that you utilize MDT when deploying the Windows operating system with Configuration Manager SP1. In addition to integrating MDT with Configuration Manager, we also recommend using MDT Lite Touch to create the Windows 10 reference images used in Configuration Manager. 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). +This topic will help you understand the benefits of integrating the Microsoft Deployment Toolkit (MDT) with Microsoft Endpoint Configuration Manager when you deploy a new or updated version of the Windows operating system. + +MDT is a free, supported download from Microsoft that adds approximately 280 enhancements to Windows operating system deployment with Configuration Manager. It is therefore recommended that you utilize MDT when deploying the Windows operating system with Configuration Manager. In addition to integrating MDT with Configuration Manager, we also recommend using MDT Lite Touch to create the Windows 10 reference images used in Configuration Manager. 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). ## Why integrate MDT with Configuration Manager As noted above, MDT adds many enhancements to Configuration Manager. While these enhancements are called Zero Touch, that name does not reflect how deployment is conducted. The following sections provide a few samples of the 280 enhancements that MDT adds to Configuration Manager. -> [!Note] -> Microsoft Deployment Toolkit requires you to install [Windows PowerShell 2.0 Engine](https://docs.microsoft.com/powershell/scripting/install/installing-the-windows-powershell-2.0-engine) on your server. +>[!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 @@ -96,8 +100,8 @@ 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: - In a deployment project, it is typically much faster to create a reference image using MDT Lite Touch than Configuration Manager. -- You can use the same image for every type of operating system deployment - Microsoft Virtual Desktop Infrastructure (VDI), Microsoft System Center 2012 R2 Virtual Machine Manager (SCVMM), MDT, Configuration Manager, Windows Deployment Services (WDS), and more. -- Microsoft System Center 2012 R2 performs deployment in the LocalSystem context. This means that you cannot 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. +- 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 cannot 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 does not 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 is automatically captured. - MDT Lite Touch does not require any infrastructure and is easy to delegate.