Exchange 2010 Mgt Console initialization failue

When opening up the Exchange 2010 Management Console "EMC"
You may see this error :  Server Initialization Failed
The WS-Management service cannot process the request. The user load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least Z milliseconds. 

The fix is to do a iisreset
Make sure you open a command prompt as an elevated user in order to run iisreset

How to change the RPCClientAccessServer for Exchange 2013

With Exchange 2013 if you have a DAG the DR server can often take on the RCPClientAccessServer name for the database.  
So you think you can use the shell command huh? Set-MailboxDatabase "Mailbox Database Name" -RpcClientAccessServer "ServerName.abccompanyname.com"
Nope this command does not exist anymore with Exchange 2013 server. So you have to use ADSIEDIT to change the legacy DN name. See below for how to change it.
Took me a while to track this down. I found a lot of hits about it a legacy DN and hwo to change it with Exchange 2010 but nothing led me to the actual location within ADSIEDIT
ADSIEDIT.msc
-Open the Configuration Container
-CN=Services
-CN=Microsoft Exchange
-CN=domain name
-CN=Administrative Groups
-CN=Exchange Administrative Group (FYxxxxxxxxxDLT)
-CN=Databases
-CN=DatabaseName
Select the DatabaseName, right-click Properties
In the Attribute Editor tab, find LegacyExchangeDN, select edit
Replace the existing servername with servername that you want
Select OK

Now to verify - from the Exchange Shell run this command below
Get-MailboxDatabase "MailboxDatabaseName" | fl Name, RpcClientAccessServer
The RPCClientAccessServer should now point to the servername that you changed above with ADSIEDIT

Error while installing Exchange 2010 SP2

First of all backup the Exchange Server databases and logs with your favorite backup software

Take a Snapshot the Exchange Server if it is virtual machine before you perform the Service Pack 2 upgrade

When applying EX2K10 SP2 you may get the error below:

Some controls aren’t valid. Setup previously failed while performing the action “Install”. You can’t resume setup by performing the action “BuildToBuildUpgrade”.

 

The Cause:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\MailboxRole\Action
Action key is present with value data: Install
The Solution:
Delete Action key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\MailboxRole\Action

Reference Article: http://azatechknow.blogspot.com/2012/02/normal-0-false-false-false-en-gb-x-none.html

  

I then attempted service pack 2 upgrade again and then I got this error below:

The Cause: Symantec Anti-Spam services have some of the listed files above open

 The Solution: I stopped all of the Symantec Mail Security Services and restarted the Service Pack 2 upgrade process again

Run the setup of EX2K10 SP2 again – Be patient again the service pack install can take a while. This time it went through...

Don't forget to Start the Symantec Anti-SPAM services again

Apply the latest Exchange 2010 SP2 Rollup patch or run Microsoft Updates - Be patient again the updates can take a while

A reboot was not  necessary however, I did one anyway

If all is well remove the VMware VM Snapshot

Your Exchange Server 2010 EMC is very slow to load

If your Exchange Server 2010 Management Console is slow to load it may be as simple as updating the service pack and or applying an Exchange rollup to the service pack.
I recently was running SP2 and Rollup4 and noticed the slowness to load the console however, once it loads it is fine. Anyway... I applied Rollup5 for SP2 and the problem was solved.

This link below is very helpful to determine what version, service pack, rollup/build # of Exchange Server you are running.
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx