The following requirements are fundamental and essential for the proper functioning of On-Prem Load Injectors. While these cover the basics, it’s important to note that certain aspects may be intricately tied to specific security policies on the client’s side. These individual nuances will be addressed on a case-by-case basis through technical support requests, as they pertain to client-specific security considerations.

System Requirements

Hardware requirements:

  • 2-core CPU or higher
  • 16 GB RAM
  • 2 GB Hard Drive space

Software prerequisites:

  • On-Prem Add-on enabled in your LoadView account
  • Administrative Access for installation and execution
  • OS Windows Server 2016 or higher x 64bit
  • .NET 7.0 Desktop Runtime (v7.0.11) – Windows x64
  • ASP.NET Core 7.0 Runtime (v7.0.11) – Windows x64
  • Chrome (latest release) or Edge (latest release) for On-Prem Agent registration only
  • Windows Media Player (for Streaming Media tasks only)
  • Remote Desktop service enabled on the machine (for browser-based tests only)
  • The Always Prompt for Password group policy is set to Not Configured
What to Do If Always Prompt for Password Is Enabled

To login to RDP services, On-prem Load Injector requires the Always Prompt for Password group policy to be set to Not Configured. You can check the policy settings in your Group Policy Editor, Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

If the setting is enabled and your policy requires enforcing a password prompt for users logging on to Remote Desktop Services, please follow the recommendations below to grant On-prem Load Injector the ability to remotely access the computer:

1. Enable Remote Desktop on your computer.

2. Enable the Require use of specific security layer for remote (RDP) connections policy as shown below.

Outbound traffic requirements for ASP.NET Core 7.0 Runtime (v7.0.11) – Windows x64

Access to the following resource from the server with the installed On-Prem Agent app:

Outbound traffic requirements for .NET 7.0 Desktop Runtime (v7.0.11) – Windows x64

Access to the following resources from the server with installed On-Prem Agent app:

The addresses should return a web service page:
The addresses should return a blank page:

Configuring On-Prem Load Injector in LoadView

To run on-premise load testing with LoadView, first you need to create and configure an On-Prem Load Injector in your LoadView account:

  1. Login into your LoadView account and go to Manage > On-Prem Load Injectors
  2. Click New Injector on the On-Prem Load Injectors screen.
  3. Give a unique name to the agent, provide a region and an agent description.
  4. If you want to limit payload for load testing in real browsers (Web app/ Web page load test), set the Maximum Load Injector Payload for Real Browser Testing parameter.
  5. Save changes. The agent name will appear in the list of On-Prem injectors.

How to Install On-Prem Load Injector with Setup Wizard

To install On-Prem Load Injectors on your server, follow the steps provided below:

1. From Manage > On-Prem Load Injectors, click Download Installer.

3. Run the installer and follow the steps of the On-Prem setup wizard.

4. Finish On-prem Load Injector setup and register the injector by logging in into your Dotcom-Monitor account.

5. To connect the agent to your account, once logged in successfully, select an injector name from the list of the On-prem injectors created in your LoadView account.

How to Silently Install an On-Prem Agent MSI Package

On-Prem Agent supports command-line installation. Using the recommendation provided in this section, you can install the On-Prem Agent application in Enterprise environments automatically by calling the installer with specific silent install parameters.

Before You Start

To register the agent automatically in LoadView, you need to set up an integration with LoadView. To do this, you must have access to an active LoadView account and create a Unique Identifier with the Load Testing Web API type to use in the authentication request:

  1. Log in to the LoadView account.
  2. In LoadView, create an integration UID under Configure Integrations > Add Integration > Load Testing Web API.
  3. If it is necessary, Whitelist IPs as described in the How to Whitelist IPs for Web API Access article of our wiki.
  4. Click Create Integration and copy the Load Testing Web API Unique Identifier from the Integration UIDs list.

Command-line Installation

A command line to silently install an On-Prem Agent MSI should look like this:

OnPremAgentSetup.msi REGISTRATORCMD="-autoinstall -authtoken=<Load Testing Web API Unique Identifier>" /log 1.txt /qb

Centralized Installation

Centralized installation of On-Prem Agent across multiple servers can be implemented with various group deployment tools. As an example, you can use our lightweight PowerShell script for installing the agent on specific servers within the Active Directory domain.

Note that the script must be run with an account that has administrator rights on the servers on which you want to install the agent.