Release LoadGen Api, Appliance and MCP Server: 1.0.0.12228
Release LoadGen Api, Appliance and MCP Server: 1.0.0.12228
LoadGen General
No general changes in this release.
LoadGen Api
[#9419] Fixed Generate PDF report ending with "Report rendering produced no output" and no downloadable file. Report rendering now has the fonts it needs, and when a render does fail the dialog shows the real reason instead of a generic message.
[#9412] Fixed the Unlock button on a Full Agent reporting "Agent unlocked successfully" without actually unlocking the session. Unlock now runs through the same credentialed path as logon and reports the real outcome, including a clear failure when the agent has no credential profile.
[#9411] Fixed detaching a load profile's Scenario via Create new scenario (Step 4) not sticking — the overview kept showing the old scenario after saving. Clearing the scenario now persists.
Insight agent licensing now reflects your actual license. The Insight agents "X / Y" limit is now read from your Insight license entitlement instead of a fixed placeholder — both the badge and enrollment enforcement. If a deployment enrolled more agents than its license allows (against the old placeholder), existing agents keep working, but no further agents can be assigned until the license is raised or agents are released.
LoadGen Appliance
[#9418] Fixed Infrastructure → Appliance → Update OS packages failing to start on the main (platform) appliance, and added OS-update visibility there: the appliance now reports pending OS and kernel security updates and whether a reboot is required to finish applying them. A patched-but-not-rebooted appliance still runs the old kernel, so a security scan keeps reporting it until you reboot — to bring an appliance current, run Update OS packages and then Reboot.
LoadGen Launcher Appliance
[#9409] Fleet update visibility and bulk updates. Launcher Appliances now report their installed OS packages, Chrome / Edge browser versions and reboot state to the Platform, which flags which appliances are behind (browser versions are checked centrally, so the appliances make no extra outbound calls). You can review per-appliance and fleet-wide drift and apply OS and browser updates across selected appliances in one action; an appliance running a test is skipped unless you override.
[#9420] Fixed the RAM (GB) value entered when creating a Windows guest not being honored (a request for 3 GB was silently raised to 4 GB). The requested value is now used exactly, and an out-of-range value is rejected up front with a clear message instead of being quietly changed.
[#9302] Fixed Windows guest KMS activation reporting a failed edition conversion that had in fact succeeded (leaving the operator to reboot and retry by hand). The evaluation → licensed edition conversion, reboot and activation now complete in a single Activate.
[#9413] Fixed enrolling freshly imaged appliances from the Platform failing every pre-flight row with an SSL error. The enrollment wizard now detects each appliance's connection scheme automatically, so newly built appliances enroll correctly.
[#9415] Fixed the remote-enrollment Platform URL field: leaving it blank previously failed the pre-flight check with an internal address the operator never entered. Blank now resolves to the platform's configured public address, or asks for one when none is configured.
The licensed-appliance count now reflects your actual license. The Launcher Appliances "X / Y licensed" limit is now read from your license entitlement instead of a fixed placeholder — both the badge and approval / enrollment enforcement. A deployment that enrolled more than its license allows keeps its existing appliances but cannot approve more until the license is raised.