"ahughes584" <> wrote in message
news:dbcff864-6c90-4344-8c2b-...
> On the entries in Event Viewer, they appear repeatedly per hour and
> each time it lists an installation time 10 minutes later than the
> entry is written to Event Vuewer. So the scheduled installation time
> keeps being pushed back.
This is highly unusual. Something else, for which I truly have no clue, must
be going on in this situation.
> On that point--in the Registry, it lists the next
> installation time as 6 AM rather than 2 AM. I can't see that being
> GMT. Any ideas where that time is pulled from?
The *policy* key of the registry records/displays time in LOCAL time.
The *currentversion* key of the registry records/displays time in GMT.
The key consideration is this:
The Windows Update Agent is timezone agnostic. It does everything in GMT. So
the log entries, the registry keys written by the WUA, the WUA datastore,
are all recorded in GMT.
The things done external to the WUA -- log timestamps, policy configuration
keys, etc, all all recorded in client machine's local time zone.
The WSUS Server stores all timestamps received from the WUA in GMT, and then
converts them for display in the WSU Server's local time zone.
On Jun 3, 7:52 pm, "Lawrence Garvin [MVP]" <lawre...@news.postalias>
wrote:
> "ahughes584" <ahughes...@gmail.com> wrote in message
>
> news:1074a765-a271-41b9-b61f-...
>
> > However, on
> > the two Server 2008 servers, Event Viewer lists the updates as having
> > been downloaded but then says "This computer is currently scheduled to
> > install these updates on ýTuesday, ýJune ý02, ý2009 at 2:08 PM". The
> > time is always 10 minutes ahead of whatever time the message appears
> > in Event Viewer and is not Thursday at 2 AM.
>
> If the installation time is scheduled for 10 minutes after the
> detection/download completes, that sounds like a deadline has been set on
> the group that contains your Win2008 servers. Truly, it's the only way I
> know of to impact an installation at some time other than the top of the
> hour.
>
> > When I look in the windowsupdate.log, I see this:
> > 2009-06-03 14:23:06:961 248 7cc AU # Reconnecting download for 1 updates
> > 2009-06-03 14:23:06:961 248 7cc AU # Reconnected 1 pending download
> > calls
> > 2009-06-03 14:23:06:961 248 7cc AU Setting AU scheduled install time to
> > 2009-06-04 06:00:00
> > It shows GP is setting the installation time for Thursday at 2 AM, but
> > then a few lines later it is changing it somehow to Thursday at 6 AM.
>
> Ummm... be sure to take into account those log entries that are displayed
> in
> GMT -- which is basically almost all of them.
>
> The log timestamps are in local time; the log text is in GMT.
>
> The log entry shown above is 2am Thursday June 4th (LOCAL TIME), if you're
> in GMT-4 (US EDT/AST)
>
> The line to validate your policy configuration (in LOCAL time) is the one
> logged at service startup:
>
> > 2009-06-03 14:23:06:899 248 7cc AU # Scheduled install day/time:
> > Thursday at 2:00
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website:http://www.microsoft.com/wsus
> My
> Websites:http://www.onsitechsolutions.com;htt...hsolutions.com
> My MVP Profile:http://mvp.support.microsoft.com/pro...awrence.Garvin
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:
http://www.microsoft.com/wsus
My Websites:
http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin
Similar Threads
Linear Mode
