Preparing to install agents


Before installing agents, ensure that you complete the tasks described in this section.

  1. If any of the target servers on which you plan to install agents are located behind a SOCKS proxy server, you must configure the routing of communication from the SOCKS proxy server to target servers. The configuration involves creating SOCKS proxy server objects and rules for routing to remote servers. For more information, see these topics:
  2. Add agent installers to the Depot as software packages. See Adding-agent-installer-packages-to-the-Depot.
  3. Ensure that the agent installers use a package type that is native to the target platform. For example, Red Hat servers require RPM packages.
  4. If you want to use the Smart Agent feature, modify the Agent installer package:

    Windows installer:
    1. Log in to the  console.
    2. Navigate to Depot > Agent Installers > <version>.
    3. Double-click Windows_64.
    4. Click Edit corresponding to the Optional MSI Customization Properties.
    5. Add the following parameters:

      The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.


      agent_job_sh_details.png

      1. In the Name and Value fields, enter the parameter name and its value, and click add_button.png.
      2. Repeat this step to add other parameters.
    6. Save the changes.

      Important

      Do not pass sensitive information like BLADELOGICDCUSERPASSWORD or BLADELOGICUSERPASSWORD through the Install command. We recommend using the Optional MSI Customization Properties.

    Linux installer:
    1. Configure the Smart Agent parameters in the nsh-install-defaults file. For more information, see Configuring-the-installation-parameters-for-the-NSH-or-the-RSCD-agent.
    2. Log in to the  console.
    3. Navigate to Depot > Agent Installers > <version>.
    4. Double-click Linux_64 or Debian_ubuntu_64 depending on the operating system that you are using.
    5. Under Support Files, click the edit option.

      edit_option.png

    6. Browse and select the nsh-install-defaults file, and click OK.
    7. Save the changes.
  5. (Windows) If you are installing agents on Windows servers, install PsExec on a server that can function as the PsExec server. See Setting-up-a-PsExec-server.

    Furthermore, for any target Windows server that is behind a SOCKS proxy server, ensure that the PsExec server is also behind the SOCKS proxy server. For more information, see Specifying or modifying information for remote host authentication.

  6. (Windows) Ensure that you must have Server Message Block (SMB) v2 enabled on a Windows target server.
  7. Add agentless devices to the system individually or importing them. For more information, see the following topics:

    You can also install agents when you add or import the agentless devices. However, ensure that you complete all the prerequisite tasks before installing them.

  8. (Optional) Specify an alternative staging directory for agentless devices. See Defining-alternative-staging-directories

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*