Discussion Locked

how do i evaluate a patch ?

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

microsoft releases many patches periodically . how do i evaluate these patches after applying them to servers. for : EX we have latest patches like MS03-026. MS03-027 & 028 . i have applied patch from MS03-026 to win2k server & now i want to test what this patch does & its upshot before i apply this patch to all the servers.

how do i test a patch ??

2 replies

by thechas

Start by reading the Tech-Net bulletin about the patch.

You should get details as to what vulnerability was fixed, and perhaps what files were changed.

To check the 'fix' that the patch implements, you need to duplicate the conditions that would cause an error or system compromise.

To check that the patch does not 'mess' things up, you need to run the PC (server) through a number of tests with normal usage and applications. The more applications you test, the more faith that you can have that the patch did not cause any un-intended problems.

Chas

by ann777

You basically need to look at the applications you have and what the patches accomplish and how they affect the Microsoft Foundation Class files (mfc*.DLL, etc).

For instance MS03-026 will affect any programs that use a non-standard DCOM. Unfortumately, not all programmers use standard files and many re-write some of the DLLs in their own way to make use of them in different flavors. Another unfortunate part is that this is particular patch is a critical patch and should not be avoided.
Reinstalling the application might fix a problem that the patch causes -- probably because a specific version of a DLL is expected and gets reinstalled with the application install -- but in turn, it will probably break the patch.

If you have standard (Microsoft) applications and do not use any specific programs that developers have written for specific tasks, then you're probably okay. But you will need to test every single application.

Look out specifically for applications that:

1) Replace ANY DLL’s in the Windows/WinNT – System/System32 directory
2) Replace ANY DLL’s in the Program Files\Common Files\Microsoft Shared directory
3) Follow BAD programming practices by requiring a specific version of a DLL(This may be hard to determine).

This discussion is closed to new replies.