Re: Fresh software updates

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 07/20/04 

Date: Tue, 20 Jul 2004 11:13:04 -0700

This is a commonly reported problem and is actually caused by your ISP or
internal proxy servers caching content. Microsoft makes the MSSECURE file
available at the same time the bulletins are released. We've had reports of
it taking hours to days and occasionally longer for the file to become
available to our users however due to caching issues. We've worked with
several ISP providers to make sure they are not caching the file, but
obviously we haven't reached them all.

As for the statement below, it is not correct. Under default site and scan
tool settings it can take up to two weeks for update information to reach
the SMS database. This is because of the latency involved in the default
advertisement settings and the default HINV settings which are each set at
"run once every 7 days." These settings are completely configurable in your
environment and can be tuned to meet your needs based on the conflicting
requirements of bandwith utilization and up-to-date status. This has
absolutely nothing to do with the mssecure.xml file or the MBSA scan tool.

Please see chapter 6 in the SMS 2003 Operations guide for detailed
information on the SMS software update feature. Addtional information on
expedited patch scenarios is available on the SMS site on Microsoft.com. 

-- 
Adam Welker
This posting is provided "AS IS" with no warranties, and confers no rights.
"tom" <tom@discussions.microsoft.com> wrote in message
news:67A42213-7818-4486-9EB7-135573A36B95@microsoft.com...
> Per MS it can take up to two weeks for patches to hit the MBSA, further
the scan tool needs to run a reocuring basis as well as HW inventory.
>
> Patch managment in SMS is pro-active, not reactive...you can also create a
package manually and get it out if its not in the catalog...hope this
helps...
>
> "Jim" wrote:
>
> > The problem seems to be with Microsoft not updating the MSSecure.cab
file.  I manually downloaded this file and the date is from 6/23/04.  That
matches the one on my SMS server.  SUS has the updates just fine, but not
SMS.
> >
> > "JavierSN" wrote:
> >
> > > Well, It's been about 20 hours since the updates were
> > > published, and still no sign of them in the console.
> > >
> > > This has happened in previous months as well. It takes
> > > ebtween 24 and 48 hours for the new updates to show up.
> > > This is seriously inconvenient when you're trying to
> > > deploy critical updates.
> > >
> > > Anyone has any suggestions to speed up the appearance of
> > > new security updates?
> > >
> > > Regards,
> > > JavierSN
> > >
> > > >-----Original Message-----
> > > >Present situation: New critical updates were made
> > > publicly
> > > >available over 6 hours ago. Since then, I've ran the
> > > >following steps 3 times:
> > > >
> > > >1- Succesfully ran Sync tool manually through the control
> > > >panel on my Syncing machine.
> > > >2- Succesfully ran Scan tool manually through the control
> > > >panel on the same machine.
> > > >3- Forced a hardware inventory on the same machine.
> > > >
> > > >Aditionally, SMS ran Sync tool on the same machine by
> > > >advertisement schedule about 3 hrs ago, and Scan tool
> > > >about 2 hours ago.
> > > >
> > > >The new updates still do not appear on the "Software
> > > >Updates" section of my management console, and I cant
> > > >start the patch management process because SMS still
> > > >doesn't know about these updates.
> > > >
> > > >I should mention that 2.5 hours ago, the sync log
> > > >reported "Distribution Points updated successfully.", and
> > > >since then I've ran the scan tool and hinv twice.
> > > >
> > > >My question is twofold: Why is it taking so long for SMS
> > > >to realize there are new updates? and what can be done to
> > > >speed-up the patch management process of recently
> > > released
> > > >updates?
> > > >.
> > > >
> > >

Relevant Pages

  • Re: SMS SUS and Update Rollup 1 for XP (826939)
    ... An SRP like this is handled outside of the SMS SUSFP. ... SUSFP by using the DSUW (Distribute Software Updates Wizard). ...
    (NT-Bugtraq)
  • Re: Office 2007 Deployment
    ... Other than the SMS restarts it's identical I ... and also in the Updates directory. ... It could be it has problems uninstalling Office 2003.. ... then rerun advertisement for office 2007 install does ...
    (microsoft.public.sms.admin)
  • RE: SMS Admin Issues
    ... SMS do NOT use GPO's to deploy the updates to the client computers. ... By default it will check update for every day but it will only install the ... "Active Directory System Group Discovery" this discovery can detect the OU ...
    (microsoft.public.sms.admin)
  • Re: Setup question
    ... specific types of software updates. ... Microsoft Updates. ... When you install a scan tool, you run a separate msi setup outside the SMS ... What exactly do you want to do with these 10 servers? ...
    (microsoft.public.sms.setup)
  • Re: how to delete obsolote Inventory Tools
    ... > discussing issues related to the software updates feature of SMS. ... > As for getting rid of the old scan tool types in inventory, ... > the client isn't still being scanned. ...
    (microsoft.public.sms.admin)