WARNING: Removing a sync policy while the sync service is running can have unpredictable results. We highly recommend disabling and backing up a sync policy before removing it.
It is important to access the correct set of Riva files and folders throughout these procedures.
To access the correct \Riva folder structure:
Before making any changes to sync policy names or files, Riva administrators should make a backup copy of those files.
To make a backup of the Riva configuration files:
Sometimes a sync policy needs to be removed because it is no longer in use. This can cause Riva to stop syncing, because the transaction records will no longer be pointing to the correct users. (It helps to understand how Riva maintains transaction records.)
To remove a sync policy:
A Riva sync policy consists of three components:
When a sync policy object is removed in the Riva Manager application:
WARNING: Removing a connection affects all sync policies that use that connection. Before removing a connection, ensure that it is not being used by any active or disabled sync policy. Usually, connections are removed only if user mailboxes have been migrated to a different host or service or if the CRM user accounts have been migrated to a different vendor CRM. If backups of the .connection files are created, it is possible to restore connections that are removed by accident.
To remove a connection:
When a connection is removed: