Deploying your first Client Management agent
Most management features in Client Management (patch management, remote control, software distribution, and so on) require that agents are installed on the target computers.
The agent rollout wizard facilitates installation of the CM agent within your environment. The two main components of this process are:
- The Rollout Server, a device that generates self-extracting agent installation packages and can push them on the target devices.
- Rollouts which include agent installation files, target devices and rollout options.
A typical Client Management architecture has a smaller number of relays directly under the master and a larger number of clients under each relay. This first section therefore teaches you how to perform the two main types of rollout:
- Rolling out relay agents (with the master server as their direct parent) and
- Rolling out final clients (with one of the previously installed relays as their parent).
Prerequisites for deploying first client agents
Before starting a rollout ensure that the following prerequisites are fulfilled:
- Remote shares are accessible from the rollout server (for example, //ClientComputer1/C$).
- The RPC service is started.
- No NAT-configurations are used.
- The remote services are accessible.
- For Linux installations ensure that the SSH service is installed and running on the targets.
- For Linux installations the root account must be enabled on the targets raiz.
- For Mac OS installations ensure that SSH and the root account are enabled on the targets.
Configuring the rollout server
A Rollout Server is an CM agent used to deploy other agents. To define a device as Rollout Server, proceed as follows:
To define other Rollout Servers, proceed as follows:
- Click Add Rollout Server
.
- Select the new device which is to be Your Rollout Server from the list.
- Click OK to add it and close the window.