Release LoadGen Insight Agent: 1.0.0.12234

Before you upgrade: this release makes Platform mode the only supported runtime mode. An agent that is not connected to a LoadGen Platform now stays idle instead of falling back to LoadGen Cloud, and logs the exact command needed to connect it. Agents still running against LoadGen Cloud must be connected to a Platform with /connect before they resume reporting.

New Features

• Both Services Installed With One Command - /install now registers the LoadGen Control and LoadGen Insight services together, sets Insight to depend on Control, configures delayed automatic start, and sets automatic restart on failure for both. Installing is idempotent, so an existing registration is stopped and replaced rather than failing. Use /control-only to register just the Control service, /insight-path: to point at a specific Insight executable instead of the standard install locations, and /no-start to register without starting.
• Install and Connect in a Single Step - /install accepts the /connect options, so a machine can be installed and enrolled against your Platform in one command.
• New /status Command - Reports the operating mode, Platform URL, masked API key and key type, agent, machine and machine group IDs, onboarding status, last check-in, and the current state of both services. It also warns when service registrations from older installations are still present.
• New /start, /stop and /restart Commands - Control both services in the correct dependency order, starting Control first and stopping Insight first, with /control-only to act on the Control service alone.
• New /uninstall Command - Removes both services along with any registrations left behind by older installations. Add /purge to also delete the agent's configuration data.
• New /connect and /disconnect Commands - These replace the previous platform setup and removal options, which still work as hidden aliases so existing scripts do not break. /connect restarts the Control service automatically on success, so the old "restart the LoadGen Control Service to apply changes" step is gone; use /no-restart to opt out.

Enhancements

• Platform Mode Is Now Required - The agent no longer falls back to LoadGen Cloud when no Platform configuration is present. An unconfigured agent reports its state, logs an error naming the exact /connect command to run, and stays idle without starting any communication. If a Platform configuration is written while the service is running, the agent picks it up on its own, so /connect takes effect without a manual restart. Existing LoadGen Cloud installations go idle after upgrading until they are connected to a Platform.
• Consistent Option Syntax - All commands now accept /name:value, -name:value and --name:value interchangeably, instead of each command supporting a different subset.
• Installation Checks for Administrator Rights Up Front - /install verifies elevation before it starts, rather than surfacing an unclear access-denied error from the Windows Service Control Manager partway through.
• The /login and /encrypt commands have been removed and now print a notice pointing at /connect
• The credential options /secure: and /iv: are still accepted but ignored, with a deprecation warning, so existing deployment scripts keep working. They are no longer needed: both services are installed to run as the local system account
• Service descriptions and the command-line help banner no longer refer to the LoadGen Cloud Suite

Bug Fixes

• Fixed /install Always Failing - Running /install failed with Value cannot be null. Parameter name: s, or with Invalid length for a Base-64 char array or string when the deprecated credential options were supplied. Installation no longer involves credentials at all and completes normally.
• Fixed Agent Self-Update Leaving Services Running - The updater looked for the services under names that did not match the ones the installer registers, so it silently failed to stop them and then tried to replace binaries that were still running and locked. It now uses the registered service names, and stopping a service is handled separately from stopping a process.
• Fixed the Command-Line Tool Reporting Success After a Failure - Every failure path exited with code 0, so installers and deployment scripts could not detect that anything had gone wrong. The tool now returns 0 on success, 1 on a usage error and 2 when an operation fails.
• Fixed /iv: being documented but never actually parsed, and /s: being documented as a switch that never existed
• Unrecognised options are now reported as usage errors instead of being silently ignored