After upgrade of CP to v3.1.0833 and Exchange 2013 to CU 11 I tried to add a user and got an error.
Connecting to remote server servername.fqdn.mydomain.com failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.
winrm qc shows running and already setup.
Any suggestions?
This installation is still being tested before going live. Previously all was working EXCEPT for getting Outlook to connect for users other than ones belonging to mydomain.com.? hosteddomain.tld will error out with “The connection to MS Exchange is unavailable…”
Disregard this post. ? 2nd reboot sorted it out.
Spoke too soon.? 2nd reboot let me create user but can’t edit/enable mailbox for that user or any other.? Same error when trying to edit old user or enable mail on new user.
Suggestions?
Thanks,
Jerry,
When you upgrade Exchange it will reset the “Basic Authentication” flag on the Powershell virtual directory. You need to go back in and enable that using EAC.
For the Outlook’s not being able to connect you need to be sure you enable MAPI on the mailbox plans because that is what allows them to use Outlook Anywhere.
If it still is not connecting then something could possibly not be setup correctly on Exchange itself (which I can help with if you want to schedule time)
Thanks Jacob, once again you pointed me in the right direction.? I will make a note for future Exchange upgrades.
In EMS this got it done:
Get-PowerShellVirtualDirectory -Server <CASServerName> | Set-PowerShellVirtualDirectory
-BasicAuthentication $true
Great! Glad its working 🙂
Rather than create a new post, I’ll post here. ?If you need me to re-post to a new entry please let me know. ?I’m having the same issue Jerry mentioned in his first post..
<p style=”box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5; font-family: Roboto, sans-serif;”>Connecting to remote server servername.fqdn.mydomain.com failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.</p>
<p style=”box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5; font-family: Roboto, sans-serif;”>winrm qc shows running and already setup.</p>
<p style=”box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5; font-family: Roboto, sans-serif;”>Any suggestions?</p>
<p style=”box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5; font-family: Roboto, sans-serif;”>I’ve run the command in my Exchange Management Shell, still no go… ?Your assistance is appreciated.</p>
<p style=”box-sizing: border-box; margin: 0px 0px 10px; line-height: 1.5; font-family: Roboto, sans-serif;”>Troy</p>
Sorry Troy I did not see this message show up. This error is always caused by:
- Application Pool CloudPanel is using doesn’t have the DOMAINUsername set (domain admin / exchange organization management)
- Basic Authentication is not enabled on the /Powershell virtual directory
Are you sure you are pointing to that same server you are enabling basic authentication on?
Also what Exchange version and CU are you on?
That’s exactly what it was. ?I was able to get this taken care of. ?I appreciate the reply and info!
Great! I’m glad its working for you now
