edits

windows/deployment/deploy-windows-cm/create-a-task-sequence-with-configuration-manager-and-mdt.md

@@ -27,7 +27,7 @@ In this article, you will learn how to create a Configuration Manager task seque
 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.  
 
- 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#configure-active-directory-permissions) for the **CM_JD** account are required for the task sequence to work properly.
+ 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.
 
 ## Create a task sequence using the MDT Integration Wizard
 
@@ -134,7 +134,6 @@ Next, see [Finalize the operating system configuration for Windows 10 deployment
 
 ## Related topics
 
-[Integrate Configuration Manager with MDT](integrate-configuration-manager-with-mdt.md)<br>
 [Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)<br>
 [Create a custom Windows PE boot image with Configuration Manager](../deploy-windows-cm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)<br>
 [Add a Windows 10 operating system image using Configuration Manager](../deploy-windows-cm/add-a-windows-10-operating-system-image-using-configuration-manager.md)<br>

windows/deployment/deploy-windows-cm/finalize-the-os-configuration-for-windows-10-deployment-with-configuration-manager.md

@@ -47,33 +47,26 @@ On **CM01**:
 
     Enable MDT monitoring for Configuration Manager
 
-## Create and share the Logs folder
+## Configure the Logs folder
 
-To support additional server-side logging in Configuration Manager, you create and share the D:\\Logs folder on CM01 using Windows PowerShell. Then in the next step, you 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?branch=cm#review-the-sources-folder-structure) and SMB permissions were added. Next, we will add NTFS folder permissions for the Network Access Account with icacls.exe, and enable server-side logging by modifying the CustomSettings.ini file used by the Configuration Manager task sequence.
 
-1.  On CM01, start an elevated Windows PowerShell prompt (run as Administrator).
+On **CM01**:
 
-2.  Type the following commands, pressing **Enter** after each one:
+1.  Type the following at an elevated Windows PowerShell prompt:
 
     ``` 
-    New-Item -Path E:\Logs -ItemType directory
-    New-SmbShare -Name Logs$ -Path D:\Logs -ChangeAccess EVERYONE
     icacls D:\Logs /grant '"CM_NAA":(OI)(CI)(M)'
     ```
 
-## Configure the rules (Windows 10 x64 Settings package)
+2. Using File Explorer, navigate to the **D:\\Sources\\OSD\\Settings\\Windows 10 x64 Settings** folder.
-
+3. Using Notepad, edit the CustomSetting.ini file with the following settings:
-
-This section will show you how to configure the rules (the Windows 10 x64 Settings package) to support the Contoso environment.
-
-1. On CM01, using File Explorer, navigate to the **D:\\Sources\\OSD\\Settings\\Windows 10 x64 Settings** folder.
-
-2. Using Notepad, edit the CustomSetting.ini file with the following settings:
 
    ``` 
    [Settings]
    Priority=Default
    Properties=OSDMigrateConfigFiles,OSDMigrateMode
+
    [Default]
    DoCapture=NO
    ComputerBackupLocation=NONE
@@ -90,10 +83,12 @@ This section will show you how to configure the rules (the Windows 10 x64 Settin
 
    The Settings package, holding the rules and the Unattend.xml template used during deployment
 
-3. 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**.
+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. That process also updates the Configuration Manager 2012 content library with changes.
+   >Although you have not yet added a distribution point, you still need to select Update Distribution Points. That process also updates the Configuration Manager content library with changes.
+
+-------stopped here--------------
 
 ## Distribute content to the CM01 distribution portal
 

windows/deployment/deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md

@@ -174,6 +174,8 @@ 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.
+
 ```powershell
 New-Item -ItemType Directory -Path "D:\Sources"
 New-Item -ItemType Directory -Path "D:\Sources\OSD"
@@ -187,8 +189,8 @@ New-Item -ItemType Directory -Path "D:\Sources\OSD\MDT"
 New-Item -ItemType Directory -Path "D:\Sources\Software"
 New-Item -ItemType Directory -Path "D:\Sources\Software\Adobe"
 New-Item -ItemType Directory -Path "D:\Sources\Software\Microsoft"
-New-Item -ItemType Directory -Path "D:\Logs"
 New-SmbShare -Name Sources$ -Path D:\Sources -FullAccess "NT AUTHORITY\INTERACTIVE", "BUILTIN\Administrators"
+New-Item -ItemType Directory -Path "D:\Logs"
 New-SmbShare -Name Logs$ -Path D:\Logs -ChangeAccess EVERYONE
 ```