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.

Reviewing minimum requirements for Microsoft Hyper-V environments

This topic lists the system requirements and access and privileges required to implement provisioning of Microsoft Hyper-V virtual machines. The topic includes the following sections:

System requirements (Microsoft Hyper-V)

To employ BMC Server Automation in an Microsoft Hyper-V virtual environment, you must meet the following minimum requirements.

System requirements for all SCVMM versions

  • Microsoft System Center Virtual Machine Manager (SCVMM) installed
  • Hyper-V role enabled
  • PowerShell 2.0 installed
  • The following SCVMM versions and corresponding Windows platform versions are supported:
    • SCVMM 2008 R2 is supported on Windows 2008 R2 and on Windows 2008 R2 SP1
    • SCVMM 2012 SP1 is supported on Windows 2012 SP1

Additional requirements for SCVMM 2012 SP1

  • Host should be Windows server 2012.

  • Microsoft .NET Framework version 3.5 must be installed on the SCVMM 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 Generation 1 Virtual Machine Templates on SCVMM.
  • Create at least one VM network, to which the VMs can connect. 
    For SCVMM 2012 SP1, only VM Network of type noIsolation is supported.
  • Apply a workaround in Windows 2012 server to point to .NET 4.0 version.

     Click here to review the steps for the workaround.
    This workaround is necessary because the Windows Server 2012 environment runs with .NET 2.0 version, while the DLLs in SCVMM 2012 SP1 and later 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"?>
      <startup useLegacyV2RuntimeActivationPolicy="true">
      <supportedRuntime version="v4.0.30319"/>
      <supportedRuntime version="v2.0.50727"/>
      </startup> </configuration>


      For a 64-bit OS you might want to create a similar powershell.exe.config file in the following location:


    2. Copy the file into the powershell root directory: C:\Windows\System32\WindowsPowerShell\v1.0.
      For a 64-bit OS, create a similar powershell.exe.config file in the C:\Windows\SysWOW64\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
  • If virtual floppy disk creation fails using Imdisk, then install IMdisk manually. The Imdisk installer is packaged with SCVMM CO. To install the Imdisk tool manually, do the following:
    1. Go to the following location:


    2. Run the following command:

Access and privileges (Microsoft Hyper-V)

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

Where to go from here

Adding the Microsoft SCVMM server to BMC Server Automation

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