Mixing manual windows/microsoft update version 6 with clients using SUS 1

Since we still do not have equipment to migrate from SUS to WSUS, we
have been using Microsoft Update version 6 to manually install Office XP and
2003 patches on some client machines. Does this cause the existing SUS
settings to be damaged or ignored? Also would scanning SUS clients with
MBSA 2.0 also cause the same damage due to the upgrade of the Windows Update
Agent to version 2.0?
Or in other words, are computers with the Windows Update Agent 2.0
backwards compatible with be managed by SUS 1? I think I remember another
forum stating that this is not the case, and when the client goes to the SUS
1 server, the older update agent will be installed over the top of the
Windows Update Agent 2. I would like confirmation from Microsoft on this
before next Tuesday so we can plan accordingly.

Why not just install WSUS on your existing SUS server???

Installing Office XP/2003 updates from Office Update or Microsoft Update
will not affect the operation of /SUS/ because /SUS/ does not provide
updates for Microsoft Office products.

Scanning /SUS/ clients with MBSA will not cause any damage.. but it /will/
cause the SUS AU client (v5.4) to be upgraded to the WSUS WUA client (v5.8).
This can actually be a good thing, as it will preclude the necessity of
dealing with this issue when you actually deploy WSUS.

Computers with the WUA v2.0 are definitely backward compatible with SUS v1.0

If another forum stated any such thing, the poster was misinformed. :-)

We've seen literally HUNDREDS of examples in this sceanrio of WUA v2.0
clients trying to talk to SUS servers because they could not find the WSUS
server. If the WUA couldn't do it.... it surely would not try. :-)

There have been a few quirky situations where it /appears/ that the v5.4
client was "reinstalled" on top of an already upgraded WUA v2.0 (AU
v5.8.0.2469) client... but the causes have not been confirmed, and I suspect
"human intervention" may have helped in those cases.

The "confirmation" from Microsoft is well documented in this forum, as well
as in the WSUS Deployment Guide, with the exception of comments regarding
the 'downgrading' of the WUA to AU v5.4 -- which, as I stated, has been
'observed' but not confirmed as a real issue. It's certainly /not/ happening
as a result of an upgraded WUA legitimately querying a SUS server for normal
operations.


<> wrote in message
news:%...
> Since we still do not have equipment to migrate from SUS to WSUS, we
> have been using Microsoft Update version 6 to manually install Office XP
> and
> 2003 patches on some client machines. Does this cause the existing SUS
> settings to be damaged or ignored? Also would scanning SUS clients with
> MBSA 2.0 also cause the same damage due to the upgrade of the Windows
> Update
> Agent to version 2.0?
> Or in other words, are computers with the Windows Update Agent 2.0
> backwards compatible with be managed by SUS 1? I think I remember another
> forum stating that this is not the case, and when the client goes to the
> SUS
> 1 server, the older update agent will be installed over the top of the
> Windows Update Agent 2. I would like confirmation from Microsoft on this
> before next Tuesday so we can plan accordingly.
>
>