New Question
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Download >>


What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more


Top Tags

View all Tags

How do I troubleshoot erratic behavior of push notifications in PRTG Desktop or the mobile apps?



Your Vote:



I have multiple PRTG instances installed and usually manage and view them with PRTG Desktop and the PRTG mobile apps. However, when I receive a push notification from PRTG Desktop or my PRTG mobile apps and want to view the object that triggered the push notification, PRTG often takes me to the wrong instance of PRTG. What can I do?

prtg-desktop prtg-mobile-app push-notifications troubleshooting

Created on Jul 4, 2019 10:09:46 AM by  Maike Behnsen [Paessler Support]

Last change on Jul 4, 2019 10:22:24 AM by  Maike Behnsen [Paessler Support]

1 Reply

Accepted Answer



Your Vote:



This article applies to PRTG Network Monitor 19 or later

Troubleshooting Erratic Behavior of Push Notifications

As of now, PRTG Desktop and the PRTG mobile apps rely on a unique identifier for each core server installation of PRTG that is connected to these apps. This unique identifier is generated from the Windows MachineGUID of the host where the PRTG core server is running.

Cloned Systems with Identical Identifiers

If you have several of these hosts that are “cloned” virtual machines (or “cloned” systems), you might end up with hosts that have the same MachineGUID - and therefore the same "unique" identifier for PRTG. In this case, PRTG Desktop and the PRTG mobile apps are not able to determine which core server installation of PRTG is the “right” instance that triggered the push notification and might take you to the “wrong” server.

Tips for Troubleshooting

The solution to the issue is to sysprep the image used for deploying new hosts. This way, the MachineGUID of every server becomes unique.

If you face this issue, do the following:

  1. Check if the MachineGUIDs of your separate PRTG core server installations are identical. To do so, run the PowerShell command below:
    Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Cryptography\
  2. If the MachineGUIDs are the same, you need to do a Sysprep of your cloned Windows image to generalize it before installing PRTG. During this process, a new MachineGUID is created so that the PRTG instance installed on this image has a “really” unique identifier.

Note: It might also be possible to change the MachineGUID via other means after PRTG has already been installed, although this is not recommended. After you have set up a new host (that you sysprepped as well), you can migrate PRTG to this new host. For more information, see the Knowledge Base: How can I move (migrate) my PRTG installation to another computer?

Finally, always keep in mind that PRTG is not the only software that might rely on MachineGUIDs. As a general rule, always sysprep new hosts before deployment. For more information, see the links below.


Created on Jul 4, 2019 10:20:54 AM by  Maike Behnsen [Paessler Support]

Last change on Jul 5, 2019 9:21:36 AM by  Brandy Greger [Paessler Support]

Please log in or register to enter your reply.

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.