Client Starting Process

On Windows computers, the DSM services start before the user logs in. After the user logs in, the other client components start.

Before the User Logs In

1. The DSM Core Services and the DSM Runtime Service are started automatically by the operating system.
2. The DSM Core Services determine the site type on the basis of the local ICDB.
3. The DSM Runtime Service fetches the access data for its net­work access.
4. The DSM Runtime Service starts the Service Installer.
5. The Service Installer performs a synchronization with the DSMDB. Thereby policies and policy instances which are relevant for the managed computer are copied into the DSMDB Cache.
6. Dependig on the configuration the Service Installer executes computer-related portions of the packages.

After the User Logs In

When the user logs on, the DSM Center (DSM icon in the Windows task bar) is started automatically.

When the user logs on, the processes described above are finished first (if they have not been completed yet).
Afterwards, the AutoInstaller can synchronize with the DSMDB whereby the policies and policy instances relevant to the computer or user are copied to the DSMDB Cache. Then, the AutoInstaller installs the packages according to the policies.

In order for the AutoInstaller to start, the DSM Agent’s has to be started in the login script first (the DSM Agent is in charge of starting the AutoInstaller).
Depending on the configuration settings (resident Agent; polling interval), the DSM Agent can also start the AutoInstaller in the background, if required.