10. Configuring Horizon Cloud Pod Architecture

This lab requires you to complete all the labs starting from Lab no. 2 to Lab no. 6 and then Lab no.8  before starting this lab.

In this section we will be enabling Horizon Cloud Pod Architecture for a Multi-site implementation.
In a previous lab you have already enabled a 3rd Global Load-balancer which is a requirement

Part 1. Cleaning up Local Entitlements for Desktop Pools

To complete our Day 1 Tasks, our Desktop Pools were configured with local entitlements.
Specific Local Entitlements will be cleared on both Site 1 and Site 2.
We will clean this out before we start off with implementing Horizon Cloud Pod Architecture

Step 1. Cleaning out Local Entitlements on Site 1
  1. On your ControlCenter server
    • Open your Site 1 browser
    • In the favourites bar
      • select the Horizon Site 1 shortcut
    • In the Horizon login page
      • In the Username area
        • enter administrator
      • In the Password area
        • enter Pa$$w0rd
      • select SIGN IN
  1. In the Horizon Admin Console
    • In the Side Menu pane
      • expand Inventory
        • select Desktops
  1. In the Desktop Pools area
    • next to W11-BLR-INST
      • select the Checkbox
    • next to ENTITLEMENTS
      • from the dropdown
        • select Remove Entitlements
  1. In the Remove Entitlements window
    • next to
      • Developers/Techseals.co
        • select the checkbox
          • select OK
    • when prompted with the Remove Entitlements window
      • select OK
Step 2. Cleaning out Local Entitlements on Site 2
  1. On your ControlCenter server
    • Open your Site 2 browser
    • In the favourites bar
      • select the Horizon shortcut
  1. In the Horizon login page
    • In the User Name area
      • enter administrator
    • In the Password area
      • enter Pa$$w0rd
    • select SIGN IN
  1. In the Horizon Admin Console
    • In the Side Menu pane
      • expand Inventory
        • select Desktops
  1. In the Desktop Pools area
    • next to W11-SEA-INST
      • select the Checkbox
    • next to ENTITLEMENTS
      • from the dropdown
        • select Remove Entitlements
  1. In the Remove Entitlements window
    • next to
      • Developers/techseals.co
        • select the checkbox
          • select OK
      • In the Remove Entitlements window
        • select OK

Part 2. Deploying Cloud Pod Architecture for multi-site

We will Initialize Cloud Pod Architecture on Site 1 and do a Federation Join on Site 2

Deploying Cloud Pod Architecture
  1. On your Site 1 Browser (Bangalore)
    • In the Horizon Admin Console
      • In the Inventory pane
        • under Settings
          • select Cloud Pod Architecture
  1. In the Cloud Pod Architecture window
    • select Initialize the Cloud Pod Architecture feature
    • In the Initialize window
      • select INITIALIZE

wait for the initialization to complete on all Connection servers on Site 1, before moving on

  1. On your Site 2 (Seattle) Browser
    • In the Horizon Admin Console
      • In the Inventory pane
        • under Settings
          • select Cloud Pod Architecture
  1. In the Cloud Pod Architecture window
    • select Join the pod federation
  1. In the Join window
    • under Connection Server (host name or IP address)
      • enter horizon-01a.techseals.co
    • under User name(domain\username)
      • enter techseals.co\administrator
    • under Password
      • enter Pa$$w0rd
    • In the bottom right corner
      • select JOIN
  1. On your ControlCenter server
    • Switch back to your Site 1 Horizon Admin Console session
      • In the Cloud Pod Architecture window
        • top right corner
          • select refresh
      • Note that you have two Pods in the same Default First Site
  1. In the Horizon Admin Console
    • In the Inventory pane
      • under Settings
        • select  Sites
  1. In the Horizon Admin Console
    • In the Inventory pane
      • In the Sites window
        • next to Default First Site
          • select the radio button
            • select EDIT
  1. In the Edit Site window
    • next to *Name
      • edit Default First Site
        • to Bangalore
        • select OK
  1. In the Horizon Admin Console
    • In the Inventory pane
      • In the Sites window
        • select Add
  1. In the Add Site window
    • next to * Name
      • type Seattle
      • select OK
  1. In the Sites window
    • next to Bangalore
      • select the radio button
    • under Pod
      • next to Cluster-HORIZON-02A
        • select the radio button
        • select EDIT
  1. In the Edit Pod window
    • next to Site
      • from the dropdown
        • change Bangalore
          • to Seattle
      • select OK
  1. In the Sites window
    • note both Seattle and Bangalore each have their own POD

Part 3: Enable Global Entitlements for  Cloud Pod Architecture for Instant Clone Windows Desktops

This session is divided into 2 steps

  • Step 1. We will configure a Global Desktop Entitlement for on Site 1
  • Step 2. We will configure Global Desktop Entitlement for on Site 2
Step 1. Configuring an Instant Clone Global Desktop Entitlement for Site 1
  1. On your ControlCenter server
    • Site 1 Chrome Browser
      • Horizon Admin Console
        • In the Inventory
          • select Global Entitlements
  1. In the Global Entitlements area
    • select Add
  1. In the Add Global Entitlement window
    • next to :
      1. Type
        • leave Desktop entitlement as default
    • In the bottom right-corner
      • select NEXT
  1. In the Add Global Entitlement window
    • next to :
      1. Name and Policies
        • under Name
          • enter Enterprise Corp Instant Clone
        • under Display Name
          • enter Enterprise_Desktop
  1. In the Add Global Entitlement window
    • next to :
      1. Name and Policies
        • under Policies > User Assignment
          • next to Floating
            • select the radio button
        • under Default Display Protocol
          • from the dropdown
            • select Horizon Blast
        • In the bottom right-corner
          • select NEXT
  1. In the Add Global Entitlement window
    • next to :
      1. Users and Groups
        • under Add users or groups to the global entitlement
          • select ADD
  1. In the Find User or Group window
    • in line with Name/User Name
      • next to Starts with
        • enter Sales
    • under Description
      • select FIND
    • under Name
      • next to sales
        • select the checkbox
    • in the bottom right-corner
      • select OK
  1. In the Add Global Entitlement window
    • next to :
      1. Users and Groups
        • under Add users or groups to the global entitlement
          • select ADD
  1. In the Find User or Group window
    • in line with Name/User Name
      • next to Starts with
        • enter Developers
    • under Description
      • select FIND
    • under Name
      • next to Developers
        • select the checkbox
    • in the bottom right-corner
      • select OK
  1. In the Add Global Entitlement window
    1. Users and Groups
      • under Add users or groups to the global entitlement
        • select ADD
  1. In the Find User or Group window
    • in line with Name/User Name
      • next to Starts with
        • enter IT support
    • under Description
      • select FIND
    • under Name
      • next to IT Support
        • select the checkbox
    • in the bottom right-corner
      • select OK
  1. In the Add Global Entitlement window
    1. Users and Groups section
      • select NEXT
  1. In the Add Global Entitlement window
    1. Ready to Complete section
      • in the bottom right-corner
        • select FINISH
  1. In the Global Entitlements window
    • select Enterprise Corp Instant Clone
  1. In the Enterprise Corp Instant Clone window
    • select the Local Pools tab
  1. In the Enterprise Corp Instant Clone window
    • In the Local Pools tab area
      • select ADD
  1. In the Assign Pools -  Enterprise Instant Clone window
    • under ID
      • next to W11-BLR-INST
        • select the checkbox
    • select ADD
  1. In the Global Entitlements window
    • Note you now have a Global Desktop Entitlement
      • called Enterprise Corp Instant Clone
Step 2. Configuring an Instant Clone Global Desktop Entitlement for Site 2
  1. On your ControlCenter server
    • Site 2 Chrome Browser
      • Horizon Admin Console
        • In the Inventory
          • select Global Entitlements
  1. In the Global Entitlements window
    • select  Enterprise Corp Instant Clone
  1. In the Enterprise Corp Instant Clone window
    • select the Local Pools tab
  1. In the Enterprise Corp Instant Clone window
    • Local Pools tab
      • select ADD
  1. In the Assign Pools - Enterprise Corp Instant Clone window
    • next to W11-SEA-INST
      • select the checkbox
      • select ADD
  1. In the Enterprise Corp Instant Clone window
    • select the Summary tab
      • Review the configurations

Part 4: Testing Cloud Pod Architecture with Global Server and Local Server Load balancing

In this test

  1. We will first do a local login and test our Global Entitlement
  2. Next note the result and see how with Cloud Pod Architecture, Global and Local Server Loadbalancing works in a  simulation of a resource constraint or disaster scenario for Site 1

Unless you login directly to a Broker, remember Cloud Pod Architecture cannot work on its own without have a local and possibly a Global Server Load balancer.

Test 1. Logging into Site 1 and Testing your Global Entitlement with Global Server and Local Load-balancing
  1. On your ControlCenter server
    • On the Desktop
      • Open the Remote Desktops Folder
        • open Site1
          • launch W11Client-01a.rdp

you should be automatically logged in as [email protected] with the password Pa$$w0rd

  1. On your  W11Client-01a
    • from the Desktop
      • launch the Horizon Client shortcut
    • on the Horizon Client,
      • select the corp.techseals.co url
        • In the Ncorp.techseals.co icon area,
          • select the more icon
            • from the dropdown
              • select Connect
  1. In the Horizon Client textbox
    • in the Enter your user name area
    • in the Enter your password area
      • enter Pa$$w0rd
        • select Login
  1. On the Horizon Client,
    • In the Enterprise_Desktop icon area,
      • select the more icon
        • from the dropdown
          1. select Display > Window - Small
          2. select Launch
  1. In the Horizon virtual desktop session
    • from the Taskbar > Search area
      • enter Command
    • in the pop-up window
      • in the Command Prompt area
        • select Open
  1. In the Command Prompt window
    • enter hostname
    • with keyboard
      • select ENTER

Note that you are consuming a virtual desktop which does not have SEA in the computer name and the desktop colour is what was configured for Site 1

  1. In the Horizon desktop session
    1. select the More Icon
    2. from the dropdown
      • select Logoff Desktop
Test 2. Logging into Site and simulating an unavailability scenario where Desktop resources are not available on Site 1
  1. On your ControlCenter server
    • On the Desktop
      • launch the Site1-Bangalore browser
  1. On the Site 1 browser
    • from the Favourites bar
      • select the Horizon Site 1 shortcut
    • In the Horizon login
      • user name area
      • enter administrator
    • in the password area
      • enter Pa$$w0rd
    • select SIGN IN
  1. In the Horizon Admin Console
    • left menu bar
      • under Inventory
        • select Desktops
    • in the Desktop Pools area
      • select W11-BLR-INST
  1. In the W11-BLR-INST Properties area
    • select the Machines tab
  1. In the W11-BLR-INST Properties area
    • Machines tab area
      • from the middle Information bar
        • next to Machine
          • select the checkbox
      • from the middle Commands bar
        • select MORE COMMANDS
          • from the dropdown
            • select Enter Maintenance Mode
        • In the Enter Maintenance Mode window
          • select OK
  1. In the W11-BLR-INST Properties area
    • Machines tab area
      • from the middle Information bar
        • next to Machine
          • select the checkbox
      • from the middle Commands bar
        • select MORE COMMANDS
          • from the dropdown
            • select Shutdown
        • In the Shutdown Virtual Machines(s) window
          • next to Terminate Active Sessions if any
            • select the checkbox
          • select OK
  1. On your ControlCenter server
    • switch to your W11Client-01a RDP session
  1. On the Horizon Client,
    • In the Enterprise_Desktop icon area,
      • select the more icon
        • from the dropdown
          • select Launch
  1. In the Horizon virtual desktop session
    • from the Taskbar > Search area
      • enter Command
    • in the pop-up window
      • in the Command Prompt area
        • select Open
  1. In the Command Prompt window
    • enter hostname
    • with keyboard
      • select ENTER

Note that you are consuming a virtual desktop which has SEA in the computer name configured for Site 2

Also you should have a purple Desktop Colour.

 We have just demonstrated how Bussines Continuity is maintained in the event of an issue in one Pod we can leverage desktop Capacity running either locally remotely with Cloud Pod Architecture

  1. In the Horizon desktop session
    1. select the More Icon
    2. from the dropdown
      • select Logoff Desktop
  1. On your Control Center server
    • switch to your Site 1 Horizon Admin Console
    • In the W11-BLR-INST Properties area
      • Machines tab area
        • from the middle Information bar
          • next to Machine
            • select the checkbox
        • from the middle Commands bar
          • select MORE COMMANDS
            • from the dropdown
              • select Exit Maintenance Mode
          • In the Exit Maintenance Mode window
            • select OK

wait for about 2 minutes

  1. On the W11-BLR-INST Properties area
    • Machines tab area
    • scroll across to the end of the Middle Information Bar
      • under Status
      • the Status should have changed from Provisioned to Available

This Concludes the Horizon Cloud Pod Architecture Lab

0 Comments

Add your comment

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