Disabled account causes error 1022

From: Peter Kaufman (no_at_email.com)
Date: 06/09/04 

Date: Wed, 09 Jun 2004 12:11:32 +0700

Hi,

If I disable an account in AD, the event log fills up with error 1022
"Logon failure on database..". While logical to a degree, it makes
disabling an account impractical.

Is there any workaround?

Thanks,

Peter

Relevant Pages

  • RE: Scavanging retired machine accounts
    ... Here's a script I wrote a while back that does exactly what you want. ... 'pull back a list of every user's account name and distinguished name ... we're probably only interested in the disabled computer accounts ... 'There is no point disabling PCs based on how many weeks it's been since the ...
    (microsoft.public.windows.server.scripting)
  • Re: "Enabling" an already enabled user account?
    ... Is that user having problems in all machines or just that one? ... (Logon failure: account currently disabled. ... see Help and Support Center at ... > I've tried actually disabling the account and then re-enabling and with ...
    (microsoft.public.windows.server.active_directory)
  • RE: Why should we disable local administrator accounts?
    ... I understand that you have concerns on disabling local Administrator ... Account on client workstations in SBS domain. ... At least if your local admin passwords are ...
    (microsoft.public.windows.server.sbs)
  • Re: "Enabling" an already enabled user account?
    ... ASF Gigabit Ethernet Controller ... I logged onto the account using another machine ... Windows cannot access the file gpt.ini for GPO ... I've tried actually disabling the account and then re-enabling and with ...
    (microsoft.public.windows.server.active_directory)
  • Re: "Enabling" an already enabled user account?
    ... I see that you've the DNS in different subnet, if you're running the logon script at site level with slow connection you probably miss that unless you force it through GPO. ... I logged onto the account using another machine ... >>> I've tried actually disabling the account and then re-enabling and ...
    (microsoft.public.windows.server.active_directory)