Re: Determining Patch Level for Client
- From: Bill <Bill@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 30 May 2006 07:58:02 -0700
Michigan, Mt. Clemens to be exact.
"Kim Oppalfens <MVP>" wrote:
Where are you located?.
--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Bill" <Bill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B63F0B77-9747-4D0A-9963-45812F1EDEBA@xxxxxxxxxxxxxxxx
ah, thanks, that makes sense... I really need a consultant who can spend
a
few days going through my SMS and making sure I am up to speed on it...
any
recommendations or MS resources I can tap into?
"Kim Oppalfens <MVP>" wrote:
Sms does report which patches have been reported how many times.
The interface shows this as the number in the requested column.
The wizard only displays patches that have been requested by at least one
client + patches that were released in the last 30 days.
You don't necesarrily advertise all patches to all clients.
You could subdivide a package per Os for instance.
But you don't directly target patches just at machines that need that
single
patch it would be way too much work to do that.
you simply build a package per os and initially add all patches that have
been requested, subsequently if new patches come out you just add them to
the existing package.
--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Bill" <Bill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A30DC92-9EBC-4385-8C91-29C0F43B2555@xxxxxxxxxxxxxxxx
Thanks, but I am not quite following this. There are about fifty
million
patches, and since I am getting this SMS going late in the game, should
I
build one advertisement with ALL the patches? SMS doesn't seem to help
me
organize them like I wish it would.
My goal is to get all clients fully patched, but there are so many
patches....
"Kim Oppalfens <MVP>" wrote:
You actually don't investigate the clients.
The clients have intelligence built-in to know which patches they need
and
which patches they don't.
So the general idea is that you advertise all patches anyone reported
as
needed to all clients.
--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Bill" <Bill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FD45FBAA-A316-4C83-B00B-59A07EAE5B41@xxxxxxxxxxxxxxxx
OK, I have everything working, and I am pushing updates to my test
group.
I am trying to understand how to query a client and find out what
patches
a
particular machine needs. I can't seem to find any documentation on
how
to
determine which patches a machine needs from within SMS...
Can anyone give me a link to a walk-through, or set of instructions?
If I
have to examine each computer individually, it will take me forever
to
get
everyone patched.
- References:
- Re: Determining Patch Level for Client
- From: Bill
- Re: Determining Patch Level for Client
- Prev by Date: Re: Determining Patch Level for Client
- Next by Date: Re: PREFSERV Tool
- Previous by thread: Re: Determining Patch Level for Client
- Index(es):
Relevant Pages
|
Loading
