Skip to content

Commit 38b4256

Browse files
authored
Merge pull request #194483 from dcbrown16/patch-77
Update deploy-updates.md
2 parents bd0b5d7 + 0ac0b3c commit 38b4256

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/automation/update-management/deploy-updates.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,9 @@ To schedule a new update deployment, perform the following steps. Depending on t
109109
12. Use the **Maintenance window (minutes)** field to specify the amount of time allowed for updates to install. Consider the following details when specifying a maintenance window:
110110

111111
* Maintenance windows control how many updates are installed.
112+
* If the next step in the update process is to install a Service Pack, there must be 20 minutes left in the maintenance window, or that update will be skipped.
113+
* If the next step in the update process is to install any other kind of update besides Service Pack, there must be 15 minutes left in the maintenance window, or that update will be skipped.
114+
* If the next step in the update process is a reboot, there must be 10 minutes left in the maintenance window, or the reboot will be skipped.
112115
* Update Management doesn't stop installing new updates if the end of a maintenance window is approaching.
113116
* Update Management doesn't terminate in-progress updates if the maintenance window is exceeded. Any remaining updates to be installed are not attempted. If this is consistently happening, you should reevaluate the duration of your maintenance window.
114117
* If the maintenance window is exceeded on Windows, it's often because a service pack update is taking a long time to install.

0 commit comments

Comments
 (0)