VMware VCENTER CONFIGURATION MANAGER 5.3, Руководство по началу работы

Страница: 265 / 274

Configuring a Collector as an Agent Proxy
B
Configuring a Collector as an Agent Proxy
Although it is not recommended, you can configure your Collector as an Agent Proxy. If you choose
configuring your Collector as your Agent Proxy, the following configuration steps replace steps 1 - 4 in the
"Configuring Agent Proxy Virtualization Collections" on page 118 . You should perform the following
configuration steps only if you are using your Collector machine as an Agent Proxy.
1. Verify membership to CSI_COMM_Proxy_SVC .
2. Generate key pairs .
3. Upload keys to database .
Verifying Membership to CSI_COMM_PROXY_SVC on the Agent Proxy
Machine
Perform the following procedure on the Collector machine that you will be using as the Agent Proxy.
1. Click Start | Administrative Tools | Computer Management .
2. Expand the Local Users and Groups node, and then click Groups .
3. Double-click the CSI_COMM_PROXY_SVC group.
4. Add the Network Authority account to the CSI_COMM_PROXY_SVC group. This account is the VCM
Collector Service account that was specified during installation.
N
OTE
This is the Network Authority Account name and VCM Service (such as SAS) that you used
during installation. For more information on the Network Authority Account, see About Available
Accounts in the online Help.
5. Add any additional users that should have access to the Collector (as Agent Proxy), and then click OK .
6. If you made changes to the group membership, you MUST reboot the Collector machine to apply the
changes.
N
OTE
If you need to replace a local user in the CSI_COMM_Proxy_SVC group with a new local user, the
new account must have full control of
[drive]:\Program Files\VMware\VCM
and have full control of
the Configuresoft registry key (
HKEY_LOCAL-MACHINE\Software\Configuresoft
).
If keys have already been generated, the
agentdata\protected
folder must be deleted and new keys
VMware, Inc. 265