deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update feature-update-maintenance-window.md

Browse Source 
- re-add the removed `> [!NOTE]` line for the new note
- properly remove an added line which should have been replaced
- remove trailing spaces (redundant blank space at the end of the lines)
This commit is contained in:
illfated
2019-10-06 18:41:59 +02:00
parent eff38d1336
commit 310e9cbeaa
1 changed files with 113 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/update/feature-update-maintenance-window.md
View File

@ -50,8 +50,8 @@ 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]
> In any enterprise, content delivery optimization via caching and peering solutions is imperative to mitigate the risk of interrupting business operations. It is important when downloading large payloads from the cloud (feature updates, quality updates, and so on). Most smaller organizations may have this enabled by default, but larger enterprises may need to plan an implementation to 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 an Internet connection local to them. Otherwise they will peer with clients potentially not in the same physical location.
> In the enterprise, content delivery optimization via caching and peering solutions is imperative to mitigate the risk of interrupting business operations. It is important when downloading large payloads from the cloud (feature updates, quality updates, and so on). Most smaller organizations may have this enabled by default, but larger enterprises may need to plan an implementation to 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 an internet connection local to them. Otherwise they will peer with clients potentially not in the same physical location.
### Step 4: Override the default Windows setup priority (Windows 10, version 1709 and later)
@ -228,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]
> 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://github.com/MicrosoftDocs/SCCMdocs/blob/master/sccm/core/clients/deploy/about-client-settings.md#computer-agent).
> 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).