Horizon Universal Services - Integration with on-premises PODS

Part 1 - Generating an SSH Key Pair  

  • This an introduction to getting started with the Horizon Universal Console
    • You will have the opportunity to login and observe what a Horizon Cloud tenants looks like not being configured
    • We will also increase the session timeout interval
    • You will validate the custom email credentials required to login to the Horizon Cloud Tenant
      • Please ensure you have received the following:
        • An assigned POD Identifier number. An example could be the number 28
        • An assigned Horizon Cloud Console Username and password. You will notice this is associated with your POD Identifier
          • e.g. [email protected]
          • For this session, make sure you never use someone else's identifier in this shared, production environment
Part 1 - Generating a key pair for SSH sessions
  1. On your ControlCenter server
    • Select and right-click the START button
    • Select Command Prompt (Admin)
  1. In the Administrator: Command Prompt window
    • Enter ssh-keygen
      • with your keyboard, select ENTER
  1. In the Administrator: Command Prompt window
    • Next to : Enter file in which to save the key (C:\Users\Administrator/.ssh/id_rsa)
      • with your keyboard, select ENTER
  1. In the Administrator: Command Prompt window
    • Next to : Enter passphrase (empty for no passphrase):
      • with your keyboard, select ENTER
    • Next to : Enter same passphrase again:
      • with your keyboard, select ENTER
  1. In the Administrator: Command Prompt window
    • Note the final result
    • Notice the key fingerprint
    • We will copy this when do the deployment of the Horizon Cloud Connector from the public key itself

Part 2 - Deploying the Horizon Cloud Connector

The Horizon Cloud Connector is an appliance that connects the  Horizon implementations to the Horizon Cloud Service. In the below labs we will see how we deploy and configure cloud connector in the vCenter

Section 1 : DNS Configuration for the Horizon Cloud Connector
FQDN IP Address Details
hznccXX-01a.euc-livefire.com
 192.168.110.12
 Site-1 Primary Node
hznccXX-01b.euc-livefire.com
 192.168.110.14
 Site-1 Worker Node
  • Where XX  is your POD Identifier.
    • For Example
      • If username assigned is [email protected], POD Identifier is 30
      • For our example FQDN will be hzncc30-01a.euc-livefire.com for the Primary Node.
  1. On your ControlCenter server
    • From the desktop Shortcut or TaskBar,
      • Launch DNS
        • From the DNS Manager
          • Expand Forward Lookup Zones on the left hand side of DNS Menu
            • Expand euc-lifefire.com
  1. In the DNS Manager Window
    • Right Click on euc-livefire.com
      • Select New Host (A or AAAA)...
  1. In the New Host Window
    • In the Name (users parent domain name if blank):
      • Type hznccxx-01a
        • Where xx is the POD Identifier. In our example it is 30
    • In the IP address:
      • Type 192.168.110.12
    • Click Add Host
  1. Repeat the steps to add  Worker Node in the DNS Record
    • In the New Host Window
      • In the Name (users parent domain name if blank):
        • Type hznccxx-01b
          • Where xx is the POD Identifier. In our example it is 30
      • In the IP address:
        • Type 192.168.110.14
      • Click Add Host
  1. In the DNS Manager Console
    • Verify the following
      1. That all entries are added in the DNS record as shown in the image above.
      2. That your entries are created in the euc-livefire.com Forward Lookup Zones
        • we have had participants create the entries in child containers of euc-livefire.com

Failure to verify the above details and accurately enter your version of entries with your unique POD ID,  in the DNS Manager database will have a severe impact on your labs in the next Section

Section 2: Deploying the OVA for the Horizon Cloud Connector  

Cloud Connector OVA deployment

Cloud Connector OVA deployment

We start off by deploying the Primary Node and then afterwards the Worker Node

Whilst the Primary Node is being deployed. Carry on with Worker Node deployment

Step 1: Deploying the Primary Node
  1. From the ControlCenter Desktop
    • Launch the Google Chrome browser
    • In the address Bar navigate to
      • https://vcenter-01a.euc-livefire.com
    • Under Getting started page of vCenter
    • Click Launch VSPHERE CLIENT (HTML 5)
    • select LOGIN
  1. In the vSphere Client
    • Expand vcenter-01a.euc-livefire.com > Region01A > Bangalore
      • Right Click on esxi-01a.euc-livefire.com
        • Click Deploy OVF Template
  1. In the Deploy OVF Template Window
    • Under Select an OVF Template
      • Select Local File radio button
        • Click on UPLOAD FILES
          • From the upload window
            • Navigate to Desktop > Software (shortcut) > Horizon
              • Select horizon-cloud-connector-2.3.0.0-20652183_OVF10.ova
                • Click Open
        • Click Next
  1. In the Select a name and folder Window
    • Virtual machine name: HznCCxx-01a
      • Where xx is the POD Identifier. In our example it is 30
    • In Select a location for the virtual machine Section
      • Select Region01A
      • Click Next
  1. In Select a compute resource Window
    • Expand by clicking Region01A > Bangalore
      • Select esxi-01a.euc-livefire.com
      • Click Next
  1. In the Review details Window
    • Click Next
  1. In the License agreements Window
    • Click on I accept all license agreements check box
    • Click Next
  1. In Select storage Window
    • Select CorpLun01a
    • From Select virtual disk format dropdown
      • Select Thin Provision
      • Click Next
  1. In the Select networks Window
    • From Destination Network dropdown
      • Select VM Network
      • Click Next
  1. On your ControlCenter server
    • On your Taskbar
      • Select the Folder icon
  1. In the File Explorer window
    • Browse to C:\Users\Administrator\.ssh
  1. In the File Explorer window
    • Select and right-click id_rsa_pub
    • Select Edit with Notepad++
  1. In the Notepad++ window
    • Ensure you copy the entire string
      • With your keyboard ,  
        • Select CTRL+A
        • Select CTRL+C
  • Keep this Notepad++ session open. Keep this aside.
  • Switch back to the OVF deployment wizard
  1. In the Customize template Window
    • Under Application Section which is denoted as 1
      • Root Password : VMware1!
      • Confirm Password : VMware1!
    • Under Public key for ccadmin user
      • Paste your Public key
    • In the Network Section
      • Leave it default
      • Click on Network to collapse the Network section
    • In the Proxy Section
      • Leave it default
      • Click on Proxy to collapse the Proxy section
      • Scroll Down to reach to Network Properties
    • In the Network Properties Section which is denoted as 2
      • Default Gateway : 192.168.110.1
      • Domain Name: euc-livefire.com
      • Domain Search Path: euc-livefire.com
      • Domain Name Servers: 192.168.110.10
      • Network IP Address: 192.168.110.12
      • Network Netmask: 255.255.255.0
      • Click Next
  1. In the Ready to Complete Window
    • Verify all the properties
    • Click Finish
  1. Notice the import OVF package task is running
    • Under vCenter > Recent Tasks
    • This may take 15 to 20 minutes.
    • While Cloud Connector ova for Site-1 is getting deployed
      • Continue with the worker node  ova deployment for Site 1b

Cloud Connector OVA Worker Node deployment

Step 2: Deploying the Worker Node
  1. In the vSphere Client
    • Expand vcenter-01a.euc-livefire.com > Region01A > Bangalore
      • Right Click on esxi-01a.euc-livefire.com
        • Click Deploy OVF Template
  1. In the Deploy OVF Template Window
    • Under Select an OVF Template
      • Select Local File radio button
        • Click on UPLOAD FILES
          • From the upload window
            • Navigate to Desktop > Software > Horizon
              • Select horizon-cloud-connector-2.3.0.0-20652183_OVF10.ova
                • Click Open
          • Click Next
  1. In the Select a name and folder Window
    • Virtual machine name: HznCCxx-01b
      • Where xx is the POD Identifier. In our example it is 22
    • In Select a location for the virtual machine Section
      • Select Region01A
      • Click Next
  1. In Select a compute resource Window
    • Expand by clicking Region01A > Bangalore
      • Select esxi-01a.euc-livefire.com
      • Click Next
  1. In the Review details Window
    • Click Next
  1. In the License agreements Window
    • Click on I accept all license agreements check box
    • Click Next
  1. In Select storage Window
    • Select CorpLun01a
    • From Select virtual disk format dropdown
      • Select Thin Provision
      • Click Next
  1. In the Select networks Window
    • From Destination Network dropdown
      • Select VM Network
      • Click Next
  1. In the Customize template Window
    • Under Application Section which is denoted as 1
      • Root Password : VMware1!
      • Confirm Password : VMware1!
      • Worker Node : Check the tick box to mark this appliance as worker node.
      • Public key for ccadmin user  : Copy the content from id_rsa.pub by opening the file on Notepad or Notepad++
        • Note:
          • This is the public key we generated using command prompt in Part 1
          • Public key should will from  ssh-rsa
          • The location of the id_rsa.pub file
            • C:\Users\Administrator\.ssh
    • In the Network Section which is denoted as 2
      • Leave it default
      • Click on Network to collapse the Network section
    • In the Proxy Section which is denoted as 3
      • Leave it default
      • Click on Proxy to collapse the Proxy section
      • Scroll Down to reach to Network Properties
    • In the Network Properties Section which is denoted as 4
      • Default Gateway : 192.168.110.1
      • Domain Name: euc-livefire.com
      • Domain Search Path: euc-livefire.com
      • Domain Name Servers: 192.168.110.10
      • Network IP Address: 192.168.110.14
      • Network Netmask: 255.255.255.0
      • Click Next
  1. In the Ready to Complete Window
    • Verify all the properties
    • Click Finish
  1. Notice the import OVF package task is running
    • Under vCenter > Recent Tasks
    • This may take 15 minutes.
  1. In the vCenter Admin Console
    • Select and right-click your hznCCXX-01a connector
      • Where XX is your POD ID
      • Select Power > Power On
  1. In the vCenter Admin Console
    • Select and right-click your hznCCXX-01b connector
      • Where XX is your POD ID
      • Select Power > Power On

You will have to wait for at least the Primary to deploy. Once the Primary Node has been deployed. Power On the Primary Node and wait for it to start up

Part 3 - Configuring the Horizon Cloud Connector

  • We will pair the Horizon Cloud Connector with your Horizon Cloud Services
  • Configure Horizon Cloud Services

What we have learned is pairing more than one connector before configuring Active Directory in the Horizon Cloud Services, will cause a large percentage of pairings to fail.

As a best practice we recommend

  1. Pairing your first Horizon Cloud Connector with Horizon Cloud Services
  2. Configuring Microsoft Active Directory in Horizon Cloud Services
  3. Pairing any additional Primary Horizon Cloud Connectors which then connect additional PODS to the Horizon Cloud Service
Configuring the Horizon Cloud Connector with the Horizon Cloud Universal Console
  1. On your ControlCenter server
    • In your Chrome browser,
    • Open a new tab
      • In the Address bar,
        • enter https://hznccXX-01a.euc-livefire.com
          • where XX is your POD ID
        • In the Your connection is not private window
          • Select Advanced
          • Select Proceed to hznccXX-01a.euc-livefire.com (unsafe)
            • where XX is your POD ID

Remember to bookmark this URL in your browser

  1. In the Horizon Cloud Connector window
    • In the My VMware username area
      • Enter your assigned username email address
    • In the My VMware password area
      • Enter VMware1!
    • Select Login
  1. In the Setup 1 of 3: Connect to Horizon Pod window
    • Next to Connect to Horizon Connection Server
      • Enter horizon-01a.euc-livefire.com
    • Select Connect
  1. Under Horizon Credentials
    • Next to *Domain: type euc-livefire.com
    • Next to Username: type administrator
    • Next to Password: type VMware1!
    • In the bottom right-corner
      • Select Connect

If your tenant ID has been used before your City will already be there and you wont need to select "New"

Select Bengaluru and move on

  1. In the Setup 2 of 3: Configure Horizon Pod window
    • Next to Name: enter HZNXXBangalore
      • Where XX is your assigned POD ID
    • In line with Data Center Location*
      • to the right, select New
      • In the New Data Center Location window
        • In line with *City Name:
          • type  benga
            • select Bengaluru, India
          • Select Save
    • Select Save
  1. In the Horizon Cloud Connector vCenter Server Details window
    • Next to vCenter Server FQDN,
      • type : vcenter-01a.euc-livefire.com
    • Select Get Certificate
  1. In the Horizon Cloud Connector vCenter Server Details window
    • Scroll down
    • Next to I have verified the above certificate and would like to continue
      • Select the checkbox
    • In the Horizon Cloud Connector vCenter Server Credentials window
    • In the Additional Static IP Details for Cloud Connector upgrade
      • Next to Static IP enter 192.168.110.13
    • Select Save
  1. In the VMware Horizon Cloud Connector Setup window
    • Note the results and information provided
    • You can login to your Horizon on premises administrative console and you should see that it has switched from perpetual to subscription based licensing
    • Scroll down and observe the health status of the admin console objects
  1. On your Chrome Browser
    • Switch back to your vCenter tab
    • In the vSphere Client admin console
      • Under Host & Clusters
        • Under your esxi-01a.euc-livefire.com
        • select and right-click your Worker Node
          • That being hznccXX-01b
            • where xx is your POD ID
  1. On your Worker NODE
    • Select Power > Power On

We will now move on and configure Horizon Cloud Services

Part 4- Configuring the Horizon Cloud Services

In the Horizon Universal Console there are certain mandatory configurations that need to be configured just to get Started. You will follow the General Setup Wizard to complete these tasks

Configuring the Horizon Universal Console
  1. On your Chrome browser
    • In the Favourites Bar
      • Select the HZN Cloud shortcut
        • In the Horizon Cloud Console Login
          • Under Email address
            • (Enter your assigned HZN Cloud username)
          • Select NEXT
            • In the Password area,
              • type VMware1!
        • Select SIGN IN
  1. In the Horizon Universal Console
    • Next to General Setup, expand the down arrow
  1. Under General Setup
    • To the right of Active Directory
      • Select CONFIGURE
  1. In the Register Active Directory window
    1. Next to Bind Username* type administrator
      • Next to Bind Password* type VMware1!
    2. Under Auxiliary account #1
      • Next to Bind Username* type admin1
      • Next to Bind Password* type VMware1!
    3. Expand the dropdown next to Advanced Properties
    4. Next to Domain Controller IP: type :192.168.110.10
    5. Select DOMAIN BIND
  1. In the Domain Join window
    • Enter the following next to:
      • Primary DNS Server IP:* 192.168.110.10
      • Secondary DNS Server IP:* 192.168.210.10
      • Default OU: OU=Computers,OU=Corp,dc=euc-livefire,dc=com
      • Join Username:* administrator
      • Join Password:* VMware1!
    • Select SAVE

If you get any "unable to register Active Directory" messages, they will most likely still work, please try and proceed

  1. In the Add Administrator window
    • Under User Group:
      • Type adm
        • Select Administrators
        • Select SAVE

If you get any "unable to register Active Directory" messages, they will most likely still work, please try and proceed

You will be logged out of the Administrative console at this point

  1. In the Welcome to VMware Horizon Logout complete page
    • Select RETURN TO LOGIN PAGE

 

  1. In the Welcome to VMware Horizon window
    • In the Username area
      • Enter your custom email address
    • In the Password area
      • Enter VMware1!
    • Select LOGIN
  1. In the Welcome to VMware Horizon window
    • Under Active Directory Credentials
      • In the Username area,
        • enter Administrator
      • In the Password area,
        • enter VMware1!
    • Select LOGIN
    • In the What's New in Horizon Cloud window
      • Select CLOSE

Part 5. Deploying the Universal Broker Plugin on the Horizon Connection server

Without the Universal Broker Plugin, we can only monitor Horizon, we can manage Horizon from the Horizon Cloud Services Console.

Deploying the Universal Broker Plugin on the Horizon Connection servers
  1. On your ControlCenter server
    • Open the Remote Desktops folder
      • Select and Launch the Horizon-01a.RDP shortcut
        • Login with the :-
          • username: EUC-Livefire\administrator
          • password: VMware1!
            • Note, RDP client should do this automatically
  1. On the Horizon Connection server
    • Select the Software shortcut
      • Browse to the ..\Software\Horizon folder
        • Select and launch the horizon-universal-broker-plugin-22.01.0-19710947-x64.exe
  1. In the VMware Horizon Service Universal Plugin Setup wizard
    • On the Welcome Screen
      • Select Next
  1. In the VMware Horizon Service Universal Plugin Setup wizard
    • On the End-User License Agreement Screen
      • Select the checkbox next to I accept the terms in the License Agreement
        • Select Next
  1. In the VMware Horizon Service Universal Plugin Setup wizard
    • On the Configuration Screen
      • Select Next
  1. In the VMware Horizon Service Universal Plugin Setup wizard
    • On the Ready to Install VMware Horizon Service Universal Broker Plugin Screen
      • Select Install
  1. In the VMware Horizon Service Universal Plugin Setup wizard
    • On the Completed the VMware Horizon Service Universal Broker Plugin Setup Wizard
      • Select Finish

Part 6- Universal Broker Configuration

The Universal Broker is a flagship feature in POD management and facilitating the user experience across multiple sites. In this section we will be enabling the Universal Broker Services

Universal Broker Configuration

This could be a feature that has already been configured in your environment.

Below are steps in case it has not been configured. If it has please verify the configurations.

Please note, we are working in a production environment and this particular feature once enabled cannot be reset. It can be reconfigured, but the once this feature is enabled. The Engineering teams are unable to reset this feature, as if its never been used before

If has already been configured you will associate your initials with the POD ID and reconfigure it

Section 1: Configuring a universal URL in the Broker
  1. In the Horizon Universal Console
    • Under Getting Started
      • Look for the Dropdown, next to General Setup
    • Select the Dropdown, next to General Setup
  1. In the General Setup area
    • Next to Broker
      • Select GO
  1. In the Broker area
    • Under Universal Broker
      • click on SELECT
  1. In the Universal Broker wizard, under:-
    • FQDN area
      1. Next to Type*,
        • next to  Customer Provided
          • select the radio button
  1. In the Universal Broker wizard, under:-
    • FQDN area
      1. Next to Brokering FQDN*,
        • enter brokerXXbb.euc-livefire.com
          • XX is represents your POD ID
          • bb represents your initials
  1. In the Universal Broker wizard, under:-
    • FQDN area
      1. Next to Certificate*,
        • select BROWSE
          • Browser to \\horizon-01a.euc-livefire.com\software\certificates
          • In the File Explorer window,
            • select Wildcard2022.pfx
        • Next to Password * enter VMware1!
    • Select NEXT
  1. In the Universal Broker wizard, under:-
    1. Authentication
      • Select NEXT
  1. In the Universal Broker wizard, under:-
    1. Settings
      • Enable the following toggles Next to
        • Select Multimedia Redirection (MMR)
        • Select USB Access
        • Select Clean UP HTML Access Credentials When Tab is Closed
      • Select  NEXT
  1. In the Universal Broker wizard, under:-
    1. Summary
      • Select FINISH
  1. In the Universal Broker window
    • Under the FQDN area
    • Next to Broker URL
      • select and right-click the URL
        • select Copy link address
Section 2: DNS configuration in your onsite euc-livefire.com zone
  1. On your ControlCenter server Taskbar
    • select the DNS Manager shortcut
  1. In your DNS Manager console
    • Select and right-click the euc-livefire.com zone
    • Select New Alias (CNAME)...
  1. In the New Resource Record window
    • Under Alias name
      • enter your BrokerXX +initialID using the following convention
        • Where XX is your assigned POD ID
          • e.g. 20
        • +initial. If your name is Tom Harry, your initial will be th
          • e.g broker20th
    • Under Fully qualified domain name (FQDN) for target host:
      • paste the copied Broker URL
        • remove the https:// part of the Broker URL
    • To close the New Resource Record window
      • Select OK
    • To close the DNS Manager window
      • In the top right-corner
        • Select X
  1. On the ControlCenter server
    • Select and right-click the START button
    • Select Command Prompt (Admin)
  • Periodically for some, this ping has failed to resolve.
    If it does for you.

Within the DNS Manager
Select and right-click ControlCenter. Stop and Restart the DNS services and try ping again

  1. In the Administrator: Command Prompt
    • type ping (YOUR BROKER FQDN)
      • With your keyboard
        • Select ENTER

Notice that the url resolves to an Azure base Cloud environment and that it has an associated IP address.

You will only see the first response resolving to public IP. Rest all ping will be Request timed out

You are now ready to move on the the next part of your lab

Part 7 - Configuring the Horizon Cloud Desktop and Virtual Application assignments

For us to be in a position to perform Desktop and Virtual Application assignments, there are certain pre-requisite tasks in the Horizon Cloud services that need to be in place. We will perform these configurations in Part 6 of this lab

Configuring the Horizon Cloud Desktop and Virtual Application assignments
  1. In the Horizon Universal Console
    • Next to Settings
      • expand the dropdown
  1. In the Horizon Universal Console
    • Under Settings
      • Select Capacity
  1. In the Horizon Universal Console
    • Under Capacity
      • Notice that both sites have a state of monitored.
        • We will changing the status to Managed so that we can entitle users to virtual Applications and Desktops
      • Select the radio button next to HZNBangalore
  1. In the Horizon Universal Console
    • Under Capacity
      • Select MORE
        • Under MORE
          • Select Change State
  1. In the Change State of HZNBangalore to managed? window
    • In line with Site
      • Below the selected New radio button (if not selected, select)
        • enter Bangalore
  • Select SAVE
  1. In the Capacity area
    • Notice the State for your site should read Managed
    • Your Site should map to Bangalore

Part 8: Configuring Application and Desktop Pools for Horizon Cloud Services

In the 2212 release of Horizon a new feature was release for on demand apps integration with App Volumes.

This will be part the exercise

Section 1: Configuring VMware Horizon to integrate with VMware App Volumes
  1. On your ControlCenter server
    • On your Chrome Browser
      • open a new tab
      • In the favourites bar
      • Launch the Horizon bookmark
  1. In the VMware Horizon login
    • In the User name area
      • enter Administrator
    • In the Password area
      • enter VMware1!
    • select Sign in
  1. In the VMware Horizon Admin Console
    • In the Inventory
      • Under Settings
        • select Servers
  1. In the Servers area
    • to the right
      • select the App Volumes Managers tab
  1. In the App Volumes Managers area
    • select Add
  1. In the Add App Volumes Manager window
    • add the following next to:--
      • Server address : appvol-01a.euc-livefire.com
      • User name : administrator
      • Password : VMware1!
    • Select OK
  1. In the Servers area
    • Note the App Volumes Manager Server you have just added
  1. In the Horizon Administrator Console
    • Under Inventory
      • select Farms
  1. In the Farms area
    • Next to your RDSHXX-01a farm
      • select the checkbox
    • Next to More Commands
      • select the dropdown
      • from the dropdown
        • select Associate App Volumes Manager
  1. In the Associate App Volumes Manager
    • select the dropdown
      • select the appvol-01a.euc-livefire.com
    • select OK
Section 2: Updating the Desktop Pool for Horizon Cloud Services
  1. In the VMware Horizon admin console
    • Under Inventory
      • Select Desktops
  1. In the VMware Horizon admin console
    • Under Desktop Pools
      • Next to HZNBLR_XX_W10 desktop pool
        • select the checkbox
      • Select Edit
  1. In the Edit Pool - HZNBLR_XX_W10 window
    • Select Desktop Pool Settings tab
  1. In the Edit Pool - HZNBLR_XX_W10 window
    • Under the Desktop Pool Settings tab
      • next to Cloud Managed
        • select the check box
      • Select OK

Part 9 - Configuring Application Pools for Horizon Cloud Services

We will configuring a Application Pools for the Bangalore POD.
Look out for a Cloud Managed check box that will you will enable for this Pool to be managed by Horizon Cloud Services

Section 1: - Configuring traditional Application Pools for Cloud Brokering
  1. In the Horizon Administration Console
    • Select Inventory > Applications
  1. In the Application Pools area
    • Select Add
    • Select Add from installed Applications
  1. In the Add Application Pool wizard
    1. Select Applications area
      • Under Name
        • Select the checkbox next to:-
          • Calculator
          • Paint
      • Select the checkbox next to:-
        • Cloud Brokered
        • Pre-Launch
      • Select Next
  1. In the Add Application Pool wizard
    1. Edit Applications area
      • Under ID
        • Append your:
          • Assigned  POD ID
          • Site ID
        • Calculator_XX_BLR
        • Paint_XX_BLR
      • Select Submit
  1. In the Add Entitlements window
    • Select Add
  1. In the Find User or Group
    • Next to Name/User Name > Starts with > type Sales
      • Select Find
      • Select the checkbox next to Sales
      • Select OK
  1. In the Add Entitlements window
    • Select OK
Section 2: - Configuring App Volumes Application Pools for Cloud Brokering
  1. In the Horizon Administration Console
    • Select Inventory > Applications
  1. In the Application Pools area
    • Select Add
    • Select Add from App Volumes Manager
  1. In the Add Application Pool wizard
    1. Select Applications area
      • Under Name
        • Select the checkbox next to:-
          • Word
          • Notepad++
          • Google Chrome
      • Select the checkbox next to:-
        • Cloud Brokered
      • Select Next
  1. In the Add Application Pool wizard
    1. Edit Applications area
      • Under ID
        • Append your:
          • Assigned  POD ID
          • Site ID
        • Word_XX_BLR
        • Paint_XX_BLR
        • Google_Chrome_XX_BLR
      • Select Submit
  1. In the Add Entitlements window
    • Select Add
  1. In the Find User or Group
    • Next to Name/User Name > Starts with > type Sales
      • Select Find
      • Select the checkbox next to Sales
      • Select OK
  1. In the Add Entitlements window
    • Select OK

Part 10. Configuring the Horizon Cloud services for Desktop  Assignments

Creating Desktop a entitlement In Horizon Cloud Services
  1. On your Chrome Browser
    • Go back to your Horizon Cloud Console tab
    • Select RETURN TO LOGIN PAGE
  1. In the Welcome to VMware Cloud Services page
    • Ensure your assigned Admin Account is in the Username area
      • If not, then enter it
    • In the Password area
      • enter VMware1!
    • select SIGN IN
  1. In the Welcome to VMware Horizon page
    • Below Active Directory Credentials area
      • In the Username area
        • enter Administrator
      • In the Password area
        • enter VMware1!
    • select LOGIN
  1. In the Horizon Universal Console
    • Expand Assign Desktops & Apps
      • Select VDI
  1. In the Assignments area
    • Select NEW
      • Under Desktop
        • Select VMware SDDC
  1. In the New Desktop Assignment wizard
    • Next to:
      1. General Information
        • Configure the following: next to:-
          • Desktop Type* :Floating (default configuration)
          • Desktop Name*: type CorpxxHZN
            • (xx is your assigned POD number)
          • In the Select Pod(s) area
            • select the checkbox next to
              • HznBangalore
        • Select NEXT
  1. In the New Desktop Assignment wizard
    • Next to:
      1. Desktops
        • Configure the following: next to:-
          • Operating System* : from the dropdown, select Windows 10 (64-bit)
          • HTML Access: toggle Enabled
          • Clean Up Redundant Sessions : toggle Enabled
        • Select the check box next to:-
          • HZNBLR_XX_W10
            • (XX being your  POD Number)
        • Select NEXT
  1. In the New Desktop Assignment wizard
    • Next to:
      1. Users
        • Configure the following: next to:-
          • Find Users: type sales
            • Select Sales
  1. In the New Desktop Assignment wizard
    • Next to:
      1. Users
    • Select NEXT
  1. In the New Desktop Assignment wizard
    • Next to:
      1. Summary
        • Review the information
    • Select FINISH
  1. In the Assignments area
    • Note that the Status for your CorpXXHZN assignment is Pending
      • Where XX is your assigned POD ID
      • It might take up to 5 minutes to show as Complete
        • Refresh the page every 2 minutes
  1. In  In the Assignments area
    • Note that your Site, Pod, Capacity information will show first
      • Keep refreshing
    • Note that the Status for CorpXXHZN is now Complete
      • Where XX is your assigned POD ID

Part 11: Testing the Horizon Cloud Services Configuration

We will now validate the function of our configurations.

You have two Windows 10 virtual desktops that are configured with external DNS server addresses. They represent external desktops in this lab environment  

Section 1: Testing the Horizon Cloud Services Configuration
  1. On your ControlCenter server
    • On the Desktop
      • Open the Remote Desktops Folder
        • Open Site1
  1. On the W10Client-01a desktop
    • Select the VMware Horizon shortcut
  1. In the VMware Horizon Client
    • Select Add Server
  1. In the Name of the Connection Server window
    • Enter YOUR assigned broker FQDN
      • brokerXXbb.euc-livefire.com
        • Where xx is your assigned POD ID
        • Where bb is your initials
    • Select Connect
  1. In the Login window
    • In the Username area,
      • type Mark
    • In the Password area,
      • type VMware1!
    • Select Login
  1. In the VMware Horizon Client
    • Select your Google Chrome Entitlement
      • When prompted for Drive Sharing
        • Select Allow
  1. On your ControlCenter server
    • On the Desktop
      • Open the Remote Desktops Folder
  1. On the W10EXT-01a desktop
    • Select the VMware Horizon shortcut
  1. In the VMware Horizon Client
    • Select Add Server
  1. In the Name of the Connection Server window
    • Enter YOUR assigned broker FQDN
      • brokerxx.euc-livefire.com
        • Where xx is your assigned number
    • Select Connect
  1. In the Login window
    • In the Username area,
      • type Jill
    • In the Password area,
      • type VMware1!
    • Select Login
  1. In the VMware Horizon Client
    • Launch the Calculator Application entitlement
    • Launch the Desktop assignment
      • That being CorpxxHZN
        • XX is representative of your assigned number

You might notice that there is an issue with Chrome not showing. We will fix this in a later exercise

  1. In the Horizon Client session on W10Client-01a
    • Launch a Command prompt session
    • Type Hostname
      • Observe the naming convention, Note the Computer name is a Bangalore abbreviated Desktop
  1. On your Horizon Universal Console
    • Under Monitor
      • Select DashBoard
      • On the right of the page
        • Select the Sessions tab
          • Note the sessions are on both the Bangalore and Seattle site,
        • In the Sesssions area
          • select HZNXXBangalore
        • In the Bengaluru, India pane
          • at the bottom, select VIEW
  1. In the Global Footprint - Sessions window
    • Note some of the monitoring options offered
Section 2: Resolving a possible issue regarding Icons with Published Applications
  1. On your ControlCenter server
    • Open your Chrome Browser
      • In the address bar, go to the following URL
        • https://icons.iconarchive.com/icons/xenatt/the-circle/256/App-Chrome-icon.png
  1. On the Chrome web page
    • select the App-Chrome-icon.png graphic
      • right-click > Save Image as....
      • select Save
  1. Switch back to your Horizon Admin Console
    • In the left Menu
      • Under Inventory
        • select Applications
  1. In the Application Pools window
    • Next to Google Chrome XX blr
      • XX being your POD ID
      • select the checkbox
    • In the menu bar
      • next to Application icon
        • select the dropdown
        • select Associate Application Icon
  1. In the Associate Application Icon window
    • select Upload Icon File
    • browse to Downloads
      • select  App-Chrome-icon.png
      • select Open
    • To close the window
      • select OK
  1. In the Application Pools window
    • Note that your Chrome application now has a new Icon
  1. On your ControlCenter Chrome browser
    • switch to your Horizon Universal Console ( if necessary login)
      • Under Assign Desktops & Apps
        • select RDSH
  1. In the Assignments - RDSH Desktops & Apps area
    • Under Assignment Name
      • select Google Chrome
  1. In the Google Chrome window
    • Under Summary
    • select the SYNC NOW button
      • you might notice a brief Application pool sync initiated notice
  1. Revert to your W10Client-01a RDP desktop session
    • In your existing VMware Horizon Client session
      • select Refresh
    • note you now have a Google Chrome Icon

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.