APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Some material is very old and may be incorrect today

© September 2003 Michael Desrosiers

I don't need no stinkin patches!!

Email: [email protected]

More Articles

Patch management is an essential administration task. By providing updated patches to your environment, security experts agree, that up to 80% of known exploits and vulnerabilities would be rendered trivial. This consists of scanning machines on the network for missing patches and deploying those patches as soon as they become available. Failure to do so makes a infrastructure vulnerable, because not only is the vulnerability there, but it has now also been publicized, making it more likely to be exploited by malicious users, hackers and virus writers.

The problem seems that time and again countless administrators fail to apply the right patches, as proven by worms such as Slammer, the January 2003 worm that spread by exploiting known vulnerabilities in non-patched Microsoft SQL 2000 servers. Until recently, the main reason for this was because installing patches in a large environment, was a cumbersome and daunting job.

Microsoft SUS is a free patch management tool used to help administrators deploy security patches and service packs, more easily. Instead of each workstation having to connect to the Internet to update Windows, each workstation connects to a trusted (internal) SUS Server instead, and updates from there. The SUS Server alone requires access to the public Internet as it connects to Microsoft's Windows Update server.

By connecting to Windows Update, the SUS Server provides notification of critical updates as well as performing automatic distribution of those updates to your workstations and servers. The SUS server gives the administrator control over updates: The administrator can test and approve updates from the public update site before deployment on the corporate intranet. Deployment takes place on a schedule created by the administrator.

To find out more about how automating Windows updates can be done in your environment, please visit http://www.microsoft.com/windows2000/windowsupdate/sus/default.asp for more information.

Other Patch Management tools:
HFNetChkPro 4.0 from Shavlik - http://www.shavlik.com/
PatchlinkUpdate 4.0 - http://www.patchlink.com
UpdateExpert - http://www.stbernard.com
BigFix - http://www.bigfix.com

If you found something useful today, please consider a small donation.

Got something to add? Send me email.

(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> I don't need no stinkin patches!!


Inexpensive and informative Apple related e-books:

Take Control of IOS 11

Take Control of High Sierra

Take Control of iCloud, Fifth Edition

Take Control of iCloud

Take control of Apple TV, Second Edition

More Articles by © Michael Desrosiers

Sat Feb 7 21:39:53 2009: 5337   anonymous

Ha, love the Blazing Saddles reference. I agree that major problems lie within applying the right patches. That's a pretty good solution having the workstations connect to an internal server. Can it be setup to work with mobile workstations from anywhere?

Sun Feb 8 20:49:06 2009: 5347   MikeDesrosiers

Yes it can. Microsoft has written a solid white paper, WSUS_remote-clients.doc on the subject. For more info, please visit (link)


Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

Printer Friendly Version

A learning experience is one of those things that say, "You know that thing you just did? Don't do that." (Douglas Adams)

Linux posts

Troubleshooting posts

This post tagged:




Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode