I am getting a few errors. First when I try to access the ESM or the power tools I get an error simial to this: VERBOSE: Connecting to s2008.AGD.org [s2008.agd.org] Connecting to remote server failed with the following error message : The WinRM client cannot process t he request. It cannot determine the content type of the HTTP response from the destination computer. The content type i s absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to S2008.AGD.org [s2008.agd.org] Connecting to remote server failed with the following error message : The WinRM client cannot process t he request. It cannot determine the content type of the HTTP response from the destination computer. The content type i s absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to S2008.AGD.org [s2008.agd.org] Connecting to remote server failed with the following error message : The WinRM client cannot process t he request. It cannot determine the content type of the HTTP response from the destination computer. The content type i s absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed Failed to connect to any Exchange Server in the current site. I have checked to mak sure kerbauth is set to native on Powershell Folder and not enabled on Default site. This all started with OWA not working, so one of the steps was to reinstall IIS, well that created another problem as you can see here. Been at this for a while, any help would be appreciated.

Hi, I think, you are receiving the error message for a user tries to connect to a ESM because the remote Shell isn't enabled. To correct it use the cmdlet Set-User "username" -RemotePowerShellEnabled $True Change the bold text to the issue username Regards from www.windowsadmin.info

I tried this in windows Power Shell and it says it doesn't recognize the cmdlet PS P:\> Set-User "jasonp" -RemotePowerShellEnabled $True The term 'Set-User' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp elling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:9 + Set-User <<<< "jasonp" -RemotePowerShellEnabled $True + CategoryInfo : ObjectNotFound: (Set-User:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

I tried in Exchange PS and got the same: [PS] C:\Windows\system32>Set-User "jasonp" -RemotePowerShellEnabled $True The term 'Set-User' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp elling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:9 + Set-User <<<< "jasonp" -RemotePowerShellEnabled $True + CategoryInfo : ObjectNotFound: (Set-User:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException [PS] C:\Windows\system32>

Hi, Try jasonp instead of "jasonp"Regards from www.windowsadmin.info

The cmdlet will require loading the exchange snap-in, so you will fail to run the cmdlet in windows powershell. Please try the procedure in this article Does the issue happen when you launch EMC/EMS on the exchange server locally? Is there any error event in the application log? Please try the suggestions in this threadJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

I actually ended up calling MS support after digging and digging. After a while of this change and that change I got pretty confused as to what actually did get things to work. James you are correct one of the first steps was to load the exchange snapin. Thanks for your replies though.