This section explains the configuration for using VMware Horizon View as a VDI management server.
Installation
This section explains installation when using VMware Horizon View.
Collect a cloning image for VDI coordination
When using VDI coordination, cloning images with Horizon View Agent installed are used.
To collect a cloning image with Horizon View Agent installed using Resource Orchestrator, perform the following procedure:
Create a virtual L-Server.
For details on how to create a virtual L-Server, refer to "8.2.7 Creating L-Servers".
Install Horizon View Agent on the virtual L-Server created in step a.
For details on how to install Horizon View Agent, refer to the VMware manual.
Collect a cloning image from the virtual L-Server created in step a.
For details on how to collect cloning images, refer to "8.2.8 Collecting Cloning Images".
It is also possible to install Horizontal View Agent on a virtual machine directly using VMware, and then collect the cloning image to use.
For details on how to do this, refer to "14.7.1 Virtual Image Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register VDI Management Software
Register a VDI management server with Resource Orchestrator as VDI management software.
For details on how to register the VDI management software, refer to "5.15 Registering VDI Management Software" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Creating Definition Files
Group authorization definition files assigned to VDI pools
Use this when using a domain group as authorization for a VDI Pool.
Define the relationship of the VDI management server, VDI Pool, and the domain group.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
vdipool_group_entitlement.rcxprop
Describe each line of the definition file in the following format:
VDI management server name:VDI pool name:domain group name 1[:domain group name 2:...] |
It is not necessary to restart the ROR manager after creating the definition files.
When the descriptions start with "#", the string is regarded as a comment line.
On each line, define the relationship of the VDI management server, VDI Pool, and the domain group, separating each using colons (":").
When multiple VDI pools exists on a VDI management server, use one line for each VDI pool.
When allocating multiple domain groups in a VDI pool, separate them using colons (":").
For the VDI management server name, specify the name of the management software specified during registration of the VDI management software.
When two or more lines contain a combination of the same VDI management server name and the same VDI pool name, the definition of the last line is valid.
Item | Description |
|---|---|
VDI management server name | Specify the name of the VDI management server. Specify a character string beginning with an alphabetical character and containing up to 15 alphanumeric characters and hyphens ("-"). |
VDI pool name | Specify the VDI pool name. Specify up to 64 characters, including alphanumeric characters, underscores ("_"), and hyphens ("-"). |
Domain group name | Specify the domain group name. For the characters that can be specified, refer to the Microsoft web site. (*) |
*: For the characters that can be specified for the domain group name, refer to "NetBIOS domain names" on the Microsoft web site.
Microsoft download web site
URL: http://support.microsoft.com/kb/909264/en-us |
# VDI Management Server Name:VDI Pool Name:Domain Group Name |
UTF-8
[Windows Manager]
CR/LF
Note
Domain group authorization is given to the VDI pool based on the group authorization definition file.
Therefore, when using the group qualification definition file, ensure that there are no errors in the specified VDI management server name, VDI pool name, and domain group name.
Server Virtualization Software Definition File
Operations related to server virtualization software can be changed by configuring values in the following definition files beforehand.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
vm.rcxprop
Describe each line of the definition file in the following format:
Key = Value |
Item | Key | Value | Remarks |
|---|---|---|---|
Guest OS customization waiting time | vmwareview_customize_wait | Integer between 1 and 1440 The unit is minutes. | Specify the time to wait for completion of guest OS customization when operating in coordination with VDI using Horizon View. This setting is valid when using VMware as the server virtualization software and Horizon View as the VDI management software. If left blank, "30 (minutes)" is set. Restarting of the server is not required after changing this configuration. When an invalid value such as an out-of-range value or non-numerical value is specified, "30 (minutes)" is set. When the waiting time is short, guest OS customization may be still in progress when L-Server deployment is completed. When changing the value, first confirm how long guest OS customization takes. |
UTF-8
[Windows Manager]
CR/LF
OS Property Definition File
In VDI coordination, participation in the Active Directory domain of a guest OS is necessary.
Specify the following items in OS property definition files.
The domain name of the Active Directory to participate in
The domain account to be used for domain participation authentication
The domain password to be used for domain participation authentication
For details, refer to "8.1.7 OS Property Definition File".
Creating roles to prevent power operations of L-Servers
This section explains how to create roles to prevent power operations of L-Servers.
Create customized roles that prevent power operations from the ROR console for tenant administrators and tenant users who will use VDI.
Use the following procedure to create roles. Refer to "Chapter 12 Role Customization Commands" in the "Reference Guide (Command/XML) CE" for details on customizing roles.
Create the roles for VDI usage based on the standard tenant administrator and tenant user roles.
rcxadm role create -name vdi_tenant_user -base tenant_user rcxadm role create -name vdi_tenant_admin -base tenant_admin
Output the detailed role information created in step a. to an XML file.
rcxadm role show -name vdi_tenant_user -format xml -outfile temp_vdi_user_role.xml rcxadm role show -name vdi_tenant_admin -format xml -outfile temp_vdi_admin_role.xml
Open the XML file from step b. using an editor, etc. and delete operation authority for starting and stopping L-Servers from the settings of the existing role. Update the XML files of both tenant administrator and tenant users.
The following example is an XML file for tenant administrators. Delete the underlined section.
<?xml version="1.0" encoding="utf-8"?>
<Role name="vdi_tenant_admin" id="ct03-m_4066" label="">
<Comment></Comment>
<BaseRole>tenant_admin</BaseRole>
<OperationGroups>
<OperationGroup name="LPlatform">
<Authorities>
<Authority>create</Authority>
<Authority>modify</Authority>
<Authority>delete</Authority>
<Authority>ruleset</Authority>
<Authority>showlog</Authority>
</Authorities>
</OperationGroup>
<OperationGroup name="LServer">
<Authorities>
<Authority>create</Authority>
<Authority>modify</Authority>
<Authority>delete</Authority>
<Authority>resource_operation</Authority>
<Authority>start</Authority>
<Authority>stop</Authority>
<Authority>image_collect</Authority>
<Authority>backup</Authority>
<Authority>restore</Authority>
<Authority>delete_backup</Authority>
</Authorities>
</OperationGroup>
<OperationGroup name="Console">
<Authorities>
<Authority>home</Authority>
<Authority>dashboard</Authority>
<Authority>template</Authority>
<Authority>lplatform</Authority>
<Authority>account</Authority>
</Authorities>
</OperationGroup>
</OperationGroups>
</Role>Change the role settings of tenant administrators and tenant users who will use VDI, based on the XML file modified in step c.
rcxadm role modify -name vdi_tenant_user -file temp_vdi_user_role.xml rcxadm role modify -name vdi_tenant_admin -file temp_vdi_admin_role.xml
When changing or registering user information of tenant administrators and tenant users who will use VDI, use the roles created in this section.
Refer to "11.7 Registering a User" and "11.8 Modifying a User" in the "User's Guide for Infrastructure Administrators CE" for details of the operation method.
The steps from a. to d. can also be performed from the ROR console. When performing the operation from the ROR console, refer to "3.6 Creating a Role" in the "User's Guide for Infrastructure Administrators (Resource Management) CE", and perform the operation to create the same role as in steps a. to d.
Settings for L-Platform management
This section explains the settings of definition files to enable VDI coordination when deploying L-Platforms and L-Platform templates.
When enabling VDI coordination
Refer to "8.5.14.1 Enabling VDI" in the "Operation Guide CE".
When enabling specification of a user name for VDI connection during application for L-Platform usage
Refer to "8.5.14.2 Settings for VDI User Names" in the "Operation Guide CE".
Create L-Server Templates
This section explains how to create an L-Server template to be specified when creating an L-Platform template.
Create an L-Server template with the settings for participation in the Active Directory domain.
For details on how to set participation in the Active Directory domain, refer to "8.2.12 Participating in an Active Directory Domain".
For information on how to create L-Server templates, refer to "Chapter 15 L-Server Template Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Create an L-Platform Template
This chapter explains how to create an L-Platform template.
Use the following procedure to create an L-Platform template.
Open the [Templates] tab from the ROR console and display the [L-Platform template] window.
Select the [Image] tab and click [Create new].
On the [Select Image] page, select the cloning image imported in step 1 and click [Next].
Set basic information of images on the [General] page.
Check "Use for desktop virtualization" and click [Next].
Set the information of software and patches on [Patch information] and [Select Software], then click [Next].
Ensure there are no mistakes in the contents displayed on the [Configuration] page, and click [Next].
Select the [Template] tab and click [Create new].
Set basic information on the [General] page and click [Next].
Drag segment the virtual server will be deployed to from [Additional Options] on the [Changing Configuration] page, and drop it on the configuration part of the L-Platform template. Specify the segment information in the details of configuration elements.
Drag the image information created in steps b. to f. from [Additional Options], and drop it on the segment added in step i. Set server information in the details of configuration elements. Specify the pool name for VDI.
Ensure there are no mistakes in the contents displayed on the [Configuration] page, and click [Next].
Select the created template in the [Template List] window and click [Release].
Refer to "8.3.1 Creating New L-Platform Template", "8.4.2 Image Information" and "8.4.4 Template Information" in the "User's Guide for Infrastructure Administrators CE" for details of the operation method.
Subscription
Use the following procedure to subscribe to an L-Platform.
Select the [L-Platforms] tab from the ROR Console.
Select [Subscribe to L-Platform] from the operation menu on the [L-Platforms] tab.
Click [Create New L-Platform] on the [Subscription] page.
On the [Select Template] page, select the L-Platform template created in "6. Create an L-Platform Template" of "Installation", and click [Next].
Specify the L-Platform name on the [General] page and click [Next]
Modify the configuration of the L-Platform template on the [Change Configuration] page if necessary.
Change the VDI user if the login user name of the ROR Console is different from the VDI user name (VDI connection user name).
When the change is complete, click [Next].
Ensure there are no mistakes in the contents displayed on the [Configuration] page, and click [Next].
Confirm the license agreement displayed on the [License Agreement] page, check [Agree to the license], and then click [Create].
As the L-Platform subscription application has been received, the [Complete] window will be displayed.
Click [Close] and return to the [Subscription] page.
Refer to "5.2 Subscribe to an L-Platform" in the "User's Guide for Tenant Users CE" or "8.2 Subscribe to an L-Platform" in the "User's Guide for Tenant Administrators CE" for details of the operation method.
Point
To display the [Changing Configuration] window, the setting to permit changing of L-Platform settings must be enabled. Refer to "8.5.1 Settings for Permissions to Change L-Platform Templates" in the "Operation Guide CE" for details.
Permissions of VDI user name settings must be granted to enable specifying of the VDI connected user name. Refer to "8.5.14.2 Settings for VDI User Names" in the "Operation Guide CE" for details.
Cancellation
Use the following procedure to cancel L-Platforms.
Select the [L-Platforms] tab from ROR Console.
Select [Management] from the operation menu on the [L-Platforms] tab.
Select the L-Platform to be canceled on the [Management] and click [Details].
If the servers to be deleted are running, click [OFF] to turn off the power.
Click [Cancel] on the [L-Platform Details] window.
Ensure there are no mistakes in the [Confirming L-Platform] window and click [Next].
Check the [Cancel] checkbox on the [Terms of Cancellation] window and click [Cancel].
The [Complete] window will be displayed when cancellation of the L-Platform has been completed.
Refer to "5.3.17 Cancel an L-Platform" in the "User's Guide for Tenant Users CE" or "8.3.19 Cancel an L-Platform" in the "User's Guide for Tenant Administrators CE" for details.
Note
In general, VDI management software does not assume that power control of managed VM guests is performed from something other than VDI management software.
For this reason, a VM guest may be started by the VDI management software, even if that guest had been stopped beforehand.
For details, refer to the manual of the VDI management software.
When the virtual L-Server on the L-Platform to be deleted was powered on by the VDI management software, the following message is displayed and canceling of an L-Platform subscription may fail.
VSYS30001 Failed to delete L-Platform. [L-Platform ID:{0}][L-Platform Name:{1}][Detail:{2}] Parameter {0}: L-Platform ID {1}: L-Platform name {2}: ROR(67391 deleting VM guest failed. detail=(message,vmerrno=104,ip=IP address)) |
In this case, the L-Platform is deleted from the [L-Platform] tab but the L-Platform and virtual L-Server are not deleted from the orchestration tree on the [Resources] tab. Delete them using the following procedure:
Power off the virtual L-Server.
From the event log of the [L-Platforms] tab, obtain the L-Platform ID of the L-Platform that was not deleted.
From the orchestration tree in the [Resource] tab of Resource Orchestrator, identify the virtual L-Servers in the L-Platform for which the same L-Platform ID as the one obtained in the previous step is displayed as "Label" in the basic information.
From "Allocated Resource Information" in the [Resource Details] tab of the virtual L-Server identified in step b, obtain the guest name of a virtual machine related to the virtual L-Server.
In the server tree in the [Resource] tab of Resource Orchestrator, identify the virtual machine based on the guest name confirmed in step c.
Power off the virtual machine identified in step d.
Or, it is also possible to power it off from VMware vCenter Server or vSphere Client by using the guest name of the virtual machine which failed to be deleted, because it is displayed in the event log mentioned in step a.
Delete the L-Platform.
Delete the L-Platform and virtual L-Server using the cfmg_deletelplatform command.
The L-Platform ID can be obtained from the above message.
For details on the cfmg_deletelplatform command, refer to "10.1 cfmg_deletelplatform (Delete L-Platform)" in the "Reference Guide (Command/XML) CE".
Point
When using the Active Directory domain participation function, and participating in an active directory domain when creating a virtual L-Server for VDI, even if the virtual L-Server is deleted from the ROR console, the computer account on the Active Directory domain will not be deleted.
When the computer account is not necessary, delete the relevant computer account from [Active Directory Users and Computers].
Guest OS Customization Waiting Time
This section explains the guest OS customization waiting time.
VDI coordination requires participation in the Active Directory domain during the guest OS customization process performed when creating a virtual L-Server.
For this reason, Resource Orchestrator is set to wait for 30 minutes by default for completion of the guest OS customization.
This waiting time can be modified using the "guest OS customization waiting time" setting in the "Server virtualization software definition file" explained in "Installation".
The completion waiting time indicates the time counted from when the second virtual machine is started (step 2) during the following internal process.
The time taken for customization of a guest OS depends on the content and performance of the virtual machine.
When customization is not completed or waiting time is longer than expected, change the value for the guest OS customization waiting time.
When changing the completion waiting time, measure how long it takes to customize the guest OS using the following procedure and then set the value based on the results as well as the VM performance and other environment conditions.
Create a virtual machine on VMware using the template which will be the entity on VMware of the cloning image used during creation of a virtual L-Server. Set the information for guest OS customization assuming the information to be specified using Resource Orchestrator.
Start the virtual machine which was created.
Connect the console to the virtual machine.
Monitor the guest OS customization status and measure the time taken to complete the customization.
The internal processes of virtual L-Server creation using Resource Orchestrator are as follow:
A virtual machine is created on VMware.
The virtual machine is started on VMware.
The guest OS customization process is performed within the guest OS. (*)
During this customization process, participation in the Active Directory domain, which is necessary for VDI coordination, is performed.
Resource Orchestrator waits for a certain time for the customization process to complete.
The default completion waiting time is 30 minutes.
The virtual machine is registered with VMware Horizon View.
When the above completion waiting time is short, guest OS customization may be still in progress when L-Server creation is completed.
In this case, wait for a while until customization is completed.
Note: When the guest OS is Windows, the initial configuration is performed using Sysprep generalization and the Mini-Setup process.
Advisory Notes for VMware Horizon View Usage
This section explains advisory notes regarding use of VMware Horizon View.
Registration of Users and Groups to the Active Directory Domain
Users and user groups of the desktop must belong to the Active Directory domain. Create domain users and groups who will use the desktop in the Active Directory domain in advance.
Creation, Configuration Modification, and Deletion of L-Servers with VDI Attributes Specified
Use the [L-Platform] tab to perform creation, configuration modification, and deletion of L-Servers with VDI attributes specified.
Power operations of servers during VDI coordination
It is not recommended to use measures other than the VDI management product to operate the power of a server for VDI coordination.
At least one of the servers of a VDI pool keeps running due to the specification of the VDI product. After stopping a server by using this product or the VM management product, it may be started automatically by the VDI management product.
Installation and Use of Software on Users' Client Devices
Desktop users must install Horizon View Client on Windows client devices.
For details on the installation and operation procedures, refer to "Using VMware Horizon View Client for Windows" provided by VMware.
When Desktop Connection Fails
When the connection from the client machine to the desktop fails, there may be a problem with the virtual machine, the user's client machine, or network settings.
Check whether the following apply:
When the infrastructure administrator checks
In order to use the desktop, Horizon View Agent must be installed on the virtual machine.
For this reason, confirm that Horizon View Agent has been installed on the virtual machine.
There is a possibility that the virtual machine cannot participate in the domain. Check whether the machine is participating in the domain. One possible reason that participation is not possible is that there is an error in the content of the OS property definition file. For details, refer to "8.2.12 Participating in an Active Directory Domain".
When the user checks
In order to establish a connection from the user's client device to the desktop, the host name of the VDI management server must be able to be resolved.
Check the following settings of the client device. Check with the infrastructure administrator when unsure of the settings.
Network and Proxy Settings
Firewall Settings
DNS Reference Settings
Updating VDI coordination parameters
When the VDI coordination parameters displayed on the ROR console have become incorrect due to modification of the settings with VMware Horizon View or other reasons, update the parameters using the following commands:
The cfmg_deletevdiparams command
The cfmg_updatevdiconnectinfo command
The cfmg_updatevdiparams command
For details of the commands, refer to "10.4 cfmg_deletevdiparams (Delete VDI Coordination Parameters) [Windows Manager]", "10.9 cfmg_updatevdiconnectinfo (Update VDI Management Server Connection Information) [Windows Manager]", and "10.10 cfmg_updatevdiparams (Update VDI Coordination Parameters) [Windows Manager]" in the "Reference Guide (Command/XML) CE".