KB908521 and WSUS

Our WSUS reported recently that KB908521 was required by our servers (DC and
Exchange). This KB is dated back to 2005, but only showed up in the list
awaiting approval last week.

My guess is that something else (another patch) triggered its requirement.
Googling around the web I noted that there has been issues relating to this
fix causing Exchange to become unstable (which seems to go against what the
fix was about).

check out
http://mrfoged.wordpress.com/2006/10...-exchange-rpc/
as an example..

Does anybody have advise on this one? Should we install or not install?

thanks in advance.

Forwarded to microsoft.public.windows.server.update_services newsgroup via
crosspost.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)

Geoff wrote:
> Our WSUS reported recently that KB908521 was required by our servers (DC
> and
> Exchange). This KB is dated back to 2005, but only showed up in the list
> awaiting approval last week.
>
> My guess is that something else (another patch) triggered its requirement.
> Googling around the web I noted that there has been issues relating to
> this
> fix causing Exchange to become unstable (which seems to go against what
> the
> fix was about).
>
> check out
> http://mrfoged.wordpress.com/2006/10...-exchange-rpc/
> as an example..
>
> Does anybody have advise on this one? Should we install or not install?
>
> thanks in advance.

> Geoff wrote:

>> Our WSUS reported recently that KB908521 was required by our servers (DC
>> and
>> Exchange). This KB is dated back to 2005, but only showed up in the list
>> awaiting approval last week.

By "list awaiting approval", do you mean that it just now synchronized, or
that you just now noticed it as an unapproved update?
Or that it suddenly downloaded to the DC/Exchange servers and was
pending installation?

>> My guess is that something else (another patch) triggered its
>> requirement.

Possible, but not likely, given the nature of the update.

Its much more likely that something (application) was installed -- most
likely... RPC, or an RPC-based service/application.
Or that the update was only recently "Approved" for installation.

The real questions, both for you, and for the author of the blog entry, is
Why was the update detected?

According to the KB article, this update is primarily intended for systems
where Outlook is (or, to be honest, /was/) installed.

You are using the following products together:
• Microsoft Office Outlook 2003 or a later version of Outlook
• Microsoft Exchange
• Microsoft Windows XP with Service Pack 2 (SP2) or Microsoft Windows
Server 2003



It's possible that the detection logic for the update is defective, and it's
being detected because the Exchange is there, without confirming the
installation of Outlook.

It may also be that the update is being detected because of a RPC/HTTP
proxy, or because of RPC being enabled, generally. Note that this is an
/RPC/ fix, not an Outlook/Exchange fix.

If you install the update, and encounter problems, then uninstall it. Note
that this is not a Security Update, nor is it a Critical Update.

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....



>> Googling around the web I noted that there has been issues relating to
>> this
>> fix causing Exchange to become unstable (which seems to go against what
>> the
>> fix was about).
>>
>> check out
>> http://mrfoged.wordpress.com/2006/10...-exchange-rpc/
>> as an example..
>>
>> Does anybody have advise on this one? Should we install or not install?
>>
>> thanks in advance.
>

Thanks Lawrence, this was very helpful...

"Lawrence Garvin (MVP)" wrote:

> > Geoff wrote:
>
> >> Our WSUS reported recently that KB908521 was required by our servers (DC
> >> and
> >> Exchange). This KB is dated back to 2005, but only showed up in the list
> >> awaiting approval last week.
>
> By "list awaiting approval", do you mean that it just now synchronized, or
> that you just now noticed it as an unapproved update?
> Or that it suddenly downloaded to the DC/Exchange servers and was
> pending installation?
>
> >> My guess is that something else (another patch) triggered its
> >> requirement.
>
> Possible, but not likely, given the nature of the update.
>
> Its much more likely that something (application) was installed -- most
> likely... RPC, or an RPC-based service/application.
> Or that the update was only recently "Approved" for installation.
>
> The real questions, both for you, and for the author of the blog entry, is
> Why was the update detected?
>
> According to the KB article, this update is primarily intended for systems
> where Outlook is (or, to be honest, /was/) installed.
>
> You are using the following products together:
> • Microsoft Office Outlook 2003 or a later version of Outlook
> • Microsoft Exchange
> • Microsoft Windows XP with Service Pack 2 (SP2) or Microsoft Windows
> Server 2003
>
>
>
> It's possible that the detection logic for the update is defective, and it's
> being detected because the Exchange is there, without confirming the
> installation of Outlook.
>
> It may also be that the update is being detected because of a RPC/HTTP
> proxy, or because of RPC being enabled, generally. Note that this is an
> /RPC/ fix, not an Outlook/Exchange fix.
>
> If you install the update, and encounter problems, then uninstall it. Note
> that this is not a Security Update, nor is it a Critical Update.
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
>
> >> Googling around the web I noted that there has been issues relating to
> >> this
> >> fix causing Exchange to become unstable (which seems to go against what
> >> the
> >> fix was about).
> >>
> >> check out
> >> http://mrfoged.wordpress.com/2006/10...-exchange-rpc/
> >> as an example..
> >>
> >> Does anybody have advise on this one? Should we install or not install?
> >>
> >> thanks in advance.
> >
>
>
>

"Geoff" <> wrote in message
news:95466413-3FCF-4D83-A1CD-...
> Thanks Lawrence, this was very helpful...

But... did you identify a solution???

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
.....



>
> "Lawrence Garvin (MVP)" wrote:
>
>> > Geoff wrote:
>>
>> >> Our WSUS reported recently that KB908521 was required by our servers
>> >> (DC
>> >> and
>> >> Exchange). This KB is dated back to 2005, but only showed up in the
>> >> list
>> >> awaiting approval last week.
>>
>> By "list awaiting approval", do you mean that it just now synchronized,
>> or
>> that you just now noticed it as an unapproved update?
>> Or that it suddenly downloaded to the DC/Exchange servers and was
>> pending installation?
>>
>> >> My guess is that something else (another patch) triggered its
>> >> requirement.
>>
>> Possible, but not likely, given the nature of the update.
>>
>> Its much more likely that something (application) was installed -- most
>> likely... RPC, or an RPC-based service/application.
>> Or that the update was only recently "Approved" for installation.
>>
>> The real questions, both for you, and for the author of the blog entry,
>> is
>> Why was the update detected?
>>
>> According to the KB article, this update is primarily intended for
>> systems
>> where Outlook is (or, to be honest, /was/) installed.
>>
>> You are using the following products together:
>> . Microsoft Office Outlook 2003 or a later version of Outlook
>> . Microsoft Exchange
>> . Microsoft Windows XP with Service Pack 2 (SP2) or Microsoft
>> Windows
>> Server 2003
>>
>>
>>
>> It's possible that the detection logic for the update is defective, and
>> it's
>> being detected because the Exchange is there, without confirming the
>> installation of Outlook.
>>
>> It may also be that the update is being detected because of a RPC/HTTP
>> proxy, or because of RPC being enabled, generally. Note that this is an
>> /RPC/ fix, not an Outlook/Exchange fix.
>>
>> If you install the update, and encounter problems, then uninstall it.
>> Note
>> that this is not a Security Update, nor is it a Critical Update.
>>
>> --
>> Lawrence Garvin, M.S., MVP-Software Distribution
>> Everything you need for WSUS is at
>> http://technet2.microsoft.com/window...s/default.mspx
>> And, everything else is at
>> http://wsusinfo.onsitechsolutions.com
>> .....
>>
>>
>>
>> >> Googling around the web I noted that there has been issues relating to
>> >> this
>> >> fix causing Exchange to become unstable (which seems to go against
>> >> what
>> >> the
>> >> fix was about).
>> >>
>> >> check out
>> >> http://mrfoged.wordpress.com/2006/10...-exchange-rpc/
>> >> as an example..
>> >>
>> >> Does anybody have advise on this one? Should we install or not
>> >> install?
>> >>
>> >> thanks in advance.
>> >
>>
>>
>>

Yes, in production we have declined the update, however our QA group will
apply it in our test systems.
As you point out it is not a security or critical issue, just a connection
stability fix.
Pending how QA pans out over the next few months, we will decide if it is
worth appying to production.

As for why it is even showing up for approval, per your comment we will
investigate how this is now in the list as "detect only". This is however,
mostly an educational exercise as I suspect we added some feature that
brought to our attention. Still it will be nice to know why.


"Lawrence Garvin (MVP)" wrote:

> "Geoff" <> wrote in message
> news:95466413-3FCF-4D83-A1CD-...
> > Thanks Lawrence, this was very helpful...
>
> But... did you identify a solution???
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
>
> >
> > "Lawrence Garvin (MVP)" wrote:
> >
> >> > Geoff wrote:
> >>
> >> >> Our WSUS reported recently that KB908521 was required by our servers
> >> >> (DC
> >> >> and
> >> >> Exchange). This KB is dated back to 2005, but only showed up in the
> >> >> list
> >> >> awaiting approval last week.
> >>
> >> By "list awaiting approval", do you mean that it just now synchronized,
> >> or
> >> that you just now noticed it as an unapproved update?
> >> Or that it suddenly downloaded to the DC/Exchange servers and was
> >> pending installation?
> >>
> >> >> My guess is that something else (another patch) triggered its
> >> >> requirement.
> >>
> >> Possible, but not likely, given the nature of the update.
> >>
> >> Its much more likely that something (application) was installed -- most
> >> likely... RPC, or an RPC-based service/application.
> >> Or that the update was only recently "Approved" for installation.
> >>
> >> The real questions, both for you, and for the author of the blog entry,
> >> is
> >> Why was the update detected?
> >>
> >> According to the KB article, this update is primarily intended for
> >> systems
> >> where Outlook is (or, to be honest, /was/) installed.
> >>
> >> You are using the following products together:
> >> . Microsoft Office Outlook 2003 or a later version of Outlook
> >> . Microsoft Exchange
> >> . Microsoft Windows XP with Service Pack 2 (SP2) or Microsoft
> >> Windows
> >> Server 2003
> >>
> >>
> >>
> >> It's possible that the detection logic for the update is defective, and
> >> it's
> >> being detected because the Exchange is there, without confirming the
> >> installation of Outlook.
> >>
> >> It may also be that the update is being detected because of a RPC/HTTP
> >> proxy, or because of RPC being enabled, generally. Note that this is an
> >> /RPC/ fix, not an Outlook/Exchange fix.
> >>
> >> If you install the update, and encounter problems, then uninstall it.
> >> Note
> >> that this is not a Security Update, nor is it a Critical Update.
> >>
> >> --
> >> Lawrence Garvin, M.S., MVP-Software Distribution
> >> Everything you need for WSUS is at
> >> http://technet2.microsoft.com/window...s/default.mspx
> >> And, everything else is at
> >> http://wsusinfo.onsitechsolutions.com
> >> .....
> >>
> >>
> >>
> >> >> Googling around the web I noted that there has been issues relating to
> >> >> this
> >> >> fix causing Exchange to become unstable (which seems to go against
> >> >> what
> >> >> the
> >> >> fix was about).
> >> >>
> >> >> check out
> >> >> http://mrfoged.wordpress.com/2006/10...-exchange-rpc/
> >> >> as an example..
> >> >>
> >> >> Does anybody have advise on this one? Should we install or not
> >> >> install?
> >> >>
> >> >> thanks in advance.
> >> >
> >>
> >>
> >>
>
>
>