Release LoadGen Api, Appliance and MCP Server: 1.0.0.12252
Release LoadGen Api, Appliance and MCP Server: 1.0.0.12252
LoadGen General
No general changes in this release.
LoadGen Api
API Testing — migration Apply now applies. Fixed the OpenAPI-source migration wizard's Apply saving an unchanged copy of the flow with a success message; it now actually applies the selected auto-fixes (and reports any that couldn't be applied instead of silently skipping them).
Appliance job progress reaches every role. Live progress for appliance jobs on the Appliance page now streams to operators of every role, not only Admins.
[#9400], [#9397] Improved the diagnosability of VMware Horizon / AVD session dial-back so a support bundle shows whether the in-session agents connected back.
[#9399] Improved diagnostic log retention so a repeat of the per-user Agent-pin persistence report can be pinpointed; investigation continues.
LoadGen Appliance
[#9495] Fixed the appliance Updates page showing an old Active version after a newer build was downloaded, so a component read "Updates available" permanently. The most recently downloaded build is now the active one and there is no separate Activate step; this also resolves the related [#9479] (Insight version) and [#9508] (Studio "Access to the path … is denied" during Update-all) reports.
[#9493]"Update all to selected set" now reports every component in its result — which were already on the requested build and which were updated — instead of naming only the ones it changed, so components that were already current are no longer mistaken for skipped.
[#9504] Fixed Reboot on the appliance returning success without actually rebooting; the reboot is now dispatched reliably and a failure is surfaced.
LoadGen Launcher Appliance
[#9499], [#9512] Fixed a freshly created Windows guest having no Run-As profile, so the very first test failed to log in with a "wrong password" error until an operator set the guest password by hand. The platform now provisions the guest's Run-As credential automatically once the guest is reachable.
[#9503], [#9500] Guest Logon and Run-As verification failures now report an actionable reason — and, for an appliance-managed guest, point at the right place to fix it — instead of "Unknown error returned by the LoadBot."
[#9502] A new Windows guest now has its time zone set to match the appliance at creation, instead of keeping the image default.
[#9507] Fixed creating a Windows guest failing on a transient image-download timeout and leaving the guest half-created (previously recoverable only by Destroy). The image pull now retries, and the message names Start guest as the way to resume.
[#9302] Fixed Windows guest KMS activation reporting a failure ("slmgr /ato failed") when the guest was in fact activated; the actual license state is now the authority, so a successful activation is no longer reported as failed.
[#9510] Fixed the Launcher Appliances overview showing "Up to date" while a Windows Full Agent update was pending on that appliance; the overview now judges against the release set and marks a component it couldn't check as unknown rather than up to date.
[#9413] Fixed freshly imaged appliances being unable to be remote-enrolled at all (the image shipped without the factory pairing token enabled). Newly built appliances now enroll from the Platform, and a refused pairing now relays the appliance's real reason.
[#9426] The VMware OVF deployment installer now works against a standalone ESXi host (no vCenter required) instead of failing partway through; a completed import that lands on the wrong network is a warning rather than an aborted deploy.