5 replies
by bkinsey1
Since most patches and hotfixes simply update god-knows-how-many files (and some are only trackable by registry key), it's probably easier and more comprehensive to do it with MS's tools.
Hfnetchk (http://microsoft.com/technet/security/tools/tools/hfnetchk.asp) does this on NT and 2000 machines from a central location on your network.
The Microsoft Baseline Security Analyzer (http://microsoft.com/technet/security/tools/tools/mbsahome.asp) does the same basic thing, but also checks IIS, SQL Server, and Office.
It's not a perfect solution to hotfix and patch management, but it's better than it used to be. (And easier than trying to identify which files should be changed to which versions by which patches installed in which order and using Track-It to do your auditing.)
by jgreer
by joseph moore
Hotfixes all write into into the Registry, so if you could add that info to your program, then do so.
If not, I know of a good Hotfix/Patch network-wide management program, called Patchlink Update 3.0:
http://www.patchlink.com/
by jgreer
by jgreer
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending