Re: Update Site Catalog?
From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 02/22/05
- Next message: Adam Welker [MSFT]: "Re: Software Update Package Config"
- Previous message: Bob Findlay: "RE: Commandline is blank in execmgr.log"
- In reply to: Richard: "Re: Update Site Catalog?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 07:19:53 -0800
The security update sync tool only affects updates detected by MBSA. You'll
actually have to create two packages, with two different types. One will be
your normal monthly security updates package with type "MBSA" or type
"Security" depending on your installation. The other will be for those
updates not detected by MBSA, which requires scanning with the EST tool and
receiving inventory back from those clients. The type for these updates
will be different than the type for MBSA updates.
-- Adam Welker This posting is provided "AS IS" with no warranties, and confers no rights. "Richard" <Richard@discussions.microsoft.com> wrote in message news:B24BF5F2-F2DF-402F-802D-C4A9284EBFEF@microsoft.com... > So does this mean that in order to use the February 2005 Update tool I'll > have to do: > > - Install the February 2005 update tool. > - Scan the clients using the February 2005 Scanwrapper.exe > - Run the Security Update Sync tool on the site server (from the original > security updates add-on) > - Collect HW Inventory from each PC. > - Under the Security Updates node locate: MS05-004, MS05-006, MS05-009 > updates to make sure they have been downloaded. > - Create a new package for the February Updates. > > Am I understanding this correctly? I ask this because this is what I am > currently doing and not noticing the updates under the Security Updates > node. > Is there something I'm missing here? > > "Adam Welker [MSFT]" wrote: > >> The ability to update the database for pre-scan approvals is only >> available >> currently in the MBSA and Dell Update scan tools. These interim scan >> tools >> for picking up deficiencies in MBSA simply do not have development time >> enough to provide said functionality. We do understand the difficulties >> this presents, and are working on a more permanent solution. >> >> -- >> Adam Welker >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> >> "Walt" <whowd@NOSPAMtruman.edu> wrote in message >> news:uEfKZSFEFHA.1564@TK2MSFTNGP09.phx.gbl... >> > This is the same behaviour that I saw, and it is disapointing. I would >> > have assumed this new EST tool would mimic the SP1 behaviour of >> > preauthorization rather then taking a step backwards to the RTM model. >> > >> > w >> > >> > "Andrew Cohen" <andrew_!dot!_cohen@cox_!dot!_com> wrote in message >> > news:%23K$vbcDEFHA.1408@TK2MSFTNGP10.phx.gbl... >> >> I'm using the SMS Feburary Update Scan Tool on SMS 2003 SP1. The >> >> February scan tool will not allow preapprovals. Very disappointing. >> >> >> >> >> >> >> >> "Adam Welker [MSFT]" <adamwel@online.microsoft.com> wrote in message >> >> news:u0tTwtuDFHA.1936@TK2MSFTNGP14.phx.gbl... >> >>> Preapprovals are only supported on SP1 sites. For RTM sites you will >> >>> need to process Hardware Inventory data from scanned clients before >> >>> the >> >>> updates will show in the site UI. >> >>> >> >>> -- >> >>> Adam Welker >> >>> This posting is provided "AS IS" with no warranties, and confers no >> >>> rights. >> >>> >> >>> >> >>> >> >>> "Shehzad Khoja [MSFT]" <srkhoja@online.microsoft.com> wrote in >> >>> message >> >>> news:OiDf$XlDFHA.3120@TK2MSFTNGP15.phx.gbl... >> >>>> Adding more appropriate news goup >> >>>> [microsoft.public.sms.software_updates] >> >>>> >> >>>> -- >> >>>> This posting is provided "AS IS" with no warranties, and confers no >> >>>> rights. >> >>>> >> >>>> >> >>>> "Dave.McKenna" <Dave.McKenna@MurrayState.edu> wrote in message >> >>>> news:ejhMryeDFHA.228@tk2msftngp13.phx.gbl... >> >>>>>I seem to be having a problem getting the site catalog to update >> >>>>>after >> >>>>>automated downloads of MSSECURE.CAB. The file downloads correctly, >> >>>>>but >> >>>>>SecuritySyncXML.log shows: >> >>>>> >> >>>>> Checking if patch preapprovals are supported by site [my site >> >>>>> server] >> >>>>> Patch preapprovals not supported by site [my site server], skipping >> >>>>> site catalog updates >> >>>>> >> >>>>> So, I can open the MSSECURE.CAB in C:\Program >> >>>>> Files\SecurityPatch\PkgSource\1033 and see the most recent patches >> >>>>> & >> >>>>> updates, but those updates never seem to make it into the "Software >> >>>>> Updates" in SMS. How do I support patch preapprovals, or is this >> >>>>> just >> >>>>> a red herring that doesn't really explain why I don't see what I >> >>>>> expect to in SMS? >> >>>>> >> >>>> >> >>>> >> >>> >> >>> >> >> >> >> >> > >> > >> >> >>
- Next message: Adam Welker [MSFT]: "Re: Software Update Package Config"
- Previous message: Bob Findlay: "RE: Commandline is blank in execmgr.log"
- In reply to: Richard: "Re: Update Site Catalog?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
