Migrating LoadGen On-Premises configuration to a new machine

Introduction

When moving your LoadGen On-Prem management components (Director, Studio, Analyzer) from one server to another, it’s critical to maintain version alignment and preserve your configuration data. This guide walks you through a reliable migration process to minimize downtime and configuration drift.

Prerequisites

• Confirm that the source and target machines run the same LoadGen version (e.g., 5.x.x). Migrating across versions can lead to configuration incompatibilities.
• Ensure you have local administrator permissions on both machines.
• Back up your SQL Server database and configuration before proceeding, in case a rollback becomes necessary.

Migration Steps

1. Install the exact same version of LoadGen on the target machine as is currently running on your source machine.

2. On the source server, copy the following directory (including sub-folders and files):%ProgramData%\LoadGen Transfer it to the equivalent location on the target machine.

3. On the source server, also copy all data from:C:\Users\Public\Public DocumentsTransfer these files to the same path on the target server.

4. Update any machine-specific references in your configuration as required (e.g., hostname of Director, SQL server name, file share paths).

5. On the target machine, verify that services start correctly and the Director connects to your existing database.

6. Run a test profile or workload to confirm Agent connectivity and that your recorded workloads and user flows behave as expected.

Post-Migration Verification

• In LoadGen Director, verify that all Agents, Workloads, User Types, and Machine Groups are visible and correctly configured.
• In Studio, open a recorded workload and test launch from the new machine to confirm scripts operate without errors.
• In Analyzer, run a quick historical query to verify that your data tables are intact and accessible.

Troubleshooting

• If the Director fails to connect to the database, verify that the SQL connection string and credentials were correctly migrated.
• If Agents appear offline, ensure network connectivity and that firewall rules are unchanged between source and target.
• If workloads fail or recordings error out, verify that the version of LoadGen on both machines indeed matches, and that the %ProgramData%\LoadGen folder contents were fully copied.