Short of looking at the IIS binaries/dll's on the host & comparing them to the SP2 versions, I don't believe there is an easy way. You're best option is to re-apply SP2 and all Post SP2 hotfixes up to the level you were already at.
In the future, put a copy of the entire Win2k3 CD (with the SP integrated) onto each machine, and change the registry to use the local copy. The registry keys are: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup SourcePath: REG_SZ: ServicePackSource: REG_SZ: If you create a folder called C:\OS_Source & copy the entire CD to this folder (+ integrate the SP here), then set the registry key to: C:\OS_Source HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ SourcePath: REG_SZ Use the path above, but append \I386 à C:\OS_Source\I386 Reboot, and any time you make a change, the OS will auto-magically use this folder for the source files. *** This also works for R2, just copy the R2 CD to the same folder, and now both CD's are in one place The downside to this approach, is if you have lots of servers, then you have to integrate the SP on each server, or do one, then copy it to all other servers. Management headache. A more elegant solution, is to create a read-only file share for the CD's on a server, and change the registry key on each server to use the UNC path. Assuming you can apply SP's to all servers with this configuration in a short time frame, integrate the SP into the folder, then apply the SP to each server. Depending on your servers, you might end up with multiple source folders, W2k3 RTM, W2k3 +SP1, W2k3 +SP2, etc... *** This also works for client PC's as well, just put the XP source files in a new folder on the same shared location, and change their registry keys. Single point of update. All of this works up to a point, and depending on your environment, may not be the best. But it has worked effectively in the mom/pop to SMB space I've implemented it. With Vista & W2k8 caching the source files locally, this is no longer needed though. Cheers. Scott Kaufman Lead Network Analyst ITT ESI, Inc. From: Bryan Garmon [mailto:[email protected]] Sent: Thursday, February 26, 2009 11:54 AM To: NT System Admin Issues Subject: Compare i386 directories? I'm troubleshooting a scenario where I think a Server was built using Server 2003 SP1, then had SP2 installed, then had IIS installed, but pointed IIS to the SP1 i386 directory for the source files. Anyone have any ideas for a quick way to figure out if this is the case? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
