Is it possible to install the LoadGen Agent manually?

Updated September 16, 2024 11:22

Yes, copy the LoadGen Agent folder to a machine which needs to be a LoadGen Agent:

Find the LoadGen Add-in folder: C:\Program Files\LoadGen\LoadGen Director\LoadGen Agent
Copy the folder to the machine which needs to have the LoadGen Agent installed
The location of the folder must be: C:\Program Files (x86)\LoadGen\LoadGen Agent

When the copy succeeded follow the next steps:

Go to the Windows Start Menu.
Type cmd.
Right-click the Command Prompt shortcut.

Press Yes when the User Account Control window pops up.
In the Command Prompt window go to the correct folder:
cd "c:\Program Files (x86)\LoadGen\LoadGen Agent"
Type "LoadGen LoadBot Agent.exe" /install in the Command Prompt.

Uninstall the LoadGen Agent

Follow steps 1 to 5, as the final step you need to type: "LoadGen LoadBot Agent.exe" /uninstall

LoadGen Agent for VMware Horizon VDI and Azure Virtual Desktop

Release: LoadGen 5.0.0.6281 - 2020-Q3

From LoadGen release 2020-Q3 it's not necessary anymore to install the LoadGen Agent for VMware / Omnissa Horizon or Azure Virtual Desktop manually although you still can by following this article

If you want to manually install the LoadGen Agent on a VMware / Omnissa Horizon or Azure Virtual Desktop VDI machine. First of all, you have to follow steps 1 to 6 in this article. After you have installed the Agent manually follow the additional steps:

Create an XML file in the location of the VDI Agent "c:\Program Files (x86)\LoadGen\LoadGen Agent" named LoadGenLocalAgent.xml
Add the following content to this file:

<?xml version="1.0"?>
<LocalAgentConfig xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Enabled>false</Enabled>
  <DirectorHostName>loadgen01.acme.local</DirectorHostName>
  <DirectorIP>0.0.0.0</DirectorIP>
  <DirectorPort>4841</DirectorPort>
</LocalAgentConfig>

Make sure you change false to true in the <Enabled> tag
Enter the correct values of your LoadGen Director machine within the <DirectorHostName> and <DirectorIP> tags
Restart the LoadGen Agent service