Release LoadGen Api, Appliance and MCP Server: 1.0.0.12222

Release LoadGen Api, Appliance and MCP Server: 1.0.0.12222

LoadGen General

  • No general changes in this release.

LoadGen Api

  • [#9379] You can now rename a load profile in place instead of cloning and deleting it. The rename cascades across everything that references the profile — its users, agents, datasource, WVD links and inline schedule — so nothing is orphaned. (A profile with an enabled schedule must have it disabled first.)
  • [#9378] You can now rename a user on Configuration → Testing → Users in place, instead of deleting and recreating the entry; the user's profile assignments, password and domain are preserved.
  • [#9401] Fixed the Load Profile wizard's Scenario (Step 4) showing another profile's scenario and raising a spurious "User count mismatch" warning. Each profile now resolves and runs with its own linked scenario instead of a single system-wide active one, and a one-time migration re-links profiles that shared a scenario from an earlier import.
  • [#9399] Fixed re-pinning an already-assigned user to a different agent in a load profile not persisting (it reverted on reopen) for classic (Omnissa / RDS / Citrix) profiles — a follow-up to the first-pin fix in [#9308].
  • [#9396] Fixed setting a Full or VDI Agent's Credential Profile back to "(None)" not being saved (the agent stayed linked, and the credential profile then could not be deleted). The clear now persists.
  • [#9310] Fixed editing a Core Agent's Credential Profile not being saved at all (Save reported success but changed nothing); it now persists, including clearing it to "(None)".
  • [#9397] Fixed a VMware Horizon / AVD (WVD) test being accepted and then silently running a headless web workload (generating no VDI load) when its profile had no Full Agent assigned. Such a run is now blocked up front with a clear reason — these desktop technologies require a Full Agent.
  • [#9400] A Horizon / AVD run where no session connects back now reports which step failed — the Platform could not reach the launcher, versus the launcher was reached but nothing dialed back — instead of one generic message, and it fails fast (rather than waiting the full timeout) when the Platform reached no launcher at all.

LoadGen Appliance

  • [#9273] OS security patching now works end to end. Fixed the appliance's automatic security updates silently not running, and Infrastructure → Appliance → Update OS packages failing with a dpkg lock error (the real cause was the agent's security sandbox, not a lock). Updates now run reliably, kernel security updates are installed (previously skipped) with a clear note when a reboot is required to finish them, and a genuine failure now reports its real cause. On the Launcher Appliance, the bundled Chrome browser used for web testing is kept current too. To catch an appliance up immediately, run Update OS packages and reboot; automatic patching resumes on its own afterwards.
  • [#9319] Fixed VMware Horizon / AVD (WVD) tests still failing to connect after an appliance update because the inbound port those sessions dial back on (4841) was not applied on upgrade — only via a separate manual step. Updating the appliance now publishes the port as part of the update.

LoadGen Launcher Appliance

  • Remote enrollment — add Launcher Appliances from the Platform, in bulk. You can now enroll Launcher Appliances from the Platform instead of opening each appliance's console: a new wizard registers one or many appliances (up to 25 at a time) in a single submission, with a pre-flight that checks each target for reachability, duplicate addresses or hostnames, the 15-character Windows computer-name limit, and whether an appliance is already claimed or its image predates this feature. Each target is reported individually, so one unreachable appliance never fails the whole batch. (Appliances imaged before this release still enroll from the console with an enrollment token.)
  • [#9302] Fixed the automatic evaluation → licensed edition conversion for a Windows Server guest not completing (activation stalled and the guest stayed on the evaluation edition). Conversion and KMS activation now finish in a single Activate, and the result message confirms the licensed outcome.
  • [#9321] Fixed the Launcher Appliances list still showing a just-powered-off appliance as active / running for several minutes (even on a manual Refresh). The list now reflects live reachability and shows an unreachable appliance Offline within seconds, clearing its stale "running" agent indicators.

LoadGen MCP Server

  • No MCP Server changes in this release.
Was this article helpful?
0 out of 0 found this helpful