As we all know, as of July 14 2015, Windows Server 2003 will no longer be a supported operating system. This means that customers using Windows Server 2003 will no longer receive new security updates, non-security updates, free or paid assisted support options or online technical content updates from Microsoft.
However, it isn’t that well publicised that on this same date, customers using System Center Endpoint Protection on Windows Server 2003 will stop receiving updates to antimalware definitions and the engine for Windows Server 2003.
As a result, the SCEP agent will stop functioning. Starting on July 14 2015, systems running Windows XP and Windows Server 2003 that have the System Center 2012 Endpoint Protection client installed will receive the following system tray notification:
After a reasonably painless recent rollout of SEP v11 to our fleet, we’ve come across some issues running it on a Windows 2003 Active-Passive Exchange 2003 cluster. Symptoms: nodes unresponsive, sometimes together, sometimes minutes after the other one – not even blue screened but completely unresponsive, nothing on the console.
Anyway the short of it was that we managed to get a memory dump and learned that system32driverswpsdrvnt.sys had been causing the issues. Doesn’t ring a bell? Well it’s the Sygate Personal Firewall which has now been rolled into Symantec Endpoint Protection, the network threat protection component.
We obviously didn’t want to completely remove AV from our email system if possible, so we modified the installation to only contain the core files plus AV protection (see below)
2 weeks running like this and the problem has not reoccurred.