Administration Guide › Managing Virtual Environments › VMware vSphere and vCenter Server › How to Configure the vCenter Server Management Components › Add the AIM Instance for the vCenter Server

Add the AIM Instance for the vCenter Server

After adding a new vCenter Server connection to the CA Server Automation manager, add a vCenter AIM instance to manage the new vCenter Server. CA Server Automation then discovers the entire vSphere environment with all its physical and virtual components, such as vCenter Server, ESX Servers, VMs, and other virtual components.

Follow these steps:

1. Open the CA Server Automation user interface from the Start menu. Click Administration, Configuration.

   The Configuration page appears.

2. Select vCenter Server from the Provisioning section in the left pane.

   The right pane refreshes and displays the managed vCenter Servers, associated vCenter AIM Servers, and the AIM Instances for managed vCenter Servers.

3. Click (Add) on the vCenter AIM Servers pane toolbar.

   The New vCenter AIM Server dialog appears.

4. Open the vCenter AIM Server drop-down list.

   The list of discovered vCenter AIM Servers appears. If you have installed the vCenter AIM on the local system, the name of the local system appears in the list too.

5. Select a vCenter AIM Server from the drop-down list.

   CA Server Automation populates the vCenter Server drop-down list with the vCenter Servers listed in the vCenter Servers pane. That is, you can only manage those vCenter Servers for which your CA Server Automation manager has a valid connection established.

6. Select the vCenter Server you want to manage and click OK.

   A new AIM instance for the selected vCenter Server is added. If the instance is not in an error or stopped state, CA Server Automation starts to discover the associated vSphere environment. When the discovery process is complete, you can start managing the virtual and physical resources of vSphere.

More information:

Verify the vCenter Server Folder Appearance in the Resources Tree

Troubleshoot the vCenter AIM Instance Connection