Client Installation

An unmanaged computer becomes a managed computer when the DSM Client has been installed, and when the computer has been subsequently assigned to a site and synchronized with the DSMDB.

The client components are usually installed with a batch file that is called in the login script or by using an interactive command.

In order for the DSM modules to manage a computer, it must be able to be assigned to an DSM site.

"Interactive" Installation via the DSMC

Unmanaged computers that are contained in the DSMC's Object window can be turned into managed computers directly in the DSMC with the Manage Computer task. This triggers a remote installation of the DSM Client on this computer.  

The Object window of the DSMC shows managed and unmanaged computers. New computers can be imported (e.g. from the Active Directory) or also created interactively.

Installation via Login Script

Please find a sample of a login script under Listing of Nilogin.cmd.

The installation via login runs through the following steps:

1. If the DSM Client is not installed yet, the login script starts the DSM Agent with the parameter /install from a specified depot:
   %NiServerDir%\niagnt32.exe" /install
   The command is executed in the user context.
   
   This command copies a minimal amount of the DSM program files and of the Infrastructure Configuration Database (ICDB) locally to a temporary directory in order to start the DSM Agent from there.
2. With the help of local ICDB, the DSM Agent determines the specified user account with local administrator rights (the DSM Runtime Service account) and performs a site assignment.
   These actions are executed in the user context as well.

   In the following, the DSM Agent uses the determined local administrator account.

3. The DSM Agent copies the DSM program files and the ICDB to the default path %ProgramFilesDir%\NetInst.
4. The DSM Agent installs the DSM Core Services and the DSM Runtime Service.
   Then, the Agent starts the DSM Core Services and afterwards, as soon as the services have been started successfully, starts the DSM Runtime Service.
   
   The services are configured with the setting Start type = Configured automatically. The DSM Runtime Service can only start if the DSM Core Services have been started successfully.
5. The DSM Core Services (more precisely: the Client State Manager) is in charge of the complete installation of the DSM Client.
   For this purpose, the DSM Core Services specify the "best" depot that guarantees a preferably smooth installation even if the network connection is weak (%NiServerDir% is re-determined).

   The DSM Services make sure that the DSM Client is synchronized regularly in the background (the users normally do not take notice of this process).

"Interactive" Installation with Command

You can also install the DSM Client by running a command on a computer.
Please enter the following command on the respective computer in Start > Run:

%NiServerDir%\installclient.exe (equivalent to the command %NiServerDir%\niagnt32.exe /install /bin)

As opposed to the command %NiServerDir%\niagnt32.exe" /install, the complete DSM Client is installed from the specified depot with the command %NiServerDir%\installclient.exe. The depot is not checked for its network connection.

The administrator specifies the installation depot and has to make sure that the depot possesses a network connection with a sufficient capacity.
This depot has to reside in the site to which the computer is to be assigned to.