don't want service accounts locked out
From: Tom McComb (tmccomb@coolsavings.com)
Date: 06/19/02
- Next message: keith sheehan: "export an importing ssl certificates"
- Previous message: WDms: "How to scan a compromised system?"
- Next in thread: David Dickinson [MVP]: "Re: don't want service accounts locked out"
- Reply: David Dickinson [MVP]: "Re: don't want service accounts locked out"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Tom McComb" <tmccomb@coolsavings.com> Date: Wed, 19 Jun 2002 11:10:22 -0500
Ok, all. Let's see if I can state my issue clearly. Our current security
policy includes having account lockouts after 3 bad password attempts, and
the usual Strong Password Policy (per MS instructions installing the
passfilt.dll). And while it can sometimes be a pain the neck, all seems to
work reasonably well (except, of course, when I lock myself out after
changing my own password :) Problem is, I have a few "service" accounts
that I need to make sure do NOT get locked out. Stuff that runs some
internal apps, etc. I've tried the "user cannot change password" and
"password never expires", and myself and the other net admin here originally
thought that would do it. Apparently, we're wrong.
Any ideas how I can keep our current lockout policy, *and* make sure those
service accounts don't get locked out?
TIA,
Tom McComb
- Next message: keith sheehan: "export an importing ssl certificates"
- Previous message: WDms: "How to scan a compromised system?"
- Next in thread: David Dickinson [MVP]: "Re: don't want service accounts locked out"
- Reply: David Dickinson [MVP]: "Re: don't want service accounts locked out"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|