Thanks Glenn! I used your example and this seemingly works, but there must be something within task scheduler that I don't understand. I put a print statement before the "tcSetEventCredentials" call and an @serror? immediately following. The command did complete successfully for the task I was testing. There must be a flaw in the way I'm trying to test though. I'm looking for tasks that are running as local administrator, if I find any, I'm changing those to a bogus password and then trying to start the task after the script runs. I'm still able to run the task. I'm wondering if it's because the currently logged in users credentials can run the task?
_________________________
I could have made a neat retort but didn't, for I was flurried and didn't think of it till I was downstairs.
-Mark Twain
