What’s the best way to track when and which hotfixes/patches were applied? It’s an endless debate amongst IT pros. Some would like to do it through dedicated patch management software. Some store this info in databases, even spreadsheets.
Here are a few handy ways to track this info – I’ve used a combination of these to track stuff.
i) On Dell servers installed using Dell’s Server Assistant CD, there’s a installsummary.htm file in the root (C:\). Every time I apply a bunch of hotfixes/patches, I simply open this html file and add the info at the very bottom of the list. If you do this from Windows Update, all you need to do is copy the list of hotfixes from the Windows Update web page (AFTER it finishes installing, but before you hit OK to reboot if a reboot’s required). Just add a line break tag at the end of each line.
Additionaly, I also copy this html file to a web server every time I do this, adding the server name to the end of the filename.
ii) For all recent hotfix installations, just filter the System event log for Event ID: 4377, source: NtServicePack. This event lists the hotfix applied, date, time and the username.
Want to upgrade NetApp SnapDrive 3.x to 3.1?
You’ll need 3 hotfixes, 2 of these cannot be downloaded from microsoft.com. You need to call Microsoft Product Support Services for these :
1. KB838894 – An updated Storport storage driver (version 5.2.3790.173) is available for Windows Server 2003
2. KB831112 – [Call PSS] You cannot import a transportable shadow volume in Windows Server 2003
3. KB840281 – [Call PSS] Volume information is lost when you extend a partition by using the DiskPart tool and then move the volume in a Windows Server 2003 cluster
Most of these hotfixes that are available from PSS are intended to correct specific issues only, and should not be applied if these issues are not faced. These come with the standard PSS disclaimer – these hotfixes have not been regression-tested, backup before you apply, et al.
To add a “Back” text link to a web page:
Using VBScript and FORM button:
<form method=”POST” name=”VBScript_Nav_Sample”>
<input type=”button” name=”Go Back!” value=”VBScript_Backup_Sample” language=”VBScript” onclick=”call window.history.back(1)” /<
Using Javacript and FORM button:
From Microsoft KB Q205693