Active Directory server exch01.xxx.com is not available. Error message: A local error occurred. It was running command 'get-ExchangeAdministrator'. The following error(s) were reported while loading topology information: get-ExchangeServerFailedError:Active Directory server exch01.xxx.com is not available. Error message: A local error occurred. A local error occurred. get-UMServerFailedError:Active Directory server exch01.xxx.com is not available. Error message: A local error occurred. A local error occurred.

Create a new account, fg. Paul and add the Paul to the Exchange Organization Administrators group and Enterprise Administrators group. Logon as Paul, then you should access the Exchange Management Console. Even I deleted the default Administrator profiles, the Active Directory not available with Get-ExchangeServer message still shows. Something is the local error as the message points out. But I don't know yet. Anyway, you could manage your Exchange 2007. Good luck! KML

This bug has been in Exchange 2007 since day 1. SP1 does not fixthe problemas some claim. My server is bang up-to-date via Windows Update and still has this problem. The user profilegets 'corrupted' in some way. The standard fix is to create a new admin account (fine until that one goesbad onyoutoo) or to re-create the affected user's profile in the usual way. If you do the latter you must reboot the server between deleting the affected user's profile and logging back on as that user to create a new one, whichmakesthis bug*really* creepy IMHO! This bug is insidious and needs to be givenmore urgency by Microsoft. This forum is littered with threads all caused by the same problem dating back to the original RTM. It appears that this bug is .NET 2.0 related in some way. NEW INFORMATION This problem appears to be due to erroneouscached password. Have discovered that this fixes it, which is far less onerous than recreating profiles: 1. Start -> Run 2. Enter "control keymgr.dll" 3. Remove all stored passwords relating to Exchange servers and DCs Not figured out how these get there in the first place yet.

Well, from the last entry about the keymgr, I know exactly what caused this issue for me - hope it helps some others. I created a test profile in OL2k7 on the server connecting to the Exch server. I checked to save password - this seems to be the mistake. I can only assume that EMC is somewhat IE based - and when connecting to the exchange server - with a user's creds - EMC tried to use those same creds to access the exch admin functions. Since the user creds didnt' have admin rights - it failed. Deleting the keys from keymgr.dll DID resolve for me, though I wouldn't consider this a bug - more the typical undocumented feature .

Hi, this keymgr.dll was helpfull for me as well.I hawe a windows server 2008 with exchange 2007 and after I installed virtual server 2005 R2 on the win2008 our exchange crashed.After a reboot still the same. So I found this solution and tried it.It works.I don't know why, but it is a solution.Cheers

Thanks, this worked for me too.

Hi,Active Directory server is not available error please follow the below steps and let me know what happens/Delete the forward lookup zone corresponding to your AD domain again. Rundcdiag /fix followed by netdiag /fix andrestart the server.Thanks and u have good day, Sachin Shetty| MCP|MCTS|MCITP|

Thanks very much. The keymgr works for me as well.

This bug has been in Exchange 2007 since day 1. SP1 does not fix the problem as some claim. My server is bang up-to-date via Windows Update and still has this problem. The user profile gets 'corrupted' in some way. The standard fix is to create a new admin account (fine until that one goes bad on you too) or to re-create the affected user's profile in the usual way. If you do the latter you must reboot the server between deleting the affected user's profile and logging back on as that user to create a new one, which makes this bug *really* creepy IMHO! This bug is insidious and needs to be given more urgency by Microsoft. This forum is littered with threads all caused by the same problem dating back to the original RTM. It appears that this bug is .NET 2.0 related in some way. NEW INFORMATION This problem appears to be due to erroneous cached password. Have discovered that this fixes it, which is far less onerous than recreating profiles: 1. Start -> Run 2. Enter "control keymgr.dll" 3. Remove all stored passwords relating to Exchange servers and DCs Not figured out how these get there in the first place yet. I just changed my DNS settings (on the exchange server) and all went back to normal! thanks anyay.