E.2.5 Pre-setup Preparations in Hyper-V Environments

Use the following procedure for pre-setup preparations for Hyper-V environments.
For details, refer to the MSFC help.

Installation of an Operating System and Configuration of a Domain Controller on the Domain Controller Server
Storage Preparations
Creation of the volume (LUN) for allocation to the MSFC of the managed server (quorum disk and cluster disk)
Configuration of Managed Servers
1. BIOS configuration (hardware virtualization and Data Execution Prevention (DEP))
2. Install an OS
  When installing an OS on a physical server, refer to the server virtualization software manual.
  When installing a VM host on an L-Server, refer to "Appendix A Installing VM Hosts on Physical L-Servers" in the "Setup Guide CE".
3. Join a domain
4. Add SNMP services
5. Configure SNMP services and SNMP traps
6. Add Hyper-V roles
7. Add a failover cluster function
Cluster Configuration of Managed Servers (MSFC)
1. Create an access point for cluster management on the admin LAN side.
2. In a quorum configuration, select one of the following:
  - When the number of nodes is even
    Select [Node and Disk Majority], and specify a quorum disk.
  - When the number of nodes is uneven
    Select [Node Majority].
3. Enable the shared volume of the cluster.
4. Add a cluster disk to a shared cluster volume.
Configuration After Creation of Clusters for Managed Servers
1. Enable remote WMI settings.
  1. In each VM host, access the Control Panel and open the [Administrative Tools]-[Computer Management].
    The [Computer Management] window is displayed.
  2. Open [Services and Applications], right-click on [WMI Control] and select [Properties].
    The [WMI Control Properties] dialog is displayed.
  3. Open the [Security] tab, select [Root]-[virtualization] and click [Security].
    The [Security for ROOT\virtualization] window is displayed.
  4. Select the login user for the VM host, and check [Allow] from [Remote Enable].
  5. When using Windows Server 2012 R2 or later, the following configuration is also needed.
    a. Open the [Security] tab, select [Root]-[virtualization]-[v2] and click [Security].
    The [Security for ROOT\virtualization\v2] window is displayed.
    b. Select the login user for the VM host, and check "Allow" from "Remote Enable".
    c. Click the [OK] button.
  6. Open the [Security] tab, select [Root]-[MSCluster] and click [Security].
    The [Security for ROOT\MSCluster] window is displayed.
  7. Check if all checkboxes are selected, excluding "Special Permissions" for the local Administrators group for the VM host. When these checkboxes are not selected, check the checkboxes.
    In the default settings, these checkboxes, other than, "Special Permissions" are all selected.
  8. Click the [OK] button.
  The remote WMI settings are enabled.
2. Configure the Windows firewall to enable remote WMI management.
  1. On each VM host, run the "GPedit.msc" command.
    The [Local Group Policy Editor] dialog is displayed.
  2. Select the following folder:
    [Computer Configuration]-[Administrative Templates]-[Network]-[Network Connections]-[Windows Firewall]
  3. 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.
  4. Right-click [Windows Firewall: Allow remote administration exception properties], and select [Properties].
    The [Windows Firewall: Allow remote administration exception properties] window is displayed.
  5. Select "Enabled".
  6. Click the [OK] button.
3. Configure DCOM.
  1. On each VM host, run the "Dcomcnfg.exe" command.
    The [Component Services] window is displayed.
  2. Right-click [Component Services]-[Computers]-[My Computer], and select [Properties].
    The [My Computer Properties] window is displayed.
  3. Select the [COM Security] tab.
  4. Click the [Edit Limits] button from [Launch and Activation Permissions].
    The [Launch and Activation Permission] window is displayed.
  5. Select the VM host's user name under [Groups or user names:], and select the [Allow] checkbox for [Remote Launch] and [Remote Activation].
  6. Click the [OK] button.
  7. Click the [Edit Limits] button under [Access Permissions].
    The [Access Permission] window is displayed.
  8. Select [ANONYMOUS LOGON] under [Group or user names], and check the [Allow] checkbox for [Remote Access].
  9. Click the [OK] button.
Configuration and Installation of SCVMM
Use the following procedure to install and configure SCVMM:
1. Install an OS
2. Join a domain
3. Install SCVMM
  Install a VMM server and a VMM management console.
4. Register a VM host
  Register by the cluster. An SCVMM agent is automatically installed on newly registered VM hosts.
5. Configure Windows remote management environment
  Configure remote administration on VM management software registered with Resource Orchestrator.
  1. Log in to the server on which VM management software operates, using administrative privileges.
  2. Execute the following command from the command prompt.
    >winrm quickconfig <RETURN>
  3. Enter "y", when requested.
6. SCVMM Server Web Services for Management Settings
Configure the Resource Orchestrator Admin Server
Configure remote management authentication settings on the machine the Resource Orchestrator admin server will be set up.
1. Log on to the admin server as the administrator.
2. Execute the following command from the command prompt to record the configuration details for TrustedHosts.
  >winrm get winrm/config/client <RETURN>
  Record the displayed details in TrustedHosts.
  Example
  When multiple SCVMMs are registered
  192.168.1.100, 192.168.1.101
  When a single asterisk ("*") is displayed, the following procedure is unnecessary as all hosts will be trusted in the configuration.
3. Execute the following command.
  Enter the result obtained from b. for Recorded_content_in_b.
  >winrm set winrm/config/client @{TrustedHosts="Recorded_content_in_b. , Additionally_ registered_SCVMM_address"} <RETURN>
  Example
  The command specification when multiple SCVMMs are registered
  >winrm set winrm/config/client @{TrustedHosts="192.168.1.100, 192.168.1.101, Additionally registered SCVMM address"} <RETURN>
4. Execute the following command to check the details for TrustedHosts.
  >winrm get winrm/config/client <RETURN>
  If the address of the SCVMM additionally registered has been added to the details recorded in b., there are no problems.
Note
- When registering multiple SCVMMs in Resource Orchestrator as VM management software, specify the IP addresses for multiple VM management software separated by commas (",") using the command for registering TrustedHosts.
- When communication from the admin server uses Windows remote management (WinRM) and is performed via a proxy server, operations such as registration of resources with Resource Orchestrator will fail.
  Therefore, perform configuration of Windows remote management (WinRM) on the admin server so that a proxy server is not used.
Apply the Latest Update Program
For the server on which the manager will be installed, managed VM hosts, SCVMM, and SCVMM agents, apply the latest updates using Microsoft Update, etc.

SCVMM Server Web Services for Management Settings

Resource Orchestrator controls SCVMM using PowerShell Web Services for Management (hereinafter WS-Management).

Change the following settings concerned with WS-Management on the SCVMM server.

MaxShellsPerUser
MaxMemoryPerShellMB
MaxConcurrentUsers
MaxConnections

Change the values of MaxShellsPerUser (the maximum number of processes that can start shell operations for each user) and MaxConcurrentUsers (the maximum number of users who can execute a remote operation from a remote shell at the same time). For Resource Orchestrator, change settings to enable a maximum of 31 sessions.
However, since WS-Management is used for Windows administration tools and Resource Orchestrator, set a value 31 or larger for each value.

Change the MaxShellsPerUser and MaxConcurrentUsers settings using the following procedure:

Execute Windows PowerShell as an administrator.
Change the current directory using the Set-Location commandlet.
PS> Set-Location -Path WSMan:\localhost\Shell <RETURN>

Check the current MaxShellsPerUser and MaxConcurrentUsers settings using the Get-ChildItem commandlet.

The contents displayed in MaxShellsPerUser and MaxConcurrentUsers are the current settings.

PS WSMan:\localhost\Shell> Get-ChildItem <RETURN>

Example

PS WSMan:\localhost\Shell> Get-ChildItem
 WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Shell

Name                      Value           Type
----                      -----           ----
AllowRemoteShellAccess    true            System.String
IdleTimeout               180000          System.String
MaxConcurrentUsers        5               System.String
MaxShellRunTime           2147483647      System.String
MaxProcessesPerShell      15              System.String
MaxMemoryPerShellMB       150             System.String
MaxShellsPerUser          5               System.String

Configure MaxShellsPerUser and MaxConcurrentUsers using the Set-Item commandlet.
Example
When setting MaxShellsPerUser and MaxConcurrentUsers as "36"
PS WSMan:\localhost\Shell> Set-Item .\MaxShellsPerUser 36 <RETURN>
PS WSMan:\localhost\Shell> Set-Item .\MaxConcurrentUsers 36 <RETURN>

Next, change the MaxMemoryPerShellMB setting.
For Resource Orchestrator, change the setting to over 1024 MB.

Change the MaxMemoryPerShellMB setting using the following procedure:

Check the current MaxMemoryPerShellMB setting using the Get-ChildItem commandlet.
The content displayed in MaxMemoryPerShellMB is the current setting.
PS WSMan:\localhost\Shell> Get-ChildItem <RETURN>
Configure MaxShellsPerUser using the Set-Item commandlet.
Example
When setting MaxMemoryPerShellMB as "1024"
PS WSMan:\localhost\Shell> Set-Item .\MaxMemoryPerShellMB 1024 <RETURN>

Finally, change the MaxConnections setting. In Resource Orchestrator, the maximum number of sessions is 31, so change the setting.
Since WS-Management is used for Windows administration tools and Resource Orchestrator, set a value of 32 or larger.

Change the MaxConnections setting using the following procedure:

Change the current directory using the Set-Location commandlet.
PS> Set-Location -Path WSMan:\localhost\Service <RETURN>
Check the current MaxConnections setting using the Get-ChildItem commandlet.
The content displayed in MaxConnections is the current setting.
PS WSMan:\localhost\Service> Get-ChildItem <RETURN>
Configure MaxConnections using the Set-Item commandlet.
Example
When setting MaxConnections as "46"
PS WSMan:\localhost\Service> Set-Item .\MaxConnections 46 <RETURN>