What is the Private Agent?

Monitoring from global distributed locations helps to see your applications as perceived by your end-user community. However, in some situations, companies would like to check response times and availability of their application within their local network. There are two cases in which customers decide to use a private agent:

  1. The application under monitoring is not available from the Internet.
  2. Performance and uptime comparison – LAN vs. WAN.

Both are good reasons and therefore we provide a Private Agent that can be installed on a dedicated Windows Server within your data center. Once the private agent has been installed you can configure monitoring devices to be executed on this internal private agent.

This guideline walks you through all steps required to prepare the installation, execute the setup and configure your devices to use the private agent. Additionally, it provides some answers to frequently asked questions.

System Requirements

Hardware requirements:

  • 2-core CPU or higher
  • 16 GB RAM
  • 2 GB Hard Drive space
  • OS Windows Server 2008 R2 or higher x 64bit

Software prerequisites:

  • .NET Framework 4.7
  • Windows Media Player (for Streaming Media tasks only)
  • Remote Desktop service enabled on the machine (for UserView/BrowserView tasks only)
  • Administrative Access for installation and execution
Make sure the Private Agent is enabled in your account before you continue.
Preparation of your Private Agent Installation

We highly recommend using a dedicated Windows Server for your private agent installation. Depending on the number of monitoring devices you are going to simulate on your private agent, the load can be high and can have an impact on CPU or Memory utilization of this server.

Follow all preparation steps below once you’ve selected your private agent server:


Step Details
1 Open Server Manager

Click the Server Manager icon on the desktop.


Click Add roles and features on the Server Manager Dashboard.


In the Add Roles and Features Wizardnavigate through tabs to the Features tab.

4. Optionally (Streaming Media monitoring)

Select and expand User Interface and Infrastructure, and then select all enclosed check boxes below. 

5. Optionally (Streaming Media monitoring)

Select Media Foundation


Select .Net Framework 4.7 Features Installed and all enclosed items.


Click Install.

8 Restart your Windows Server.

Install Private Agent on your Server

Once all preparation steps are done you can install the private agent software on your server. This section covers all installation steps. Follow those instructions step by step.

Step Details
1 Account with Admin Permission You need an account with Admin permission for this Private Agent installation. Ask your domain admin to get administrative rights on your Windows Server.
2 Configure Private Agent

2.1 Login to your DCM Account. 

2.2 Go to ConfigurePrivate Agent.

2.3 Click Add Agent.

2.4 Specify a descriptive name that is recognizable in a list of other Private Agents. Optionally, fill in the Description field.

2.5 Adjust Private Agent options (if it is necessary) and click the Add button. 

A new Private Agent will be displayed in the list of Private Agents.

3 Setup Private Agent

3.1 Login to your Windows Server (with Admin Account). 

3.2 Start a browser on your Windows Server.

3.3 Login to your DCM Account.

3.4 Go to Configure > Private Agent.

3.5 Click Download Private Agent.

If the Download Private Agent button is disabled, please contact Dotcom-Monitor support team.

3.6 On the Tools page, click Download on the Private Agent Installer panel.

3.7 Click the Save button in the displayed popup.

3.8 Click the Run button after all files have been downloaded.

3.9 Follow the steps of the Setup Wizard by clicking Next.

Accept the terms in the license agreement and confirm or change the destination folder.

3.10 To finish the installation process, click Install and Finish.

3.14 In the appeared Private Agent Registrator dialog, add your DCM User ID and Password and click Continue.

3.15 On the summary page, make sure that all prerequisites are completed and click Continue.

3.16 Choose the Private Agent in the list and click Continue.

3.17 Review details of the Private Agent Configuration, and then click Continue

Registration of Private Agent will take a few minutes.

3.18 If successful, click Close in the corresponding dialog Setup Successful.

4 Check Services on your Windows Server

4.1 Open Service Overview on your Windows Server.

There are 5 services with the name Dotcom-Monitor Private Agent.

Those are used to simulate up to 5 monitoring devices in parallel.

5 Check User on your Windows Server

5.1 Open Task Manager

5.2 Click Users.

5.3 Check if there is a user called DotcomMonitorRdpUser.


6.1 Restart your Windows Server.

In some cases, the Private Agent can’t be used without a restart. It’s recommended to restart your Windows Server now.

Use the Private Agent

Step Details
1 Login DCM Account Login in into your Dotcom-Monitor account.
2 Configure a Device to use Private Agent

2.1 Open the Device Manager.

2.2 Create a new device or open an existed one to edit (the actions  menu).

2.3 Go to the Monitoring tab and select the Private agents monitoring location.

2.4 Save and Close.


Question: Why are there 5 Dotcom-Monitor Private Agent Services?
Question: Why is there a new DotcomMonitorRdpUser on my Window Server?
Question: Will this DotcomMonitorRdpUser block a Client RDP License?
Question: How many Private Agents will be required?

Question: Why are there 5 Dotcom-Monitor Private Agent Services?


Those services are used for executing monitoring devices on your new Private Agent. After the installation, one of those is running and the other four are in the Manual Start Type. Each of those services can run a single monitoring device in parallel. If you configure multiple monitoring devices to run on your Private Agent those services will be started and used to execute your devices.

Question: Why is there a new DotcomMonitorRdpUser on my Window Server?


This user has been created during the private agent installation. It will be used for the communication with the dotcom-monitor private agent services and is required for the execution of monitoring devices on your private agent server

Question: Will this DotcomMonitorRdpUser block a Client RDP License?


Our DotcomMonitorRdpUser will block one RDP License. After the private agent has been installed you won’t be able to establish two parallel RDP connections to your private agent server.

Question: How many Private Agents will be required?


Avoid overload situations. If you configure 20 devices to run on a 5-minute frequency and each device will take 5 minutes to complete, the Private Agent won’t be able to execute those. The number of Private Agents required depends on:

  1. Execution Frequency
  2. Execution Duration of your Devices


# Private Agents = ((# Devices * Duration (min)) * (1 / Frequency (min)) / 5 Devices in parallel

Sample calculation:

20 devices

5-minute Execution Frequency

5-minute session time of each device (Duration)

# Private Agents = ((20 * 5)*(1 / 5) / 5 = 4 PA will be required