Adding and configuring an agent-based vCenter server
To add a vCenter server as an agent-based managed server, perform the following tasks:
Before you begin
Ensure that your environment meets the requirements described in Reviewing minimum requirements for VMware environments.
To add an agent-based (Windows) vCenter server
Install the Windows agent on the vCenter server, as described in Installing an RSCD agent (Windows).
Previous versions of BMC Server Automation required the installation of a special vCenter agent. That requirement no longer applies, as you now install the Windows agent on the vCenter server.
- Open the c:\windows\rsc\exports file and edit the permissions. Follow whatever permission guidelines you are using for exports or users or users.local files.
- Open a command window and run the following command from the system on which NSH is installed:
agentinfocommand displays various types of information, including an entry for the OS. The OS should be a Microsoft Windows OS and the letters "VC" should be appended on the same line, which signifies that it is a Windows computer with vCenter running on it.
- From within the BMC Server Automation Console, add the server as a managed server to a server group by right-clicking a server group and selecting Add Server.
On a virtual center instance that is clustered with MSCS (MicroSoft Cluster Services), ensure that you register the Master server of your virtual MSCS center with the BSA product.
Ensure that the RSCD agent installed on this server is of the same version as the BMC Server Automation Application Server.
To configure the agent-based vCenter server in BMC Server Automation
- From within the BMC Server Automation Console, select Configuration > Property Dictionary View.
- Browse the Built-in Property Classes > Connection class.
On the Instances tab, create a Connection instance using the following naming convention:
For example, if your vCenter server was added into BMC Server Automation with the name prodvcs02.example.local, you would name the instance Connection_prodvcs02.example.local. This new instance contains the connection details for the vCenter server.
NoteYour user role must have the appropriate RBAC permissions to create or update the Connection instance. Otherwise, the association between the instances will not be created and the server will not be enrolled.
After creation of the connection instance, a connection PSI is automatically created for the server in virtualization and the value of
VIRTUAL_ENTITY_CONNECTIONis set to the
CONNECTION PSIthat is created.
Set the following properties for the new Connection instance:
Enter the web URL of the SDK of the vCenter server (for example, https://<vCenterServerName>/sdk).
Note: This name should match the VMware vCenter server name registered in BMC Server Automation.
Enter the name of an administrator of VMware vCenter, or another user with required privileges.
If you need to provide a domain name with the username, enter it here as
Enter the password of the user that is mentioned in the above property.
- Save the instance.
- Run an Update Server Properties Job (New > Administration Task > Update Server Properties Job) against the vCenter server.
- Distribute the vCenter configuration object on the vCenter server:
- From the BMC Server Automation Console, navigate to the Jobs folder.
- Right-click a job group and select New > Administration Task > Distribute Configuration Objects.
- Provide a name for the Job and click Next.
- Expand the Global Configuration Objects list, select the VMware vCenter Server object, and add it to the Selected Configuration Objects section. Click Next.
- On the Targets panel, select the agent installed on the vCenter host.
Click Finish, and execute the job. For details, see Distributing configuration objects.
Where to go from here
Now that you have set up the VMware vSphere environment, you are ready to perform various vSphere management tasks, as discussed in Managing a VMware vSphere environment.