I’ve been using toolboxes and alerts that run toolbox scripts for many years, and their behavior has become increasingly unpredictable and erratic.
If you create a script and run it manually on different devices, there is usually no problem.
The problems start when you schedule a script and assign it to an alert or monitoring rule, especially when you later try to modify the original script.
-
If you keep the administrator console open for several hours, at some point changes made to scripts stop being saved. You can click Save, the system will not display any error, but the changes simply are not saved. You only discover this after closing the administrator console and reopening it.
-
I am completely unable to determine when changes are propagated to alerts, and from alerts to the client devices. I have seen cases where it takes a few hours, others where it takes several days, and others where the changes never propagate at all. I do not understand whether there is some kind of cache involved, whether the alert needs to be disabled and re-enabled, or something else. I have never been able to achieve consistent behavior.
-
If you mark toolboxes as favorites, the erratic behavior becomes even worse. You never really know whether running a favorite toolbox is executing the original version or the version you have just modified.
-
Recently, I converted all my scripts from VBS to PowerShell. Several weeks have passed, the VBS toolboxes have been deleted, the corresponding alerts have been removed, I have restarted all the servers and installed all available updates, and yet, for some reason, some devices are still periodically running VBS scripts that have not existed for weeks.
I know the team has had other important priorities to deal with, but the entire system responsible for propagating toolbox changes really needs a thorough review.