I created a template of a device. But when I apply the template to other devices the sensors are not added. Its very simple and all sensors are supported.

They are...

Ping CPU Load Memory Hard Drive Space (multi)


Article Comments

Hello,

is it correct that not a single sensor was created after adding the template?

Which PRTG Version you have installed?

Could you please send your template file to support@paessler.com and refer to this case.

Best Regards.


Dec, 2012 - Permalink

Even though this is an old post. I have the same problem. Should I mail to?


May, 2014 - Permalink

Yes please submit a ticket to support@paessler.com


May, 2014 - Permalink

Is there any solution on this Problem?

I'm re-building our PRTG-Servers after new installation of Server 2012R2. Before that I created Templates from several special configured Servers.

After the Installation of PRTG I tried to build an Auto-Discovery Group based on one of the Templates with Machines based on "List of individual IP's...".

There is only the "Ping" Sensor after Auto-Discovery but nothing else...

And this was working before new installation.

Any help is appreciated Regards


Sep, 2015 - Permalink

The issue with templates being used and only seeing a ping sensor is usually that the protocol that was used in the template isn't turned on on the new servers or something has changed on the server that won't allow PRTG to create the same sensors so it will only create the ping sensor.

This is unfortunately a very specific problem since most of the time the template and the machines that it is being used on are at fault but each custom template is different so it's hard to say why no sensors are being created. Please send us as much information about the templates or the templates themselves that you are trying to use in a ticket like the others above and give us any information that you can about the systems being monitored and we will see if we can help.


Oct, 2015 - Permalink

Actually i have the same problem and imho & in customers view it Looks like old Firmware Releases -> Cisco iOS update recommended in this case ;-)


Jul, 2017 - Permalink