System Center Integration Pack for System Center Virtual Machine Manager 2008 R2
Applies To: System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator, System Center 2012 SP1 - Orchestrator
The System Center Integration Pack for System Center Virtual Machine Manager 2008 R2 is an add-in for System Center 2012 - Orchestrator that enables you to automate the following activities:
Manage the self-service virtual machine library
Create virtual machine resources such as disks, virtual hard disks (VHDs), and network adapters, as needed
Create virtual machines from templates, VHDs, and from other virtual machines (modifying disk and network resources if needed)
Modify existing virtual machines
Turn on and shut down virtual machines in batch mode
Restart virtual machines
Move virtual machines to a new host to manage availability and performance
Create and restore virtual machine checkpoints
The VMM Integration Pack requires the following software to be installed and configured before you deploy the integration. For more information about how to install and configure the Orchestrator and the System Center Virtual Machine Manager application, see the respective product documentation.
System Center 2012 - Orchestrator
System Center Virtual Machine Manager 2008 R2
Windows Management Framework (Windows PowerShell 2.0 and WinRM 2.0)
The activities from the VMM Integration Pack connect to a Virtual Machine Manager Administration Console which in turn connects to a Virtual Machine Manager server. You can install this console on the Orchestrator runbook server or connect to the Administration console on another computer. If the Orchestrator components and the Virtual Machine Manager Administration Console are installed on the same 64-bit computer, the Virtual Machine Manager server must be in the same domain to be able to connect to it.
Downloading the Integration Pack
For information about how to obtain this integration pack, see System Center 2012 – Orchestrator 2012 Component Add-ons and Extensions (https://go.microsoft.com/fwlink/?LinkID=228718).
Registering and Deploying the Integration Pack
After you download the integration pack file, you must register it with the Orchestrator Management Server and then deploy it to one or more runbook servers or clients.
To register and deploy the integration pack
Copy the Virtual_Machine_Manager_2008_R2_Integration_Pack.oip integration pack file to the location of your choice on the runbook server that the Orchestrator is running.
Click Start, then All Programs, then Microsoft System Center 2012, and then click Orchestrator. Right-click Deployment Manager, and then click Run as Administrator.
In the left pane of the Deployment Manager, expand Management Server. Right-click Integration Packs, and then select Register IP with the Management Server. The Integration Pack Registration Wizard opens. Click Next.
In the Integration Pack or Hotfix Selection window, click Add. Locate and select the Virtual_Machine_Manager_2008_R2_Integration Pack.oip file that you copied in step 1. Click Open.
In the Completing the Integration Pack Wizard dialog box, click Finish. The End User Agreement dialog box appears. Click Accept. The Log Entries pane displays a confirmation message when the integration pack is successfully registered.
In the left pane of Deployment Manager, right-click Integration Packs, and then select Deploy IP to Action Server or Client. Click Virtual Machine Manager 2008R2 Integration Pack, and then click Next.
Enter the name of a runbook server or a computer with Runbook Designer installed, on which you want to deploy the integration pack, click Add, and then click Next.
In the Installation Options dialog box, select the options that apply to this deployment, and then click Next.
To choose a time to deploy the integration pack, select Schedule installation check box, and then select the time and date from the Perform installation list box.
Select one of the following:
Stop all running runbooks before installing the integration pack to stop all running runbooks before deploying the integration pack.
Install the Integration Packs without stopping the running Runbooks to install the integration pack without stopping any running runbooks.
In the Completing Integration Pack Deployment Wizard dialog box, click Finish.
When the integration pack is deployed, the Log Entries dialog displays a confirmation message.
If you did not configure a deployment schedule, the integration pack deploys immediately to the computers that you specified. If you configured a deployment schedule, verify that the deployment occurred by verifying the event logs after the scheduled time has passed.
Configuring Windows Management Framework
The VMM Integration Pack uses Windows PowerShell Remoting to be configured between the Orchestrator runbook server and the computer running the Virtual Machine Manager Administration Console. Windows PowerShell Remoting relies on Windows Remote Management (WinRM) to establish the communications between the two systems. You must perform the following tasks before you configure the Virtual Machine Manager connection in the Runbook Designer.
The Runbook Designer will also connect to the computer running the VMM Administration Console when you are configuring activities from the VMM Integration Pack. If the Runbook Designer is installed on a different computer than the runbook server, then you will also need to configure Windows PowerShell and WinRM on that computer.
Confirm Windows PowerShell 2.0 Installation
PowerShell 2.0 must be installed on both the Orchestrator runbook server and the computer running the VMM Administration Console.
To confirm Windows PowerShell 2.0 installation
Open Registry Editor.
Expand the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine subkey.
Confirm that the value of the Runtime Version entry begins with v2.0.
If this value begins with 1.0, or the subkey is not present, see Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0) for information on installing Windows PowerShell 2.0.
Confirm Windows Remote Management Installation
Windows Remote Management 2.0 (WinRM 2.0) must be installed and configured on the on both the Orchestrator runbook server and the computer running the VMM Administration Console. You can do this using the Local Group Policy Editor.
To confirm Windows Remote Management installation
Click Start and then Run, type gpedit.msc, and then click OK.
Under Local Computer Policy, then expand Computer Configuration, then expand Administrative Templates, and then expand Windows Components
Verify that Windows Remote Management (WinRM) is listed.
For more information abouthow to install and configure WinRM 2.0, see Installation and Configuration for Windows Remote Management.
Windows Remote Management Trusted Hosts
WinRM requires that you explicitly specify the name of any host computers that you are going to connect to. This enhances security by ensuring that the Orchestrator runbook server is connecting to the expected computer running the VMM Administration Console.
To enable Windows Remote Management Trusted Hosts
On the Orchestrator runbook server, open the Local Group Policy Editor. To do this click Start, click Run, type gpedit.msc, and then click OK.
Under Local Computer Policy, then expand Computer Configuration, then expand Administrative Templates, then expand Windows Components, then expand Windows Remote Management, and then select WinRM Client.
Double-click Trusted Hosts.
In the Trusted Hosts dialog box, select Enabled.
Add the name or IP address of the computer running the VMM Administration Console to the TrustedHostsList . Click OK.
PowerShell Execution Policy
The execution policy in Windows PowerShell determines which scripts must be digitally signed before they will run. By default, the execution policy is set to Restricted which prohibits loading any configuration files or running any scripts. To run the scripts in this integration pack, you must set the execution policy to RemoteSigned on both the Orchestrator runbook server and the computer running the VMM Administration Console.
To set the execution policy in Windows PowerShell
Click Start, then All Programs, then Accessories, and then Windows PowerShell.
Right-click Windows PowerShell and select Run As Administrator. Click Yes when prompted by User Account Control.
Type the following command and press Enter:
For more information abouthow to configure the Windows PowerShell execution policy, see Set-ExecutionPolicy in the Microsoft TechNet Library.
Windows PowerShell Remote Connection Quota
You can use WS-Management quotas in Windows PowerShell remoting to protect the Orchestrator runbook server and the computer running the VMM Administration Console from excessive resource use, both accidental and malicious. The MaxConcurrentOperationsPerUser quota setting in the WSMan:\<ComputerName>\Service node provides this protection by imposing a limit on the number of VMM objects that can run concurrently.
By default, MaxConcurrentOperationsPerUser is set to 5. This means that a maximum of five VMM objects can run concurrently across all VMM activities. If this default setting does not meet the needs of your organization, see About_Remote_Troubleshooting in the Microsoft TechNet Library for information about how to configure remote operations in Windows PowerShell.
The MaxConcurrentOperationsPerUser affects all Windows PowerShell objects whether or not they are from a runbook. If there are remote sessions from other applications, they will be included in this limit.
Configuring the System Center Virtual Machine Manager Connections
Once you have validated the WinRM configuration, you must add a Configuration that defines communications between the Orchestrator runbook server and a computer running the VMM Administration Console. This configuration will include the credentials required to access VMM and the authentication protocol that should be used. When you configure actions from the VMM Integration Pack, you select a configuration that defines the connection that the activity should use. You can create multiple configurations if you have multiple VMM computers to connect to.
To configure the System Center Virtual Machine Manager integration
In the Runbook Designer, click the Options menu, and then select Virtual Machine Manager 2008R2. The Virtual Machine Manager 2008R2 dialog box appears.
On the Configurations tab, click Add to begin the connection setup.
In the Name box, type a descriptive name for the connection. This could be the name of the VMM computer for example.
In the Type box, click the ellipsis button (...), select System Center Virtual Machine Manager, and then click OK.
In the Properties box, enter a value for each property according to the table below.
Add any additional configurations as required.
Virtual Machine Manager Properties
The name or IP address of the computer running the VMM Administration Console.
The name of a user with access to VMM. This user account must have permissions to the VMM Administration Console and to the VMM server to perform the actions requested by the activities.
If you leave this property empty, the configuration will use the credentials from the Runbook Service Account. If this account has appropriate permissions to VMM, then you do not need to provide credentials for the configuration.
The domain that the user account resides in.
The password for the specified user account.
Authentication Type (Remote only)
The type of authentication to use. This is only required if the runbook server and VMM Administration Console are installed on different computers.
The authentication method that you choose must be enabled in WinRM. You can enable the authentication methods using the Local Group Policy Editor. For more information see Installation and Configuration for Windows Remote Management.
Port (Remote only)
The port used for PowerShell remoting between the Orchestrator runbook server and the computer with the VMM Administration Console. This is only required if the runbook server and VMM Administration Console are installed on different computers.
Use SSL (Remote only)
Specifies whether SSL should be used for the connection. This is only required if the runbook server and VMM Administration Console are installed on different computers.
Cache Session Timeout (min.)
The number of minutes before the session will timeout from lack of activity and need to reconnect.
The name of the VMM server that action will be performed on. Use localhost to if the VMM Administration Console is installed on the VMM server.