25% of the time, it fails to open, and even when it does work, it seems to be very slow. this is a test system with plenty of hardware resources. running server 2k3r2 sp2. Exchange 2k7

Mike An MMCrunning slow makes me think of resources accessed on the network. Perhaps connectivity to a DC/GC or availability to resources through a firewall. If it were DC/GC-related, you would expect to see related errors on the DC and on the host. Starting up the Exchange Management Console also instantiates an Exchange Management Shell instance. If there were corruption or incompatibility issues in one or more of the constituent components, that might cause the kind of behavior you're experiencing. It might be worth updating or reinstalling .Net or PowerShell, just to make sure. A failure like you describe should also generate an error in the Event log. Have you seen anything in the System or Application logs that can be associated with the failure or slowness events? Finally, you may want to run Exchange Best Practices Analyzer, if you haven't already to ensure that the system you are working on is correctly configured. Regards, Larry

Mike Crowley wrote: 25% of the time, it fails to open, and even when it does work, it seems to be very slow. this is a test system with plenty of hardware resources. running server 2k3r2 sp2. Exchange 2k7 I have the SAME problem and it is related to Windows 2003 R (64-bit) SP2! It was working fine and when I installed SP2, it takes abotu 5 minutes to open System Manager. With Exchange 2007 SP1 (built 206), the speed improved tremendously from before... -Glenn

Flglenn - interesting. it was around the time I installed sp2 that i noticed this issue. not sure why i didnt put 2 and 2 together. I dont have time to beta test exchange sp1 but i'll give it a try when it comes out. in the mean time i guess its a good time to learn powershell (ugg).

Ditto for me on our 64-bit system. Exchange SP1 didn't seem to improve anything in our case.