Lab 18: Create a published app on demand

Objective and tasks

In this lab, you will learn how to extend the functionality of Horizon 8 by integrating it with an App Volumes Manager instance to publish applications that are delivered on demand.

You will also understand how to register an App Volumes Manager instance with the Horizon 8 pod, associate it with an RDS farm, and then publish applications that are delivered by App Volumes on-demand.

  1. Login to Horizon Admin Console.
  2. Register an App Volumes Manager instance with a Horizon 8 pod.
  3. Associate a registered App Volumes Manager instance with a RDS farm.
  4. Create an application pool using an App Volumes delivered package.
  5. Verify the launch of applications from the Horizon Client.

When a user selects an application icon in the Horizon Client, the corresponding application package is dynamically attached to the Remote Desktop Session Host (RDSH) running their session. No local installation of the application on the host is required.

Expand or collapse content Task 1: Login to 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
  2. Login to the Horizon admin console.
    • Username: administrator
    • Password : Pa$$w0rd
    • Domain: OmnissaTraining
Expand or collapse content Task 2: Register an App Volumes Manager instance with a Horizon 8 pod

In this task, you will register an App Volumes Manager instance to a Horizon 8 pod.

This lab uses the previously installed Horizon-01a Connection server. You will integrate App Volumes Manager, AppVol-02a, which already has App Volumes Manager installed, configured, and has some sample packages.

  1. Start the Add App Volumes Manager wizard.
    • In the Horizon admin console navigate to Settings > Servers.
    • Click ADD.
  2. Enter the required information for the App Volumes Manager instance.
    • Server Address: appvol-02a.omnissatraining.com
    • Port: 443
    • User Name: administrator
    • Password: Pa$$w0rd
  3. Complete the wizard.
    • Click OK.

In a production environment with multiple App Volumes Managers servers in the instance, you would use the FQDN of the load balancer address for the App Volumes Managers.

Expand or collapse content Task 3: Associate a registered App Volumes Manager instance with a RDS farm

Now associate the registered instance of App Volumes Manager with an RDS farm.

  1. Locate and select the server farm that you want to update.
    • In the Horizon admin console navigate to Inventory > Farms
    • Tick the box next to the farm with the ID RDSH-Farm.
  2. Start the Associate App Volumes Manager wizard.
    • Click on the MORE COMMANDS button.
    • Select Associate App Volumes Manager from the drop-down menu.
  3. Select the desired App Volumes Manager instance using the drop-down.
    • App Volumes Manager: appvol-02a.omnissatraining.com
    • Click OK.

The App Volumes Manager Server will now be associated with the RDS farm. This allows it to be used by that farm when creating  application pools.

Expand or collapse content Task 4: Create an application pool using an App Volumes delivered package

Add application pools that are App Volumes packages that are attached on-demand to an RDS farm.

  1. Start the new application pool wizard using the App Volumes Manager option.
    • In the Horizon admin console navigate to Inventory > Applications
    • Click ADD.
    • Select Add from App Volumes Manager.
  2. Select the RDS Farm to use.
    • Ensure that the previously created farm RDSH-Farm is selected in the drop-down.
  3. Select the App Volumes Manager Applications you want to publish.
    • In the Select App Volumes Manager Applications section, select Notepad++.

In environments where there are many applications presented by the App Volumes instance, you can use the filter field.

  1. Review the other configuration options available.
    • Investigate the other options on this screen.
    • Click NEXT.

Note that the Entitle Users After Adding Pool option is selected by default. This will cause the user entitlement wizard to launch after you complete the application pool wizard. You can also use the entitle entitlement wizard separately from this sequence.

  1. Define the application names and complete the wizard.
    • On the Edit Applications screen, you can change the ID and Display Names for the chosen application.
    • Leave as the defaults and click SUBMIT.

Entitle the users and groups to the application pool you created.

  1. 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.
  2. Close the entitlement wizard.
    • Click OK.

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

  1. Verify the application is shown under Application Pools.
Expand or collapse content Task 5: Verify the launch of applications from the Horizon Client

In this task, the user will launch applications that are dynamically attached to an RDS server.

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

Depending on which other labs you have already completed, you may have to add a new server entry to the client for your new Horizon 8 pod.

If you have already added it to the Horizon Client, just double-click the horizon-01a.omnissatraining.com tile to connect.

  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.
    • Username: Student1
    • Password : Pa$$w0rd
    • Click Login.
  2. Review the entitlements for Student1 in the Horizon-01a pod, noting that Notepad++ now present.
  3. Launch a published application delivered by App Volumes.
    • Click on Notepad++ to launch the application.

At this point the App Volumes Manager is used to attach the Notepad++ application to an RDSH host for your session.

  1. Close the Horizon session.
    • Close the Notepad++ application you launched.
    • Close the Horizon Client.

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.