The error you get: The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found
If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console:
The solution is to first export and then delete
HKCU\Software\Microsoft\ExchangeServer\v14\AdminTools\NodeStructureSettings (REG_BINARY key) registry key.
All credits go to Paul Newell on this forum http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/cef4a010-0a64-40a7-8601-1539ffdb2568.
If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console:
The following error occurred while attempting to connect to the specified Exchange server 'yourserver.domain.com':The attempt to connect to http://yourserver.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.
The solution is to first export and then delete
HKCU\Software\Microsoft\ExchangeServer\v14\AdminTools\NodeStructureSettings (REG_BINARY key) registry key.
All credits go to Paul Newell on this forum http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/cef4a010-0a64-40a7-8601-1539ffdb2568.
anybody tried this? was it successful?
ReplyDeleteWell, actually everything that you see on this blog was in fact done by me and tested before it is put out for public. There are no "sounds like" stories here. Just facts. :)
ReplyDeleteThis fixed did indeed fix my issue! consider it tested
ReplyDeleteyup worked like a charm
ReplyDeleteThis worked for me - confirmed nice easy fix. Thank You !
ReplyDelete2pages.co.uk
No luck. Now it fails with "the client cannot connect to the destination specified in the request. Verify that the service on the destination is running." and yes, it's running.
ReplyDeleteThanks it worked but no before I restarted the server I am using 2008 R2, after deleted the registry key it showed another error message so I restarted and tried again to open EMC and it worked , restarted a couple of time and it keeps working. Thanks
ReplyDeleteThis worked perfectly.
ReplyDeleteThanks!
Thanks for this information, wish I had gotten this sooner.
ReplyDeleteGreg Tench
Thanks so much for this. You are a genius!
ReplyDeleteNo change here.
ReplyDeleteI tried it, it work like a charm
ReplyDeleteThanks Dušan
Mahmood Sabt
Thank you very much for the great post Dusan, worked wonders in minutes!
ReplyDeleteTruly saved my backside... Thanks my friend.
ReplyDeleteWorked a charm. Thanks
ReplyDeletethanks.saved a lot of time for me.
ReplyDeleteThis worked perfectly. Note:I had to log off after and log back in before it worked. Thank you for this article. -Willy
ReplyDeleteWe havn't un/installed Exchange and have 3xMB 3xCas 2xEdge... Oddly I could connect to the EMC on everything except one of the MB servers.
ReplyDeleteRemoving this key on that one server fixed the issue!
Thanks!
Thank you.
ReplyDeletei tested it and its worked right away :)
ReplyDeleteMillion Thanks
Thank you that was a quick and easy fix, that came up on my first search for the issue. Well done!
ReplyDeleteWorks Great
ReplyDeleteThis procedure works, only need to IIS reset
ReplyDeleteThanks a lot
ReplyDeleteWorked for me - didn't need an IIS reset or server reboot. Made the change and launched EMC, right in. Still get an error on PowerShell but otherwise EMC works...
ReplyDeleteСпасибо огромное, очень пригодилось.
ReplyDeleteIt didn't work for me, I had to restart IIS in order for it to connect. the problem happened when I changed the local DNS to an external one in order to check whether Exchange's Hybrid wizard will be able to confirm the public DNS changes for my domain. but didn't work.
ReplyDeleteThis worked perfect for me after an IISreset, no need to reboot server.
ReplyDeleteThis worked perfect for me
ReplyDeleteNot worked...
ReplyDeleteexperienced the same issue with EMC on exch2010sp3/w2008r2 server after applying Windows patch for wannacry virus, i ve tried all the solutions posted here without succes, finally got it to work again by modifying this IISmanager>default web site>ecp>Windows authentication>Advanced setting> extended protection = accept (it was on OFF)
ReplyDeletethanks everybody
Mouden
i can't fix i had the same issue
ReplyDelete