I was wondering if anyone else is having issues with using environmental variables in your procedures?? When testing the procedures, they will not run, when I use variables, but if I use full paths it works. Example, if I want to set the dirty bit on the C: drive, I can not get it to set through a procedure with the %SYSTEMDRIVE% variable, it works if I open the system in the RMM and run it from the remote shell. I also could not get it to run using the system32 variable, in the enter working directory field either. I feel that using these variables could really help, but they do not want to work for me.
Thank you for your feedback! Indeed, system variables are not yet supported by RMM, but I have forwarded your request and so it can be evaluated as a feature of a future release of RMM.