Adding the Microsoft VMM server to BMC Server Automation

The following sections provide instructions for adding the Microsoft Hyper-V System Center virtual machine manager (VMM) to BMC Server Automation:

Before you begin

Ensure that your environment meets the following requirements.

System requirements

To use BMC Server Automation in a Microsoft Hyper-V virtual environment, you must have the following minimum hardware and software:

  • Microsoft Hyper-V 2012 System Center VMM installed
  • Hyper-V role enabled
  • PowerShell 2.0 installed

The BMC Server Automation Application Server must be allowed access to the target through the RSCD agent on the VMM server.

Access and privileges

For a Microsoft Hyper-V virtual environment, Administrative Privilege to the VMM is required. 

Prerequisites for SCVMM 2012 SP1

The following are the pre-requisites for SCVMM 2012 SP1 support for Hyper-V Custom Object:

  • SCVMM version should be SCVMM 2012 SP1
  • Host should be Windows Server 2012
  • To enable BMC Server Automation to execute Powershell commands on the SCVMM setup, set the Execution Policy. On SCVMM Setup, open a Powershell command prompt, and run the following command:
    Set-ExecutionPolicy RemoteSigned
  • Ensure that Windows templates and Linux templates are created as described in Creating Virtual Machine Templates on SCVMM in the BMC Server Automation online technical documentation.
  • Create at least one VM network, to which the VMs can connect. BMC Server Automation supports VM Network of type noIsolation only.
  • Apply a workaround in Windows 2012 server to point to .NET 4.0 version. This workaround is necessary because the Windows Server 2012 environment runs with .NET 2.0 version, while SCVMM 2012 SP1 DLLs are built with a newer .NET framework 4.0. The workaround is as follows:
    1. Create powershell.exe.config with the following:

      <?xml version="1.0"?><configuration>
        <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0.30319"/>
        <supportedRuntime version="v2.0.50727"/>
        </startup>
      </configuration>
    2. Copy the file into powershell root directory: C:\Windows\System32\WindowsPowerShell\v1.0
    3. Run following from the command line:

      reg add hklm\software\microsoft\.netframework /v OnlyUseLatestCLR /t REG_DWORD /d 1
      reg add hklm\software\wow6432node\microsoft\.netframework /v OnlyUseLatestCLR /t REG_DWORD /d 1

To install the Windows agent on the Microsoft VMM server

  1. Install the RSCD agent on the VMM server, as described in Installing an RSCD agent (Windows). Be sure to install the Windows x64 agent.
  2. Push Acls to the system and ensure the Role(s) that will be interacting with SCVMM are mapped to a local or domain account with the appropriate privileges to mange the server.

To add the Microsoft VMM server to BMC Server Automation

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

  1. From within the BMC Server Automation Console, add the SCVMM server as a managed server to a server group (right-click a server group and select Add Server ).
  2. Select Configuration > Property Dictionary View.
  3. Browse the Built-in Property Classes > Connection class.
  4. Click the Instances tab.
    A Connection instance is automatically created with the name Connection_<nameofVMMEnrolled>, where <nameofVMMEnrolled> is the name of the SCVMM server.

    Note

    Your user role must have the appropriate role-based access permissions to update the Connection instance, otherwise the association between the instances is not created and the server is not enrolled. Also, if a Connection instance is already associated with the Virtualization instance then a new instance is not automatically created.

    This new instance contains the connection details for the SCVMM server.

  5. You can modify the following properties for the new Connection instance:

    Property

    Value

    CONNECTION_URL

    Enter the host name or IP address of the Microsoft VMM Server. Ensure that this URL matches with the VMM server name registered in BMC Server Automation.

    For example, if the VMM server name is pw-aus-bsa-qa02.sqltest.bladelogic.com then the CONNECTION_URL will be pw-aus-bsa-qa02.sqltest.bladelogic.com

    CONNECTION_USER

    Enter the name of an administrator of Microsoft VMM, or another user with required privileges.
    If you need to provide a domain name with the username, enter it here as <domainName\adminUserName>.

    CONNECTION_PASSWORD

    Enter the password of the user that is mentioned in the CONNECTION_USER property.

  6. Distribute configuration objects to the SCVMM server:
    1. From the BMC Server Automation Console, navigate to the Jobs folder.
    2. Right-click a job group and select New > Administration Task > Distribute Configuration Objects.
    3. Provide a name for the Job and click Next.
    4. Expand the Global Configuration Objects list, select the Microsoft VMM object, and add it to the Selected Configuration Objects section. Click Next.
    5. On the Targets panel, select the VMM server.
    6. Click Finish, and execute the job. For details, see Distributing configuration objects.

Note

If you upgrade to the latest version of BMC Server Automation, you must immediately update the RSCD agent on the system used for the integration and add the new configuration object version for the integration.

Where to go next

Configuring blueprints for Microsoft Hyper-V switches

Was this page helpful? Yes No Submitting... Thank you

Comments