Keith,

I am trying out the desktop unlock trigger. It works, sort of, and fails. Though you can make the "Run function: Add new custom function" accept a .vbs file, the trigger doesn't successfully run the .vbs (silently fails), so I tried using an application of CMD.EXE with a /C command line including the .vbs file. That silently fails, also. So I put the .vbs file in a .bat file. That runs, and the .vbs file is presented as having run, but it actually does nothing (i.e., silently fails). If I run the batch file from the command line or by double-clicking it (or the .vbs directly), it runs. I also find the named trigger in the taskbar button context menu under Run Function on Window>Custom Functions>Numlock (the name I gave it), and when I run that it works. It just silently fails to run the .vbs file in the .bat file when started by a trigger. The bottom line, no matter how you specify it, you cannot make the .vbs file run.

Since the information for the triggers seems to be in the troubleshooting section, I'm including that an the VBS and BAT file.

PS: When I use the Run Function: Add New Custom Function and then subsequently us the Remove button to delete it, it is not removed from the interface. You will see in the troubleshooter various iterations of a name that includes "numlock" that were discarded but not deleted. This may also be a bug.

Thanks. Set it up, but I cannot toggle numlock remotely. Since MS Remote Desktop on Mac does so when I quit, tomorrow when I log on to the affect PC, I hope to see the trigger save me the trouble. Will report after the test.

Worked like a champ. The VBS ran and turned off the numlock after logging back on, exactly as desired.

While closing this problem report, perhaps you might want to make it more obvious in your help how to run scripts. Perhaps add a new function action in addition to Launch Application that might read Launch Windows script?

Thanks for all the help.
-Robert