The script in this blog post can help you track down services running under non-system-accounts:
http://theessentialexchange.com/blogs/michael/archive/2008/02/29/finding-ser vices-using-non-system-accounts-with-powershell.aspx Good for documentation, if nothing else. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Rankin, James R [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 5:32 PM To: NT System Admin Issues Subject: RE: how to find out which service is locking down a user? If I understand your question rightly, you want to find out which service is locking out a user account. Unless the services are specific to certain servers and you can cross-reference the lockout events (644) by server, then your job is going to be nigh on impossible. Which is why I run every application/service under a separate user account that denotes which service it is tied to. _____ From: Boaz Galil [mailto:[EMAIL PROTECTED] Sent: 12 March 2008 20:44 To: NT System Admin Issues Subject: how to find out which service is locking down a user? ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
