Hi John:
I would like to think you would use WSUS for the functionality that it offers
in controlling the selection and timing of the update process. Yes, you
could go around to each workstation and server and specify which updates
you wanted and when, but with WSUS you have a management console that allows
you to select updates based on the timing you specify.
This allows you to postpone updates that you don't understand or don't want
that might affect your line of business application, for example, or, as
we all know, that affect the functionality of the SBS until such time as
the kinks are known and worked out.
So, for that reason, I recommend that you use WSUS to allow you to manage
the update process.
I feel fairly certain that WSUS will offer up the same number and variety
of updates as MU or WU if the selections are done correctly in the WSUS console.
-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com
> We're running SBS R2 Premium with WSUS 3 (I think)
>
> I was reviewing Update Services status since we got over moving from
> 2.0 to 3.0.
>
> For evaluation, we'd only setup three computers as clients: the
> SBServer itself; our Teminal Server; and one PC client running Vista.
>
> The Vista client says it is completely up to date with updates.
> However, it is unclear whether this was due to WSUS or to the built-in
> Update process (I'm not sure how to tell the difference).
>
> On the two servers I started Microsoft Update and on each of them
> found over 20 High Priority updates waiting to be done.
>
> Having done these (manually) I'm now at the point of wondering why we
> need to use WSUS at all (we dont have very many PC clients, <10)
>
> On the other hand, trying to uninstall WSUS seems to be a very unclear
> and problematic process.
>
> I'd appreciate any advice or recommendations on how to proceed.
>
> TIA
>
> JohnK
>