deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fix typos / acro fix

Browse Source
This commit is contained in:
Rebecca Agiewich 2025-02-24 14:28:50 -08:00 committed by GitHub
parent fcb6599081
commit 0aa7f0159e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/update/update-policies.md
View File

@ -94,7 +94,7 @@ options must be **Disabled** in order to take advantage of intelligent active ho
If you do set active hours, we recommend setting the following policies to **Disabled** in order to increase update If you do set active hours, we recommend setting the following policies to **Disabled** in order to increase update
velocity: velocity:
- [Delay automatic reboot](waas-restart.md#delay-automatic-restart). While it's possible to set the system to delay restarts for users who are logged in, this setting might delay an update indefinitely if a user is always either logged in or shut down. Instead, we recommend setting the following polices to **Disabled**: - [Delay automatic reboot](waas-restart.md#delay-automatic-restart). While it's possible to set the system to delay restarts for users who are logged in, this setting might delay an update indefinitely if a user is always either logged in or shut down. Instead, we recommend setting the following policies to **Disabled**:
- **Turn off auto-restart during active hours** - **Turn off auto-restart during active hours**
- **No auto-restart with logged on users for scheduled automatic updates** - **No auto-restart with logged on users for scheduled automatic updates**
@ -183,7 +183,7 @@ As administrators, you have set up and expect certain behaviors, so we expressly
> expected. For example, if a device is not reacting to your MDM policy changes, check to see if a similar > expected. For example, if a device is not reacting to your MDM policy changes, check to see if a similar
> policy is set in Group Policy with a differing value. > policy is set in Group Policy with a differing value.
> If you find that update velocity is not as high as you expect or if some devices are slower than others, it might be > If you find that update velocity is not as high as you expect or if some devices are slower than others, it might be
> time to clear all polices and settings and specify only the recommended update policies. See the Policy and settings reference for a consolidated list of recommended polices. > time to clear all policies and settings and specify only the recommended update policies. See the Policy and settings reference for a consolidated list of recommended policies.
The following are policies that you might want to disable because they could decrease update velocity or there are better policies to use that might conflict: The following are policies that you might want to disable because they could decrease update velocity or there are better policies to use that might conflict:
- **Defer Feature Updates Period in Days**. For maximum update velocity, it's best to set this to **0** (no - **Defer Feature Updates Period in Days**. For maximum update velocity, it's best to set this to **0** (no