One of my clients has an Enterprise Agreement with MS & as part of this they migrated to Exchange 2007. Now thanks to the EA, they are allowed to use ForeFront Security for Exchange on their servers at no additional charge- this makes sense too since it does integrate so well into the Exchange 07 Org.

So I went in there yesterday to deploy & configure the forefront on their Hub/Cas and Mailbox SCC Cluster servers. I started with the hub/cas servers & everything went Great, it took a while to donload updates- I think the MS site where you get them from is reasonably busy so many timeouts while downloading but they came eventually.

I also configured one of the HUB/CAS servers as an update distribution server so the other 3 servers on the network do not have to download from the web.

As expected, all of the above went smoothely with no problems @ all! How ever, once I got to deploying it on the Single Copy Cluster I found that somewhere in the middle of the installation (in fact before it begins copying files) the installation crashes, just literally disappears off screen!

I tried the installation several times on both nodes with different accounts & for the life of me could not get it to work. Eventually, fed up with being stubborn I resorted to asking google, which gave me the solution & get this:

The solution was to rename the Exchange Cluster Group so that it has the same name as the Exchange Network Name Resource.

See the following MS KB: support.microsoft.com/kb/934287

Now lets consider: its MS ForeFront, MS Windows, MS Clustering & MS Exchange - surely their AV should be able to differentiate between the various cluser groups & install its resources in the correct one with out us having to rename our groups, which in some cases may have been done according to a naming convention...