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 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

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

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

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

To add the Microsoft VMM server to BMC Server Automation

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

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Where to go next

Configuring-blueprints-for-Microsoft-Hyper-V-switches

 

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