Published: March 23, 2017
Updated: June 5, 2018
Applies to: Cayosoft Administrator 3.x and above
Licenses needed: Enterprise or Exchange On-premises
Summary: There are three items that need to be correctly configured to establish a successful connection from Cayosoft Administrator to a Microsoft Exchange On-premises Server. These three items are: 1) the Exchange Server, 2) the security settings on the two servers, and 3) the connection settings within Cayosoft Administrator.
In this article:
- Troubleshooting Exchange On-Premises Settings
- Verify the Cayosoft Administrator Configuration
- Connectivity error after installing Windows Update KB4103725
- Connectivity error with Failure category 'Cafe-SendFailure'
- Enumeration error in Cayosoft Web Portal
Troubleshooting Exchange On-Premises Settings
Verify the TrustedHosts setting on the Exchange Server:
1. Open a Powershell prompt and run the command:
WinRM get winrm/config/client
2. See the example results below:
3. If the results are empty like the are in the example above continue to step 4. Otherwise move to the next section of this guide.
4. Run the following command on the Exchange Server.
5. Check that the settings are applied, running the command again
WinRM get winrm/config/client
6. See the example results below:
Note the last line of output have changed to "TrustedHosts = *".
Verify the Cayosoft Administrator Configuration
Restart the Cayosoft Administration Server - Reboot the Cayosoft Administrator Server. This is to make 100% certain that we didn't have some cached credentials somewhere.
Verify service account permissions - Verify the service account holds the Exchange Role Organizational Management
Connectivity error after installing Windows Update KB4103725
Symptoms: you installed Windows Update KB4103725 on Exchange Server or Cayosoft Administrator server. After that you start to get connectivity error message in Cayosoft Administrator Console:
"Sessions to 'Microsoft Exchange' could not be established. Please read the platform returned error message(s) to identify the problem. The Check Settings Action, located on each extension's configuration page, may be useful for troubleshooting connections issues.
Error Details: [<exchange.domain.com>] Connecting to remote server <exchange.domain.com> failed with the following error message : The WinRM client received an HTTP server error status (500), 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."
Solution: By default, after KB4103725 is installed, patched clients cannot communicate with unpatched servers. So, you need to install it on both Cayosoft Administrator server and Exchange Server and reboot both of them.
More information about KB4103725 you can found here:
Connectivity error with Failure category 'Cafe-SendFailure'
Error: [<server name>] Connecting to remote server <server name> failed with the following error message : [ClientAccessServer=CHWT11BA21066,BackEndServer=<server name>,RequestId=7e62cc75-46d2-46c7-a96f-ad2a7a4610ae,TimeStamp=6/11/2018 1:26:05 PM] [FailureCategory=Cafe-SendFailure] For more information, see the about_Remote_Troubleshooting Help topic.
Solution: the most possible reason is binding errror on IIS for the Exchange Web Service. To fix it, follow the steps below:
- Open IIS on exchange server (Press the Windows+R keys to open the Run dialog, type inetmgr, press Enter), navigate to the server name > Sites, right-click on Exchange Back End and select Edit Bindings...
- In the new window, select https and then click Edit...
- If SSL certificate field has option 'Not selected' change it to a valid certificate, for example 'Microsoft Exchange'
- Click Ok and then Close Site Bindings dialog
Enumeration error in Cayosoft Web Portal
- In Cayosoft Administrator Console navigate to Microsoft Exchange extension
- In Connect URI check the server name where Microsoft Exchange Server is installed
- Login to the machine with Microsoft Exchange Server
- Check the installed PowerShell version. The PowerShell version should be 5.1. Please see How to determine the current PowerShell version.