Exchange 2010 - Out of Office not working - MAC Entourage cannot connect to EWS (Default Web Site)

  • Thread starter Simon Lown
  • Start date Views 1,730
Status
Not open for further replies.
S

Simon Lown

Hi,
I have Exchange 2010 installed on Server 2008 R2 Standard.
Until recently, both out of office and MAC connection to EWS was working fine.
Now both have stopped working.
To try and get them working again, I have so far tried:
Set-WebServicesVirtualDirectory
http://technet.microsoft.com/en-us/library/aa997233.aspx
Remove / Re-Install WinRM IIS Extensions.
Run WinRM quickconfig
Re-Created EWS
To remove EWS: http://technet.microsoft.com/en-us/library/bb124231.aspx
To re-create EWS: http://technet.microsoft.com/en-us/library/bb125176.aspx
Re-started IIS several times.
Restarted Server.
I now find that since re-creating the EWS, I am no longer able to connect to the Exchange Management Console or Shell.
I get the Error:
VERBOSE: Connecting to myserver.mydomain.com
[myserver.mydomain.com] 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
If anyone has any ideas where I went wrong and how to get back to a working EMC/EMS and EWS, you would be my hero.

Thanks in advance,

Simon.
 
G

Gen Lin

Hi,

Please follow these steps to repair:

Step 1:
===============
Open CMD, and type:

WinRM quickconfig
Step 2:
===============
IIS manager -> Default website -> Edit bindings -> Confirm HTTP is configured to work on port 80

Step 3:
=============
IIS manager ->Default website -> Edit bindings -> HTTP -> hostname value should be blank
(Some time you will see hostname as local host)
Step 4:
==========
Try accessing OWA and the default website from the IIS and make sure we are able to access the websites. SSL is not required on the Powershell virtual directory.



 
Status
Not open for further replies.
Top