I installed a SBS 2011 server about a year ago and didn't complete the Exchange setup as it wasn't needed at that time. I am now circling back to finish Exchange setup and am encountering issues. Specifically:
When I run the "Connect to the Internet" Wizard in the Console ( subsequent steps won't run until I complete this step ) it fails with the error:
Windows SBS did not properly configure your e-mail. To correct this, re-run this wizard.
I checked the CTIW.log and it shows this:
[23816] 150430.123403.4921: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Tasks.RebindConnectorsTask.Run
[23816] 150430.123403.5077: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.Initialize
[23816] 150430.123403.5233: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize
[23816] 150430.123404.3033: Messaging: Openning remote runspace failed due to the error: Connecting to remote server 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.. Retry...
[23816] 150430.123414.3192: Messaging: Openning remote runspace failed due to the error: Connecting to remote server 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.. Retry...
[23816] 150430.123424.3506: Messaging: MessagingTaskException: Unexpected failure creating runspace -- Error# (800001)
[23816] 150430.123424.3506: Messaging: Inner exception: Connecting to remote server 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.
Okay, so something about WInRM is not happy. l tried to launch the Exchange Management Console and can connect without any issues - no WinRM errors.
I then run EMTshooter.ps1 just to be safe... all checks out.
The only variable that I haven't eliminated is that we are running a production website on port 80 and binding do the same IP that the default website is using. However, all Exchange virtual directories are binding on 443 and I can access those through a web browser without any issues.
I'm stumped. Any help or direction would be very much appreciated!