Best Practice for SUS?

[bkrauthamer]

Hi,

After installing SMS 2003 and getting 500+ clients recognized and added to my site, the first Software Update distribution was simple. I advertised the scan tools to the collection, created an advertisment with EVERY available patch and update up to that point and published the advertisement to the collection. Now, MS has released the April 2004 security/patch updates. What is the best way to build a package using only the LATEST updates since the last software update package was advertised? Or do I have to build a new package each time with ALL current patches and updates in it and let the clients choose the ones they need?

Thanks,
Bryan

 

[tbrennans]

Ask 5 diff admins get 5 diff answers. Some guys have been doing an uber-patch (one forever growing patch for all OSes) others are breaking them down to OSes. At any rate, seems the most practicle thing is to just keep adding to exisiting patches to your existing package whether it is by os or just one huge one. This way if someone without a certain patch logs on they will get it after they get a client.

Personally I wouldnt bother with making a new one everytime.

Tim B

 

[bkrauthamer]

Thanks Tim! That makes sense. Still learning this as I go (could not get the company to pay for SMS training). What is the easiest way to ADD more patches to an existing package?

Many thanks,
Bryan

 

[tbrennans]

You just re-run the DSUW wizard which allows you to edit the package and patches inside it just like the first time you created it.

 

[tbrennans]

On another note (thats really cheap for what ya get)

check out

http://www.learnsms2003.com/demo.htm

take a look at his demo's see what ya think actually the one demo should come in handy for ya.

 

[bkrauthamer]

Tim, thanks for taking the time to answer a couple of silly questions! The demos are BOTH very helpful!

Bryan

 

[tbrennans]

Never a problem