This article applies as of PRTG 22
Troubleshooting erratic behavior of push notifications
As of now, PRTG Desktop and the PRTG apps for iOS or Android rely on a unique identifier for each PRTG core server installation that is connected to these PRTG apps. This unique identifier is generated from the Windows MachineGUID of the PRTG core server system.
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 apps are not able to determine which PRTG core server installation 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:
- 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\
- 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 How can I move or migrate my PRTG installation to a different system or server?
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.