New WINRM issues
Since upgrading we are getting winrm errors:
Connecting to remote server servernamegoeshere 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.
this was working perfectly prior to the upgrade.
all servers are 2008 R2
exchange 2013 WITH CU10 (this worked prior to the upgrade)
running C:>winrm qc gives me the following:
WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer.
i can remote manage any of the servers in any direction.
we have been having this issue for over a week. please advise.
also ran emtshooter –
Welcome to the Exchange Management Troubleshooter!
We recommend that you run the troubleshooter after making changes to IIS to ensure that connectivity to Exchange Powershell is unaffected.
Checking IIS Service…
Checking the Exchange Install Path variable…
Checking the Powershell Virtual Directory…
Checking the Powershell vdir SSL setting…
Checking the Powershell vdir path setting…
Checking HTTP Port 80…
Checking HTTP Port 80 Host Name…
Testing for errors…
3
Location ConnectToAnyServer 2
VERBOSE: Connecting to servernamgoeshere
The Exchange Management Troubleshooter successfully completed connecting to:
servernamgoeshere
i am looking into the “3” errors – but it does say it completed successfully
the “3” is not an error. the log says that everything ran fine.
In CloudPanel if you select Basic Authentication under the settings you need to make sure you enable Basic Authentication on the /powershell virtual directory.
That is most likely the issue.
Other issues would be your application pool that CloudPanel is using isn’t running under a domain user with rights.
THANK YOU MICROSOFT FOR MESSING WITH THE SETTINGS IN OUTLOOK WITHOUT ADVISING US!
Friken frak !#$!%$#@#
Cloud panel is working again. thank you Jacob.
meant that MS messed with Exchange settings.
- 5 Forums
- 714 Topics
- 3,630 Posts
- 0 Online
- 253 Members