|
|
In checking WSUS the last few days to be sure updates have been applied I
noticed that many machines were waiting for a reboot. Until the June updates
this has not been an issue.
My GPO is set as follows:
Policy Setting
Automatic Updates detection frequency Enabled
Check for updates at the following
interval (hours): 8
Policy Setting
Configure Automatic Updates Enabled
Configure automatic updating: 4 - Auto download and schedule the install
The following settings are only required
and applicable if 4 is selected.
Scheduled install day: 0 - Every day
Scheduled install time: 09:00
Policy Setting
No auto-restart for scheduled Automatic Updates installations Enabled
Reschedule Automatic Updates scheduled installations Disabled
Specify intranet Microsoft update service location Enabled
Set the intranet update service for detecting updates: http://nhtools1:8530
Set the intranet statistics server: http://nhtools1:8530
(example: http://IntranetUpd01)
Normally the machines would get the notification that a restart was needed
to complete the updates and they could move the notification out of the way
but it would keep reminding them. That does not seem to have happened this
time. I've checked several of the machines waiting for the reboot and there
is no notification visible.
I know there is the policy for Re-prompt for restart with scheduled
installations, but I have never configured it because the explaination says:
Specifies the amount of time for Automatic Updates to wait before prompting
again with a scheduled restart.
If the status is set to Enabled, a scheduled restart will occur the
specified number of minutes after the previous prompt for restart was
postponed.
If the status is set to Disabled or Not Configured, the default interval is
10 minutes.
Note: This policy applies only when Automatic Updates is configured to
perform scheduled installations of updates. If the "Configure Automatic
Updates" policy is disabled, this policy has no effect.
So according to this with it Not Configured the default interval is 10
minutes.
This was the behavior I have seen prior to the June updates. Has something
changed? Do I now need to configure this policy in order for it to reprompt
the user?
Thanks.
|
|
|