Hi all,
Fresh install of Exchange 2013, patched to CU12, running on Server 2012 R2.? Running great (albeit brand new fresh, so… who knows really).? Brand new domain.? Fresh install of CloudPanel on a fresh Server 2012 R2 system.? SQL 2012 Express.? Followed the installation instructions right down to the letter (I think).
So everything great, humming along thru the install of CP v3.1.1.0, and?I go to update the database list and I get this message:
The WinRM client received an HTTP bad request status (400), but the remote service did not include any other information about the cause of the failure.? For more information, see the about_remote_troubleshooting Help topic.
I verified that I set the PowerShell virtual directory to Basic Authentication (and even unchecked it, saved, then rechecked it just to make sure that Microsoft had not had a total brain f*rt).
So I’m kinda stuck here.? Any thoughts?
Rick
Hi Jacob,
I made no alterations in IIS, set Basic Authentication from within Exchange ECP, and verified that the IIS Application Pool?is running under a domain user (it is running under a domain administrator, actually).
Thanks in advance!
Rick
There is a log folder in the cloudpanel directory to check. The FQDN for the Exchange server needs to be pointed to the server with 443 and the /powershell virtual directory. You just put in the server name / fqdn and don’t put https:// or anything else in there.
It should be compiling the URL for you… so if you put in then it will try to reach https://exchange2016.ad.mydomain.com/powershell
Are you able to reach that URL and get prompted for credentials if you put it in IE?
Hi Jacob,
I am able to resolve that url from the CloudPanel system with no problem and I’m presented with a normal request for login credentials.? If I put in the credentials they are accepted properly.
Rick
