Configure load profiles

Mode: the create and edit controls described on this page are shown in Expert mode (sidebar footer toggle Mode: Basic / Expert). In Basic mode the page shows only Refresh.

Overview

Use load profiles to define how test users connect to a target environment. This workflow covers the Load Profiles list, the New Load Profile technology selector, and all four wizards behind it: the dedicated RDP, Citrix and Azure Virtual Desktop wizards, and the generic wizard that serves every other technology.

LG050 is the base platform module, shown on Infrastructure: Licensing as API Base and licensed per user (250 users on the demo appliance); Load & Performance Testing runs under it, which is why the Run Test page names LG050 when it is missing. Test scheduling is a separate module, LG053 (Testing Scheduling).

Before you begin

• Testing module is licensed.
• You know which connection technology the test must use: RDP, Citrix, or Azure Virtual Desktop.
• You have the required connection details, such as host names, StoreFront or Gateway URLs, credentials source, and resource names.

Steps

Step 1

In the left navigation, select Load Profiles. Expect the Load Profiles page. On a licensed system, use Refresh to reload profiles, New Profile to add one, or Create Load Profile if no profiles exist.

Step 2

Click New Profile. Expect the New Load Profile page with Select Technology cards: Citrix Basic, Citrix Enhanced, RDP, Azure Virtual Desktop, Omnissa Horizon, Web Testing, Core, Local Client and Test Client (infrastructure testing), grouped as VDI Technologies, Web & Automation and Special Modes.

Step 3

On New Load Profile, select RDP and continue to the RDP wizard. Enter the profile basics, assign users and agents, configure RDP Host and Port, add RD Gateway details when required, set display and session options, select the scenario the profile runs, review the settings, and save.

Step 4

On New Load Profile, select Citrix Basic or Citrix Enhanced and continue to the Citrix wizard. Enter the profile name, choose the Citrix type, configure the connection method, enter the required connection fields such as StoreFront URL, server, PNAgent URL, ICA file path, or login URL, assign users and agents, set display and session options, review the settings, and save.

Step 5

On New Load Profile, select Azure Virtual Desktop and continue to the Azure Virtual Desktop wizard. Enter the profile basics, assign users and agents, configure Azure AD and resource settings, complete the remaining wizard steps, review the settings, and save.

Step 6

In the left navigation, open the Scenarios page. Expect the scenarios list, where saved load profiles can be used when building or editing a scenario. Scenarios are built from an ordered sequence of user phases and idle phases, see the task guide "Create and manage test scenarios".

Step 7

Understand which wizard you landed in, because there are four of them for ten technologies. Citrix Basic and Citrix Enhanced share one wizard, RDP and Azure Virtual Desktop have their own, and every remaining technology opens the same generic wizard with your choice already selected. Clicking the card is what selects it, so you never pick the technology twice.

Step 8

Work through the generic wizard's six steps: Technology, Users & Agents, Connection, Scenario, Advanced and Review. Opening it from a technology card starts you on Users & Agents, because the card already answered step 1. Only the Connection step changes from one technology to the next; every other step is the same whichever card you picked, which is why one wizard can serve six technologies.

Profile Name is required on the Connection step and Next stays greyed out until it has a value.

Step 9

Fill in the Connection step for your technology. The step opens with a connection diagram of the traffic flow, so you can check you are configuring the path you meant before entering anything.

For Omnissa Horizon, configure the connection to the Horizon environment. The Horizon Client must already be installed on the agent that launches the sessions, which is a separate machine from the one hosting the desktops.

For Core, the Core Agent drives the session itself over a command line, so the connection settings describe the command to run rather than a broker to connect through.

For Web Testing, the Core Agent drives a browser (Chrome, Edge or Playwright) and the target is the web application itself.

Step 10

Fill in the technology-specific step of a dedicated wizard. Each one asks for the connection details its own technology needs, and they sit at different points in each wizard, so count the steps in the wizard you are actually in rather than carrying a number over from another.

The Citrix Connection step is where you choose the connection method and enter the matching details, such as the StoreFront URL, the server, the PNAgent URL or an ICA file path.

The RDP Connection step takes the RDP host and port.

RDP then gives RD Gateway a step of its own, so a gateway deployment is configured separately from the host itself. The step only requires a gateway address when the gateway is enabled.

The Azure Virtual Desktop wizard replaces Connection with an Azure step for the Azure AD and resource settings.

Verify the result

The saved load profile appears in the Load Profiles list and can be selected from the Scenarios workflow. If the page shows Unlock Load & Performance Testing with Module LG050, the Testing module is not active and the load profile workflow is blocked.

Troubleshooting

• If the Load Profiles page shows Unlock Load & Performance Testing, activate Module LG050 before creating or editing load profiles.
• If the Continue button is not available on New Load Profile, select a technology card first.
• If a wizard blocks the next step, complete the required fields marked with an asterisk, such as Profile Name, RDP Host, StoreFront URL, Citrix Server, Published Application, PNAgent URL, ICA File Path, External Login Script, or Login URL.
• If Citrix resources cannot be fetched, verify the URL, credentials, domain, and selected connection method, then use Fetch Resources again.
• If a password warning appears for a selected test user, enter the password required for that user before saving.

Related articles

• Create and run a load test
• Create and manage test scenarios
• Testing: Load Profiles
• Configuration: Virtualization
• Configuration: Add-in Machines