Release LoadGen Api, Appliance and MCP Server: 1.0.0.12257

Release LoadGen Api, Appliance and MCP Server: 1.0.0.12257

LoadGen General

  • No general changes in this release.

LoadGen Api

  • [#9400] VMware Horizon / AVD test failures now report a specific reason and name the LoadGen VDI Agent (the in-session agent) explicitly, leading with the most useful check — whether that agent is installed and configured on the session host — instead of a generic port-connect message.
  • [#9399] Fixed a pinned per-user agent not being added to its load profile's active agent pool, so the pinned user's agent wasn't actually usable for the run; and corrected a misleading validation message that told operators to swap a Core Agent when the profile in fact had no agents assigned. (A separate reported case where the per-user Agent still reverts on reopen remains under investigation.)

LoadGen Appliance

  • [#9521] Fixed the appliance Debug tab's per-file download saving a small HTML file instead of the actual log (for example the API log). The download now returns the real file; the same fix covers the debug-archive download.

LoadGen Launcher Appliance

  • [#9520] Windows guest templates can now carry Hosts entries and Trusted certificates (for example an internal CA), and a template assigned during enrollment now applies itself automatically as soon as the new guest becomes reachable — instead of having to be re-entered per guest and remembered to apply once the guest exists (a 20–40 minute wait). The hosts and certificate steps run before software installs, so an installer that needs an internal name to resolve or a trusted CA works.
  • [#9502] Fixed a Windows guest's time zone / clock drifting out of sync with the appliance — the guest could show UTC while the appliance was on local time, and revert after every restart. The guest clock is now anchored correctly, the Sync action also corrects a running guest, and the Windows tab reports the actual clock skew rather than only the zone label.
  • [#9519] The Windows guest's status now verifies that the RDP port (3389) is actually listening inside the guest (the same way the Full Agent port is checked), so a dead RDP listener is diagnosable instead of assumed, and the guest's first boot explicitly enables Remote Desktop.

LoadGen MCP Server

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