Configuration: Add-in Machines

Updated

Configuration: Add-in Machines

Overview

Use this page to review and refresh the add-in machines that extend LoadBots with Citrix and Remote Desktop Services (RDS) capabilities. An add-in machine is a Windows host running Citrix Workspace app or Remote Desktop client software; a LoadBot delegates to it when a scenario must interact inside a Citrix-published application or an RDS session. Without one registered, Citrix- and RDS-based scenarios cannot run.

LoadBots run on LoadGen full agents, and add-in machines extend what those LoadBots can reach. This view does not expose a control to register a new add-in machine, so confirm with your administrator if one needs to be added. Once registered, scenarios that target Citrix or RDS sessions consume it.

On this page itself, you can see every add-in machine currently registered and select Refresh to reload the list without leaving the page. Until at least one is registered, the panel shows an empty state, confirming no Citrix or RDS capability is currently available to your LoadBots.

Key concepts

  • add-in machine - A Windows host running Citrix Workspace app or Remote Desktop client software that a LoadBot delegates to when a scenario must interact inside a Citrix-published application or an RDS session. (related: Configuration: LoadGen Agents: Full Agents)
  • LoadBot - The load-generation process that drives a virtual user through a test scenario; for Citrix and RDS scenarios it hands session-level interaction to a registered add-in machine. (related: Configuration: LoadGen Agents: Full Agents)

When to use it

  • Before scheduling a Citrix or RDS test scenario, to confirm an add-in machine is registered and available to the LoadBot.
  • When a Citrix- or RDS-based scenario fails to start and you need to rule out a missing add-in machine.
  • After an add-in machine is provisioned elsewhere, to confirm it now appears in the platform.
  • When auditing which LoadBots currently have Citrix or RDS capability available.

Before you begin

  • An add-in machine (a Windows host with Citrix Workspace app or a Remote Desktop client installed) must already be provisioned and registered with the platform; this page does not expose a control to create one.
  • A LoadGen account with access to the Configuration section is required to open this page.
  • At least one LoadGen full agent should be configured under Configuration: LoadGen Agents: Full Agents, since add-in machines extend LoadBot capability on those agents.

Common workflows

Confirm whether an add-in machine is available before running a Citrix or RDS scenario

Persona: Load test administrator

  1. Open the Add-in Machines page under Configuration.
    • Expect: The page loads and shows either a list of registered add-in machines or the empty-state message No add-in machines configured.
  2. Select Refresh in the page header.
    • Expect: The list reloads from the server; if a machine was registered since the page last loaded, it now appears in place of the empty-state message.

Verify: If the panel still reads No add-in machines configured after refreshing, no add-in machine is available and Citrix- or RDS-based scenarios cannot run until one is registered.

Steps

Step 1

Open the Add-in Machines page under Configuration.

Expected result: The page loads with the heading Add-in Machines, the description Configure LoadBot capabilities for Citrix and Remote Desktop Services sessions, and an empty-state panel reading No add-in machines configured because none are registered yet.

This is the starting point for confirming whether any LoadBot currently has Citrix or RDS capability available.

  • The empty-state panel explains: Add-in machines extend LoadBots with Citrix and RDS capabilities.
  • A Credentials expiring banner may appear in the corner; it refers to an unrelated API token, not to add-in machines. Configuration: Add-in Machines - step 1

Step 2

Select Refresh in the page header.

Expected result: The page reloads; the Credentials expiring banner clears, and the panel still reads No add-in machines configured, confirming no add-in machines have been registered yet.

Refreshing confirms the list is current without requiring you to leave and re-open the page.

  • Refresh is read-only: it reloads data but does not create or remove any add-in machine. Configuration: Add-in Machines - step 2

Controls reference

Refresh

Reloads the add-in machines list from the server.

When to use: Use it after an add-in machine is registered or removed elsewhere, to confirm this page reflects the current state without navigating away.

Side effects: Read-only: it reloads data but does not create, modify, or delete any add-in machine.

Verify the result

The page is working correctly when it shows either a list of registered add-in machines or the empty-state message No add-in machines configured, and selecting Refresh reloads that view without an error. If you just registered an add-in machine elsewhere and select Refresh, the empty-state message should be replaced by that machine. If the message still reads No add-in machines configured after a Refresh, the registration has not been picked up or has not completed. If Refresh produces no visible change and you expect new machines, recheck the registration source rather than the page itself, since this view has no control to fix a registration problem.

Troubleshooting

  • Symptom: The panel reads No add-in machines configured even though you expect machines to exist. Fix: Select Refresh to reload the list; if it still shows empty, the add-in machine has not been registered with the platform and this page has no control to register one.
  • Symptom: A Credentials expiring banner appears on this page. Fix: This is a general system notice unrelated to add-in machines; it flags an Orders API token nearing expiration. Reissue it under Configuration: Credential Profiles or dismiss the banner.
  • Symptom: A Citrix or RDS scenario fails to launch. Fix: Open this page and confirm at least one add-in machine is registered; if the list is empty, the scenario cannot proceed until one is added.
  • Symptom: No column headers or table are visible on this page. Fix: This is expected while the list is empty; a table with columns appears once at least one add-in machine is registered.
Was this article helpful?
0 out of 0 found this helpful