As a part of installing AppManager for VMware vSphere, you install an agent with the module. You can install the module in one of the following locations:
On the vCenter server
On a Windows computer that serves as a proxy agent computer
A proxy agent remotely monitors the vCenter Server. Using a proxy agent computer can help avoid any possible performance issues the agent might cause if installed on the vCenter Server.
NOTE:If you have been monitoring a particular vCenter server with a proxy agent computer, and want to change to a different vCenter server, first delete the original vCenter server from the TreeView. If you try to run a Knowledge Script on both objects, errors will occur.
If your AppManager agent is monitoring vCenter remotely (in proxy mode) and you run the VirtualCenter_Alarms, VirtualCenter_Events, or VirtualCenter_Tasks Knowledge Scripts, any other VMware Knowledge Script jobs that try to connect to vCenter will get delayed for long periods of time. For example, the VirtualCenter_HostCPUUsage Knowledge Script will take a long time to query CPU performance metrics if the Alarms, Events, or Tasks scripts are running and the AppManager agent is in proxy mode. To avoid long delays when running other VMware Knowledge Scripts, you should only run the Alarms, Events, or Tasks scripts if your AppManager agent is running on the vCenter server, and not in proxy mode.
If you want to run the Alarms, Events, or Tasks scripts in proxy mode, configure the .NET machine configuration file, machine.config, to avoid the delays described above. You can find the machine.config file in the %runtime install path%\config directory on the proxy agent computer.
To configure the .NET machine configuration file on a proxy agent computer:
Add the following lines of code to the machine.config XML file: <configuration> <system.net> <connectionManagement> <add address = "*" maxconnection = "X" /> </connectionManagement> </system.net> </configuration> Where X is the largest number of concurrent jobs you will ever need to run on the proxy agent.
If the <connectionManagement> tag is already present, ensure the <add address line is added to the XML file.
Save and close the machine.config file.
NOTE:The changes you made might not take effect immediately, but you can reboot the proxy agent computer to speed up this process.