Schemus synchronization tool actions

Products

• Email Security.cloud

Issue/Introduction

This article describes each available action within the GUI when using the Schemus synchronization tool.

Environment

Email Security.cloud

Resolution

 Below is the detailed explanation for each action within the Schemus GUI before performing any Synchronization from your data source to the Messagelabs Clientnet portal.

 

• Summary - shows a summary of the configuration settings, It displays a summary of the configuration profile settings. If the profile includes more than one synchronization type, review the settings of each type by clicking the Mail, Groups, and Users tabs

• Test Update - reads the data source to indicate which changes would be made at the next synchronization. Looks at the data in your source (file or LDAP server) and lists the additions, removals, or exclusions. For users, this setting includes the email address and the groups that the user is a member of.

  Note: When you use the Test Update method, no data is synchronized with the cloud security services

• Update - uploads data which have changed since the last synchronization. This action compares the details that are held in your local change tracking database and sends those that have been removed or added. An incremental update is an efficient way of passing changes to the cloud security services and preserving unchanged data.

• Replace - replaces the data on Symantec.cloud with the data read from the local sources. Recreates your local change tracking database and resend all data to the cloud security services, replacing the data that is currently present for that synchronization.

  Warning! Take care when using this method. The data that is currently present in the cloud security services for the synchronization is removed, before the update takes place

• Stop - stops the current synchronization operation.

• Refresh - recreates the local change-tracking data. Retrieves all data from the cloud security services and recreates your local change tracking database. You might want to use the Refresh method in the following situations:

  1 - If you have reinstalled the Synchronization Tool software on a different computer and want to recreate the change tracking database

  2 - If you have added or deleted entries through the portal.A subsequent update operation is based upon calculating changes from a current copy of the data that is held in the cloud security services.

• Close - closes the current configuration.