Configuration: Virtualization

Updated

Configuration: Virtualization

Overview

Use this page to register and manage Omnissa Horizon applications and Azure Virtual Desktop resources as load-testing targets. Virtualization Resources is LoadGen's inventory of virtual desktop infrastructure (VDI) endpoints: published applications and desktops on an Omnissa Horizon connection server, or host-pool resources in Azure Virtual Desktop, that a load test can connect to and launch sessions against. Recording each one here means you enter its connection details once instead of re-entering them every time you build a test.

The Horizon connection server or AVD host pool itself must already exist and be reachable before you register it here; this page only stores and manages the reference inside LoadGen, it doesn't provision new desktops or applications. Once a resource is listed here, it becomes available as a session target when you build load profiles for VDI or AVD testing, and the VDI agents that run those sessions connect using the details you've registered.

On this page you see which Omnissa Horizon applications and Azure Virtual Desktop resources are currently registered, refresh the list to pick up changes made elsewhere, and start the add flow for either platform independently.

Key concepts

  • Omnissa Horizon application - A published application or desktop pool hosted on an Omnissa Horizon connection server that LoadGen can launch a session against during a load test. (related: Configuration: LoadGen Agents: VDI Agents)
  • Azure Virtual Desktop resource - A published desktop or application group in an Azure Virtual Desktop host pool that LoadGen can connect to for session-based load testing. (related: Configuration: LoadGen Agents: VDI Agents)

When to use it

  • When you're setting up a load test against a VDI or DaaS (desktop-as-a-service) environment and need to register the connection target before building a load profile.
  • When your organization runs Omnissa Horizon and you need to make a published application or desktop pool available for session-based testing.
  • When you're testing against Azure Virtual Desktop and need to register a host-pool resource before referencing it in a test.
  • When you need to confirm which virtualization resources are already registered before building a new load profile that targets VDI sessions.
  • When a resource was added or removed by another administrator and you need to pull the current list.

Before you begin

  • You need administrative or configuration permissions in LoadGen (a GlobalAdmin-type role) to add or modify virtualization resources.
  • You need a reachable Omnissa Horizon connection server with at least one published application or desktop pool, if you plan to register a Horizon application.
  • You need an Azure Virtual Desktop host pool already deployed in Azure, if you plan to register an AVD resource.
  • Decide which platform you're registering first: Omnissa Horizon and Azure Virtual Desktop are managed in separate panels on this page and don't share entries.

Common workflows

Register an Omnissa Horizon application

Persona: Load-test administrator

  1. Open Configuration, then Virtualization.
    • Expect: The Virtualization Resources page loads with the Omnissa Horizon and Azure Virtual Desktop panels, each showing their current contents.
  2. Click Add Application in the Omnissa Horizon panel.
    • Expect: The add-application flow opens for you to register the application's connection details.
  3. Complete the form, for example naming the application svc.lg.eider, and save it.
    • Expect: The Omnissa Horizon panel now lists the application in place of the 'No Omnissa Horizon applications configured.' message.

Verify: The application appears as an entry under Omnissa Horizon, and it can be selected as a target when you build a load profile for VDI session testing.

Register an Azure Virtual Desktop resource

Persona: Load-test administrator

  1. Open Configuration, then Virtualization.
    • Expect: The Virtualization Resources page loads with the Omnissa Horizon and Azure Virtual Desktop panels, each showing their current contents.
  2. Click Add Resource in the Azure Virtual Desktop panel.
    • Expect: The add-resource flow opens for you to register the host-pool resource's connection details.
  3. Complete the form and save it.
    • Expect: The Azure Virtual Desktop panel now lists the resource in place of the 'No Azure Virtual Desktop resources configured.' message.

Verify: The resource appears under Azure Virtual Desktop in place of the empty-state message, and it's available for AVD session-based load profiles.

Steps

Step 1

Open the Virtualization page under Configuration.

Expected result: The Virtualization Resources page loads showing two panels, Omnissa Horizon and Azure Virtual Desktop, each displaying an empty-state message because no resources have been registered yet.

This is the starting point for registering the virtual desktop or published-application targets you'll use in VDI and AVD load tests.

  • Refresh reloads both panels without opening either add flow.
  • Add Application in the Omnissa Horizon panel and Add Resource in the Azure Virtual Desktop panel each start a separate registration flow for their own platform. Configuration: Virtualization - step 1

Controls reference

Refresh

Reloads the Omnissa Horizon and Azure Virtual Desktop panels from the server.

When to use: Use it after adding or removing a resource in another session, or when you suspect the displayed list is out of date.

Side effects: Read-only: it only reloads the displayed lists and makes no configuration changes.

Add Application

Starts the flow to register a new Omnissa Horizon published application as a virtualization target.

When to use: Use it when you have a Horizon published application or desktop pool you want available for load testing.

Side effects: Mutating: once you complete and save the flow, a new entry appears in the Omnissa Horizon panel, replacing the empty-state message.

Add Resource

Starts the flow to register a new Azure Virtual Desktop resource as a virtualization target.

When to use: Use it when you have an AVD host-pool resource you want available for load testing.

Side effects: Mutating: once you complete and save the flow, a new entry appears in the Azure Virtual Desktop panel, replacing the empty-state message.

Verify the result

Once you've registered a resource, the matching panel, Omnissa Horizon for applications or Azure Virtual Desktop for resources, lists it by name in place of the 'No ... configured.' message, and it becomes available to attach to load profiles that test VDI or AVD sessions. If you click Refresh and the resource still doesn't appear, the registration likely wasn't saved. If a resource you expect to see is missing, confirm you're checking the correct panel, since Horizon applications and AVD resources are tracked separately and never appear in each other's list.

Troubleshooting

  • Symptom: The panel still reads 'No Omnissa Horizon applications configured.' after you add one. Fix: Click Refresh to reload the list; if it still doesn't appear, confirm the registration was saved rather than canceled.
  • Symptom: A resource you registered doesn't show up where you expect it. Fix: Check that you used Add Application for Omnissa Horizon and Add Resource for Azure Virtual Desktop; the two panels manage separate platforms and don't share entries.
  • Symptom: A registered resource isn't available as a target when you build a load profile. Fix: Confirm the resource is actually listed in the matching panel on this page; only resources shown here are available for selection elsewhere.
  • Symptom: Both panels still show empty on a newly configured environment. Fix: This is expected until you register at least one Omnissa Horizon application or Azure Virtual Desktop resource; it isn't an error.
  • Symptom: A change made by another administrator isn't visible on your screen. Fix: Click Refresh to pull the current state from the server; if it still doesn't appear, confirm their change was actually saved.
Was this article helpful?
0 out of 0 found this helpful