Merge pull request #5120 from illfated/peer_cache_note

Windows/Deployment: add Peer Cache Enterprise note

windows/deployment/update/feature-update-maintenance-window.md

@@ -4,7 +4,8 @@ description: Learn how to deploy feature updates during a maintenance window
 ms.prod: w10
 ms.mktglfcycl: manage
 ms.sitesec: library
-audience: itpro
+audience: itpro
+author: greg-lindsay
 ms.localizationpriority: medium
 ms.author: greglin
 ms.date: 07/09/2018
@@ -27,9 +28,9 @@ Use the following information to deploy feature updates during a maintenance win
 1. In the Configuration Manager console, choose **Assets and Compliance > Device Collections**.
 2. In the **Device Collections** list, select the collection for which you intended to deploy the feature update(s).
 3. On the **Home** tab, in the **Properties** group, choose **Properties**.
-3. On the **Home** tab, in the **Properties** group, choose **Properties**. 
-4. In the **Maintenance Windows** tab of the `<collection name>` Properties dialog box, choose the New icon. 
-5. Complete the `<new>` Schedule dialog. 
+4. In the **Maintenance Windows** tab of the **`<collection name>` Properties** dialog box, choose the **New** icon.
+5. Complete the **`<new>` Schedule** dialog.
+6. Select **Apply this schedule** from the drop-down list.
 7. Choose **OK** and then close the **\<collection name\> Properties** dialog box.
 
 ### Step 2: Review computer restart device settings
@@ -49,20 +50,23 @@ Use **Peer Cache** to help manage deployment of content to clients in remote loc
 
 [Enable Configuration Manager client in full OS to share content](https://docs.microsoft.com/sccm/core/clients/deploy/about-client-settings#enable-configuration-manager-client-in-full-os-to-share-content) if you have clients in remote locations that would benefit from downloading feature update content from a peer instead of downloading it from a distribution point (or Microsoft Update).
 
+> [!NOTE]
+> Content delivery optimization via caching and peering solutions can avoid interruptions to business operations, especially when you download large payloads from the cloud (such as feature or quality updates). To avoid peering with clients that are not in the same physical location, you can logically group different sites via AD Site or SCCM boundary group, as the egress/ingress point may be a data center in another location, rather than a local internet connection. 
+
 ### Step 4: Override the default Windows setup priority (Windows 10, version 1709 and later)
 
 If you’re deploying **Feature update to Windows 10, version 1709** or later, by default, portions of setup are configured to run at a lower priority. This can result in a longer total install time for the feature update. When deploying within a maintenance window, we recommend that you override this default behavior to benefit from faster total install times. To override the default priority, create a file called SetupConfig.ini on each machine to be upgraded in the below location containing the single section noted.
 
 %systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini
 
-
+```ini
 [SetupConfig]
 Priority=Normal
 ```
 
 You can use the new [Run Scripts](https://docs.microsoft.com/sccm/apps/deploy-use/create-deploy-scripts) feature to run a PowerShell script like the sample below to create the SetupConfig.ini on target devices.
 
-
+```PowerShell
 #Parameters
 Param(
   [string] $PriorityValue = "Normal"
@@ -199,7 +203,7 @@ After you determine which feature updates you intend to deploy, you can manually
      > After you create the software update deployment, you cannot later change the type of deployment.
 
      > [!NOTE]
-     >[!NOTE]
+     > A software update group deployed as **Required** will be downloaded in the background and honor BITS settings, if configured.
 
    - **Use Wake-on-LAN to wake up clients for required deployments**: Specify whether to enable Wake On LAN at the deadline to send wake-up packets to computers that require one or more software updates in the deployment. Any computers that are in sleep mode at the installation deadline time will be awakened so the software update installation can initiate. Clients that are in sleep mode that do not require any software updates in the deployment are not started. By default, this setting is not enabled and is available only when Type of deployment is set to Required.
 
@@ -224,7 +228,7 @@ After you determine which feature updates you intend to deploy, you can manually
    - **Specific time**: Select this setting to automatically install the software updates in the deployment at a specific date and time. Set the date and time value to correspond with your defined maintenance window for the target collection. Allow sufficient time for clients to download the content in advance of the deadline. Adjust accordingly if clients in your environment will need additional download time. E.g., slow or unreliable network links.
 
    > [!NOTE]
-   >[!NOTE]
+   > The actual installation deadline time is the specific time that you configure plus a random amount of time up to two hours. This reduces the potential impact of all client computers in the destination collection installing the software updates in the deployment at the same time. Configure the Computer Agent client setting **Disable deadline randomization** to disable the installation randomization delay for the required software updates to allow a greater chance for the installation to start and complete within your defined maintenance window. For more information, see [Computer Agent](https://docs.microsoft.com/sccm/core/clients/deploy/about-client-settings#computer-agent).
 7. On the User Experience page, configure the following settings:
    - **User notifications**: Specify whether to display notification of the software updates in Software Center on the client computer at the configured **Software available time** and whether to display user notifications on the client computers. When **Type of deployment** is set to **Available** on the Deployment Settings page, you cannot select **Hide in Software Center and all notifications**.
    - **Deadline behavior**: Available only when **Type of deployment** is set to **Required** on the Deployment Settings page. Specify the behavior that is to occur when the deadline is reached for the software update deployment. Specify whether to install the software updates in the deployment. Also specify whether to perform a system restart after software update installation regardless of a configured maintenance window. For more information about maintenance windows, see [How to use maintenance windows](https://docs.microsoft.com/sccm/core/clients/manage/collections/use-maintenance-windows).