I've had an exchange environment running fine with a handful of mailboxes running on windows server 2012 R2. OWA, ECP were working fine off domain.com and exchange shell never had any prior issues.

I was following this guide to install Office Web Apps on the same server https://technet.microsoft.com/en-gb/library/jj219455 Using "Deploy a single-server Office Web Apps Server farm that uses HTTPS"

I got to the end tested https://domain.com/hosting/discovery and it worked as prescribed using New-OfficeWebAppsFarm -InternalUrl "https://server.domain.com" -ExternalUrl "https://wac.domain.com" -CertificateName "domain.com" -EditingEnabled. So I went to proceed with the Exchange integration (https://technet.microsoft.com/en-us/library/jj150495(v=exchg.150).aspx) and that was when I noticed Exchange Shell was no longer connecting. 

I am seeing the following error

-----------------------------------------------------------------------------------------------------------------------------------------------------

New-PSSession : [servername.domain.com] Connecting to remote server servername.domain.com failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed

-----------------------------------------------------------------------------------------------------------------------------------------------------

Default Website has now gone in IIS and there is HTTP80 and HTTP809

Exchange Back End appears to be as it was before.

WinRM and all other services are reported as running. I have checked a few other things but really stuck as to where to go from here

OK so I found that running Exchange and Office Web Apps on the same server is a bad move so have restored backup. Happy for someone to comment if there is a way to do this, I'm sure I'm not the only one.

Hi Gav,

Thank you for your question.

As you said, we suggest you didnt install Office Web Apps on Exchange. Because two application will use the same port so that there is a conflict. It affect the high availability of Exchange server and Office Web Apps.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim