For those of you who are unfortunate enough to have to continue to monitor Windows 2000 systems, despite the fact the OS is long out of Microsoft support, I thought I'd share an insight that was recently shared with me. LGarvin, our resident Microsoft WSUS MVP, shared with me last week that you can continue to monitor Windows 2000 systems for patch compliance in WSUS, but it takes some extra configuration. Basically, what you do is set up a stand-alone WSUS server running a down-level version to monitor just the Windows 2000 boxes. The reason for the down-level version is because Windows 2000 systems can no longer connect to WSUS server running versions higher than 3.2.7600.226. For more detailed information about how to set something like this up, see the following article on the SolarWinds knowledge base: How to monitor Windows 2000 clients with a down-level WSUS server.
One of the concerns in the scenario I just described is that of monitoring several WSUS environments at once. Since the down-level WSUS server would not be part of the production publishing environment, you would typically need to monitor both environments in separate consoles. With a patch management product like SolarWinds Patch Manager, the ideal patch management software, you can monitor multiple WSUS servers, regardless of whether or not they are related to one another. As mentioned in the KB article, Patch Manager no longer supports Windows 2000 clients, but that shouldn't stop you from leveraging it to make your life a bit easier. Will you be able to publish patches for the Windows 2000 systems from Patch Manager? No. But at least you'll be able to see everything in one place.
For additional information about what Patch Manager, patch management solution can do for your WSUS environment, check out the Patch Manager product page. Patch management, simplified!