Exchange 2010: Unable to open Exchange Management Console – Initialization Failed

Problem:  Exchange Management Console in Exchange 2010 will not open and references a server that is down or has been removed from the environment.

Error Verbiage: Initialization Failed

The following error occurred while attempting to connect to the specified Exchange server '':

The attempt to connect to using 'Kerberos' authentication failed: Connecting to the remote server failed with the following error message : WinRM cannot process the request. The following error occurred while using Kerberos  authentication: The network path was not found.



Method 1:

  1. Close all MMC/EMC instances before proceeding.
  2. Open Registry Editor (regedit) as the user you run the EMC under.
  3. Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14\AdminTools
  4. Look for value NodeStructureSetting.
  5. If it is there, back it up and then remove it.

Method 2:

  1. Close all MMC/EMC Instances before proceeding.
  2. Open Powershell or Powershell IDE as the user you run the EMC under and execute the following command:.
  3. Remove-ItemProperty -Path HKCU:\Software\Microsoft\ExchangeServer\v14\AdminTools\ -Name NodeStructureSettings
  4. Close Powershell

After performing either of the methods above to remove the registry entry you should be able to open the Exchange Management Console and it will discover another Exchange server and connect.


Comments (115)

  1. Anonymous says:

    Have to add my experience… Deleted the NodeStructure key, attempted opening EMC, same old same old…. had a user who's EMC did open up, so I had them export the key, then deleted mine, imported theirs and all is working fine… Ahhhhhhhh! Got Exchange?

  2. Marty_v says:

    Looks like your resolution is working pretty much across the board – didn't get to your post in time to know if it would have worked for me. Got my Initialization Failed using Kerberos authentication error fixed by starting the world wide web publishing

  3. @John Healy

    You either have removed a server from the environment, have a server offline, or a server is inaccessible due to stopped services or.local firewall.

  4. Anonymous says:

    Thank you!

  5. Anonymous says:

    Thank u

  6. Anonymous says:

    Thank you!

  7. Anonymous says:

    if all else fails. Login to IIS
    Stop all websites except the default website containing the ecp, ews owa folders etc.
    Then reconnect to the emc.
    If the connection is made, go back to IIS and enable each site individually while testing the EMC.

  8. Anonymous says:

    Hi did not worked for me. now iam getting diferent erro message after removing this regentry.

    still cannot access either of the consoles exchagne 2010.

  9. @Jac – If the time between your Exchange Server and Domain vary that much then you need to correct your time sync design. By design, every windows server will get it’s time from the domain aka domain controllers. Then usually you configure one DC to get
    it’s time from a precise source. If you have windows server with various times then either the time was never set on the server when it was installed, was set incorrectly, or is possibly using a third party time sync/NTP tool. If the server is a VMware virtual
    machine make sure the VMware Tools are NOT configured to sync guest time with the VMware Host. And yes, a large time delta between the server and domain will cause various issues as it causes Kerberos authentication to fail.

  10. Anonymous says:

    First method worked for me, thanks.

  11. Khaled says:

    Perfect solution, spent more that 2 hours and finally found your post


  12. Gary says:

    Thank you!! #1

  13. Bruce says:

    You the man.. appreciate it

  14. Troy says:

    This steps I followed but did not resolved the problem, I have the Exchange server 2010 installed on the same server running active directory on server 2008 r2 standard edition.

    It is really frustrating and why can't Microsoft give us a hint , i have lost my 2nd job interview just to this problem

  15. chaitanya says:

    Sometimes cache credentials also gave the same error.

  16. Lighty9909 says:

    Worked perfect for me!

  17. Steve says:

    You are a god among men! Worked perfectly.

  18. PEP says:

    Worked ! 🙂 thanks

  19. John Healy says:

    Worked for me too. Many thanks.

    Any idea how it got broken?

  20. Mike Smith says:

    Worked Great 🙂

  21. Sunilkumar says:

    Thanks a lot… 🙂

  22. Jim E says:

    Quick and Eazy.  The way I like it!!!  Thanks

  23. Abhay M. says:

    Such a Great Post !

  24. Chris S. says:

    Had the same issue on a fresh install. After I started to replicate Free & Busy and OAB sys files from my 2003 exchange.  I could no longer connect from 2010 exchange to the 2003 exchange.  Tried deleting the mentioned reg key it did not work for me>> Any ideas??

  25. Hemant says:

    Thanks Man..

  26. David W says:

    Yup, sure enough, the PowerShell solution worked perfectly for me in a Production environement. THANK YOU!

  27. yves says:

    if this does not work it may a time sync issue between Exchange and its GC servers. If that's the case run the following command on DC and Exchange, wait up to 15 minutes and it should resolve this issue:

    w32tm /config / /syncfromflags:manual /reliable:yes /update 


    w32tm /resync

  28. Jiman says:

    Thanks for the solution given work like charm

  29. Jeff25 says:

    awesome 1st method worked great. thanks again.

  30. irfan says:

    perfect … worked for me. i wonder why microsoft exchange not able to see that the configured node is down and it shud automatically detect the next exchange server and connect to it.
    Why have to perform this manual solution.

  31. Bari Naon says:

    Thank you very much. work like megic . this happen to me whan configred a internrt adress on remote sbs console

  32. BumSkull says:

    The solution didn't work for me but in reading the comments i seen "Chaitanya 24 May 2013 1:16 AM Sometimes cache credentials also gave the same error." Once I removed all cached credentials from Control PanelAll Control Panel ItemsCredential Manager
    opened up the EMC and all worked perfect again!

  33. Tiago Patricio says:

    Amazing, worked like a charm. Thanks you very much.

  34. anai says:

    Muchas gracias!!!!!

  35. javier says:


  36. adam says:

    how to back it up ?? thx

  37. Anonymous says:

    Pingback from Exchange 2010: Cannot open EMC (Kerberos) | Things Geeky MKII

  38. Anonymous says:

    Pingback from Exchange 2010: Cannot load EMC (Initialisation Failed) | Things Geeky MKII

  39. Anonymous says:

    Pingback from Exchange 2010: Cannot load EMC (Initialisation Failed) | Things Geeky MKII

  40. Anonymous says:

    Pingback from Exchange 2010: Cannot load EMC (Initialisation Failed) | Things Geeky MKII

  41. Andrew says:

    Experienced this after a Windows Server 2008 R2 Standard to Windows Server 2008 R2 Enterprise upgrade, thanks!

  42. Jody says:

    Worked perfect for me (option 1) Adam – in Regedit go to File – Export with the reg entry selected 🙂

  43. Vinod Shukla says:

    Thanks alot Sir, it is very useful for resolving exchange mgmt console opening..

  44. Kevin says:

    deleting the node in Admin tools did not work for me. I followed Marty_v suggestion of starting the world wide web publishing service and mine was running. I stopped the service and then restarted it and that fixed my EMC

  45. Denise W says:

    Quick & easy, worked like a charm. Thanks

  46. Larry B says:

    DIdn't work at first, have to stop/start the World Wide Web Publishing service and THEN let it discover the Exchange Server. Then I could get into the MMC.
    Got an easy fix for Windows Update service being stuck in "Stopping" not updating… at all ??

  47. Jac says:

    Its time sync issue. First verify which domain controller,the exchange is connected to with below command
    cmd:> set logon
    And verify the time of that DC with exchange time and change if required. then logoff and logon exchange server and see console works.

  48. Oleg M says:

    You da MAN!

  49. Raimundo Salas says:

    Thx it work great….:)

  50. tony says:

    You are a star! Thanks

  51. Guillem says:

    In my case, restarting WWW Service resolved the isue.

  52. Great. How come you came up with the solution?. Thanks indeed.

  53. Scott says:

    Man, thanks soooo much. I've tried so many things trying to get this fixed. Your solution worked! Gracias!!!

  54. Rajeshkumar.A says:

    Excellent Thanks !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  55. Nir says:

    Thanks man

  56. Ravi says:

    Perfect Solution Greate

  57. naren says:

    Man your great !!! Method 1 work great

  58. Siegbert says:

    thanks a lot buddy

  59. Anand-Singapore says:

    This worked for me.Thank you for the post.

  60. Dan G says:

    The easiest way I found was to open command window and restart IIS ,"IISRESET" that fixes it for me.

  61. Jules says:

    Love it Loveit Worked perfectly…

  62. Gabor Joo says:

    The first solution is great. After deleting you must restart the server.

  63. Thank you. Great solution

  64. Mahnaz R. says:

    Thank you it is perfect

  65. quintin says:

    @ Dan G. Thanks! Restarting IIS fixed it for me!

  66. Rob Brookbanks says:

    A NEW solution to this problem, check that the key HKLM.UsersDefaultEnvironment exists. My console and EMS mysteriously stopped working, after running Procmon from SysInternals suite I found it was looking for the Environment key in the default profile,
    not mine. Added the Environment key and WHOOSH, everything fixed. Only took me about sixteen hours to find this after trying all the other steps.

  67. Polad Hasanov says:

    thank you

  68. Lifesaver says:

    Thanks so much! Yours was the first thread I came upon after discovering this issue and it was a quick fix. Thanks again.

  69. Mike Porter says:

    In my case this was a time issue. Exchange server was off network time by over 6 minutes. Set correct time, logged off and back in. Was able to open EMC just fine!

  70. jim says:

    TYVM for posting this.

  71. Scott says:

    None of the solutions worked for me. The new error is Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer.
    The content type is absent or invalid.
    This is an SBS2011 server. I have tried removing the reg entry, restarting www services. It also seems to be stopping the delivery of mail to & from the company iPhones. Everything else seems fine.
    What's next to try?

  72. satish says:

    thanks it is working but connecting to another server,still geting the same error when manualy trying to connect the same server

  73. chrisr says:

    Yay! Thank you! But the question is what suddenly caused it to happen in the first place…..

  74. Berto Eli says:

    I used to first method and it worked well.


  75. Anil says:

    Yes it worked.

  76. mike says:

    Thank you so much… life saver!!

  77. James Daniel says:

    Yes Its working. But i want to work EMC in that server to check the configuration. do you know any other solution

  78. Sabarish says:

    Thanks a lot for given exact solution ..

    It's working fine..

  79. Richard says:

    Perfect and easy solution, Thank you!

  80. Vijay Anupoju says:

    Thanks.. it worked for me..:)

  81. Henry says:

    Easier with the PowerShell command. Great post. Thank you very much.

  82. Rich The Tech says:

    I have been trying to sort this issue out for 2 years, gave up looking until today (had created a new admin in order to manage exchange) this sorted out the issue!! hurrah and thank you.

  83. amoore says:

    Thank you very much this was the only method that worked!!!

  84. Darren says:

    Work perfectly thank ypou

  85. Great solution, many thanks

  86. Frank says:

    it works

  87. Patrck says:

    Restart all IIS services (Or restart the the site in IIS Manager.) Fixed the problem for me.

  88. PLalonde says:

    THANK YOU! I never would have found this!!!

  89. Jean-Marie AGBO says:

    No comment, my problem is resolved, perfect solutions !

  90. jimmy says:

    if everything else above fails, Log onto the Exchange Server, go to Control Panel, Credential Manager, Windows Vault, Remove All Accounts from Windows Credentials

  91. jimmy says:

    If the above fails, log onto the Exchange Server, go to Control Panel, Credential Manager, Windows Vault, Remove All Accounts from Windows Credentials

  92. Hieu T. says:

    Worked for me. Thank you so much.

  93. sujith says:


  94. mr_burgess says:

    Excellent !!! thank you.

  95. Reza Racer says:

    I have Small Business Server 2011 Standard – from time to time this problem comes up and generally I do a server restart and it then works. However, I just tried method 1, and it worked. Just a word of advice – when you try to open of the MMC again, and
    try to expand the management console to get to your server, it does a search for the Exchange servers in the environment and in my case, even though it is all part of the same server, it took about two minutes before the search finished so be patient. What
    I don't know is if this will permanently fix the problem – I guess time will tell since this problem comes back about once every two months or so.

  96. Arturo C. says:

    Excelente. Muchas Gracias.

  97. Sandileg says:

    Thanks alot you the man

  98. DNC says:

    Thanks a lot.

  99. Dekopajing says:

    Thanks man thanks

  100. Gar says:

    Brilliant – Thanking you.

  101. shabber.shaik says:

    you are saved my frustration … Thank you very much

  102. Steve says:


  103. amol says:

    it is not resolve for me can you explain me where to run above command exactly & before run this command can i delete the Remove-ItemProperty -Path HKCU:SoftwareMicrosoftExchangeServerv14AdminTools -Name NodeStructureSettings from registry

  104. @amol You run the command from within PowerShell under the user you normally run the Exchange Management Console as. Method 2 – Step 3: The command deletes the registry key HKCU:SoftwareMicrosoftExchangeServerv14AdminToolsNodeStructureSettings
    If you are not experienced at PowerShell or navigating the registry you should probably request assistance from your IT department, specifically your Windows Administrators. Let them know that they need to run the command under your user account.

    Please make sure you are experiencing the situation and "EXACT" same error as outlined in the article above.

  105. Troy says:

    The registry change didn't make any difference for me. However restarting the world wide publishing service appears to have resolved the issue.

  106. Hedayatullah Zamani says:

    Worked Perfectly thank you very much for your post.

  107. Davige says:

    28 Jul 2015 6:26 PM

    if everything else above fails, Log onto the Exchange Server, go to Control Panel, Credential Manager, Windows Vault, Remove All Accounts from Windows Credentials"

    This worked for me. Tried other solutions, but there was weird credential in the vault that has the wrong admin name. No idea how it got there. This was affecting the EMC and an Acronis 11.7 Exchange backup. Thank you Jimmy!

  108. Sandile says:


    It does connect to other server but not local, what might be the problem?


  109. Carl Giles says:

    After all steps had to log off and back in and then it worked.

  110. Alexdfc says:

    I had the same problem with EMS and EMC ( Discover-ExchangeServer -UseWIA $true -SuppressError $true' ) access denied to http://server/PowerShell
    on the Windows SBS 2011

    It must enable HTTP persistent connections in IIS on the default Web site.
    – In IIS, Under Default site, including the Exchange directory, launch the menu En-heads http response
    – Open menu "Set Common Headers"
    – Enable persistent HTTP connections:

  111. stephen says: