This section describes the settings required to properly configure each different virtualization product for use with Resource Coordinator VE.
Configuration Requirements for Each Server Virtualization Product
The required configuration differs with each server virtualization product. For details on the configuration of each virtualization product refer to the manual of each product.
[VMware]
Installation of VMware Tools is required to properly display the hostnames of guest OS's and enable their remote shutdown via the power control functions of Resource Coordinator VE. Install VMware Tools after installing an operating system in a VM guest.
[Hyper-V]
Use the following procedure to enable remote management in Hyper-V.
Enable remote control in WMI settings.
In each VM host, access the Control Panel and open the [Administrative Tools]-[Computer Management].
The [Computer Management] dialog is displayed.
From the [Computer Management] dialog, open [Services and Applications], right-click on [WMI Control] and select [Properties].
The [WMI Control Properties] dialog is displayed.
In the [WMI Control Properties] dialog, open the [Security] tab, select [Root]-[virtualization] and click on the <Security> button.
The [Security for ROOT\virtualization] dialog is displayed.
In the [Security for ROOT\virtualization] dialog, select the VM host's user name, select the "Allow" checkbox for "Remote Enable" and click the <OK> button.
Configure the Windows Firewall to enable remote WMI management.
In each VM host, run the "GPedit.msc" command.
The [Local Group Policy Editor] dialog is displayed.
In the [Local Group Policy Editor] dialog, open the following folder.
[Computer Configuration]-[Administrative Templates]-[Network]-[Network Connections]-[Windows Firewall]
If the VM host is a member of a domain, double-click [Domain Profile]; otherwise double-click [Standard Profile].
Either one of the [Domain Profile] or [Standard Profile] screen is displayed.
In the displayed screen, right-click "Windows Firewall: Allow inbound remote administration exception" and select [Properties].
The [Windows Firewall: Allow inbound remote administration exception] dialog is displayed.
Select "Enabled" and click the <OK> button.
Configure DCOM
In each VM host, run the "Dcomcnfg.exe" command.
The [Component Services] dialog is displayed.
In the [Component Services] dialog, expand [Component Services]-[Computers], right-click [My Computer] and select [Properties].
The [My Computer Properties] dialog is displayed.
In the [My Computer Properties] dialog, open the [COM Security] tab.
Click the <Edit Limits> button under "Launch and Activation Permissions".
The [Launch and Activation Permission] dialog is displayed.
In the [Launch and Activation Permission] dialog, select the VM host's user name under "Groups or user names:", and select the "Allow" checkbox for "Remote Activation" and click the <OK> button.
Click the <Edit Limits> button under "Access Permissions".
The [Access Permission] dialog is displayed.
In the [Access Permission] dialog, select "ANONYMOUS LOGON" under "Groups or user names:", select the "Allow" checkbox for "Remote Access" and click the <OK> button.
Note
[Hyper-V]
If a VM host belongs to a domain, make sure that its hostname can be properly resolved by the Admin Server (from the VM host IP address).
If host name resolution fails, perform the necessary DNS (or hosts file) settings to enable host name resolution.
Configuration Requirements for VM Guest Switchovers
Depending on the virtualization product being used, the following settings should be made to enable switchover of a newly created VM guest.
[VMware]
The VM guest's UUID must be changed.
Perform the following settings before switchover of a VM guest.
From the VM management client, add the following parameter to the guest's virtual machine configuration.
Name Value uuid.action keep |
Refer to the help section of the VM management client for details on how to add parameters to a virtual machine configuration.
Without this setting, a confirmation dialog is show each time a virtual machine is started after being moved to a different VM host. Enabling this setting will prevent such confirmation dialogs from being shown, and the virtual machine will be set to always keep its UUID when moved between different servers.
[Hyper-V]
No re-configuration is required.
Integration with VM Management Consoles
The following setup is required to enable launch of VM management consoles from the RC console.
[VMware]
The VMware Infrastructure Client or the VMware vSphere Client should be installed on the Resource Coordinator VE Admin Client.
[Hyper-V]
Hyper-V Manager should be installed on the Resource Coordinator VE Admin Client.