• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 820
  • Last Modified:

Creating Software Update Packages in SMS 2003

When creating software update packages in SMS 2003, is there a way to only add the updates from the previous patch Tuesday into a package? For example, our current package for updating Windows XP clients is up to over 900 megs now. We don't have a problem keeping this package to bring new Windows XP clients up to speed with patches, but for clients that already have those updates from the past, we would like to use a much smaller package with only the most recently released patches and push it out after patch Tuesday. There doesn't seem to be a way to tell the most recent updates when using the software updates wizard. Any help is appreciated. Thank you.
0
WabashIT
Asked:
WabashIT
  • 3
  • 2
1 Solution
 
thesupplyguy26Commented:
We break ours down by the year. 2006, 2007 etc. When you create the packages you can name then what you please. We ususally have the Yearly patch that would contain everything except the current months patches. and then roll those up into the yearly patch when Septembers are released. Make sense or did I misunderstand the question?
0
 
WabashITAuthor Commented:
I'm wondering how you can tell the date the patches are released. Right now I just see every patch that's been released for the life of the product. I can narrow them down by product, but I can't tell the newly released ones from the old ones. The KB numbers don't seem to always go chronological. If there was a way to tell when the patch was released, we would be all set. Am I missing that somewhere?
0
 
NJComputerNetworksCommented:
having the All Inclusive package is OK.  The size only means that you should not use the Download and execute method.  Instead use the Run from Distribution point.

During the SMS Microsoft Updates scan on the client, a database is created to show which patches are installed and what patches need to be installed.  This information is used when running the all inclusive patch package on the client.  Even if the package contains 100 patches and is 2GB's in size, the client will only install the 5 patches it needs.  In this way, only 20MB (for example) traverses the network and installs on the client.

What I do, is I have two sets of packages.  One is the All Inclusive monster package (like 1GB) in size.  The advertisement for this one says Run over the network (and don't download and execute).   This package runs once a month....every month.

Then, each month, the patches come out...  I create a monthly patch package (usually well under 100mb's in size).  I program this adverisement to "download and execute"  This advertisement is distributed to the clients as a one time distribution.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
WabashITAuthor Commented:
NJComputerNetworks,
Thanks for the info, we do run the all-inclusive from the distribution point. There's no problem there, and doing it that way will of course work. I just think it would be nice for us to do it the same way you detailed.

How do you create the monthly patch package? How can you tell which patches are from the previous month? That's my exact question. Are you able to sort them by release date when creating the package?

I'll be out shortly until the 15th, so I'll be slow on responding until then. Thanks for your help so far.
0
 
NJComputerNetworksCommented:
Microsoft typically releases security patches the SECOND Tuesday of each month.  So, you need to go to this website to see the monthly patches released: http://www.microsoft.com/technet/security/current.aspx

This will be easy to group the patches on a monthly basis going forward.  However, to go back in time, you will need to type the KB number into the search (on http://www.microsoft.com/technet/security/current.aspx page) to find out what month it was released.  As far as I know, there is no way natively in SMS to figure out what month the patch was released in the ITMU Wizard.
0
 
WabashITAuthor Commented:
NJComputerNetworks,
That's exactly what I needed. I just didn't know if there was a simpler way to do it than manually dividing them up. That's still easy enough though. Thanks for your help and patience while I was away.

Thank you supplyguy for your input as well.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now