Installing the Deployment Agent
In this section:
Install the Deployment Agent
The Deployment Agent must be installed on all endpoints to be managed by Management Center. The Deployment Agent can be distributed using the integrated Install Deployment Agent functionality within the Management Console, by downloading the ClientCommunicationsAgent.msi package from the Management Server web site or by third-party deployment mechanisms.
Prerequisites
The following are prerequisites for all computers to allow Deployment Agent installation:
-
Allow File and Print Sharing in the Firewall settings.
The default Windows File and Print share exception opens up the following ports:
- NetBIOS - TCP 139, UDP 137, UDP 138
- LLMNR - TCP 5255, UDP 5355
- SMB - TCP 445
- RPC - TCP 135, TCP 445, UDP 445
- Access to ADMIN$ share and IPC$ share.
-
Access to the Service Control Manager (SCM) with the following rights:
- Create a service (SC_MANAGER_CREATE_SERVICE)
- Query service status (SERVICE_QUERY_STATUS)
- Service all access (SERVICE_ALL_ACCESS)
- Service stop (SERVICE_STOP)
- Service start (SERVICE_START)
- Service delete (DELETE)
- Windows Installer service running.
- Server service running.
We recommend setting up deployment groups and configuring settings in the Management Console before installing the Deployment Agent.
You can run the Install Deployment Agent functionality in small and medium scale enterprise environments to deploy the Deployment Agent to multiple computers, or to repair or modify the URL path for currently deployed agents to change the http or https prefix and port number. The Install Deployment Group functionality is available in Home > [Server] > Deployment Groups > [Deployment Group] > Computers.
The IT administrators in organizations often create master images which include the operating system with all the required software and updates required for a new computer, as a labor saving approach to setting up multiple computers. It is recommended to install the Deployment Agent on a gold image prior to rolling out to computers in your organization.
Integrated Install Deployment Agent Functionality
The Management Console provides an Install Deployment Agent function which allows you to deploy the Deployment Agent to multiple computers which match the Management Center Deployment Group and Membership Rules.
The software requirements for the target client computers are detected and the 32-bit or 64- bit version of the Deployment Agent, assigned to the deployment group of which the computer is a member, is downloaded. If no version of the Deployment Agent is assigned to the group then the latest version is downloaded.
Deployment Agents are copied to the target computers and installed silently, along with the correct URL of the Management Server.
The basic steps required to install the Deployment Agent are as follows:
Home > [Server] > Deployment Groups
- Create a Deployment Group.
-
Configure the polling settings in Deployment Group > Settings > General tab - Polling is where the Deployment Agent on the endpoint initiates communication with the Management Server. The poll period is split into the following:
-
Server Polling and Downloads - Deployment Agent downloads updates to the deployment groups and agent and configuration packages.
- Poll variance - reduces the impact of multiple machines polling the Management Server at any one time.
-
Event Data Uploads - Deployment Agent uploads event data to the Management Server.
- Poll variance - reduces the impact of multiple machines polling the Management Server at any one time.
-
- Setup the agent and configuration installation schedules in the Installation tab.
A warning displays in Deployment Groups > [Deployment Group] > Computers if an installation schedule is set to Disable.
Home > [Server] > Membership Rules
Every Deployment Group has a one to one relationship with a set of Membership Rules. The Membership Rules act like a filter to discover computers within Active Directory.
- Highlight a Deployment Group, select Edit Conditions to add a new condition based on NetBIOS Name or Active Directory. Click OK.
- Select Submit from the Membership Rules work area.
- Select Discover from the Actions panel.
- The discovered computers that match the Membership Rules are listed in the relevant Deployment Group > Computers node.
For the computers discovered by Membership Rules the Computer Status should initially display: No Deployment Agent deployed.
Custom - Home > [Server] > Deployment Groups > [Deployment Group] > Details section > Manage Credentials button
or
Global - Home > [Server] > Global Settings > Access Credentials tab
Enter the user credentials; user name and password, for an account which has local administrator privileges on the endpoint that the Deployment Agent is being installed.
You can add multiple accounts, they will be attempted in order of the list.
Caution: You will not be able to install the Deployment Agent on any endpoint using the integrated Install Deployment Agent functionality if the credentials have not been set up.
Home > [Server] > Deployment Groups > [Deployment Group] > Computers
- Select the computer or computers on which you want to install the Deployment Agent.
-
Select Install Deployment Agent from the Actions panel.
The Client Access Log provides details on the installation progress. The Deployed (%)
column indicates the percentage of all the packages assigned to the group that have been deployed.
Install the Deployment Agent using an Installation Schedule
You can deploy the Deployment Agent assigned to a group to the computers listed in the Computers page using an installation schedule.
The Management Center uses group membership rules to create a list of computers to which it can deploy the Deployment Agent. For further information, refer to Membership Rules.
You must specify Access Credentials before installing the Deployment Agent.
Management Center deploys the Deployment Agent installation package that has been assigned to the group. If you did not assign a Deployment Agent installation package, Management Center detects the latest available version for the target computers and downloads the 32-bit or 64-bit version as required.
Deployment Agents are installed silently, along with the correct URL of the Management Server.
To install the Deployment Agent using the Install Deployment Agent Functionality:
- Select the Home navigation button.
- Expand [Server] > Deployment Groups > [Deployment Group] > Settings > Installation tab.
- Setup the Installation schedule.
- Navigate to Deployment Groups > [Deployment Group] > Computers.
- Select the computer you want to deploy to and select Install Deployment Agent from the Actions panel.
- You can review installation feedback on the Client Access Log tab in the work area.
A warning displays in Deployment Groups > [Deployment Group] > Computers if the installation schedule is set to Disable.
After the Deployment Agent is installed it registers with the Management Server. After registering, the deployment agent implements the policies to install software, generate events and poll the server for further changes and package updates. The Deployment Agent regularly polls the server for updates and changes to the deployment policy, according to the deployment group settings.
Install the Deployment Agent Manually
You can manually install the Deployment Agent on a managed computer by downloading and running the Deployment Agent installation package on a client computer.
-
Launch a web browser such as Microsoft Internet Explorer and navigate to the Management Server web site at the following address: http://<computer name>/ManagementServer
If you have configured SSL communications, use the HTTPS prefix for the Management Server web site: https://<computer name>/ManagementServer/
The Management Center download page displays where you can download the Deployment Agent, product consoles, release notes and components which are prerequisites for installing User Workspace Manager.
-
Download and run the appropriate 32-bit or 64-bit Deployment Agent installation MSI package.
Make a note of the Management Server URL displayed in the download page.
From the website you can also download the Management Console, EULA, release notes, Application Control, Environment Manager and Performance Manager consoles, and prerequisites software. - In the Deployment Agent installation Welcome screen, click Next.
- Accept the End User License Agreement and click Next.
- Leave the default installation directory unchanged, and click Next.
-
The Deployment Agent Settings screen displays: Enter the Management Server computer name, http://<Computer Name>:Port Number/.
If you have configured SSL communications, use the HTTPS prefix for the Management Server web site: https://<computer name>:Port Number/
- Click Next to proceed.
- When the installation is complete, click Finish to exit the installation wizard.
You have now successfully installed the Deployment Agent. The host computer is able to connect to your Management Server ready to download product Agents, license and configuration software packages according to the settings configured for the deployment group to which the current computer belongs.
Install the Deployment Agent in Silent Mode
You can install the Deployment Agent silently via a third-party deployment mechanism using the command line prompt.
msiexec.exe /qn /i "<MSI file path>\ClientCommunicationsAgent.msi" WEB_SITE="http://<Management Server Name>:Port Number" GROUP_NAME="<DeploymentGroup>"
Use the HTTPS prefix for the Management Server web site only if you intend to install an SSL certificate on the server computer and managed computers are located in the same Active Directory domain as the Management Server.
- /i - Install
- /qn — Quiet mode install without the user interface.
- WEB_SITE — Enter the Management Server web site address using the name of the host computer.
-
GROUP_NAME — (Optional) Enter the Deployment Group name to which the Deployment Agent should register. The Deployment Agent can only register with a group which is set up to allow the Deployment Agent to self-register, otherwise, it will register to the Default group, likewise If the GROUP_Name specified is invalid registration to the Default group will take place.
Note that