Reports the last time a Contacts synchronization completed successfully. If a scheduled synchronization is more than 12 hours overdue, or if a synchronization reported as failed, this status check fails. The SyncManagerService.log file on the server running the SyncManager in your environment may contain information that is useful for debugging failures.

If this readiness check fails, follow this procedure. After completing each troubleshooting step, please log into the AMS Admin Console to verify whether synchronization issue has been resolved.

1. Verify that the machine running the SyncManager software is currently running and has outbound HTTPS (port 443) access to the Internet. HTTPS access can be verified by opening a web browser on the machine running the SyncManager and connecting successfully to the AMS URL provided to you by Support. If you are unable to connect to this URL, verify your proxy/firewall settings with your network administrator.
2. Verify that the Sync Manager Service is running in the Services Control Panel Applet. If the service is already running, restart the Sync Manager Service.
3. Check the Application Event Log for non-informational events from the Sync Manager Service. (Information events can generally be ignored.)
4. Launch the SyncManager (Start > Programs > Aurea > SyncManager) and execute a manual sync. This may take some time to complete based on the size of your organization. Verify successful operation after the manual run dialog box has been dismissed.
5. If none of the steps above resolves the synchronization issue, contact Support for assistance.

Reports the last time a Calendar synchronization completed successfully. If a scheduled synchronization is more than 12 hours overdue, or if a synchronization reported as failed, this check fails. The SyncManagerService.log file on the server running the SyncManager in your environment may contain information that is useful for debugging failures.

If this readiness check fails, follow the procedure for troubleshooting Sync Manager issues under Default contacts synchronization above. After completing each troubleshooting step, please log into the AMS Admin Console to verify whether synchronization issue has been resolved.

Reports the last time a Directory synchronization completed successfully. If a scheduled synchronization is more than 12 hours overdue, or if a synchronization reported as failed, this check fails. The SyncManagerService.log file on the server running the SyncManager in your environment may contain information that is useful for debugging failures.

If this readiness check fails, follow the procedure for troubleshooting Sync Manager issues under Default contacts synchronization above. After completing each troubleshooting step, please log into the AMS Admin Console to verify whether synchronization issue has been resolved.

If you have chosen to have Email Continuity mail transfer agents (MTAs) listed as an MX record in your public DNS, this readiness check verifies the appropriate DNS entries exist for each domain. If this check fails, verify the appropriate DNS entries exist on all public DNS servers for the domain(s).

If this readiness check fails, contact Support immediately for assistance.

Reports the last time a particular Authentication Manager connected to the data center.

If this readiness check fails, verify that the Authentication Manager service is running on the specified computer and that it can access the data center over port 443. If this does not resolve the issue, contact Support.

Reports the last time a particular RedirectorController connected to the data center.

If this readiness check fails, verify that the Controller service is running on the specified computer and that it can access the data center over port 443. If this does not resolve the issue, contact Support.

Reports Exchange servers that have a Redirector installed, as well as servers that have a Redirector installed, but are not currently in communication with at least one RedirectorController.

The best practice recommendation is that all Exchange Hub Transport servers have the RedirectorAgent installed, and that each of these be in communication with at least two RedirectorControllers.

If this readiness check fails:

1. Verify that the Controller service is running on the specified computer and that it can access the data center over port 443.
2. Verify that you are following the best practice above and all Hub Transport servers are communicating with RedirectorControllers.
3. If these steps do not resolve the issue, contact Support.

Reports user ID conflicts detected by the SyncManager using primary email address.

If this readiness check fails, follow the instructions under Resolve User ID Conflicts. If this does not resolve the issue, contact Support.

Reports the last time a VaultBox connected to the data center.

If this readiness check fails, verify that the Simple Mail Transfer Protocol (SMTP) service, Selective Replication Transfer Service, and VaultBox monitor are started. Additional information for debugging can be found in the SRTransferService.log files on the associated VaultBox. If this does not resolve the issue, contact Support.

Reports any servers that are currently not assigned to a replication zone. All servers must be assigned to a replication zone.

If this readiness check fails, follow the instructions under Replication Zones to ensure that the reported servers are assigned to replication zones. If this does not resolve the issue, contact Support.

A readiness check to determine if there are users assigned to receive fault alert notifications. If no users are assigned to receive alerts, then the following message is displayed: Fault Alert Users: No users have been configured to receive fault alerts.

If users have been assigned, then the following message is displayed: Fault Alert Users: At least one user has been configured to receive fault alerts

At least one user should be assigned to receive fault alerts to ensure error messages are not lost.

This check is to verify whether or not a journaled message has been received in the last 12 hours. If it hasn’t, this warning will display.
Office 365 Journaling Service: EMS has not received a journaled message in the last 12 hours.This error message could also mean there is a misconfiguration, like an improper journaling address.

If this readiness check is displayed, verify your Office 365 environment is set to send journaled messages. Contact Support if further assistance is required

If a message is sent from Office 365 without using Transport Layer Security (TLS) a readiness check warning will appear.
Office 365 Journaling Service: EMS received a journal message without Transport Layer Security (TLS).

If this readiness check is displayed, verify your Office 365 environment is set to send secure messages. Contact Support if further assistance is required.

This check is a test over port 25 from the AMS to whatever next hop destinations are configured in Email Routing: Configure Mail Routing, to confirm they are capable of receiving messages from AMS.

The status message:
Next Hop Status: 2 of 4 next hops passed. Details...
indicates the number of ports which passed the test, with the Details link showing a table detailing the test results. See Next Hops Readiness Check.

If AMS detects an Exchange mailbox that is enabled for Exchange Envelope Journaling, but is not in an Email Archival retention policy, a readiness check will display:
Journaled Message Retention: 22 journaled mailboxes are not included in a retention policy. Show List...Click on Show List to see the mailboxes (first 50 are shown, remainder can be downloaded into CSV file).

If AMS detects an Exchange mailbox that is in an Email Archival retention policy, but not enabled for Exchange Envelope Journaling, a readiness check will display:
Non-Journaled Message Retention: 2 non-journaled mailboxes are included in a retention policy. Show List...Click on Show List to see the mailboxes (first 50 are shown, remainder can be downloaded into CSV file).

If a mailbox or distribution list is hidden or disabled, but is enabled for Exchange Envelope Journaling, a readiness check will display:
Hidden Journaled Mailboxes: 1 hidden/deleted, journaled mailboxes are not included in a retention policy. Show list...Click on Show List to see the mailboxes (first 50 are shown, remainder can be downloaded into CSV file).