Re: SMS 2.0 Feature pack problems
From: Peter Johnson (stikfasnut_at_gmail.com)
Date: 10/04/04
- Next message: Dave Halperin: "Re: EVENT ID 4100 problem"
- Previous message: Kerwin Medina [MSFT]: "Re: Sample Logon Script"
- In reply to: Wally Mead [MS]: "Re: SMS 2.0 Feature pack problems"
- Messages sorted by: [ date ] [ thread ]
Date: 4 Oct 2004 10:49:46 -0700
Well I followed JoeSMS's advice and looked in all the logs and
everything looked like it worked. When I got the the hinv32.log, I
noticed that the Hardware Inventory had not run since before this
problem had taken place. I thought I had done that when I selected
Update Membership for that client, but I guess that means something
else.
That along with Wally's advise, it was pretty clear that was it. So I
started the Hardware Inventory Agent from the Systems Managment icon,
and this fixed the problem.
Thanks guys for your help, wish the problem was a little more complex,
but I'm a newb at this.
Wally, I'll be sure to post any new topics in the software_updates
newsgroup as I am sure I will be posting again.
"Wally Mead [MS]" <wallym@online.microsoft.com> wrote in message news:<usQ5mIXqEHA.3868@TK2MSFTNGP15.phx.gbl>...
> Did you force another hardware inventory cycle after the updates were
> applied? We only pick up current update status through hardware inventory,
> so you must collect it after the patch updates.
>
> Also, patching related posts should really be posted to the new
> software_updates newsgroup. People who concentrate on the SMS patch process
> monitor that newsgroup.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Peter Johnson" <stikfasnut@gmail.com> wrote in message
> news:29f56a69.0410011455.4a6ad9f9@posting.google.com...
> > I have recently installed the SMS 2.0 Feature pack and have setup
> > software/office update inventory installers as well as SDUW. I have
> > installed these clients on my test machine, and have also created
> > packages, programs, collections, and advertisements. Everything looks
> > good, and I have no errors. The packages are distributing to the
> > selected sites and all looks good.
> >
> > From the software scan I saw that some security patches need to be
> > in
stalled (namely XP SP2, and MSXML), so with the help of DSUW I
> > created packages and advertisements for these two. They have been
> > sucessfully installed on my test machine. I have rebooted, ran MSBA
> > and everything looks and is working great on my PC.
> >
> > However, when I go to the SMS console and I look at the Resource
> > Explorer for my test PC under Software Updates History, those two
> > patches are still listed as Applicable. Not only this, but when I run
> > the very same security check that told me to install the patches in
> > the first place, it still says to install them.
> >
> > I have even updated the collection membership for this client and can
> > even see these newly installed patches in Quick Software Inventory
> > History.
> >
> > What am I doing wrong? I can't figure it out at all. Any advice or
> > direction would be great.
- Next message: Dave Halperin: "Re: EVENT ID 4100 problem"
- Previous message: Kerwin Medina [MSFT]: "Re: Sample Logon Script"
- In reply to: Wally Mead [MS]: "Re: SMS 2.0 Feature pack problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
