In addition to the operations in "Chapter 8 Defining and Configuring the Server Environment", the following operations are necessary.
Register vCenter Server
Register the vCenter Server that manages VM hosts for VDI on the admin server of VMware Horizon View.
Note
In order to have VDI management software operate properly using Resource Orchestrator, ensure vCenter Server is registered using the IP address instead of the host name.
Install vSphere PowerCLI
Install VMware vSphere PowerCLI 6.0 on the management server of VMware Horizon View.
Place VMware Scripts
The infrastructure administrator places VMware scripts on the VDI management server using the following procedure.
VMware scripts are stored in the following folder of the Resource Orchestrator manager:
[Windows Manager]
Installation_folder\SVROR\Manager\opt\FJSVrcxmr\sys\VMwareViewScript
AddRemovePoolVms.ps1
MachineId.ps1
Copy the scripts placed in step a into the following folder of the VDI management server:
VMware Horizon View installation folder\extras\PowerShell\
Configure winrm
Configure Windows remote management for the VDI management server.
Log in to the VDI management server using administrator privileges and execute the following command from the command prompt: Enter "y" when prompted for confirmation.
> winrm quickconfig <RETURN> |
Configure TrustedHosts
Configure remote management authentication settings on the machine the Resource Orchestrator admin server will be set up.
Log on to the admin server as the administrator.
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
Display results when multiple VDI Management Servers 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.
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 VDI management server address"} <RETURN> |
Example
The command when multiple VDI Management Servers are registered
>winrm set winrm/config/client @{TrustedHosts="192.168.1.100, 192.168.1.101, Additionally registered VDI management server address"} <RETURN> |
Execute the following command to check the details for TrustedHosts.
>winrm get winrm/config/client <RETURN> |
If the address of the additionally registered VDI management server has been added to the details recorded in b., there are no problems.
Note
For coordination with multiple VDI management servers, specify the IP addresses of those VDI management servers separated by commas (",") when executing the TrustedHosts registration command.
Modify the PowerShell Execution Policy
On the machine where the Resource Orchestrator admin server is setup and on the VDI management server, modify the PowerShell execution policy to "RemoteSigned".
Start the PowerShell console using administrator privileges and execute the following command:
>Set-ExecutionPolicy -ExecutionPolicy RemoteSigned <RETURN> |
Note
When the VDI management server is not connected to the internet, it takes longer to load the View PowerCLI snap-in used for VDI coordination, which may inhibit creation and deletion of L-Servers.
For this reason, be sure to connect the VDI management server to the Internet.
When it is not possible to connect to the Internet, configure Internet Explorer using the following procedure:
Log in to the VDI management server as the administrator of the VDI management server explained in "K.1.1 VDI Coordination Function".
Start Internet Explorer, and uncheck the following check box:
[Internet Options] - [Advanced] tab - [Check for publisher's certificate revocation]
