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:
- Either one of the following Microsoft Hyper-V System Center VMM installed:
- Hyper-V 2012
- Hyper-V 2016 (supported with TrueSight Server Automation 8.9.04.001 from BMC Cloud Lifecycle Management 4.6.07.002 onwards)
- Hyper-V 2019 (supported with TrueSight Server Automation 8.9.04.001 from BMC Cloud Lifecycle Management 4.6.07.002 onwards)
- 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
Prerequisites for SCVMM 2012 SP1
The following are the prerequisites 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:
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>
- Copy the file into powershell root directory: C:\Windows\System32\WindowsPowerShell\v1.0
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
Prerequisites for SCVMM 2016
The following are the prerequisites for SCVMM 2016 support for Hyper-V Custom Object:
- SCVMM version should be SCVMM 2016.
- Host should be Windows Server 2016.
- Ensure that Windows templates and Linux templates are created. To create VM templates for provisioning Hyper-V VMs, see Creating Generation 1 Virtual Machine Templates on SCVMM and Creating Generation 2 Virtual Machine Templates on SCVMM .
- Create at least one VM network, to which the VMs can connect. BMC Server Automation supports VM Network of type noIsolation only.
Prerequisites for SCVMM 2019
The following are the prerequisites for SCVMM 2019 support for Hyper-V Custom Object:
- SCVMM version should be SCVMM 2019.
- Host should be Windows Server 2019.
- Ensure that Windows templates and Linux templates are created. To create VM templates for provisioning Hyper-V VMs, see Creating Generation 1 Virtual Machine Templates on SCVMM and Creating Generation 2 Virtual Machine Templates on SCVMM .
- Create at least one VM network, to which the VMs can connect. BMC Server Automation supports VM Network of type noIsolation only.
To install the Windows agent on the Microsoft VMM 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:
Comments
Log in or register to comment.