Client Synchronization

All of the control data that is relevant for a managed computer is synchronized automatically with the DSM Database (DSMDB); this procedure is called client synchronization.

The client synchronization is performed by the Installer on the managed computer: AutoInstaller, Service Installer and Software Shop perform the synchronization automatically.

Scope of the Synchronization

The client synchronization considers control data for the respective computer and the logged-on user. This mainly includes policies, policy instances, package control data and schemas.

Synchronization Process

When started, every Installer sends the existing status data of the managed computer to the Management Point. Based on this status data, the relevant control data for the managed computer is determined on the server and then synchronized with the managed computer.

As soon as the control data has been synchronized in the DSMDB Cache, the Installer executes the existing policies.
When the policies are executed, new status data is produced, which may result in new control data; then, the Installer restarts the synchronization with the server.

In this way, the synchronization is repeated up to 5 times each time the Installer is running until there is no new control data. This guarantees that the status of the managed computer is always current after an installation.

In case the Installer cannot establish the desired state of the policy, a corresponding status is established and sent to the server (e.g. Not compliant or Not possible). By evaluating the detailed information (further status properties and log files), errors, that may occur when executing a policy, can be detected and solved.
Using the command CommitChangesToServer in an eScript will always be followed by another client synchronization, regardless how many times the synchronization has already been repeated.