Lab 7: Entitle users to a desktop pool

Objective and Tasks

In this lab, you will entitle users to a desktop pool and test connectivity.

  1. Log in to the Horizon admin console (Horizon-01a).
  2. Entitle a user group to a desktop pool.
  3. Validate desktop pool launch for entitled users/groups.
Expand or collapse content Task 1: Log in to the Horizon admin console

You may already have launched and be logged into the Horizon admin console.

  1. Open the Horizon admin console for horizon-01a.
    • On your ControlCenter desktop, open the Google Chrome browser.
    • Click the bookmark on the bookmark bar for Horizon-01a
    • This will connect you to the Horizon administrator console at https://horizon-01a.omnissatraining.com/admin
  2. Login to the Horizon admin console.
    • Username: administrator
    • Password : Pa$$w0rd
    • Domain: OmnissaTraining
Expand or collapse content Task 2: Entitle users to a desktop pool

You can entitle both users and user groups to a desktop pool. In this task, you will entitle a user group to the desktop pool, Win11-Site1.

  1. View the details of a desktop pool
    • In the Horizon admin console navigate to Inventory > Desktops
    • Click on the entry with an ID of Win11-Site1.
  2. Start the entitlement wizard.
    • Click on the Entitlements button, and select Add Entitlements.
  3. Select the Users and Groups to entitle.
    • Click ADD.
    • In the row Name/User Name enter horizon in the right-hand box, and click FIND.
    • Tick the box for the row Horizon-Students that is displayed, and click OK.
  4. Close the entitlement wizard.
    • Click OK.

If you still see a warning that No users or groups are entitled to this pool, refresh the page using the circular arrow in the top-right.

You can add multiple entries for different users and groups to an entitlement.

Expand or collapse content Task 3: Validate desktop pool launch for entitled users/groups

You should always test access and behavior of a desktop pool before giving users access to it.

  1. Launch the Omnissa Horizon Client.
    • From the desktop of ControlCenter desktop, double click the Omnissa Horizon Client icon.

As this is the first time this Horizon Client has connected to this new Horizon 8 pod, you need to add a new server entry to the client.

  1. Add a new Horizon 8 Pod to the Horizon Client.

In this lab, you will use the Connection Server FQDN. In a production deployment of a pod with multiple Connection Servers the load balancer virtual IP address or name would be used instead of an individual Connection Server address.

  1. Login and authenticate with an assigned user from the Horizon-Students group.
    • Username: Student1
    • Password : Pa$$w0rd
    • Click Login.
  2. Once logged in, you will see a tile for the entitled desktop pool Win11-Site1
  3. Launch the virtual desktop.
    • Click on the 3 dots on the pool tile for Win11-Site1 and click Launch.
    • Alternatively you can double-click on the tile.
  4. Confirm successful desktop launch.
    • Ensure the virtual desktop opens successfully and the user is logged into the Windows desktop.
    • Verify that the desktop is functioning properly and the user can interact with the environment (login, desktop display, basic functionality).
  5. Monitor user session from the Horizon admin console.
    • Switch back to the ControlCenter desktop and the Horizon admin console tab in the Google Chrome browser.
    • Navigate to Inventory > desktops > Win11-Site1
    • Select the Machines tab.
    • On one of the desktops you will see a Connected User (omnissatraining\student1)
    • Scroll to the right and check the Status. The same machine clone should display Connected.
  6. Logout of the virtual desktop.
    • Switch back to the virtual desktop session for Win11-Site1
    • Use Windows > Student 1 > Sign out
    • Alternatively, you can use the Horizon menubar at the top of the screen, selecting the three dots (...), then Logoff Desktop, and confirm with OK.
  7. Close the Omnissa Horizon Client.

This confirms that user entitlements, pool provisioning, and connectivity are functioning correctly.

This concludes this lab.

0 Comments

Add your comment

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