Right and Tight

Security is a good thing.

I wanted to create a scheduled task that would pop up the list of resolutions I referred to earlier. Created the list as a text file, created a batch file to display the list, created a scheduled task to run the batch file. Scheduled task would not run -- said I didn't have the authority. (Right there, I flinched. I hated that phrase when I did security at IBM, and I hate it now. Its okay not to have the authority to do something; its not okay to make it clear why not.)

So I did some research, and came to find that the error meant that the ID I told scheduled tasks to use didn't give the right password for the ID. But..but.. the ID doesn't have a password. I grew tired of typing it in, so I turned that off. Ah, but the password still exists... you have to cite it. So I did. Guess I'll have to go back to typing it in, every time. But then I saw an article that said I could tell the security manager that although there was a password, you didn't have to use it.

Uh-huh.