all topics rewritten

windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image.md

@@ -109,7 +109,7 @@ On **MDT01**:
     - Full set of source files
     - Source directory: (location of your source files)
     - Destination directory name: <b>W10EX64RTM</b>
-5. After adding the operating system, in the **Operating Systems / Windows 10** folder, double-click the added operating system name in the **Operating System** node and change the name to: **Windows 10 Enterprise x64 RTM Default Image**. See the following example.
+5. After adding the operating system, in the **Operating Systems / Windows 10** folder, double-click it and change the name to: **Windows 10 Enterprise x64 RTM Default Image**. See the following example.
 
     ![Default image](../images/deployment-workbench01.png)
 
@@ -419,7 +419,8 @@ To configure the rules for the MDT Build Lab deployment share:
 On **MDT01**:
 
 1.  Using the Deployment Workbench, right-click the **MDT Build Lab** deployment share and select **Properties**.
-2.  Select the **Rules** tab and replace the existing content with the following information: (edit the settings as needed to match your deployment)
+2.  Select the **Rules** tab and replace the existing content with the following information (edit the settings as needed to match your deployment). For example, If you do not have a WSUS server in your environment, delete the **WSUSServer** line from the configuration:
+
     ``` 
     [Settings]
     Priority=Default
@@ -457,7 +458,7 @@ On **MDT01**:
     ![figure 11](../images/mdt-rules.png)
 
     The server-side rules for the MDT Build Lab deployment share.
-
+ 
 3.  Click **Edit Bootstrap.ini** and modify using the following information:
 
     ``` 

windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

@@ -25,12 +25,19 @@ This topic will show you how to take your reference image for Windows 10 (that
 
 We will prepare for this by creating an MDT deployment share that is used solely for image deployment. Separating the processes of creating reference images from the processes used to deploy them in production allows greater control of on both processes. We will configure Active Directory permissions, configure the deployment share, create a new task sequence, and add applications, drivers, and rules.
 
-For the purposes of this topic, we will use four computers: DC01, MDT01, HV01 and PC0005. DC01 is a domain controller, MDT01 is a Windows Server 2019 domain member server, HV01 is a Hyper-V server, and PC0005 is a blank device to which we will deploy Windows 10. MDT01 and PC0005 are members of the domain contoso.com for the fictitious Contoso Corporation.  HV01 used to test deployment of PC0005 in a virtual environment.
+For the purposes of this topic, we will use four computers: DC01, MDT01, HV01 and PC0005. 
+
+- DC01 is a domain controller 
+- MDT01 is a domain member server 
+- HV01 is a Hyper-V server 
+- PC0005 is a blank device to which we will deploy Windows 10
+
+MDT01 and PC0005 are members of the domain contoso.com for the fictitious Contoso Corporation.  HV01 used to test deployment of PC0005 in a virtual environment.
 
    ![devices](../images/mdt-07-fig01.png)
 
 >[!NOTE]
->For important details about the setup for the procedures in this article, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
+>For details about the setup for the procedures in this article, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
 
 ## Step 1: Configure Active Directory permissions
 

windows/deployment/deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md

@@ -21,50 +21,59 @@ ms.topic: article
 **Applies to**
 -   Windows 10
 
-The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a Microsoft Deployment Toolkit (MDT) 2013 Update 2 task sequence to completely automate the process.
+The simplest path to upgrade PCs that are currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. 
 
-## Proof-of-concept environment
+>[!TIP]
+>In-place upgrade is the preferred method to use when migrating from Windows 10 to a later release of Windows 10, and is also a preferred method for upgrading from Windows 7 or 8.1 if you do not plan to significantly change the device's configuration or applications. MDT includes an in-place upgrade task sequence template that makes the process really simple. 
 
-For the purposes of this topic, we will use four machines: DC01, MDT01, and PC0001. DC01 is a domain controller and MDT01 is a Windows Server 2012 R2 standard machine, fully patched with the latest security updates, and configured as a member server in the fictional contoso.com domain. PC0001 is a machine with Windows 7 SP1, targeted for the Windows 10 upgrade. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
+In-place upgrade differs from [computer refresh](refresh-a-windows-7-computer-with-windows-10.md) in that you cannot use a custom image to perform the in-place upgrade. In this article we will add a default Windows 10 image to the production deployment share specifically to perform an in-place upgrade.
 
-![fig 1](../images/upgrademdt-fig1-machines.png)
+Four computers are used in this topic: DC01, MDT01, and PC0002. 
 
-Figure 1. The machines used in this topic.
+- DC01 is a domain controller for the contoso.com domain
+- MDT01 is a domain member server 
+- PC0002 is a domain member computer running Windows 7 SP1, targeted for the Windows 10 upgrade
 
-## Set up the upgrade task sequence
+![computers](../images/mdt-upgrade.png)
 
-MDT adds support for Windows 10 deployment, including a new in-place upgrade task sequence template that makes the process really simple.
+The computers used in this topic.
+
+>[!NOTE]
+>For details about the setup for the procedures in this article, please see [Prepare for deployment with MDT](prepare-for-windows-deployment-with-mdt.md).
+
+If you have already completed all the steps in [Deploy a Windows 10 image using MDT](deploy-a-windows-10-image-using-mdt), then you already have a deployment share and you can skip to [Add Windows 10 Enterprise x64 (full source)](#add-windows-10-enterprise-x64-full-source).
 
 ## Create the MDT production deployment share
 
-The steps to create the deployment share for production are the same as when you created the deployment share to create the custom reference image:
+On **MDT01**:
 
-1. On MDT01, log on as Administrator in the CONTOSO domain with a password of <strong>P@ssw0rd</strong>.
-2. Using the Deployment Workbench, right-click **Deployment Shares** and select **New Deployment Share**.
-3. On the **Path** page, in the **Deployment share path** text box, type **E:\\MDTProduction**, and then click **Next**.
-4. On the **Share** page, in the **Share name** text box, type **MDTProduction$**, and then click **Next**.
-5. On the **Descriptive Name** page, in the **Deployment share** description text box, type **MDT Production**, and then click **Next**.
+1. Ensure you are signed on as: contoso\administrator.
+2. In the Deployment Workbench console, right-click **Deployment Shares** and select **New Deployment Share**.
+3. On the **Path** page, in the **Deployment share path** text box, type **D:\\MDTProduction** and click **Next**.
+4. On the **Share** page, in the **Share name** text box, type **MDTProduction$** and click **Next**.
+5. On the **Descriptive Name** page, in the **Deployment share description** text box, type **MDT Production** and click **Next**.
 6. On the **Options** page, accept the default settings and click **Next** twice, and then click **Finish**.
 7. Using File Explorer, verify that you can access the **\\\\MDT01\\MDTProduction$** share.
 
-## Add Windows 10 Enterprise x64 (full source)
+## Add Windows 10 Enterprise x64 (full source)
 
-In these steps we assume that you have copied the content of a Windows 10 Enterprise x64 ISO to the E:\\Downloads\\Windows 10 Enterprise x64 folder.
+>If you have already have a Windows 10 [reference image](create-a-windows-10-reference-image.md) in the **MDT Build Lab** deployment share, you can use the deployment workbench to copy and paste this image from the MDT Build Lab share to the MDT Production share, and skip the steps below that will create this image again.
 
-1.  Using the Deployment Workbench, expand the **Deployment Shares** node, and then expand **MDT Production**.
-2.  Right-click the **Operating Systems** node, and create a new folder named **Windows 10**.
-3.  Expand the **Operating Systems** node, right-click the **Windows 10** folder, and select **Import Operating System**. Use the following settings for the Import Operating System Wizard:
-    -   Full set of source files
-    -   Source directory: E:\\Downloads\\Windows 10 Enterprise x64
-    -   Destination directory name: W10EX64RTM
-4.  After you add the operating system, in the **Operating Systems / Windows 10** folder, double-click the added operating system name in the **Operating System** node and change the name to the following: **Windows 10 Enterprise x64 RTM Default Image**
+On **MDT01**:
 
-![figure 2](../images/upgrademdt-fig2-importedos.png)
-
-Figure 2. The imported Windows 10 operating system after you rename it.
+1. Sign in as **contoso\\administrator** and copy the content of a Windows 10 Enterprise x64 DVD/ISO to the **D:\\Downloads\\Windows 10 Enterprise x64** folder on MDT01, or just insert the DVD or mount an ISO on MDT01.
+2. Using the Deployment Workbench, expand the **Deployment Shares** node, and then expand **MDT Production**.
+3. Right-click the **Operating Systems** node, and create a new folder named **Windows 10**.
+4. Expand the **Operating Systems** node, right-click the **Windows 10** folder, and select **Import Operating System**. Use the following settings for the Import Operating System Wizard:
+    - Full set of source files
+    - Source directory: (location of your source files)
+    - Destination directory name: <b>W10EX64RTM</b>
+5. After adding the operating system, in the **Operating Systems / Windows 10** folder, double-click it and change the name to: **Windows 10 Enterprise x64 RTM Default Image**.
 
 ## Create a task sequence to upgrade to Windows 10 Enterprise
 
+On **MDT01**:
+
 1.  Using the Deployment Workbench, select **Task Sequences** in the **MDT Production** node, and create a folder named **Windows 10**.
 2.  Right-click the new **Windows 10** folder and select **New Task Sequence**. Use the following settings for the New Task Sequence Wizard:
     -   Task sequence ID: W10-X64-UPG
@@ -72,33 +81,32 @@ Figure 2. The imported Windows 10 operating system after you rename it.
     -   Template: Standard Client Upgrade Task Sequence
     -   Select OS: Windows 10 Enterprise x64 RTM Default Image
     -   Specify Product Key: Do not specify a product key at this time
-    -   Full Name: Contoso
     -   Organization: Contoso
-    -   Internet Explorer home page: about:blank
-    -   Admin Password: Do not specify an Administrator Password at this time
-
-![figure 3](../images/upgrademdt-fig3-tasksequence.png)
-
-Figure 3. The task sequence to upgrade to Windows 10.
+    -   Admin Password: Do not specify an Administrator password at this time
 
 ## Perform the Windows 10 upgrade
 
-To initiate the in-place upgrade, perform the following steps on PC0003 (currently running Windows 7 SP1).
+To initiate the in-place upgrade, perform the following steps on PC0002 (the device to be upgraded).
+
+On **PC0002**:
 
 1. Start the MDT deployment wizard by running the following command: **\\\\MDT01\\MDTProduction$\\Scripts\\LiteTouch.vbs**
-2. Select the **Windows 10 Enterprise x64 RTM Upgrade** task sequence, and then click **Next**.
-
-   ![figure 4](../images/upgrademdt-fig4-selecttask.png)
-
-   Figure 4. Upgrade task sequence.
-    
-3. On the **Credentials** tab, specify the **MDT\_BA** account, <strong>P@ssw0rd</strong> password, and **CONTOSO** for the domain. (Some or all of these values can be specified in Bootstrap.ini so they are automatically populated.)
+2. Select the **Windows 10 Enterprise x64 RTM Upgrade** task sequence, and then click **Next**. 
+3. Select one or more applications to install (will appear if you use custom image): Install - Adobe Reader
 4. On the **Ready** tab, click **Begin** to start the task sequence.
    When the task sequence begins, it automatically initiates the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
 
-![figure 5](../images/upgrademdt-fig5-winupgrade.png)
+![upgrade1](../images/upgrademdt-fig5-winupgrade.png)
 
-Figure 5. Upgrade from Windows 7 to Windows 10 Enterprise x64 with a task sequence.
+<br>
+
+![upgrade2](../images/mdt-upgrade-proc.png)
+
+<br>
+
+![upgrade3](../images/mdt-post-upg.png)
+
+Upgrading to Windows 10 with an MDT task sequence
 
 After the task sequence completes, the computer will be fully upgraded to Windows 10.