What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

How can I automatically deploy and configure remote probes using Kaspersky Admin Kit or other tools?



I want to set up remote probes automatically and configure them remotely via Kaspersky's Admin Kit or other deployment tools.

configuration google-code kaspersky prtg remote-probe

Created on Mar 2, 2010 9:04:34 AM by  Daniel Zobel [Product Manager]

Last change on Mar 10, 2010 12:57:57 PM by  Daniel Zobel [Product Manager]

10 Replies

Accepted Answer



Deploying Remote Probes

For a general introduction to remote probes, please see manual section Remote Probes and Multiple Probes.

You can perform a remote installation of a probe directly via PRTG's web interface: PRTG Manual: Remote Probe Quick Install. This is basically a silent remote probe installation. Note: This is an experimental feature as of PRTG 12 and might not work in every case.

Important note: The approach below might not work with current versions of PRTG! Please try this workaround if remote probe installation via the web interface does not work:

The information below is outdated! We provide it for your information only.

Deploy and Auto-Configure Remote Probes Using Kaspersky

There is a small C++ command line program that can be used to auto-configure remote probes using Kaspersky Admin Kit deployment. The program uses minimal DLLs (only Kernel32.dll and advAPI32.dll) to avoid installation of MSVC++ 2008 Runtime. This article describes how you can set up and configure PRTG's remote probes remotely.

Note: PRTGRemoteProbeCfg is a freeware add-on from PRTG's user community. It comes with no warranty and we cannot officially support it.

A big "Thank You!" to Vincent from Nolmë Informatique for sharing this tool!

Steps to take

  1. In the PRTG web interface, choose Setup | Downloads / Add-Ons | Remote Probe Installer from the main menu and download the Remote Probe Installer (PRTG_Remote_Probe_Installer.exe).
  2. Deploy the remote probes using Kaspersky Network Agent: PRTG_Remote_Probe_Installer.exe /SILENT For help with this, see Kaspersky Technical Support.
  3. Download http://code.google.com/p/prtg7addons/downloads/detail?name=PRTGRemoteProbeCfg1.0.0.500.exe from Google Code

    [UPDATE] New version for PRTG v13 available here: http://www.nolme.com/datas/prtg/PRTGRemoteProbeCfgV13.exe
  4. Set parameters for a remote computer using Kaspersky Network Agent and PRTGRemoteProbeCfg.exe (renamed). Example: PRTGRemoteProbeCfg.exe /SERVERADDRESS <MyServerPublicIPAddress> /SERVERPORT 23560 /KEY <MyHashKey> /TAG NOLME_
  5. Machine does not need to be rebooted to take changes. If you want to check the connection between Remote Probe and Server, please see PRTG manual section Remote Probes and Multiple Probes for more information.


  • You can run PRTGRemoteProbeCfg.exe without any parameter to display help.
  • The program produces a debug log file in %TEMP%/NolmeDebug.log
  • If no name is specified, the program gets the machine's name (which should be unique for all good network admin ;p). Tag is inserted before for "classification".
  • Although these instructions are optimized for Kaspersky, remote deploy should work similar with other tools like OCS Inventory, Kaseya, ManageEngine Desktop Central, etc.


Paessler PRTG Remote Probe Configuration Help - (c) 2010 Nolmë Informatique     
Version  : 1.0
Encoding : UNICODE
Set remote probe configuration for Paessler PRTG Monitor
PRTGREMOTEPROBECFG [/SERVERADDRESS[:]address] [/SERVERPORT[:]port] [/KEY[:]access key] [/LANGUAGE[:]language] [/RECONNECTTIME[:]time]
                   [/TAG[:]tag name] [/WORKGROUPPREFIX] [/NAME[:]probe name]
  /?     Display help. Must be UNIQUE parameter
  /SERVERADDRESS    Define remote server address
          Address can be an IP or FQDN
          Default :
  /SERVERPORT       Define remote server port
          Port can be in [1..65536]
          Default : 23560
  /KEY              Access key hash code
          See in registry of server to get hash code (DECIMAL)
          Default : 0
  /LANGUAGE         Set default language
          English : english.lng
          French  : french.lng (Default)
          German  : german.lng
          Japanese: japanese.lng
          Spanish : spanish.lng
  /RECONNECTTIME    Time sync (in seconds) with server
          Default : 300
  /TAG              Define local probe tag name
          Add this tag before probe name
          Default : PROBE_
  /WORKGROUPPREFIX  Add computer workgroup name in probe name
          Default : <none>
  /NAME             Define local probe name
          If not specified, machine name will be used. /TAG can be combined
          Default : MyProbe
  /NORESTARTSERVICE Don't restart PRTG service after installation (Default: false)
Arguments are not case sensitive. You can use both slash '/' or '-' for specifying options.

Version History

Build : : Help displayed from command line display good default value

Build : : No need to restart computer to apply changes Add workgroup/domain name in probe name generation (see parameter: WORKGROUPPREFIX) Add parameter to avoid service restart (see parameter NORESTARTSERVICE)

Created on Mar 2, 2010 9:39:01 AM by  Daniel Zobel [Product Manager]

Last change on Apr 8, 2016 2:55:29 PM by  Gerald Schoch [Paessler Support]



Can this tool (PRTGRemoteProbeCfg.exe) be updated for PRTG v9? Currently the tool is geared for v7, and it essentially is updating the Registry with the settings defined in the command line. The tool works properly and successfully, but it stores the settings at [HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor\V7\Probe] which is an old location no longer used by PRTG v9. The correct new location is [HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor\Probe] for v9. Hopefully this is a quick and simple fix, because we could really, really use this function for our remote deployments. Right now, we are having to push .REG files, which are much more difficult to script for special per-machine settings like Probe Name, etc. Thank you!

Oh yes, I also forgot to mention. We noticed that this tool hangs if we don't include the /NORESTARTSERVICE switch. I assume it is because the older v7 used a different Service Name than on v9? Probably another fairly easy fix, I hope. Thanks!

Created on Nov 2, 2011 4:39:00 PM

Last change on Nov 2, 2011 5:00:05 PM by  Daniel Zobel [Product Manager]




I'll make a new version to update the tool to V9.

Created on Nov 2, 2011 5:30:02 PM



@nolme: Please let us know when we can help. We would be happy to upload the new version, too!

Created on Nov 3, 2011 10:07:46 AM by  Dirk Paessler [Founder Paessler AG] (11,025) 3 6



Please find the new version of the tool on the Google Code page:


Created on Feb 28, 2012 12:11:40 PM by  Daniel Zobel [Product Manager]

Last change on Feb 28, 2012 12:14:32 PM by  Daniel Zobel [Product Manager]



@nolme: The configuration tool does not work anymore for PRTG 12/13. Would you mind releasing an update?
Please let us also know if we can be of any assistance.
Thank you!

Created on Jan 17, 2013 8:55:04 AM by  Konstantin Wolff [Paessler Support]



The configuration tool does not work anymore for PRTG 12/13. Would you mind releasing an update

Created on May 23, 2013 6:10:38 PM



Is there an updated configuration tool "RTGRemoteProbeCfgV1x.exe" available for PRTG version 14?

Created on Aug 26, 2014 9:11:32 AM



the v13 version should be used for V14 & newer.

Created on Mar 19, 2016 9:41:35 PM



This is good. Do you have something comparable for UPDATING EXISTING installed probes? Occasionally the automatic probe updates fail, and we have to do it manually.

Ideally I would like a silent command line we could execute remotely -- we have a few ways we could execute such commands "in background", non-intrusively.

I have been given


as a way to do this, but it doesn't appear to have any silent or no-reboot provision. A local command line option (non-web) would be a potential option as well.

We can potentially use our LabTech remote admin software (comparable to Kasperski above). But again, those options would be useful.

-- Ken

Created on Mar 29, 2016 6:18:37 PM

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.