mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Update windows/deployment/update/feature-update-maintenance-window.md
- rephrase the Note text, based on MS Docs style guide Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com>
This commit is contained in:
committed by
illfated
parent
6d2ae5f01d
commit
925d1c1eff
@ -51,7 +51,7 @@ 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.
|
||||
> 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)
|
||||
|
||||
|
Reference in New Issue
Block a user