I sometimes find it convenient and necessary to run scheduled tasks or services as myself. I know this is bad, but what can I say. I've been cleaning up my act.

We recycle passwords every 45 days. Password reset day is always kind of stressful for me. I am going along with my business and bam! Locked out. Call help desk. "You again?" Get unlocked...

Next time, I'll be ready:

@('localhost','server1','server2','server3') `
| %{gwmi -Class Win32_Service -computerName $_ `
| where {$_.StartName -like '*cbilson'} `
| select Name, StartName, Status }

So that's the services, what about scheduled tasks? Well, there is the Win32_ScheduledJob WMI class, but it looks like that doesn't find scheduled tasks created using the scheduled task wizard? It's not working for my scheduled tasks anyway. Bummer.

Of course, this is a band-aid. They should just check the event log on my login server and see why I got locked out. Or maybe monitoring this kind of stuff even. I wonder what they do when an authority figure locks out their account. Even scarier: when a service account locks out! Our help desk doesn't seem to know how to trouble shoot this problem though and since we're still in business, I guess it's not as serious a problem as I am making it out to be.