|
|
RebootRelaunchTimeout is mysteriously being ignored. I had an issue
previously where I had it set to something like 340 and instead of 340
minutes it did the default of 10 minutes. After posting a question about
it here someone from MS suggested that this was too high a number, so I
lowered it to 120 and it worked after that. Now I have noticed that it's
back to only doing the default 10 minutes. I've tried adjusting it to
other times and it seems to make no difference. Even setting it below 10
minutes, the timer still lasts for exactly 10 minutes and then the
restart now/restart later pop-up window returns.
Has anyone seen this happen before? Any idea how to fix it?
|
|
"Nigel Jett" <jettn[ at ]evergreen.edu> wrote in message
news:u4HRYR4sHHA.4132[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > RebootRelaunchTimeout is mysteriously being ignored. I had an issue
> previously where I had it set to something like 340 and instead of 340
> minutes it did the default of 10 minutes.
It does that when it's configured to use an invalid value,
or if the matching and required "RebootRelaunchTimeoutEnabled" =
dword:0x1 value is not present.
> After posting a question about it here someone from MS suggested that this
> was too high a number, so I lowered it to 120 and it worked after that.
Well now.. that might also depend on *how* you configured that number. But
even if you tried to configure it as dword:0x340, not noting the distinction
between hex and decimal, you'd still have a valid value of 832 minutes. The
actual maximum value for this setting is 1440 minutes, which is dword:0x5a0.
There's *no* reason that 340 minutes would not work, unless something else
is flawed -- like the missing/required *Enabled registry value.
> Now I have noticed that it's back to only doing the default 10 minutes.
> I've tried adjusting it to other times and it seems to make no difference.
> Even setting it below 10 minutes, the timer still lasts for exactly 10
> minutes and then the restart now/restart later pop-up window returns.
> Has anyone seen this happen before? Any idea how to fix it?
Well, the *best* way to eliminate these type of errors is to use LOCAL
POLICY to configure the settings. That way you're ensured of getting all of
the necessary keys as well as configuring valid ranges of values.
The next best way to fix is it to refer to the WSUS Deployment Guide and
configure *ALL* of the registry settings, so that there aren't any required
values missing from the registry key.
Given that you've only mentioned this one value, and not any of the other
registry values that may or may not be configured, the best I can do is
speculate. I'm speculatin' that you've missed the required
"RebootRelaunchTimeoutEnabled"=dword:0x1 registry value.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
[Quoted Text] > Given that you've only mentioned this one value, and not any of the other
> registry values that may or may not be configured, the best I can do is
> speculate. I'm speculatin' that you've missed the required
> "RebootRelaunchTimeoutEnabled"=dword:0x1 registry value.
>
>
I have every registry value configured. My method was to do it via local
policy and then export the settings and then use the .reg on other clients.
Everything worked great until within the past week or two when the timer
stopped working.
Here is the current setting with a 240 minute timer that lasts for 10
minutes:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"NoAUShutdownOption"=dword:00000000
"NoAUAsDefaultShutdownOption"=dword:00000000
"AutoInstallMinorUpdates"=dword:00000001
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000004
"ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:0000000c
"IncludeRecommendedUpdates"=dword:00000001
"DetectionFrequencyEnabled"=dword:00000001
"DetectionFrequency"=dword:0000000c
"RescheduleWaitTimeEnabled"=dword:00000001
"RescheduleWaitTime"=dword:00000001
"UseWUServer"=dword:00000001
"AUPowerManagement"=dword:00000001
"RebootRelaunchTimeoutEnabled"=dword:00000001
"RebootRelaunchTimeout"=dword:000000f0
"RebootWarningTimeoutEnabled"=dword:00000001
"RebootWarningTimeout"=dword:0000000f
|
|
Nigel Jett wrote:
[Quoted Text] > I have every registry value configured. My method was to do it via local
> policy and then export the settings and then use the .reg on other clients.
> Everything worked great until within the past week or two when the timer
> stopped working.
You're sure there isn't group policy configured that is overriding the local
settings? Have you doublechecked that the actual setting in the registry is
still the same as you expect?
Harry.
|
|
"Nigel Jett" <jettn[ at ]evergreen.edu> wrote in message
news:Ojchwe0tHHA.4440[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] >> Given that you've only mentioned this one value, and not any of the other
>> registry values that may or may not be configured, the best I can do is
>> speculate. I'm speculatin' that you've missed the required
>> "RebootRelaunchTimeoutEnabled"=dword:0x1 registry value.
> I have every registry value configured. My method was to do it via local
> policy and then export the settings and then use the .reg on other
> clients.
> Everything worked great until within the past week or two when the timer
> stopped working.
>
> Here is the current setting with a 240 minute timer that lasts for 10
> minutes:
It would be much more accurate if you could post the output from an actual
REG QUERY, so that we can see the *actual* registry values, rather than
just type into the message what you want the settings to be. There are
several reason why that value might not be getting read correctly, but the
only way to have a possible clue as to why that is, would be to look at the
*actual* configured values on a machine demonstrating this behavior.
Also, since your registry listing has some WSUS v3.0/WUA v7.x registry
values configured, it would be extremely critical that the client is
actually running the WUA v7.x client, as if the WUA v5.8 client saw those
undefined (to its knowledge, of course) registry values, it would ignore the
rest of the key and revert to all default options.
Such a thing would look something like this:
C:\Temp>reg query hklm\software\policies\microsoft\windows\windowsupdate /s
> wuaout.reg
C:\Temp>type wuaout.reg
! REG.EXE VERSION 3.0
HKEY_LOCAL_MACHINE\software\policies\microsoft\windows\windowsupdate
WUServer REG_SZ http://wsus-srv
WUStatusServer REG_SZ http://wsus-srv
HKEY_LOCAL_MACHINE\software\policies\microsoft\windows\windowsupdate\AU
NoAutoRebootWithLoggedOnUsers REG_DWORD 0x1
NoAutoUpdate REG_DWORD 0x0
AUOptions REG_DWORD 0x4
ScheduledInstallDay REG_DWORD 0x0
ScheduledInstallTime REG_DWORD 0x3
UseWUServer REG_DWORD 0x1
RescheduleWaitTimeEnabled REG_DWORD 0x1
RescheduleWaitTime REG_DWORD 0x5
DetectionFrequencyEnabled REG_DWORD 0x1
DetectionFrequency REG_DWORD 0x4
NoAUShutdownOption REG_DWORD 0x1
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|