During the portion of the EMC startup you describe the console is doing discovery; it's not just connecting to the one server but reading the org to determine how to populate the console's layers. I once worked on an environment where someone had stood several EX servers for testing and then just deleted the VM without uninstalling Exchange. The console was slow to load as it tried to verify the existence of the zombie servers. So, knowing you had issues with the one CAS server, what is the state of your environment? Have you run the ExBPA to see what the self-reporting has to say? This is based on the assumption that AD and the network themselves are healthy and not the source of hurdles.
---------------------------------------- > Date: Thu, 25 Sep 2014 11:44:54 -0700 > Subject: [Exchange] Exchange EMC still slow > From: [email protected] > To: [email protected] > > So...on the new CAS server I thought I'd fixed the slow EMC console issues > but it was short-lived (I think it was fast twice). I have other techs > here that is is also slow to launch for as well (slow> 3 minutes). I have > tried the following to remedy the issue, but none have worked: > > *Delete > HKCU\Software\Microsoft\Exchangeserver\v14\AdminTools\NodeStructureSettings > *Run WinRM QuickConfig > *Disable server certificate revocation > *Checked HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters - > EnableTCPA (does not exist) > *Recycled MSExchangePowerShellAppPool > *Add 127.0.0.1 crl.microsoft.com to HOSTS > > My gut says it's an authentication timeout, but it is slow at the > "attempting to connect to the specified Exchange server at > MYCAS.mydomain.org" portion. > > The management shell is fast (fixed by the WinRM change), but the EMC GUI > is sloooow to open, but responsive once it's opened. > > Ideas? > > >
