WSUS won't bring down KB928388 (DST for W2K3)

Hi Folks,

My WSUS server has brought down the patches for the Australian DST
(913670) and for XP (29120), but it will not bring down the patch for
the W2K3 servers here in the US. This is not an optional patch from
what I can see. I currently have synch set to pull:

* Critical Updates
* Security Updates
* Service Packs
* Tools
* Update Rollups
* Updates

(and yes, the W2K3 operating system is selected).

This server is running IE7, WSUS 2.0.0.2620 against the default msde
sqlserver.

Any ideas what might cause it to not download a patch? And how do I fix
this?

KB928388 is still optional. I am having the same issue with SMS 2003 SP2
(ITMU). I have imported January's CAB file and like you, no KB928388.
Microsoft has put the brakes on this until they have a DST fix for Outlook.
If they put out the OS patch out without the Outlook patch, bad things are
reported to happen.

I'm told any day now !!

"" wrote:

> Hi Folks,
>
> My WSUS server has brought down the patches for the Australian DST
> (913670) and for XP (29120), but it will not bring down the patch for
> the W2K3 servers here in the US. This is not an optional patch from
> what I can see. I currently have synch set to pull:
>
> * Critical Updates
> * Security Updates
> * Service Packs
> * Tools
> * Update Rollups
> * Updates
>
> (and yes, the W2K3 operating system is selected).
>
> This server is running IE7, WSUS 2.0.0.2620 against the default msde
> sqlserver.
>
> Any ideas what might cause it to not download a patch? And how do I fix
> this?
>
>

Thank you for the quick reply! It all makes sense now ... as much as
it can. LOL!

Didi


On Jan 25, 2:56 pm, Van <V...@discussions.microsoft.com> wrote:
> KB928388 is still optional. I am having the same issue with SMS 2003 SP2
> (ITMU). I have imported January's CAB file and like you, no KB928388.
> Microsoft has put the brakes on this until they have a DST fix for Outlook.
> If they put out the OS patch out without the Outlook patch, bad things are
> reported to happen.
>
> I'm told any day now !!
>
>
>
> "ddgeekg...@gmail.com" wrote:
> > Hi Folks,
>
> > My WSUS server has brought down the patches for the Australian DST
> > (913670) and for XP (29120), but it will not bring down the patch for
> > the W2K3 servers here in the US. This is not an optional patch from
> > what I can see. I currently have synch set to pull:
>
> > * Critical Updates
> > * Security Updates
> > * Service Packs
> > * Tools
> > * Update Rollups
> > * Updates
>
> > (and yes, the W2K3 operating system is selected).
>
> > This server is running IE7, WSUS 2.0.0.2620 against the default msde
> > sqlserver.
>
> > Any ideas what might cause it to not download a patch? And how do I fix
> > this?- Hide quoted text -- Show quoted text -

What kind of "bad things" ?

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Calendared items posted before applying the OS patch. Once you apply
KB928388, but before Outlook patch, calendar items will be one hour off for
the three weeks in Spring and again one hour off for the one week in the
Fall. I have seen this in both Outlook and GroupWise. Mostly GroupWise
because we are primarily still GroupWise house. Timing I think is the biggest
key to minimize the impacted.

It is real obvious when you have a repeating once a week or once a month
appointment that spans the entire year and then apply KB928388, you can then
see the bad shift during those key weeks. Easy to duplicate.

We have pushed KB928388 to our seven offices, and putting it on our users to
review their calendar for the four key weeks of the DST shift. And if anyone
complains to our IT staff, we have decided to tell them to write to their
Congress person.

"Tony" wrote:

> What kind of "bad things" ?
>
> EggHeadCafe.com - .NET Developer Portal of Choice
> http://www.eggheadcafe.com
>