I've managed to break the management (WinRM) interface. This started because we were having some ActiveSync authentication issues, so I was messing with IIS to fix them. I actually did fix them, but during the process I've killed the Exchange WinRM interface... so I can no longer connect through the console or the shell. VERBOSE: Connecting to PEYOTE.ad.isillc.com [peyote.ad.isillc.com] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. The WinRM client trie d to use Kerberos authentication mechanism, but the destination computer (PEYOTE.ad.isillc.com:80) returned an 'access denied' error. Change the configuration to allow Kerberos authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the loc al computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException + FullyQualifiedErrorId : PSSessionOpenFailed Anyways, I know this has something to do with the kerbauth module in the PowerShell virtual directory. What I'd rather do, instead of picking this all apart, is figure out how to have Exchange reconfigure these settings back to their appropriate defaults automatically. Is there a way to do this? I should note that Enter-PSSession works fine.

I can think of two options. (1) Call Microsoft Support. (2) Rebuild the server. I can't fathom what to tell you to fix, sorry.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, 1. Please check there is no redirect settings in Default web site. 2. Create a new powershell virtual directory: http://technet.microsoft.com/en-us/library/dd335058.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT