Hello Mark,
thank you for your KB-Post.
All (with very few exceptions) of PRTG's configurations are stored in a single file, the PRTG Configuration.dat. If you copy this file to a different system before starting PRTG, it will use this configuration instead of creating a new one. Please beware that even "identical" systems may report data in a slightly different systems, so some sensors may not work right-away after deploying this configuration on a new location and adding different addresses to existing devices/sensors. Please refer to the following KB-Posts about PRTG's Data/Configuration file:
Sensors like Ping, HTTP and others will work straight away, but sensors that rely on indexes or other unique identification may fail or display incorrect readings, this could affect traffic, memory, disk, system health and other "complex" sensors.
You could "preserve" the original deployment for most configurations, re-use the group/device structures but perform an "Auto-Discovery" using custom Device Templates, this will cause specific-sensor types to be deployed when possible, the sensors deployed by the template will take the fact that this is a "new device" into account and re-assign/query indexes, making sure that the queried data is correct/valid. Device Templates can also be copied from one deployment to another, they're XML-compatible files stored in the following folder:
C:\Program Files (x86)\PRTG Network Monitor\devicetemplates\ |
Best Regards,
Luciano Lingnau [Paessler Support]
Add comment