Deploy client computers from the BigFix console by running the Install IBM BigFix Clients with Client Deploy Tool Fixlet. This Fixlet cannot be imported into a custom site. You must use it from the BES Support site.
To deploy the clients from the console, perform the following steps:
- Log in to the BigFix console.
- Open the Fixlets and Tasks icon in the Domain Panel.
- In the search bar, enter Client Deploy Tool.
- Select the Fixlet named Install IBM BigFix Clients with Client Deploy Tool.
- In the Description tab, you must:
- Select all the operating systems associated to the client computers that you want to deploy. Select the client version that you want to deploy.
- Enter the credentials needed to access the computer on which you installed the Client Deploy Tool. These credentials are required only if you installed the Client Deploy Tool on a Windows system. Specify either a domain administrator account with all necessary permissions or any administrator account with full local administrative permissions on the Client Deploy Tool computer.
- Enter the following required information for the client computers that you want to
Enter the client computer names by using one of the following options:
- The list of host names of the client computers.
- The list of IP addresses of the client computers.
- The IP address range of the client computers.
If you specify a range of IP addresses, use the following format:
The user ID needed for the connection. For example, Administrator on Windows systems or root on Linux systems.
The password associated to the user ID of the client computers.
In the Computers text box, you can specify more than one line by pressing Enter at the end of each line.
For each line, you have the possibility to enter the specific credentials associated to the client computers
- (Optional) Select, if not already selected, the Show advanced settings check box. The advanced settings are generic and apply to all your client computers.
- (Optional) Add a custom setting to each client deployed, in the form of a Name / Value pair.
- (Optional) Set up a proxy connection, if the clients to be deployed must communicate through a proxy, by specifying the following information:
The host name that is used to reach the proxy.
The port that is used to communicate with the proxy.
The user name that is used to authenticate with the proxy if the proxy requires authentication.
The password that is used to authenticate with the proxy if the proxy requires authentication.
- Click Take Action.
- On the Target tab, select one or more devices, which are target computers on which you installed the Client Deploy Tool instances.
- Click OK.
- Verify the status and the exit code of the Fixlet. The exit code 0 represents the Success status.
When running the Fixlet, depending on the operating systems that you selected in the Description tab of the Fixlet, the platform-specific packages are cached on the BigFix server and downloaded only on the client computers where the Client Deploy Tool is installed. Packages are downloaded only if they are not found; they are not overwritten each time you run the Fixlet.
- Depending on the platforms of the deployed target computers, the platform-specific packages are cached on the BigFix server and downloaded only on the client computers where the Client Deploy Tool is installed. Typically, one or more computers or relays in your environment.
The Client Deploy Tool helps you roll out targets in an easy way, but there are some requirements and conditions:
- The Client Deploy Tool can only install target computers running the supported target operating systems.
- Depending on whether you are using the Client Deploy Tool on a Windows or on a Linux system, you can use the tool to install different platforms:
CDT on Windows
Installs Windows, UNIX and Mac target computers.
CDT on Linux
Installs UNIX and Mac target computers.
- For performance reasons, the Client Deploy Tool was tested to deploy one hundred target computers (clients) at a time.
To install target computers on Windows, the Client Deploy Tool issues a Remote Procedure Call that accesses the shared installer and, with the appropriate administration credentials, runs it silently with no user interaction, and to install target computers on UNIX, the Client Deploy Tool issues an SSH connection, uses SCP to copy the installer and run the installation remotely.