I think this all started when we updated PRTG version, right now we use PRTG 16.2.24.3792+, is this a bug or a feature?
And it is fixed with the last version of PRTG?
I think this all started when we updated PRTG version, right now we use PRTG 16.2.24.3792+, is this a bug or a feature?
And it is fixed with the last version of PRTG?
2 Replies
Please log in or register to enter your reply.
Add comment