There is some incompatibility between Forefront and Outlook Web App, that is periodical and really annoying. (see screenshot of the error screen below) Luckily you just need to stop all services, disconnect Forefront from OWA, restart the services, stop them again, connect Forefront to OWA and finally start all services again. Here is the breakdown with screenshots:
OWA error:
First off, on the server that runs OWA we start the Services snap-in, services.msc:
Than we locate all the services that start with “Microsoft Exchange”:
We stop them one by one, if a service has dependencies we will get a notification of that and we can stop them too:
Some services take a long time to stop, be patient:
After the first service and all of its dependencies are stopped we still have some left:
Now that all the Exchange services are stopped, we need to stop all the Forefront services:
Now we start a command prompt:
Navigate to the Forefront installation directory and run “FSCUTILITY.exe /status” just to make sure that forefront is indeed enabled:
See the last line of the output? It is integrated:
Lets change that, simply run: “FSCUTILITY.exe /disable”. It should output something similar to this:
Now let us start the Exchange services:
The Forefront services will start automatically, if not leave them stopped:
Now we re-integrate Forefront via “FSCUTILITY.exe /enable”
And start the Forefront services if they didn’t already start automatically. Note: i didn’t start ALL the Forefront services, only the ones that where previously running:
Because we have 2 nodes that run Exchange services, I usually like to stop the affected node entirely via the Server Manager under the Features -> Failover Cluster Management:
Simply select the node, left click on it and select Stop:
It will mark it as “Down”:
And switch automatically to the other (running) node:
