Deactivating synchronization
Regular synchronization cannot be started until the synchronization project and the schedule are active.
To prevent regular synchronization
-
In the Synchronization Editor, open the synchronization project.
-
Select the start up configuration and deactivate the configured schedule.
Now you can only start synchronization manually.
An activated synchronization project can only be edited to a limited extend. The schema in the synchronization project must be updated if schema modifications are required. The synchronization project is deactivated in this case and can be edited again.
Furthermore, the synchronization project must be deactivated if synchronization should not be started by any means (not even manually).
To deactivate the synchronization project
-
In the Synchronization Editor, open the synchronization project.
-
Select the General view on the home page.
-
Click Deactivate project.
Related topics
Displaying synchronization results
Synchronization results are summarized in the synchronization log. You can specify the extent of the synchronization log for each system connection individually. One Identity Manager provides several reports in which the synchronization results are organized under different criteria.
To display a synchronization log
-
In the Synchronization Editor, open the synchronization project.
-
Select the Logs category.
-
Click 
in the navigation view toolbar.
Logs for all completed synchronization runs are displayed in the navigation view.
-
Select a log by double-clicking it.
An analysis of the synchronization is shown as a report. You can save the report.
To display a provisioning log
-
In the Synchronization Editor, open the synchronization project.
-
Select the Logs category.
-
Click 
in the navigation view toolbar.
Logs for all completed provisioning processes are displayed in the navigation view.
-
Select a log by double-clicking it.
An analysis of the provisioning is shown as a report. You can save the report.
The log is marked in color in the navigation view. This mark shows you the status of the synchronization/provisioning.
TIP: The logs are also displayed in the Manager under the <target system> > synchronization log category.
Synchronization logs are stored for a fixed length of time.
To modify the retention period for synchronization logs
Synchronizing single objects
Individual objects can only be synchronized if the object is already present in the One Identity Manager database. The changes are applied to the mapped object properties. If a membership list belongs to one of these properties, the entries in the assignment table will also be updated.
NOTE: If the object is no longer present in the target system, then it is deleted from the One Identity Manager database.
To synchronize a single object
-
In the Manager, select the Azure Active Directory category.
-
Select the object type in the navigation view.
-
In the result list, select the object that you want to synchronize.
-
Select the Synchronize this object task.
A process for reading this object is entered in the job queue.
Features of synchronizing memberships
If you synchronize changes in an object's member list, run single object synchronization on the assignment's root object, The base table of an assignment contains an XDateSubItem column containing information about the last change to the memberships.
Example:
Base object for assigning receive restrictions for Exchange Online email users and mail-enabled distribution groups is the distribution group.
In the target system, mail acceptance for a mail-enabled distribution group was allowed for an email user. To synchronize this assignment, in the Manager, select this distribution group and run single object synchronization. In the process, all of the distribution group's assignments are synchronized.
The email user must already exist as an object in the One Identity Manager database for the assignment to be made.
Detailed information about this topic
Tasks following synchronization
After the synchronization of data from the target system into the One Identity Manager database, rework may be necessary. Check the following tasks:
