Hello,

At this time, we do not have the ability to use stored credentials as variables for scripts or sensors in PRTG.

Let me know if I can answer any other questions.

Benjamin Day
Paessler Support

We have abilities with the %windowsuser / %windowspassword and %windowsdomain. Just i need in futur update this abilities to obtaine placeholder on notifications

Ex: If disk space is low the notification system can lunch an EXE to delete all temporary file on the server...

(This is a feature request :p )

It's probably more secure to just use Windows' integrated credential store. Think about it: A bad guy obtaining access to your PRTG web interface, using HTTP notifications to send credentials to a target URL where he collects your credentials. That's what we'd like to prevent here.

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Hi,

Yeah, your Windows's Integrated Credential is more secure, just my PRTG has only an access with VPN. I have 250+ server (VM) with different credential for all server (because i execute powershell script or EXE) and script need the "Opened Account" on the server same for EXE... And i have many probe in PRTG.

My team does not support prtg (im alone to maintain it) and i have automated all prtg (Automatically grab all VM on each HyperV (many hyperV), create sensor...) All C# exe created does not use the Credential Store... And it's not possible to copy the Credential Store to other PRTG Probe. Is not a solution for me :'(

Sorry, there's not much we can do in this case :/ Perhaps this kind of storage is more suitable: https://blog.kloud.com.au/2016/04/21/using-saved-credentials-securely-in-powershell-scripts/

You could use the device name as template and access them by name? Sorry that this is such a hassle for you :(

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team