Page tree
Skip to end of metadata
Go to start of metadata

Agentless collection, or proxy data collection, enables a computer to act as a proxy host and collect data from other computers without having to install BMC TrueSight Capacity Optimization on those computers. You can collect data using a VMware ESX proxy host, vmWare vCenter host, or Windows proxy agent. You can also use a proxy host to collect data for specific components, such as Investigate, Manager, Collect Data, and the Best1Collect command. The advantages of proxy data collection include:

  • Fewer computers to deploy.
  • Fewer computers to manage.
  • Minimal footprints on the agentless computers.

For more information about collecting BMC TrueSight Capacity Optimization data using proxy hosts, see: 

For information about the recommended resources required for proxy data collection, see Sizing guidelines for BMC TrueSight Capacity Optimization proxy collection agents.


The Windows Proxy Agent component remains deprecated in version 10.7 of TrueSight Capacity Optimization. This was deprecated in version 10.5. For more details, see Deprecated and dropped features and components.

Proxy data collection terms

The following table defines a few of the terms related to proxy data collection:

Proxy terminology



Proxy host

The computer configured as the proxy to manage the agentless computers.

Agentless computer

Computer that does not have Perform Agent installed and is therefore being managed by the proxy host.

Proxy domain

The domain that contains the agentless computers. This is defined for the Microsoft Windows proxy host.

Logical domain

The domain that contains the agentless ESX servers. This is defined for the VMware ESX proxy host.

Outline of the proxy data collection process

These steps provide a basic outline of what you need to do to configure and implement proxy data collection in your environment.

  1. Determine the domains and computers you want to manage.
  2. Gather information about all the computers in the domain, such as computer name, username, and password.
  3. Identify which computers you want to manage.
  4. Identify the computers to use as proxy hosts. They must have Capacity Agent installed.
  5. Determine the domain accounts and privileges necessary for proxy hosts. See Knowing Domain accounts and privileges for specific requirements.
  6. Create a list of agentless computers for each proxy host.
  7. Identify which proxy host will manage which agentless computers.
  8. Prepare the configuration file (agentlessComputers.cfg) with the list of agentless computers that are candidates for proxy data collection. See Populating the proxy data collection configuration file.
  9. Enable proxy data collection. See Enabling proxy collection, history, and selecting the VMware proxy type for the full procedure.
  10. Configure each proxy host computer using Capacity Agent, accessible from Start > Settings > Control Panel on the proxy host computer.
  11. Perform a sample data collection to verify that all agentless computers can be discovered and that data is collected from them.

Preparing for proxy data collection

This section covers step 8 and step 9 of Outline of the proxy data collection process. It assumes you have completed all necessary research and design decisions (steps 1 through 7) and are ready to begin implementation. After you complete these tasks, you can continue with steps 10 and 11, configuring the proxy host and performing a sample data collection. 

The tasks described in this section are:

Populating the proxy data collection configuration file

The configuration of proxy hosts for proxy data collection is a post-install activity. A configuration file, agentlessComputers.cfg, lets you control the scale of service provided by a given proxy host. This file limits the set of agentless computers from which a proxy host can collect data. By default the file is located in C:\Program Files\BMC Software\Patrol3\BEST1versionNumber\local\setup.


For optimal performance and reliability of the proxy data collection process, consider the recommendations outlined in Proxy Agents, prior to populating the configuration file.

The configuration file is initially empty. After you decide how to deploy proxy data collection for your system, populate the configuration file with a list of agentless computers that are enabled for proxy collection. Specify the name, domain, and (optional) enable history collection for each agentless computer.



agentless computer

Name of the agentless computer from which you want to collect data.


Name of the domain to which the agentless computer belongs.

history enabled

Boolean value that indicates whether the History feature is disabled (0) or enabled (1).

The format of the file, with example entries, follows. Commented lines are preceded by a pound (#) sign:

# comment line
# format : one agent less computer per line
# contents: agentless computer,domain,history enabled(0 or 1)
# example:
# calbro1,development,1
# calbro2,development,0


The contents of the agentlessComputers.cfg file is read at agent startup and stored in memory. Changes to the list requires an agent restart in order for the modifications to take effect. The content of this file is case-sensitive.

After the configuration file is populated with the list of agentless computers, use Capacity Agent to enable proxy collection and then configure the proxy host.

Restarting Capacity Agent

Whenever a change is made to the configuration of a proxy host, including during the initial setup, the Capacity Agent application must be restarted.

This occurs automatically after you click OK. A message box appears to inform you that the agent is restarting and a second message appears to let you know if the restart was successful.

If you are notified that the restart failed, you must restart Perform Agent manually (from Start > Settings > Control Panel > Capacity Agent.) in order for your changes to take effect.