Ran into an interesting error when trying to create an Exchange Server 2010 mailbox for a user object where I would constantly encounter the following error:

The attempt to connect to http://exchange.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: “winrm quickconfig”. For more information, see the about_Remote_Troubleshooting Help topic.

The first thought that came to my mind was to check the Exchange services and when I did, all of them were already up:

After searching on the internet and coming across the following 2 links:

… none of the purposed solutions worked but through reading the The Exchange Team Blog, I realized that this might have something to do with IIS. Restarting the Exchange services during office hours was definitely out of the question but I had to get this working because I needed to create the user’s mailbox. After thinking about what options I had for a bit, I realized I could probably restart the World Wide Web Publishing Service quickly and so I did:

Once the World Wide Web Publishing Service successfully restarted, the Exchange Management Console was now able to load the organization:

I ran thru a number of suggestions that I found on other sites, but I always found that we had the server already configured the way they suggested. I was left with restarting Exchange and/or IIS when I found your blog. Sounded like a Hail Mary pass to me but weighed against the potential negative impact of restarting Exchange or IIS - I gave it a shot and Surprise! - it worked. So simple - thanks.

Terrence, THANK YOU for posting this. I reset one of the virtual directories to see if HTTP/RPC was fixed on our clients and I got the same error. I almost threw up my breakfast. WWW was turned off. Once I started the service, bam. Thank you!!

I had this problem with a 303 error and ended up having toBasically re-create the powershell VD and reset the poweshell appPool. Then reset all of the Exchange virtual directories and setup the redirect again.

This solution didn't work for me, but you got me thinking. My issue was caused by a company wide power cut. I looked for all sorts of Kerberos issues in the logs of my domain controllers and exchange server. Then I suddenly remembered something from my Windows 98 days.....I power cycled the netlogon service and bingo it all worked. Thanks for getting the Grey matter working at 5:00am in the morning

I've tried removing the mention regkeys. Tried reseting IIS, rebooted the server and all did not work for me.Just decided to delete my profile on the server, relogged with another admin user, used the simple method "advanced System Settings" - User profiles Settings - Clicked on my profile and hit delete.After logging on again an starting the EMC everyting worked fine again.