February 4 2009

Exchange 2007 BuildToBuildUpgrade error

Whilst recently installing the Hub Transport role of Exchange 2007 SP1, the installation failed because it could not start the OpsMan server (it was disabled, another story). After enabling the service I went to reinstall the role and had the error shown below, indicated that I needed to perform the “BuildToBuildUpgrade” action.

After checking out the Exchange Team Blog (http://msexchangeteam.com/archive/2007/05/21/439529.aspx) it looked like I needed to remove a registry key.

Delete Watermark
Delete Watermark

Delete the Watermark key and restart your Exchange installation. For me, the Hub Transport role had successfully installed, it just looked like the installation said it had failed after unsuccessfully trying to start the OpsMgr services as one of the last tasks in the installation.

I use a maximum of one Google Ad per post to help offset some of my blog hosting costs.


December 16 2008

Exchange 2003 cluster with Symantec Endpoint Protection (SEP)

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.