From ba31438ad05d00b5609548eec4ad66184afa2689 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Tue, 23 Feb 2021 20:29:49 +0530
Subject: [PATCH 01/22] updated  adobe reader version and made words to bold

this is my own PR, I edited some paragraphs, I added an Adobe reader version number.
I successfully a few paragraphs  only, But remaining i need to edit. I will continue my work after merging this content.
Also, i  need  help from contributors with suggestions .
Thanking you
---
 .../deploy-a-windows-10-image-using-mdt.md    | 106 +++++++++---------
 1 file changed, 53 insertions(+), 53 deletions(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 2779d317f6..2017acc4d7 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -21,18 +21,18 @@ ms.topic: article
 **Applies to**
 -   Windows 10
 
-This topic will show you how to take your reference image for Windows 10 (that was just [created](create-a-windows-10-reference-image.md)), and deploy that image to your environment using the Microsoft Deployment Toolkit (MDT). 
+This topic will show you how to take your reference image for Windows 10 (that was just [created](create-a-windows-10-reference-image.md)), and deploy that image to your environment using the **Microsoft Deployment Toolkit (MDT)**. 
 
-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.
+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. 
+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
+- **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.
+**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)
 
@@ -45,14 +45,14 @@ These steps will show you how to configure an Active Directory account with the
 
 On **DC01**:
 
-1. Download the [Set-OUPermissions.ps1 script](https://go.microsoft.com/fwlink/p/?LinkId=619362) and copy it to the **C:\\Setup\\Scripts** directory on DC01.  This script configures permissions to allow the MDT_JD account to manage computer accounts in the contoso > Computers organizational unit.
-2. Create the MDT_JD service account by running the following command from an elevated Windows PowerShell prompt:
+1. Download the [Set-OUPermissions.ps1 script](https://go.microsoft.com/fwlink/p/?LinkId=619362) and copy it to the **C:\\Setup\\Scripts** directory on **DC01**.  This script configures permissions to allow the **MDT_JD** account to manage computer accounts in the contoso > Computers organizational unit.
+2. Create the **MDT_JD** service account by running the following command from an elevated **Windows PowerShell prompt**:
 
    ```powershell
    New-ADUser -Name MDT_JD -UserPrincipalName MDT_JD -path "OU=Service Accounts,OU=Accounts,OU=Contoso,DC=CONTOSO,DC=COM" -Description "MDT join domain account" -AccountPassword (ConvertTo-SecureString "pass@word1" -AsPlainText -Force) -ChangePasswordAtLogon $false -PasswordNeverExpires $true -Enabled $true 
    ```
 
-3. Next, run the Set-OuPermissions script to apply permissions to the **MDT\_JD** service account, enabling it to manage computer accounts in the Contoso / Computers OU. Run the following commands from an elevated Windows PowerShell prompt:
+3. Next, run the **Set-OuPermissions script** to apply permissions to the **MDT\_JD** service account, enabling it to manage computer accounts in the Contoso / Computers OU. Run the following commands from an elevated **Windows PowerShell prompt**:
 
    ```powershell
    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force
@@ -76,7 +76,7 @@ The following is a list of the permissions being granted:
 
 ## Step 2: Set up the MDT production deployment share
 
-Next, create a new MDT deployment share. You should not use the same deployment share that you used to create the reference image for a production deployment. Perform this procedure on the MDT01 server.
+Next, create a new **MDT** deployment share. You should not use the same deployment share that you used to create the reference image for a production deployment. Perform this procedure on the **MDT01** server.
 
 ### Create the MDT production deployment share
 
@@ -85,21 +85,21 @@ On **MDT01**:
 The steps for creating the deployment share for production are the same as when you created the deployment share for creating the custom reference image:
 
 1. Ensure you are signed on as: contoso\administrator.
-2. In the Deployment Workbench console, right-click **Deployment Shares** and select **New Deployment Share**.
+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.
+7. Using **File Explorer**, verify that you can access the **\\\\MDT01\\MDTProduction$** share.
 
 ### Configure permissions for the production deployment share
 
-To read files in the deployment share, you need to assign NTFS and SMB permissions to the MDT Build Account (MDT\_BA) for the **D:\\MDTProduction** folder
+To read files in the deployment share, you need to assign **NTFS** and **SMB** permissions to the **MDT Build Account (MDT\_BA)** for the **D:\\MDTProduction** folder
 
 On **MDT01**:
 
 1.  Ensure you are signed in as **contoso\\administrator**.
-2.  Modify the NTFS permissions for the **D:\\MDTProduction** folder by running the following command in an elevated Windows PowerShell prompt:
+2.  Modify the **NTFS** permissions for the **D:\\MDTProduction** folder by running the following command in an elevated **Windows PowerShell prompt**:
 
     ``` powershell
     icacls "D:\MDTProduction" /grant '"CONTOSO\MDT_BA":(OI)(CI)(M)'
@@ -112,33 +112,33 @@ The next step is to add a reference image into the deployment share with the set
 
 ### Add the Windows 10 Enterprise x64 RTM custom image
 
-In these steps, we assume that you have completed the steps in the [Create a Windows 10 reference image](create-a-windows-10-reference-image.md) topic, so you have a Windows 10 reference image at **D:\\MDTBuildLab\\Captures\REFW10X64-001.wim** on MDT01.
+In these steps, we assume that you have completed the steps in the [Create a Windows 10 reference image](create-a-windows-10-reference-image.md) topic, so you have a Windows 10 reference image at **D:\\MDTBuildLab\\Captures\REFW10X64-001.wim** on **MDT01**.
 
-1.  Using the Deployment Workbench, expand the **Deployment Shares** node, and then expand **MDT Production**; select the **Operating Systems** node, and create a folder named **Windows 10**.
+1.  Using the **Deployment Workbench**, expand the **Deployment Shares** node, and then expand **MDT Production**; select the **Operating Systems** node, and create a **folder** named **Windows 10**.
 2.  Right-click the **Windows 10** folder and select **Import Operating System**.
 3.  On the **OS Type** page, select **Custom image file** and click **Next**.
 4.  On the **Image** page, in the **Source file** text box, browse to **D:\\MDTBuildLab\\Captures\\REFW10X64-001.wim** and click **Next**.
 5.  On the **Setup** page, select the **Copy Windows 7, Windows Server 2008 R2, or later setup files from the specified path** option; in the **Setup source directory** text box, browse to **D:\\MDTBuildLab\\Operating Systems\\W10EX64RTM** and click **Next**.
 6.  On the **Destination** page, in the **Destination directory name** text box, type **W10EX64RTM**, click **Next** twice, and then click **Finish**.
-7.  After adding the operating system, double-click the added operating system name in the **Operating Systems / Windows 10** node and change the name to **Windows 10 Enterprise x64 RTM Custom Image**.
+7.  After adding the **Operating System**, double-click the added **Operating System** name in the **Operating Systems / Windows 10** node and change the name to **Windows 10 Enterprise x64 RTM Custom Image**.
 
 >[!NOTE]
->The reason for adding the setup files has changed since earlier versions of MDT. MDT 2010 used the setup files to install Windows. MDT uses DISM to apply the image; however, you still need the setup files because some components in roles and features are stored outside the main image.
+>The reason for adding the setup files has changed since earlier versions of **MDT**. **MDT 2010** used the setup files to install Windows. **MDT** uses **DISM** Command to apply the image; however, you still need the **setup files** because some components in **roles and features** are stored outside the main image.
  
 
-![imported OS](../images/fig2-importedos.png)
+![Imported OS](../images/fig2-importedos.png)
 
 ## Step 4: Add an application
 
-When you configure your MDT Build Lab deployment share, you can also add applications to the new deployment share before creating your task sequence. This section walks you through the process of adding an application to the MDT Production deployment share using Adobe Reader as an example.
+When you configure your **MDT Build Lab deployment** share, you can also add a**pplications** to the new deployment share before creating your task sequence. This section walks you through the process of adding an application to the **MDT Production deployment** share using **Adobe Reader** as an example.
 
 ### Create the install: Adobe Reader DC
 
 On **MDT01**:
 
-1. Download the Enterprise distribution version of [Adobe Acrobat Reader DC](https://get.adobe.com/reader/enterprise/) (AcroRdrDC1902120058_en_US.exe) to **D:\\setup\\adobe** on MDT01.
-2. Extract the .exe file that you downloaded to an .msi (ex: .\AcroRdrDC1902120058_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
-3. In the Deployment Workbench, expand the **MDT Production** node and navigate to the **Applications** node.
+1. Download the Enterprise distribution version of [**Adobe Acrobat Reader DC**](https://get.adobe.com/reader/enterprise/) (AcroRdrDC2100120140_en_US.exe) to **D:\\setup\\adobe** on MDT01.
+2. Extract the **.exe** file that you downloaded to an **.msi** (ex: .\AcroRdrDC2100120140_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
+3. In the **Deployment Workbench**, expand the **MDT Production** node and navigate to the **Applications** node.
 4. Right-click the **Applications** node, and create a new folder named **Adobe**.
 5. In the **Applications** node, right-click the **Adobe** folder and select **New Application**.
 6. On the **Application Type** page, select the **Application with source files** option and click **Next**.
@@ -153,7 +153,7 @@ The Adobe Reader application added to the Deployment Workbench.
 
 ## Step 5: Prepare the drivers repository
 
-In order to deploy Windows 10 with MDT successfully, you need drivers for the boot images and for the actual operating system. This section will show you how to add drivers for the boot image and operating system, using the following hardware models as examples:
+In order to deploy Windows 10 with **MDT** successfully, you need drivers for the boot images and for the actual operating system. This section will show you how to add drivers for the boot image and operating system, using the following hardware models as examples:
 -   Lenovo ThinkPad T420
 -   Dell Latitude 7390
 -   HP EliteBook 8560w
@@ -166,19 +166,19 @@ For boot images, you need to have storage and network drivers; for the operating
  
 ### Create the driver source structure in the file system
 
-The key to successful management of drivers for MDT, as well as for any other deployment solution, is to have a really good driver repository. From this repository, you import drivers into MDT for deployment, but you should always maintain the repository for future use.
+The key to successful management of drivers for **MDT**, as well as for any other deployment solution, is to have a really good driver repository. From this repository, you import drivers into MDT for deployment, but you should always maintain the repository for future use.
 
 On **MDT01**:
 
 > [!IMPORTANT]
 > In the steps below, it is critical that the folder names used for various computer makes and models exactly match the results of **wmic computersystem get model,manufacturer** on the target system.
 
-1.  Using File Explorer, create the **D:\\drivers** folder.
+1.  Using **File Explorer**, create the **D:\\drivers** folder.
 2.  In the **D:\\drivers** folder, create the following folder structure:
-    1.  WinPE x86
-    2.  WinPE x64
-    3.  Windows 10 x64
-3.  In the new Windows 10 x64 folder, create the following folder structure:
+    1.  **WinPE x86**
+    2.  **WinPE x64**
+    3.  **Windows 10 x64**
+3.  In the new **Windows 10 x64** folder, create the following folder structure:
     -   Dell Inc
         -   Latitude E7450
     -   Hewlett-Packard
@@ -193,12 +193,12 @@ On **MDT01**:
  
 ### Create the logical driver structure in MDT
 
-When you import drivers to the MDT driver repository, MDT creates a single instance folder structure based on driver class names. However, you can, and should, mimic the driver structure of your driver source repository in the Deployment Workbench. This is done by creating logical folders in the Deployment Workbench.
-1.  On MDT01, using Deployment Workbench, select the **Out-of-Box Drivers** node.
+When you import drivers to the **MDT driver repository**, **MDT** creates a single instance folder structure based on driver class names. However, you can, and should, mimic the driver structure of your driver source repository in the Deployment Workbench. This is done by creating logical folders in the Deployment Workbench.
+1.  On **MDT01**, using Deployment Workbench, select the **Out-of-Box Drivers** node.
 2.  In the **Out-Of-Box Drivers** node, create the following folder structure:
-    1.  WinPE x86
-    2.  WinPE x64
-    3.  Windows 10 x64
+    1.  **WinPE x86**
+    2.  **WinPE x64**
+    3.  **Windows 10 x64**
 3.  In the **Windows 10 x64** folder, create the following folder structure:
     -   Dell Inc
         -   Latitude E7450
@@ -209,7 +209,7 @@ When you import drivers to the MDT driver repository, MDT creates a single insta
     -   Microsoft Corporation
         -   Surface Laptop
 
-The preceding folder names should match the actual make and model values that MDT reads from devices during deployment. You can find out the model values for your machines by using the following command in Windows PowerShell:
+The preceding folder names should match the actual make and model values that MDT reads from devices during deployment. You can find out the model values for your machines by using the following command in **Windows PowerShell Prompt:
 
 ``` powershell
 Get-WmiObject -Class:Win32_ComputerSystem
@@ -220,7 +220,7 @@ Or, you can use this command in a normal command prompt:
 wmic csproduct get name
 ```
 
-If you want a more standardized naming convention, try the ModelAliasExit.vbs script from the Deployment Guys blog post entitled [Using and Extending Model Aliases for Hardware Specific Application Installation](https://go.microsoft.com/fwlink/p/?LinkId=619536).
+If you want a more standardized naming convention, try the **ModelAliasExit.vbs script** from the Deployment Guys blog post entitled [Using and Extending Model Aliases for Hardware Specific Application Installation](https://go.microsoft.com/fwlink/p/?LinkId=619536).
 
 ![drivers](../images/fig4-oob-drivers.png)
 
@@ -229,19 +229,19 @@ The Out-of-Box Drivers structure in the Deployment Workbench.
 ### Create the selection profiles for boot image drivers
 
 By default, MDT adds any storage and network drivers that you import to the boot images. However, you should add only the drivers that are necessary to the boot image. You can control which drivers are added by using selection profiles.
-The drivers that are used for the boot images (Windows PE) are Windows 10 drivers. If you can’t locate Windows 10 drivers for your device, a Windows 7 or Windows 8.1 driver will most likely work, but Windows 10 drivers should be your first choice.
+The drivers that are used for the boot images (Windows PE) are Windows 10 drivers. If you can’t locate **Windows 10** drivers for your device, a **Windows 7 or Windows 8.1** driver will most likely work, but Windows 10 drivers should be your first choice.
 
 On **MDT01**:
 
-1.  In the Deployment Workbench, under the **MDT Production** node, expand the **Advanced Configuration** node, right-click the **Selection Profiles** node, and select **New Selection Profile**.
-2.  In the New Selection Profile Wizard, create a selection profile with the following settings:
-    1.  Selection Profile name: WinPE x86
-    2.  Folders: Select the WinPE x86 folder in Out-of-Box Drivers.
+1.  In the **Deployment Workbench**, under the **MDT Production** node, expand the **Advanced Configuration** node, right-click the **Selection Profiles** node, and select **New Selection Profile**.
+2.  In the New **Selection Profile Wizard**, create a **selection profile** with the following settings:
+    1.  Selection Profile name: **WinPE x86**
+    2.  Folders: Select the **WinPE x86 folder** in **Out-of-Box** Drivers.
     3. Click **Next**, **Next** and **Finish**.
 3.  Right-click the **Selection Profiles** node again, and select **New Selection Profile**.
-4.  In the New Selection Profile Wizard, create a selection profile with the following settings:
-    1.  Selection Profile name: WinPE x64
-    2.  Folders: Select the WinPE x64 folder in Out-of-Box Drivers.
+4.  In the New **Selection Profile Wizard**, create a **selection profile** with the following settings:
+    1.  Selection Profile name: **WinPE x64**
+    2.  Folders: Select the **WinPE x64 folder** in **Out-of-Box** Drivers.
     3.  Click **Next**, **Next** and **Finish**.
 
 ![figure 5](../images/fig5-selectprofile.png)
@@ -250,22 +250,22 @@ Creating the WinPE x64 selection profile.
 
 ### Extract and import drivers for the x64 boot image
 
-Windows PE supports all the hardware models that we have, but here you learn to add boot image drivers to accommodate any new hardware that might require additional drivers. In this example, you add the latest Intel network drivers to the x64 boot image.
+**Windows PE** supports all the hardware models that we have, but here you learn to add boot image drivers to accommodate any new hardware that might require additional drivers. In this example, you add the latest Intel network drivers to the x64 boot image.
 
 On **MDT01**:
 
 1. Download **PROWinx64.exe** from Intel.com (ex: [PROWinx64.exe](https://downloadcenter.intel.com/downloads/eula/25016/Intel-Network-Adapter-Driver-for-Windows-10?httpDown=https%3A%2F%2Fdownloadmirror.intel.com%2F25016%2Feng%2FPROWinx64.exe)).
-2.  Extract PROWinx64.exe to a temporary folder - in this example to the **C:\\Tmp\\ProWinx64** folder.
-    a. **Note**: Extracting the .exe file manually requires an extraction utility. You can also run the .exe and it will self-extract files to the **%userprofile%\AppData\Local\Temp\RarSFX0** directory. This directory is temporary and will be deleted when the .exe terminates. 
-3.  Using File Explorer, create the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
+2.  Extract **PROWinx64.exe** to a temporary folder - in this example to the **C:\\Tmp\\ProWinx64** folder.
+    a. **Note**: Extracting the **.exe** file manually requires an extraction utility. You can also run the .exe and it will self-extract files to the **%userprofile%\AppData\Local\Temp\RarSFX0** directory. This directory is temporary and will be deleted when the **.exe** terminates. 
+3.  Using **File Explorer**, create the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
 4.  Copy the content of the **C:\\Tmp\\PROWinx64\\PRO1000\\Winx64\\NDIS64** folder to the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
-5.  In the Deployment Workbench, expand the **MDT Production** > **Out-of-Box Drivers** node, right-click the **WinPE x64** node, and select **Import Drivers**, and use the following Driver source directory to import drivers: **D:\\Drivers\\WinPE x64\\Intel PRO1000**.
+5.  In the **Deployment Workbench**, expand the **MDT Production** > **Out-of-Box Drivers** node, right-click the **WinPE x64** node, and select **Import Drivers**, and use the following Driver source directory to import drivers: **D:\\Drivers\\WinPE x64\\Intel PRO1000**.
 
 ### Download, extract, and import drivers
 
 ### For the Lenovo ThinkStation P500
 
-For the ThinkStation P500 model, you use the Lenovo ThinkVantage Update Retriever software to download the drivers. With Update Retriever, you need to specify the correct Lenovo Machine Type for the actual hardware (the first four characters of the model name). As an example, the Lenovo ThinkStation P500 model has the 30A6003TUS model name, meaning the Machine Type is 30A6.
+For the **ThinkStation P500** model, you use the Lenovo ThinkVantage Update Retriever software to download the drivers. With Update Retriever, you need to specify the correct Lenovo Machine Type for the actual hardware (the first four characters of the model name). As an example, the Lenovo ThinkStation P500 model has the 30A6003TUS model name, meaning the Machine Type is 30A6.
 
 ![ThinkStation image](../images/thinkstation.png)
 

From cc1a12eaebc07606c90855e7d820052e66cf330c Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:22:23 +0530
Subject: [PATCH 02/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 2017acc4d7..11753d97af 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -23,7 +23,7 @@ ms.topic: article
 
 This topic will show you how to take your reference image for Windows 10 (that was just [created](create-a-windows-10-reference-image.md)), and deploy that image to your environment using the **Microsoft Deployment Toolkit (MDT)**. 
 
-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.
+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 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**. 
 

From 4a4ba2dda0175c1cb8e35dd47c080a6ae7b50f5e Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:22:50 +0530
Subject: [PATCH 03/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 11753d97af..586ec55aa7 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -32,7 +32,7 @@ For the purposes of this topic, we will use four computers: **DC01, MDT01, HV01
 - **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.
+**MDT01** and **PC0005** are members of the domain contoso.com for the fictitious Contoso Corporation.  **HV01** is used to test the deployment of **PC0005** in a virtual environment.
 
    ![devices](../images/mdt-07-fig01.png)
 

From f719cd43215e0bb60b0edad159749646968b00a0 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:23:12 +0530
Subject: [PATCH 04/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 586ec55aa7..47c87e09b0 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -122,7 +122,7 @@ In these steps, we assume that you have completed the steps in the [Create a Win
 6.  On the **Destination** page, in the **Destination directory name** text box, type **W10EX64RTM**, click **Next** twice, and then click **Finish**.
 7.  After adding the **Operating System**, double-click the added **Operating System** name in the **Operating Systems / Windows 10** node and change the name to **Windows 10 Enterprise x64 RTM Custom Image**.
 
->[!NOTE]
+> [!NOTE]
 >The reason for adding the setup files has changed since earlier versions of **MDT**. **MDT 2010** used the setup files to install Windows. **MDT** uses **DISM** Command to apply the image; however, you still need the **setup files** because some components in **roles and features** are stored outside the main image.
  
 

From 5429df8bcd62e94713e1fb34ff58d2b98b53e420 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:23:49 +0530
Subject: [PATCH 05/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 47c87e09b0..9387540124 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -130,7 +130,7 @@ In these steps, we assume that you have completed the steps in the [Create a Win
 
 ## Step 4: Add an application
 
-When you configure your **MDT Build Lab deployment** share, you can also add a**pplications** to the new deployment share before creating your task sequence. This section walks you through the process of adding an application to the **MDT Production deployment** share using **Adobe Reader** as an example.
+When you configure your **MDT Build Lab deployment** share, you can also add **applications** to the new deployment share before creating your task sequence. This section walks you through the process of adding an application to the **MDT Production deployment** share using **Adobe Reader** as an example.
 
 ### Create the install: Adobe Reader DC
 

From 60f91e5deff68abb03d6b9b47b7bd09a0faa1f1b Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:24:11 +0530
Subject: [PATCH 06/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 9387540124..e96ae41179 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -123,7 +123,7 @@ In these steps, we assume that you have completed the steps in the [Create a Win
 7.  After adding the **Operating System**, double-click the added **Operating System** name in the **Operating Systems / Windows 10** node and change the name to **Windows 10 Enterprise x64 RTM Custom Image**.
 
 > [!NOTE]
->The reason for adding the setup files has changed since earlier versions of **MDT**. **MDT 2010** used the setup files to install Windows. **MDT** uses **DISM** Command to apply the image; however, you still need the **setup files** because some components in **roles and features** are stored outside the main image.
+> The reason for adding the setup files has changed since earlier versions of **MDT**. **MDT 2010** used the setup files to install Windows. **MDT** uses the **DISM** command to apply the image; however, you still need the **setup files** because some components in **roles and features** are stored outside the main image.
  
 
 ![Imported OS](../images/fig2-importedos.png)

From d027375bcff6484e46321f28cd8cfe38fa91d0ef Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:24:24 +0530
Subject: [PATCH 07/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index e96ae41179..300e73b186 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -137,7 +137,7 @@ When you configure your **MDT Build Lab deployment** share, you can also add **a
 On **MDT01**:
 
 1. Download the Enterprise distribution version of [**Adobe Acrobat Reader DC**](https://get.adobe.com/reader/enterprise/) (AcroRdrDC2100120140_en_US.exe) to **D:\\setup\\adobe** on MDT01.
-2. Extract the **.exe** file that you downloaded to an **.msi** (ex: .\AcroRdrDC2100120140_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
+2. Extract the **.exe** file that you downloaded to a **.msi** (ex: .\AcroRdrDC2100120140_en_US.exe -sfx_o"d:\setup\adobe\install\" -sfx_ne).
 3. In the **Deployment Workbench**, expand the **MDT Production** node and navigate to the **Applications** node.
 4. Right-click the **Applications** node, and create a new folder named **Adobe**.
 5. In the **Applications** node, right-click the **Adobe** folder and select **New Application**.

From 2932031718b27aa5a8947d1c082c7f67465246fb Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:24:42 +0530
Subject: [PATCH 08/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 300e73b186..fb16dd3c37 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -209,7 +209,7 @@ When you import drivers to the **MDT driver repository**, **MDT** creates a sing
     -   Microsoft Corporation
         -   Surface Laptop
 
-The preceding folder names should match the actual make and model values that MDT reads from devices during deployment. You can find out the model values for your machines by using the following command in **Windows PowerShell Prompt:
+The preceding folder names should match the actual make and model values that MDT reads from devices during deployment. You can find out the model values for your machines by using the following command in an elevated **Windows PowerShell prompt**:
 
 ``` powershell
 Get-WmiObject -Class:Win32_ComputerSystem

From 04f89ef9c4869c381b7f9b277f4f0be0c04c7ef9 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:24:55 +0530
Subject: [PATCH 09/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index fb16dd3c37..6b18f752b6 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -153,7 +153,7 @@ The Adobe Reader application added to the Deployment Workbench.
 
 ## Step 5: Prepare the drivers repository
 
-In order to deploy Windows 10 with **MDT** successfully, you need drivers for the boot images and for the actual operating system. This section will show you how to add drivers for the boot image and operating system, using the following hardware models as examples:
+In order to deploy Windows 10 with **MDT** successfully, you need drivers for the boot images and for the actual operating system. This section will show you how to add drivers for the boot images and operating system, using the following hardware models as examples:
 -   Lenovo ThinkPad T420
 -   Dell Latitude 7390
 -   HP EliteBook 8560w

From eda636b6ae45bc9e16d86aac34bd590d14d608e4 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:27:28 +0530
Subject: [PATCH 10/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 6b18f752b6..ac608d2f37 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -229,7 +229,7 @@ The Out-of-Box Drivers structure in the Deployment Workbench.
 ### Create the selection profiles for boot image drivers
 
 By default, MDT adds any storage and network drivers that you import to the boot images. However, you should add only the drivers that are necessary to the boot image. You can control which drivers are added by using selection profiles.
-The drivers that are used for the boot images (Windows PE) are Windows 10 drivers. If you can’t locate **Windows 10** drivers for your device, a **Windows 7 or Windows 8.1** driver will most likely work, but Windows 10 drivers should be your first choice.
+The drivers that are used for the boot images (Windows PE) are Windows 10 drivers. If you can’t locate **Windows 10** drivers for your device, a **Windows 7** or **Windows 8.1** driver will most likely work, but Windows 10 drivers should be your first choice.
 
 On **MDT01**:
 

From b397cda4516761e21f2b62245cc0405b908d8c6f Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:31:23 +0530
Subject: [PATCH 11/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index ac608d2f37..3b90fab699 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -234,7 +234,7 @@ The drivers that are used for the boot images (Windows PE) are Windows 10 driver
 On **MDT01**:
 
 1.  In the **Deployment Workbench**, under the **MDT Production** node, expand the **Advanced Configuration** node, right-click the **Selection Profiles** node, and select **New Selection Profile**.
-2.  In the New **Selection Profile Wizard**, create a **selection profile** with the following settings:
+2.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:
     1.  Selection Profile name: **WinPE x86**
     2.  Folders: Select the **WinPE x86 folder** in **Out-of-Box** Drivers.
     3. Click **Next**, **Next** and **Finish**.

From 800fe3abf2c9e38348d17cd51432f2b96ae58bfd Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:31:42 +0530
Subject: [PATCH 12/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 3b90fab699..0aa865e362 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -239,7 +239,7 @@ On **MDT01**:
     2.  Folders: Select the **WinPE x86 folder** in **Out-of-Box** Drivers.
     3. Click **Next**, **Next** and **Finish**.
 3.  Right-click the **Selection Profiles** node again, and select **New Selection Profile**.
-4.  In the New **Selection Profile Wizard**, create a **selection profile** with the following settings:
+4.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:
     1.  Selection Profile name: **WinPE x64**
     2.  Folders: Select the **WinPE x64 folder** in **Out-of-Box** Drivers.
     3.  Click **Next**, **Next** and **Finish**.

From f8fb238d7997a6cc56e28f75a61f24c1ffa37baf Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:31:55 +0530
Subject: [PATCH 13/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 0aa865e362..c57ab65032 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -25,7 +25,7 @@ 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 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**. 
+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 

From 22a12e714123031d004e64c282ae1da811670de1 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:32:09 +0530
Subject: [PATCH 14/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index c57ab65032..b3075c2cfa 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -94,7 +94,7 @@ The steps for creating the deployment share for production are the same as when
 
 ### Configure permissions for the production deployment share
 
-To read files in the deployment share, you need to assign **NTFS** and **SMB** permissions to the **MDT Build Account (MDT\_BA)** for the **D:\\MDTProduction** folder
+To read files in the deployment share, you need to assign **NTFS** and **SMB** permissions to the **MDT Build Account (MDT\_BA)** for the **D:\\MDTProduction** folder.
 
 On **MDT01**:
 

From 1905cb6c08e9bc2fc99e8d50223727abbba1e68d Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:32:23 +0530
Subject: [PATCH 15/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index b3075c2cfa..1ab83e7066 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -236,7 +236,7 @@ On **MDT01**:
 1.  In the **Deployment Workbench**, under the **MDT Production** node, expand the **Advanced Configuration** node, right-click the **Selection Profiles** node, and select **New Selection Profile**.
 2.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:
     1.  Selection Profile name: **WinPE x86**
-    2.  Folders: Select the **WinPE x86 folder** in **Out-of-Box** Drivers.
+    2.  Folders: Select the **WinPE x86 folder** in **Out-of-Box Drivers**.
     3. Click **Next**, **Next** and **Finish**.
 3.  Right-click the **Selection Profiles** node again, and select **New Selection Profile**.
 4.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:

From 112543582b835f1ac483441fa0192abfef96a1c7 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:32:40 +0530
Subject: [PATCH 16/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 1ab83e7066..ad33d40fd6 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -250,7 +250,7 @@ Creating the WinPE x64 selection profile.
 
 ### Extract and import drivers for the x64 boot image
 
-**Windows PE** supports all the hardware models that we have, but here you learn to add boot image drivers to accommodate any new hardware that might require additional drivers. In this example, you add the latest Intel network drivers to the x64 boot image.
+**Windows PE** supports all the hardware models that we have, but here you learn how to add boot image drivers to accommodate any new hardware that might require additional drivers. In this example, you add the latest Intel network drivers to the x64 boot image.
 
 On **MDT01**:
 

From 5ddf048a4a6fb22960678a7bd1bd514b054015ea Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:33:05 +0530
Subject: [PATCH 17/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index ad33d40fd6..9fdb2b3c3e 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -242,7 +242,7 @@ On **MDT01**:
 4.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:
     1.  Selection Profile name: **WinPE x64**
     2.  Folders: Select the **WinPE x64 folder** in **Out-of-Box** Drivers.
-    3.  Click **Next**, **Next** and **Finish**.
+    3.  Click **Next**, **Next**, and **Finish**.
 
 ![figure 5](../images/fig5-selectprofile.png)
 

From 4aa7f8847ef6a7b141b9d8e6d0c9a36c8a6a0160 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:33:17 +0530
Subject: [PATCH 18/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 9fdb2b3c3e..e2ca2fafc0 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -237,7 +237,7 @@ On **MDT01**:
 2.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:
     1.  Selection Profile name: **WinPE x86**
     2.  Folders: Select the **WinPE x86 folder** in **Out-of-Box Drivers**.
-    3. Click **Next**, **Next** and **Finish**.
+    3. Click **Next**, **Next**, and **Finish**.
 3.  Right-click the **Selection Profiles** node again, and select **New Selection Profile**.
 4.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:
     1.  Selection Profile name: **WinPE x64**

From 7918ccd38d147a892cf0ead86df0b389af6dbb1b Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:33:31 +0530
Subject: [PATCH 19/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index e2ca2fafc0..b64a3b7a0b 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -241,7 +241,7 @@ On **MDT01**:
 3.  Right-click the **Selection Profiles** node again, and select **New Selection Profile**.
 4.  In the **New Selection Profile Wizard**, create a **selection profile** with the following settings:
     1.  Selection Profile name: **WinPE x64**
-    2.  Folders: Select the **WinPE x64 folder** in **Out-of-Box** Drivers.
+    2.  Folders: Select the **WinPE x64 folder** in **Out-of-Box Drivers**.
     3.  Click **Next**, **Next**, and **Finish**.
 
 ![figure 5](../images/fig5-selectprofile.png)

From cc3f83cf159fea69f586d754c614dccbbe224101 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:35:46 +0530
Subject: [PATCH 20/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index b64a3b7a0b..bf3cde3a44 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -259,7 +259,7 @@ On **MDT01**:
     a. **Note**: Extracting the **.exe** file manually requires an extraction utility. You can also run the .exe and it will self-extract files to the **%userprofile%\AppData\Local\Temp\RarSFX0** directory. This directory is temporary and will be deleted when the **.exe** terminates. 
 3.  Using **File Explorer**, create the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
 4.  Copy the content of the **C:\\Tmp\\PROWinx64\\PRO1000\\Winx64\\NDIS64** folder to the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
-5.  In the **Deployment Workbench**, expand the **MDT Production** > **Out-of-Box Drivers** node, right-click the **WinPE x64** node, and select **Import Drivers**, and use the following Driver source directory to import drivers: **D:\\Drivers\\WinPE x64\\Intel PRO1000**.
+5.  In the **Deployment Workbench**, expand the **MDT Production** > **Out-of-Box Drivers** node, right-click the **WinPE x64** node, select **Import Drivers**, and use the following driver source directory to import drivers: **D:\\Drivers\\WinPE x64\\Intel PRO1000**.
 
 ### Download, extract, and import drivers
 

From 6ab718e9dd7c5188305bc84ff7d873b8ea988446 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:45:39 +0530
Subject: [PATCH 21/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md    | 1 -
 1 file changed, 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index bf3cde3a44..e7c0e7dbde 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -256,7 +256,6 @@ On **MDT01**:
 
 1. Download **PROWinx64.exe** from Intel.com (ex: [PROWinx64.exe](https://downloadcenter.intel.com/downloads/eula/25016/Intel-Network-Adapter-Driver-for-Windows-10?httpDown=https%3A%2F%2Fdownloadmirror.intel.com%2F25016%2Feng%2FPROWinx64.exe)).
 2.  Extract **PROWinx64.exe** to a temporary folder - in this example to the **C:\\Tmp\\ProWinx64** folder.
-    a. **Note**: Extracting the **.exe** file manually requires an extraction utility. You can also run the .exe and it will self-extract files to the **%userprofile%\AppData\Local\Temp\RarSFX0** directory. This directory is temporary and will be deleted when the **.exe** terminates. 
 3.  Using **File Explorer**, create the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
 4.  Copy the content of the **C:\\Tmp\\PROWinx64\\PRO1000\\Winx64\\NDIS64** folder to the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
 5.  In the **Deployment Workbench**, expand the **MDT Production** > **Out-of-Box Drivers** node, right-click the **WinPE x64** node, select **Import Drivers**, and use the following driver source directory to import drivers: **D:\\Drivers\\WinPE x64\\Intel PRO1000**.

From 8191fb51fe1df989de32006b8e982410342d4a50 Mon Sep 17 00:00:00 2001
From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:45:55 +0530
Subject: [PATCH 22/22] Update
 windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md

accepted

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 .../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index e7c0e7dbde..355ea08482 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -255,7 +255,7 @@ Creating the WinPE x64 selection profile.
 On **MDT01**:
 
 1. Download **PROWinx64.exe** from Intel.com (ex: [PROWinx64.exe](https://downloadcenter.intel.com/downloads/eula/25016/Intel-Network-Adapter-Driver-for-Windows-10?httpDown=https%3A%2F%2Fdownloadmirror.intel.com%2F25016%2Feng%2FPROWinx64.exe)).
-2.  Extract **PROWinx64.exe** to a temporary folder - in this example to the **C:\\Tmp\\ProWinx64** folder.
+2.  Extract **PROWinx64.exe** to a temporary folder - in this example to the **C:\\Tmp\\ProWinx64** folder. Note that extracting the **.exe** file manually requires an extraction utility. You can also run the .exe and it will self-extract files to the **%userprofile%\AppData\Local\Temp\RarSFX0** directory. This directory is temporary and will be deleted when the **.exe** terminates.
 3.  Using **File Explorer**, create the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
 4.  Copy the content of the **C:\\Tmp\\PROWinx64\\PRO1000\\Winx64\\NDIS64** folder to the **D:\\Drivers\\WinPE x64\\Intel PRO1000** folder.
 5.  In the **Deployment Workbench**, expand the **MDT Production** > **Out-of-Box Drivers** node, right-click the **WinPE x64** node, select **Import Drivers**, and use the following driver source directory to import drivers: **D:\\Drivers\\WinPE x64\\Intel PRO1000**.