System: Exch2007 sp1 on Win2003 R2 x64 The EMC is so slow to open afterI decommisioned one of the domain controllers that was inplace during the Exch2007 install. Prior to decommissioning this dc the console opened in less than 5 seconds, now it takes 2 minutes to open. Its as if the exchange server is still looking for the old decommissioned dc! Here is what happens: 1. Click on the EMC icon 2. I get a small window in the middle of the screen that says "Expand" and a blue progress bar scrolling across for at least 2 minutes. 3. Finally another window opens: "End Snap-in" This snap-in is not responding....blah blah I can click either End Now or Cancel 4. Behind the "End Snap-in" window the EMC has finally opened Any thoughts? Thanks!

I don't know if this is relevent or not but the old (decommissioned) dc was Win2003 sp2 x86 and the new dc is Win2008 x64.

After a little more digging I think this may be related to the global catalog that the 2007 server is looking at. There is still an old (read=sloooow)2003 dc/gc server on my network (that I will be decommissioning soon). It appears that my exchange server is choosing to use that old slow server instead my2 brand new shiny 2008 dc/gc servers. How can I specify which gc server my exchange 2007 server uses?

Hi, Is it PDC Emulator also? By default, DSAccess chooses it to handle requests in Microsoft Exchange and face poor performance if other programs are heavy using PDC emulator. http://support.microsoft.com/?id=298879 DSAccess scan every 15 minutes to search all GCs & Dcs in in-site and out-site. You can use below command to exclude it from being used. Set-ExchangeServer -Identity Exchange Server Name StaticExcludedDomainControllers DCs & GCs Hope this helps!

Hi Amit, All the FSMO roles were transferred to one of the new 2008 dc's prior to decommissioning the 2003 dc I referred to in my first post. Thanks for the reply. Jeremy

Hi Jeremy, Personally, I also like to confirm you about below questions: 1) Do you find any error/information regarding it in application log? 2) whether there is any subsequent issues? such as does Outlook client access normally etc. Beside checking which DC\GCs is using by the Exchange Server, I also suggest we use Exchange Best practice analyzer(BPA) tool for analyzing. Exchange 2007 shipped it in toolbox. Below are the Process: 1) open EMC 2) Select the Go to Welcome screen option. There is no need to check for updates since you now have the latest version. 3) Choose Select options for a new scan 4) The name of the AD server should be populated. If it is, click the option to continue using the listed GC. Otherwise, enter the name of a GC. 5) Type a label for this scan. Just entering the date would be fine. 6) Leave all of the options at their defaults. The scope should have all servers checked and the type of scan should be Health Check 7) Dont select the Performance Baseline option because that takes 2 hours to complete. 8) Select the speed of the network. 9) Click on the Start Scanning option. 10) The scan will take several minutes to complete. 11) Click on the option to View the Report. If there is any existing information, please post here for discussing. I hope your issue resolves soon. Regards, Jason