How to Set Up a Proxy for the LoadGen Cloud Agent for End-to-End Monitoring

In environments where internet access is managed through a proxy, configuring your LoadGen Agent for End-to-End Monitoring to utilize this proxy is essential for its operation. This guide will walk you through setting up a proxy specifically for the Local System account, which the LoadGen Agent uses to perform its tasks. If your setup requires configuring a proxy for a different account, please refer to the latter section of this article.

Setting up Proxy for Local System Account

  1. Download the Psexec tool from the Microsoft website.
  2. Open the Start menu, type cmd, right-click on Command Prompt, and select "Run as administrator".
  3. In the administrator command shell, execute the following command to open a new command shell under the Local System authority:
    PsExec -i -s cmd.exe
  4. To verify you're running as the Local System, type whoami in the new command shell. It should return "nt authority\system".
  5. Within the Local System command shell, enter inetcpl.cpl to open Internet Properties.
  6. Navigate to the Connections tab and click on LAN settings.
  7. In the Proxy server section, input your proxy's address and port number.
  8. If your setup requires bypassing the proxy for local addresses, make sure to tick the checkbox labeled "Bypass proxy server for local addresses".
  9. Click on Advanced if you need to specify exclusions. Here, you can enter URLs that shouldn't use the proxy in the Exceptions section. Press OK once done.
  10. Click OK to apply the proxy settings and close all open command shells.
  11. Restart the LoadGen Cloud Agent service.

By following these steps, you have successfully configured the proxy settings for the Local System account. This setup is crucial for the LoadGen Agent for End-to-End Monitoring to operate correctly in environments that use a proxy for internet access.

For any assistance or further information on configuring your LoadGen Cloud Agent, please refer to our comprehensive support documentation or contact our support team.

Was this article helpful?
0 out of 0 found this helpful