1  Deploying Software Through File Sharing for Manual Installation

To view this video, click the download link.

Software Version Used

This video was recorded based on the following versions:

l          iMC: iMC PLAT 3.20-R2602, iMC UAM 3.60-E6102, iMC EAD 3.60-E6102

l          iNode (integrates the DAM client): iNode PC 3.60-E6104

Web interfaces of different versions may vary.

Application Scenario

In an enterprise, some software needs to be installed on some specific PCs. For example, all PCs need to install the anti-virus software and firewall, office PCs need to install Microsoft Office, and PCs of art designers need to install Photoshop. If only one FTP server is deployed, every employee has to download and install the software by themselves, and the administrator can hardly monitor and track software installation of every employee.

iMC DAM provides the software deployment function to solve the problem. After deploying the software deployment server, the administrator only needs to configure the software deployment policies on the iMC DAM. After that, PCs in the enterprise can easily download and install the software according to different policies and the administrator can track and monitor software installation of each PC in real time.

Recommended Configuration Flow

This configuration example shows the process of deploying software Beyond Compare to an asset group in file sharing mode, and manual installation of the software by the asset owner. The network diagram is shown as follows.

Note: iMC DAM does not save and deploy software, but triggers the PC to download software from the share server.

The configuration flow is as follows:

Step1   Add group G and Move Asset A to Group G

Add a new asset group G, and move registered asset A to group G.

Step2   Configure Share Server

Add the share server information to the iMC, including IP address, username and password.

Step3   Add Software Deployment Task for Group G

Configure the task information, including the software server configured at Step 2, the software name, the file source path, installation method, and the deployment object (group G added at Step 1).

Note: The DAM client (generally integrated into the iNode client) periodically obtains the software deployment tasks from the iMC DAM. The period depends on Period for Download, which is configured on Service > Desktop Asset Service > Service Parameters.

Step4   Download and Install Software on Asset A

On a user asset, the DAM client downloads the software as the task requires and allows the asset owner to install the software.

Step5   Track Software Installation.

With the asset change monitoring, the administrator can track whether the required software is installed.

Step6   Move Asset B to Group G and Track Task Status

Move asset B to group G, and track whether the required software is installed on asset B.