Infrastructure on Server Side for Linux

Installation of the DSM Client Proxy

In order for Linux Support to work correctly, the DSM Client Proxy management application must be installed on the management point the Linux clients connect to. The DSM Client Proxy application is part of DSM NetInstall. You don't need a license for DSM OS Deployment. The Client Proxy settings also apply to OSD Clients.

If you are using DSM OS Deployment and your Linux clients boot over the network, please install DSM Client Proxy and DSM OSD Proxy on the same Management Point. This is important so that the Linux clients do not change the Management Points each time they start. Changing the Management Points leads to client synchronizations and increased network loads.

Configuration of the DSM Client Proxy

After installing the management point application, you can configure the DSM Client Proxy in the configuration table.

In the context menu of the Management Point in the Client Proxy section you can select the following properties:

• Virtual directory on the DSM Client Proxy
  Directory the Microsoft IIS uses for the DSM Client Proxy (Default: Client Proxy). If you change the default setting make sure to change the configuration of the Microsoft IIS accordingly.
• Select the client depot according to the site definitions
  Default setting is No. If you change the setting to Yes, the Client Proxy determines the respective site according to the site definitions. The site definitions must only consist of inclusions of IP ranges.

  If you change the setting to Yes, the system does not consider the settings you defined for OSD Clients in the DepotRange.ini (on the DSM share or on the OSD Proxy). The setting only affects OSD Clients that always connect to a depot via SMB. This setting does not apply to Linux clients. Linux clients get their data only from the Client Proxy Web Service.

• Alternative depots for the Client Proxy
  Default setting is Use site definitions. You can specify an alternative depot for the client proxy instead of the default depot that was determined by the site. This setting applies to the depot the client proxy accesses.

  If you did not specify a specific depot for the OSD Clients, they will connect to the depot of the client proxy you specified here. This setting does not apply to Linux clients. They get their data only from the Client Proxy WebService.

Selecting the Depot via 'DepotRange.ini' or via Site Definition

If the OSD Proxy resides in another location than the clients in your DSM environment, the clients should get their mass data from the depot in their location.

Open the configuration file that resides in \\<Management Point>\DSM$\SSI\Extern$\Depotrange.ini to assign the OSD Clients from a specific IP range to a depot. The DSM Client Proxy tries to find the DepotRange.ini in the local NetInst directory and afterwards in the DSM share. The DepotRange.ini can be derived from the DepotRange.ini.sam sample file.

Alternatively you can also specify the depot the clients are to use via site definition. Select Yes for the configuration table setting Select Client Depot by site definitions.

The site definition must only consist of inclusions of IP addresses.

Log Files

In the NILogs directory:

• clientproxy_<ascending number>.log
  Log file of the DSM Client Proxy management application
• clientproxy_webservice.log
  Log file of the Client Proxy Webservice. Old versions have a date.
• clientproxySvc_<ascending number>.log
  Log file of the Client Proxy Service

In the NILogs\ClientProxy directory:

• ClientProxyRpcClient(<DSM ClientID | MacAddress | Name of the calling procedure>)_<ascending number>.log
  Log file of the RPC call placed by individual clients to the Client Proxy. If the DSM client ID is already known, the system uses it; if not it uses the computer's MAC address of the name of the calling procedure.
• ClientProxyRpcClient(<DSM ClientID | MacAddress | Name of the calling procedure>)_AGG.log
  Aggregated log file of the RPC call placed by individual clients to the Client Proxy