Integration Pack for System Center Virtual Machine Manager
Applies To: Opalis 6.3
The Integration Pack for System Center Virtual Machine Manager (VMM) is an add-in for Opalis Integration Server 6.3 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 (VHD)s, 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
This integration pack lets you create workflows that interact with and transfer information to the other Opalis integrations for System Center Service Manager, System Center Data Protection Manager, System Center Operations Manager, and System Center Configuration Manager.
Opalis, a Microsoft Subsidiary, is committed to protecting your privacy, while delivering software that brings you the performance, power, and convenience you want. For more information, see the Opalis 6.3 Privacy Statement (http://go.microsoft.com/fwlink/?LinkID=202690).
The Integration Pack for System Center Virtual Machine Manager requires the following software to be installed and configured before you deploy the integration. For more information abouthow to install and configure the Opalis Integration Server and the System Center Virtual Machine Manager application, see the respective product documentation.
Opalis Integration Server 6.3 (and later versions)
System Center Virtual Machine Manager 2008 R2
Windows Management Framework (Windows PowerShell 2.0 and WinRM 2.0)
If the Opalis Integration Server 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
Registering and Deploying the Integration Pack
After you download the integration pack file, you must register it with the Opalis Management Server and then deploy it to one or more action servers or clients.
To register and deploy the integration pack
Copy the IP_SystemCenterVirtualMachineManager_1.0.oip integration pack file to the Opalis Integration Server computer.
Click Start, point to Programs, point to Opalis Software, and then click Opalis Integration Server. 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.
In the Integration Pack or Hotfix Selection window, click Add. Locate and select the IP_SystemCenterVirtualMachineManager_1.0.oip file that you copied in step 1. Click Next.
Click Finish. The Log Entries pane displays a confirmation message when the integration pack is successfully registered.
In the left pane, right-click Integration Packs, and then select Deploy IP to Action Server or Client. Click Opalis Integration Pack for Microsoft System Center VMM, and then click Next.
Select the action server or client Computer on which you want to deploy the integration pack, click Add, and then click Next.
Select the Installation Configuration options that apply to this deployment, and then click Next.
Click Finish. The Log Entries pane displays a confirmation message when the integration pack is successfully deployed.
For more information abouthow to install integration packs, see the "Deploying Hotfixes and Integration Packs" section of the Opalis Integration Server Administrator Guide (http://go.microsoft.com/fwlink/?LinkId=205302).For more information abouthow to install integration packs, see the "Deploying Hotfixes and Integration Packs" section of the Opalis Integration Server Administrator Guide.
Windows Management Framework
The Integration Pack for System Center Virtual Machine Manager uses Windows PowerShell Remoting on the Opalis client and Integration Server, and on the Virtual Machine Manager server. Perform the following tasks on the Opalis Client and Integration Server and on the Virtual Machine Manager server before you configure the Virtual Machine Manager connection in the Opalis client.
To confirm the Windows Management Framework prerequisites
Confirm that you have Windows PowerShell 2.0 installed on the Opalis Client and Integration Server, and on the Virtual Machine Manager server. One way to do this is to 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, install Windows PowerShell 2.0 using the instructions in article 96829 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?linkID=193574).
Confirm that you have Windows Remote Management 2.0 (WinRM 2.0) installed and configured on the Opalis Client and Integration Server, and on the Virtual Machine Manager server. One way to confirm your configuration is in the Local Group Policy Editor.
For more information abouthow to install and configure WinRM 2.0, see Installation and Configuration for Windows Remote Management (http://go.microsoft.com/fwlink/?linkID=171111).
To enable Windows Remote Management Trusted Hosts
On the Opalis Client and Integration Server, open the Local Group Policy Editor. To do this click Start, click Run, type gpedit.msc, and then click OK.
In the Local Group Policy Editor, under Local Computer Policy, expand Administrative Templates, expand Windows Components, expand Windows Remote Management, expand WinRM Client, and then double-click Trusted Hosts.
On the Setting tab, click Enabled. Add the name or IP address of the Virtual Machine Manager Server to the Trusted Hosts list. Click OK.
To set the execution policy in Windows PowerShell
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. This 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. Use the following command: <System Drive>:\PS>set-executionpolicy remotesigned. For more information abouthow to configure the Windows PowerShell execution policy, see Set-ExecutionPolicy in the Microsoft TechNet Library (http://go.microsoft.com/fwlink/?linkID=113394).
To confirm the remote connection quota setting in Windows PowerShell
You can use WS-Management quotas in Windows PowerShell remoting to protect the Opalis and VMM computers 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 you can run a maximum of five VMM objects (shells) concurrently across all VMM policies.
If this default setting does not meet the needs of your organization, see About_Remote_Troubleshooting in the Microsoft TechNet Library (http://go.microsoft.com/fwlink/?linkID=135188) for information about how to configure remote operations in Windows PowerShell.
Configuring the System Center Virtual Machine Manager Connections
To set up communications between the Opalis Integration Server and the Virtual Machine Manager computer, perform the following procedure.
To configure the System Center Virtual Machine Manager integration
In the Opalis Integration Server Client, click the Options menu, and then select System Center Virtual Machine Manager. The System Center Virtual Machine Manager dialog box appears.
On the Configurations tab, click Add to begin the connection setup.
In the Name box, type the name or IP address of the computer on which Virtual Machine Manager is running.
In the Type box, click the ellipsis button (...), select Microsoft SCVMM Connection, and then click OK.
In the Properties box, enter values for each of the properties as they apply to your organization. Ensure the values that you enter for the remote connection and authentication properties are compatible with the WinRM settings that you entered or confirmed in the previous procedure.