The configuration of the VMware Horizon View Cloud Pod Architecture is done entirely through command line. The lmvutil command line tool is used to configure and manage a VMware Horizon View Cloud Pod Architecture environment. The lmvutil tool is installed as part of the VMware Horizon View installation. You can use the VMware Horizon View Administrator to investigate the pod health and desktop session information.
At this moment, there is no GUI available to configure and manage the VMware Horizon View Cloud Pod Architecture. I hope this will change in the future because at this moment and time it is in my opinion not advisable to handover the operation of the VMware Horizon View Cloud Pod Architecture to standard Horizon View operators who might not be aware of all the details of the lmvutil command line.
Initialization Pod Federation
Log on to the first connection server in DC1
Open a command line (Run as Administrator)
cd C:\Program Files\VMware\VMware View\Server\tools\bin
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –initialize
Join Pods to the Pod Federation
Log on to the first connection server in DC2
Open a command line (Run as Administrator)
cd C:\Program Files\VMware\VMware View\Server\tools\bin
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –join –joinServer <fqdn_First_Connection_Server_in_DC1> –userName NETBIOSDOMAIN\<view_service_account> –password xxxx
Change Default Pod Names
Log on to the first connection server in DC1
Open a command line (Run as Administrator)
cd C:\Program Files\VMware\VMware View\Server\tools\bin
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –listPods
Note: This command will show the default names of the Pods: <defaultpodname_in_DC1> and <defaultpodname_in_DC2>
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –updatePod –podName <defaultpodname_in_DC1> –newPodName DC1-POD01
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –updatePod –podName <defaultpodname_in_DC2> –newPodName DC2-POD01
Create Sites and assign Pods to the Sites
Log on to the first connection server in DC2
Open a command line (Run as Administrator)
cd C:\Program Files\VMware\VMware View\Server\tools\bin
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –listSites
Note: This command will show the default names of the Sites: <defaultpodname_in_DC1> and <defaultpodname_in_DC2>
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –createSite DC1-SITE01
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –createSite DC2-SITE01
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –assignPodToSite –podName DC1-POD01 –siteName DC1-SITE01
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –assignPodToSite –podName DC2-POD01 –siteName DC2-SITE01
Create and Configure a global Entitlement
For each pool which will be created the following will need to be done:
- a global entitlement will need to be created
- a VMware Horizon View pool will need to be associated with this global entitlement
- an Active Directory group will need to be added to this global entitlement
In the example below a global entitlement with the name GLOBAL_ENT-POOLTEST will be created for pool with Pool ID POOLTEST
Log on to the first connection server in DC1
Open a command line (Run as Administrator)
cd C:\Program Files\VMware\VMware View\Server\tools\bin
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –createGlobalEntitlement –entitlementName GLOBAL_ENT-POOLTEST –scope ANY –isFloating –multipleSessionAutoClean –defaultProtocol PCOIP
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –addPoolAssociation –entitlementName GLOBAL_ENT-POOLTEST –poolId POOLTEST
lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –addGroupEntitlement –entitlementName GLOBAL_ENT-POOLTEST –groupName NETBIOSDOMAIN\group_POOLTEST