I had this issue on a server in my test lab – EMS couldn’t connect to the local machine. There were several differnet errors at different times – couldn’t find a domain controller, http bad response, general ‘couldn’t connect’ type error. This box was a proper test machine- I had Exchange 2010 on it, uninstalled, installed Exchange 2013, uninstalled, changed domain. All stuff you shouldn’t do. But all was ok until it was made into a DC in a child domain. Then when installed Exchange 2013, EMS couldn’t connect locally. I uninstalled Exchange, put 2010 on – same issue. Went back to 2013 after removing the server from the domain, adding to the parent, dcpromoed to a DC in a new child domain, installed Exchange 2013 – same thing. Research over a period of a couple of weeks proved fruitless, until I saw an issue on the forums related to kerbauth.dll. Then I found this: http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx.
On investigation, I found that the kerbauth module (in IIS Manager – \Sites\Default Web Site\PowerShell – modules in the right pane) was pointing at the V14\bin directory, not v15. So, to fix the issue:
- I removed the module from IIS (\Sites\Default Web Site\PowerShell – modules – right-click -remove)
- Edited C:\Windows\System32\Inetsrv\config\ApplicationHost.config to point to the v15\bin directory (searched for v14, found the offending line pointing at v14/bin/kerbauth)
- Did an iisreset
- Restarted WinRM service
- Clicked on ‘Configure Native Modules’ and enabled kerbauth
Boom! EMS can now connect to the local machine.