Exchange 2010 EMC connects to wrong server

Question

I have an Exchange 2010 organization installed at two sites with one server at each site. I set up my local site first. Exchange Management Console always chooses to connect to the remote server instead of a local one. I can open the properties of "Microsoft Exchange On-Premises (remotemail.example.com)" and tell EMC to connect to the local server, but it ignores the request and stays connected to the remote server.

How do I get EMC to default to the local server, and why can't I change which server it connects to?

Solution 1

You can try this approach or check the bindings in the Default WebSite in IIS. Is should point to "All Unassigned". Please read-through this article as well.

Solution 2

This discussion provided the answer. When I started Exchange Management Shell, it attempted to connect to the local server and failed with the message:

The system load quota of 1000 requests per 2 seconds has been exceeded

I followed the quick-fix advice of running iisreset, and it appears to be working at the moment. If the issue reoccurs, I will change the PowerShellMaxCmdlets and PowerShellMaxCmdletTimePeriod properties using Set-ThrottlingPolicy.

Comments

[Craig Putnam]

That wasn't it, but it did point me in the right direction. I got an actual error message when I fired up the Exchange Management Shell (thanks MS for hiding the error in EMC).

[Jeremy Lyons]

When this happens in the future, you can just recycle the MSExchangePowerShellAppPool app pool so you don't disrupt client access.