Preparing and Distributing the DSM Client Program Files

To manage computers in an DSM environment, the DSM Client has to be installed on every computer. For this purpose, some parts of the DSM components are installed locally on the client computer which is managed by DSM. These local components represent the DSM Client.

The system provides two packages in every DSM share containing the required program files for x32 and x64 architectures (ClientBinaries32bit, ClientBinaries64bit). They are compressed and stored in the directory \$SysDb$. The packages are not distributed; the Update Manager (or the DSMC) automatically recreates the packages on every depot after each update. You may also create the DSM Client program files independently by opening the depot's context menu and selecting the task Prepare the DSM Client program files:

How to create the DSM Client program files manually:

  1. Select a depot in the Infrastructure view (e.g. Central Depot)
  2. Select the command Prepare the DSM Client program files.
    The system prepares the DSM Client program files and makes them available for distribution.
  3. Click Finish to close the dialog.

The DSM Client binaries are now residing in the depot's directory <share>\$SysDb$\Packages and are ready to be installed on the client computers.

If you start Update Manager from the Central Depot's share, Update Manager will create the DSM Client program files in the Central Depot (on ORG level). The DSMC also checks the status of these packages at start-up if they are started from the Central Depot's share. A message pops up if the program files are not current.

Distributing the DSM Client program files via SMB

If the client uses the SMB protocol to access the depot, the packages are optional. To use the packages, please specify the option Load DSM Client binaries into the cache before installation in the Site Settings. Since the data is compressed in the packages, the network load can be reduced considerably when updating the clients.

Distributing the DSM Client program files via HTTP

If you are using HTTP when updating the DSM Clients, the packages with the DSM Client program files are mandatory.

It is not possible to use HTTP for reinstalling clients.

DSM Clients that are already installed can be updated via HTTP and you can employ software via HTTP, provided that the assigned depot has been set up for HTTP support. For this purpose, both packages are loaded to the Repository Cache first and then copied to the Program Files directory.

If a package is waiting to be installed on a client which is connected to the depot via HTTP, the package will be downloaded to the client's Repository Cache and then installed from there.