Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Adding the vCenter server to BMC Server Automation

The following sections provide instructions for adding a VMware vSphere environment to BMC Server Automation:

Before you begin

Ensure that your environment meets the following requirements.

System requirements

Note

The following list of VMware vCenter and vSphere supported versions applies to BMC Cloud Lifecycle Management 3.1.x and BMC Server Automation 8.2.x. But even though BMC does not automatically certify newer versions of vCenter and vSphere, BMC does support customers running these newer versions as long as backward-compatibility is guaranteed.  For more information, review Product-versions-and-compatibility.

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

Access and privileges

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To install the Microsoft Windows agent on the vCenter server

  1. Install the Windows agent on the vCenter server, as described in Installing an RSCD agent (Windows).

     

    Note

    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.

  2. Open the c:\windows\rsc\exports file and edit the permissions. Ensure that the permissions in the Exports file follow the permissions guidelines you are using in regards to exports or users or users.local files.

  3. Open a command window and run the following command from the system on which NSH is installed:
    agentinfo <vCenterServerHostname>
     The agentinfo command 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.
    For example:

    U:\>agentinfo  10.128.25.3

    10.128.25.3:

      Agent Release   : 8.5.00.336

      Hostname        : vm-w28-blg28

      Operating System: WindowsNT 6.0 Windows-VC5.1 (x86_64)

      User Permissions: BladeLogicRSCD@VM-W28-BLG28->Administrator@VM-W28-BLG28:PrivilegeMapped (Identity via trust)

      Security        : Protocol=5, Encryption=TLS1

      Host ID         : C0A16568

      # of Processors : 2

      License Status  : Licensed for NSH/CM

 

To add the vCenter server to BMC Server Automation

To add the vCenter server to BMC Server Automation, complete the following steps:

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

Related BMC Communities blog entry

The following link provides supplemental information available from a blog entry in BMC Cloud Lifecycle Management Communities:

The Pulse: Configurations when switching to new vCenter server

This blog entry provides information to help you configure your existing BMC Cloud Lifecycle Management stack when you introduce a new vCenter server while keeping the naming convention, for Clusters and Data-stores the same.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*