fresh build 3/11/16

This commit is contained in:
Brian Lich
2016-03-11 16:58:05 -08:00
parent be55b9a0bb
commit c06b42d84a
726 changed files with 1340 additions and 618 deletions

View File

@ -1,8 +1,9 @@
---
title: Monitor the Windows 10 deployment with Configuration Manager (Windows 10)
description: In this topic, you will learn how to monitor a Windows 10 deployment that was started previously using Microsoft System Center 2012 R2 Configuration Manager and the Microsoft Deployment Toolkit (MDT) Deployment Workbench.
description: In this topic you will learn how to monitor a Windows 10 deployment that was started previously using Microsoft System Center 2012 R2 Configuration Manager and the Microsoft Deployment Toolkit (MDT) Deployment Workbench.
MSHAttr: PreferredLib /library
ms.assetid: 4863c6aa-6369-4171-8e1a-b052ca195fce
keywords: ["deploy, upgrade"]
keywords: ["deploy upgrade"]
ms.prod: W10
ms.mktglfcycl: deploy
ms.sitesec: library
@ -16,10 +17,6 @@ author: CFaw
- Windows 10
**In this article**
- [Related topics](#related-topics)
In this topic, you will learn how to monitor a Windows 10 deployment that was started previously using Microsoft System Center 2012 R2 Configuration Manager and the Microsoft Deployment Toolkit (MDT) Deployment Workbench. You will also use the Deployment Workbench to access the computer remotely via the Microsoft Diagnostics and Recovery Toolkit (DaRT) Remote Connection feature.
For the purposes of this topic, we will use four machines: DC01, CM01, and PC0001. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard. PC0001 is a Unified Extensible Firmware Interface (UEFI) machine to which Windows 10 Enterprise has been deployed. DC01, CM01, and PC0001 are all 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](deploy-windows-81-with-the-microsoft-deployment-toolkit.md).