Horizon Universal Services - Integration with on-premises PODS

Part 1 - Logging in to Horizon Universal Console  

  • 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 attendee Identifier number. An example could be the number 28
        • An assigned attendee email address. You will notice this is associated with your attendee Identifier
          • e.g. [email protected]
          • For the entire course, 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
hznccXX-02a.euc-livefire.com
 192.168.210.12
 Site-2 Primary Node
hznccXX-02b.euc-livefire.com
 192.168.210.14
 Site-2 Worker Node
  • Where XX  is attendee Identifier.
    • For Example
      • If username assigned is [email protected], attendee Identifier is 30
      • For our example FQDN will be hzncc30-01a.euc-livefire.com for Site-1 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 attendee 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 for Site-1 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 attendee Identifier. In our example it is 30
      • In the IP address:
        • Type 192.168.110.14
      • Click Add Host
  1. Repeat the steps to add  Primary Node for Site-2 in the DNS Record
    • In the New Host Window
      • In the Name (users parent domain name if blank):
        • Type hznccxx-02a
          • Where xx is the attendee Identifier. In our example it is 30
        • In the IP address:
          • Type 192.168.210.12
        • Click Add Host
  1. Repeat the steps to add  Worker Node for Site-2 in the DNS Record
    • In the New Host Window
      • In the Name (users parent domain name if blank):
        • Type hznccxx-02b
          • Where xx is the attendee Identifier. In our example it is 30
        • In the IP address:
          • Type 192.168.210.14
        • Click Add Host
    • Close the new host window.
  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 attendees 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 on Site 1 and Site 2

Cloud Connector OVA deployment for Site-1

Step 1: Cloud Connector OVA deployments for Site-1

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 1a: Deploying the Primary Node
  1. From the ControlCenter Desktop
    • Launch Google Chrome Site1 profile
    • In the address Bar Navigate to
      • https://vcenterXX-01a.euc-livefire.com
        • XX is your unique POD
    • Under Getting started page of vCenter
    • Click Launch VSPHERE CLIENT (HTML 5)
  1. In the vSphere Client
    • Expand vcenterXX-01a.euc-livefire.com > Region01A > Bangalore
      • Where XX is your assigned POD ID
        • 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-01a
      • Where xx is the attendee 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!VMware1!
      • Confirm Password : VMware1!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 for Site-1

Step 1b: Deploying the Worker Node
  1. In the vSphere Client for Site 1
    • Expand vcenterXX-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 attendee 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!VMware1!
      • Confirm Password : VMware1!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

If either the Primary or Worker node or both have not deployed, carry on with Site 2 Deployment and momentarily switch back to power on your Horizon Cloud Connectors

Step 2: Cloud Connector OVA deployments for Site-2

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 2a: Deploying the Primary Node
  1. From the ControlCenter Desktop
    • Launch Google Chrome Site2 profile
      • In the address Bar Navigate
        • https://vcenterXX-02a.euc-livefire.com
          • Where XX is your assigned POD ID
    • Under Getting started page of vCenter
    • Click Launch VSPHERE CLIENT (HTML 5)
  1. In the vSphere Client
    • Expand vcenterXX-02a.euc-livefire.com > Region02A > Seattle
      • Right Click on esxi-02a.euc-livefire.com
        • Select 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 ova 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-02a
      • Where xx is the attendee Identifier. In our example it is 30
    • In Select a location for the virtual machine Section
      • Select Region02A
      • Click NEXT
  1. In Select a compute resource Window
    • Expand by clicking Region02A > Seattle
      • Select esxi-02a.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 CorpLun02a
    • 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!VMware1!
      • Confirm Password : VMware1!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.210.1
      • Domain Name: euc-livefire.com
      • Domain Search Path: euc-livefire.com
      • Domain Name Servers: 192.168.210.10
      • Network IP Address: 192.168.210.12
      • Network Netmask: 255.255.255.0
      • Click Next
  1. In the Ready to Complete Window
    • Verify all the properties
    • Click Finish
    • Wait for the deployment of the OVA to complete.
    • This would take around 15 to 20 minutes

Proceed with Step 2b: Deploying the Worker Node

Step 2b: Deploying the Worker Node
  1. In the vSphere Client
    • Expand vcenterXX-02a.euc-livefire.com > Region02A > Seattle
      • Right Click on esxi-02a.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 ova 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-02b
      • Where xx is the attendee Identifier. In our example it is 22
    • In Select a location for the virtual machine Section
      • Select Region02A
      • Click NEXT
  1. In Select a compute resource Window
    • Expand by clicking Region02A > Seattle
      • Select esxi-02a.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 CorpLun02a
    • 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!VMware1!
      • Confirm Password : VMware1!VMware1!
    • In the Worker Node area
      • Select the Checkbox
    • 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 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.210.1
      • Domain Name: euc-livefire.com
      • Domain Search Path: euc-livefire.com
      • Domain Name Servers: 192.168.210.10
      • Network IP Address: 192.168.210.14
      • Network Netmask: 255.255.255.0
      • Click Next
  1. In the Ready to Complete Window
    • Verify all the properties
    • Click Finish
      • Wait for the deployment of the OVA to complete.
      • This would take around 15 minutes
  1. In the vCenter Admin Console
    • Select and right-click your hznCCXX-02a connector
      • Where XX is your POD ID
      • Select Power > Power On
  1. In the vCenter Admin Console
    • Select and right-click your hznCCXX-02b connector
      • Where XX is your POD ID
      • Select Power > Power On

If either the Primary or Worker node or both have not deployed, carry on with Site 1 Horizon Cloud Connector configuration .

Momentarily switch back to power on your Horizon Cloud Connectors

Part 3 - Configuring the Horizon Cloud Connector on Site 1

We will configure a Horizon Cloud Connector for Site 1 and pair this with your 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 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 on Site 1
  1. On your ControlCenter server
    • In your Site 1 profile 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

Please 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 : vcenterXX-01a.euc-livefire.com
        • Where XX is your assigned POD ID
    • 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

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 ControlCenter Server
    • Select your Site 1 profile - Chrome browser

If you have problems logging in. Consider selecting the New Incognito window option for your browser

  1. On your Site 1 profile browser
    • In the Favourites bar
      • Select the HZN Cloud shortcut
  1. In the Horizon Cloud Console Login
    • In the Username area
      • Enter your Horizon Cloud Services assigned username
    • In the Password area,
      • type VMware1!
    • Select LOGIN
  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 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
  1. In the Horizon Universal Console
    • Expand Settings
    • Select Active Directory
      • In the right pane,  validate your Active Directory Configuration

Part 5 - Configuring the Horizon Cloud Connector on Site 2

We will configure a Horizon Cloud Connector for Site 2 and pair this with your Horizon Cloud services

Configuring the Horizon Cloud Connector with the Horizon Cloud Universal Console on Site 2

From the vSphere client. Take a moment to validate that both your Horizon Cloud Connectors are powered-on on Site 2.

Remember to bookmark your URL in your Browsers favourites bar

  1. On your ControlCenter server
    • In your Site 2 profile browser,
      • In the Address bar,
        • enter https://hznccXX-02a.euc-livefire.com
          • where XX is your POD ID
      • In the Your connection is not private window
        • In the Your connection is not private window
          • Select Advanced
            • Select Proceed to hznccXX-02a.euc-livefire.com (unsafe)
              • Where XX is your assigned POD ID
  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 Horizon Cloud Connector window
    • In the Enter your Active Directory credentials section
      • In the Username area
        • enter administrator
      • In the 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-02a.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
  1. In the Setup 2 of 3: Configure Horizon Pod window
    • Next to Name: enter HZNXXSeattle
      • 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  Seat
          • select Seattle, WA United States
          • Select Save
    • Select Save
  1. In the Horizon Cloud Connector vCenter Server Details window
    • Next to vCenter Server FQDN,
      • type : vcenterXX-02a.euc-livefire.com
        • where XX is your assigned POD ID
    • 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.210.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

Part 6. Deploying the Universal Broker Plugin on the Horizon Connection servers

Deploying the Universal Broker Plugin The Universal Broker plugin is a mandatory component when it comes to Horizon Cloud services. In section 1 we will deploy the Universal Broker Plugin on Site 1

Section 1: Deploying the Universal Broker Plugin on the Horizon Connection servers
  1. On your ControlCenter server
    • Open the Remote Desktops folder
      • Select and Open Site 1
        • 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 Open File - Security Warning window
    • Select Run
  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

Deploying the Universal Broker Plugin The Universal Broker plugin is a mandatory component when it comes to Horizon Cloud services. In section 2 we will deploy the Universal Broker Plugin on Site 2

Section 2: Deploying the Universal Broker Plugin on Horizon-02a.euc-livefire.com
  1. On your ControlCenter server
    • Open the Remote Desktops folder
      • Select and Open Site 2
        • Select and Launch the Horizon-02a.RDP shortcut
        • username: EUC-Livefire\administrator
        • password: VMware1!
  1. On the Horizon-02a 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 Open File - Security Warning window
    • Select Run
  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 7- 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 this is already configured move on to Section 2

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. Under the  Broker interface
    • Click on the SELECT button
  1. In the Universal Broker wizard, under:-
    1. FQDN area
      1. Next to Type*,
        • Select the radio button next to
          • Customer Provided
  1. In the Universal Broker window
    1. FQDN area
      • next to Brokering FQDN*
        • type a custom broker FQDN, using the below convention
          • brokerxx(Your initials).euc-livefire.com
            • xx is your assigned Pod identifier e.g. 25
            • Your initials. (If my name is Tom Harry, then my initials will be th)
              • e.g. broker25th.euc-livefire.com
      • Next to Certificate*
        • Select BROWSE
  1. In the Open window
    • copy and paste the following in the address bar
      • \\horizon-01a.euc-livefire.com\software\certificates
      • Select Enter on your keyboard
    • Select Wildcard2022.pfx
    • Select Open
  1. In the Universal Broker window
    1. FQDN area
      • Next to Password*
        • type VMware1!
      • Next to VMware Provided FQDN
        • copy the FQDN
        • Save the FQDN to Notepad++  
      • 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
Section 2: DNS configuration in your onsite euc-livefire.com zone
  1. On your ControlCenter server Desktop
    • Launch your DNS Manager shortcut
  1. In your DNS Manager console
    • Select and right-click the euc-livefire.com zone
    • Select New Alias (CNAME)...
  1. In your Horizon Universal Console
    • In the Broker area
      • Under FQDN
        • Select and copy your Copy link address
  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 8 - 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
      • Next to New
        • select the radio button
      • Under New
        • type Bangalore
      • Select SAVE
  1. In the Horizon Universal Console
    • Under Capacity
      • Notice that HznBanglore is now Managed and the HZNSeattle site has a state of Monitored.
        • We will change the HZNSeattle status to Managed so that we can entitle users to virtual Applications and Desktops
      • Select the radio button next to HZNSeattle
  1. In the Horizon Universal Console
    • Under Capacity
      • Select MORE
        • Under MORE
          • Select Change State
  1. In the Change State of HZNSeattle to managed? window
    • In line with Site
      • Next to New
        • select the radio button
      • Under New
        • type Bangalore
    • Select SAVE

 

  1. In the Capacity area
    • Notice the State of both your sites should read Managed

Check that your location HZNxxBangalore maps to Bengaluru, India and HZNxxSeattle maps to Seattle, WA, United States. If the location for Seattle did not take effect

Edit your Seattle configuration and repeat the process

If the Status throws errors, ignore and move on.

Part 9: Configuring Desktop Pools for Horizon Cloud Services

We will configuring the Desktop Pool for Site 1 in this Section.  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 a Desktop Pool for Site 1
  1. On your Horizon Universal Console
    • Under  Capacity
      • Double click the HZNBangalore link
  1. In the HZNBangalore window
    • Select LAUNCH HORIZON CONSOLE
  1. In the VMware Horizon admin console
    • Under Inventory
      • Select Desktops
  1. In the VMware Horizon admin console
    • Under Desktop Pools
      • Select Add
  1. In the Add Pool wizard
    • Next to:-
      1. Type
        • Select Automated Desktop Pool
        • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Server
        • Accept the Defaults
        • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. User Assignment
        • Select the radio button next to Floating
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. Storage Optimization
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. Desktop Pool Identification
        • Enter the following under:-
          • ID type HZNBLR_xx_W10
            • Where xx is your assigned POD number
          • Display Name, type Bangalore_XX_W10
            • Where xx is your assigned POD number
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. Provisioning Settings
        • Enter the following under:-
          • Use a Naming Pattern type BLRXX-W10-
            • Where XX is your assigned POD ID
          • Desktop Pool Sizing
            • Maximum Machines, type 3
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • To the right of Golden image in vCenter
          • Select Browse
  1. In the Select Golden Image window
    • Select the radio button, next to W10-Master-01a
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • To the right of *Snapshot
          • Select Browse
  1. In the Select Default Image window
    • Select the radio button, next to baseline
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • To the right of *VM Folder Location
          • Select Browse
  1. In the VM Folder Location window
    • Select the Region01A cluster icon
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • In the Resource Settings area
          • To the right of *Cluster
            • Select Browse
  1. In the Select Cluster window
    • Select the Bangalore cluster icon
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • In the Resource Settings area
          • To the right of *Resource Pool
            • Select Browse
  1. In the Resource Pool window
    • Select the Bangalore cluster icon
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • In the Resource Settings area
          • To the right of *Datastores
            • Select Browse
  1. In the Select Instant Clone Datastores window
    • Select the checkbox next to CorpLun01a
      • Select Submit
    • In the Warning window
      • Select OK
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • Leave VM Compute Profile Settings as default
        • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. Desktop Pool Settings
        • Select the checkbox next to Cloud Managed
        • Under Log Off after Disconnect
          • From the dropdown, select Immediately
          • Select Next
  1. In the Add Pool wizard
    1. Remote Display Settings area
      • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. Guest Customization
        • Under *AD Container
          • Select Browse
  1. In the AD Container window
    • Expand OU=Corp
      • Select OU=Computers,OU=Corp
      • Select Submit
  1. In the Add Pool wizard
    1. Guest Customization area
      • Select the checkbox next to
        • Allow Reuse of Existing Computer Accounts
      • Select Next
  1. In the Add Pool wizard
    1. Ready to Complete area
      • Select Submit

We will configuring a Desktop Pool for Site 2 in this Section.  Look out for a Cloud Managed check box that will you will enable for this Pool to be managed by Horizon Cloud Services

Section 2: Configuring a Desktop Pool for Site 2
  1. On your Horizon Universal Console
    • In the HZNBangalore area
      • Select Back
  1. In the Capacity area
    • Under Pods (default)
      • Under Name
        • Select HZNSeattle
  1. In the HZNSeattle window
    • Select LAUNCH HORIZON CONSOLE
  1. In the VMware Horizon admin console
    • Under Inventory
      • Select Desktops
  1. In the VMware Horizon admin console
    • Under Desktop Pools
      • Select Add
  1. In the Add Pool wizard
    • Next to:-
      1. Type
        • Select Automated Desktop Pool
        • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Server
        • Accept the Defaults
        • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. User Assignment
        • Select the radio button next to Floating
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. Storage Optimization
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. Desktop Pool Identification
        • Enter the following under:-
          • ID type HZNSea_xx_W10
            • Where xx is your assigned number
          • Display Name, type Seattle_xx_W10
            • Where xx your assigned number
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. Provisioning Settings
        • Enter the following under:-
          • Use a Naming Pattern type SEAXX-W10-
            • Where XX is your assigned POD ID
          • Desktop Pool Sizing
            • Maximum Machines, type 3
        • Select  Next
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • To the right of Golden image in vCenter
          • Select Browse
  1. In the Select Golden Image window
    • Select the radio button, next to W10-Master-02a
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • To the right of *Snapshot
          • Select Browse
  1. In the Select Default Image window
    • Select the radio button, next to baseline
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • To the right of *VM Folder Location
          • Select Browse
  1. In the VM Folder Location window
    • Select the Region02A cluster icon
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • In the Resource Settings area
          • To the right of *Cluster
            • Select Browse
  1. In the Select Cluster window
    • Select the Seattle cluster icon
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • In the Resource Settings area
          • To the right of *Resource Pool
            • Select Browse
  1. In the Resource Pool window
    • Select the Seattle cluster icon
    • Select Submit
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • In the Resource Settings area
          • To the right of *Datastores
            • Select Browse
  1. In the Select Instant Clone Datastores window
    • Select the checkbox next to CorpLun-02a
      • Select Submit
    • In the Warning window
      • Select OK
  1. In the Add Pool wizard
    • Next to:-
      1. vCenter Settings
        • Leave VM Compute Profile Settings as default
        • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. Desktop Pool Settings
        • Select the checkbox next to Cloud Managed
        • Under Log Off after Disconnect
          • From the dropdown, select Immediately
          • Select Next
  1. In the Add Pool wizard
    1. Remote Display Settings area
      • Select Next
  1. In the Add Pool wizard
    • Next to:-
      1. Guest Customization
        • Under *AD Container
          • Select Browse
  1. In the AD Container window
    • Expand OU=Corp
      • Select OU=Computers,OU=Corp
      • Select Submit
  1. In the Add Pool wizard
    1. Guest Customization area
      • Select the checkbox next to
        • Allow Reuse of Existing Computer Accounts
      • Select Next
  1. In the Add Pool wizard
    1. Ready to Complete area
      • Select Submit

Part 10 - Configuring Application Pools for Horizon Cloud Services

We will configuring a Application Pools for Site 1  . 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 a Application Pools for Site 1
  1. In your VMware Horizon Console for Site1 Bangalore
    • Note: this should be an open tab in your browser
      • Under Inventory > Desktops
        • Validate that you are indeed in Site 1
        • Note: this should be an open tab in your browser
  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

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

Section 2: Configuring a Application Pools for Site 2
  1. In your VMware Horizon Console for Site2 Seattle
    • Under Inventory > Desktops
      • Validate that you are indeed in Site 2
  1. In the Horizon Administration Console
    • Select Inventory > Applications
  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:-
          • WordPad
          • Internet Explorer
      • 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 the following
          • Assigned POD ID
            • Where XX is your assigned POD ID
            • SEA
        • Wordpad_xx_SEA
        • Internet_Explorer_xx_SEA
      • Select Submit

If you get an error message similar to this , append a letter like A or B to your POD ID and submit again

  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
  1. In the VMware Horizon Management Console
    • On Both Site 1 and Site 2
      • Select Desktops
        • Select the Desktop Pools
          • In the Summary area
            • Scroll down and wait provisioning of your Desktop Pools to complete
            • If the provisioning is still busy
              • You will see a status bar with a percentage rating.
                • you will have to refresh your browser for this to update
  1. In the VMware Horizon Management Console
    • On Both Sites
    • Go to Inventory > Machines
      • Wait for the Desktops being provisioned, show a status of Available

Part 11. Configuring the Horizon Cloud services for Desktop and Application Assignments

We will do a Desktop entitlement In the Horizon Cloud Services. The objective is to include both the Bangalore and Seattle site in this entitlement. In this lab environment we do not have location as a function as both sites are physically located in the same VMware Cloud Director vAPP. The Bangalore and Seattle site definitions in this lab are purely there to show the potential. We will therefore use the HOME SITE function and associate the Bangalore and Seattle sites in this lab with an Active Directory Security Group. That being Sales and Marketing

Creating Desktop a entitlement In Horizon Cloud Services
  1. In the Horizon Universal Console
    • Under Settings
      • Select Users & Groups

It is possible that the Home site configuration is already done

Validate that:

  • Sales is associated with Bangalore
  • Marketing is associated with Seattle

Once this is validated, move on to step 9

  1. In the Users & Groups area
    • Under Home Site Assignment
      • Select NEW
  1. In the Users area
    • Next to Find Users
      • Type sales
    • Select Sales
  1. Under Selected Users/User Groups
    • Select the checkbox, next to Sales
    • Select ASSIGN HOME SITE
    • Select Bangalore
    • At the bottom of the page,
      • select NEXT
      • select FINISH
  1. In the Users & Groups area
    • Under Home Site Assignment
      • Select NEW
  1. In the Users area
    • Next to Find Users
      • Type Market
    • Select Marketing
  1. Under Selected Users/User Groups
    • Select the checkbox, next to Marketing
    • Select ASSIGN HOME SITE
    • Select Seattle
    • At the bottom of the page,
      • select NEXT
      • select FINISH
  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
              • HZNSeattle
  1. In the New Desktop Assignment wizard
    • Next to:
      1. General Information
        • Scroll down until you see
          • Scope*
          • Site Connection Affinity*
  1. In the New Desktop Assignment wizard
    • Next to:
      1. General Information
        • Next to Site Connection Affinity*
          • Select Home Site
        • Next to Home Site Restriction
          • Turn the TOGGLE ON
    • 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:-
          • HZNSea_XX_W10
            • (XX being your  POD Number)
          • 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
        • Configure the following: next to:-
          • Find Users: type Marketing
            • Select Marketing
  1. In the New Desktop Assignment wizard
    • Next to:
      1. Users
        • Review your selections
          • Note!
            • If necessary individual users HOME SITE can be overriden
    • 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 10 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 12: Testing the Horizon Cloud Services Configuration

We will now validate the function of our configurations.

In your lab environment you have two sites. Each site has 3 separate vlans. There is an Internal, DMZ and External VLAN for each site. You have two Windows 10 virtual desktops that are configured with external DNS server addresses. They represent external desktop in this lab environment  

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
      • brokerxx.euc-livefire.com
        • Where xx is your assigned number
    • 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 CorpxxHZN desktop assignment
      • Where xx is your assigned number
  1. On your ControlCenter server
    • On the Desktop
      • Open the Remote Desktops Folder
        • Open Site2
        • Select OK
  1. On the W10Client-02a 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 Fernando
    • In the Password area,
      • type VMware1!
    • Select Login
  1. In the VMware Horizon Client
    • Launch your Desktop entitlement
      • That being CorpxxHZN
        • XX is representative of your assigned number
  1. In the Horizon Client session on W10Client-02a
    • Launch a Command prompt session
    • Type Hostname
      • Observe the naming convention, Note the Computer name is a Seattle abbreviated Desktop
  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 Session tab
          • Note the sessions are on both the Bangalore and Seattle site,

0 Comments

Add your comment

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