Re: User Creation

From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 04/18/04


Date: Sun, 18 Apr 2004 17:21:38 -0400

Didn't catch which version of Windows Active Directory you were running?

What else was in the event logs? I've set up hundreds of active directories
and have not had this same issue, so I'm curious how you arrived at the
issue.

"david" <anonymous@discussions.microsoft.com> wrote in message
news:0a3e01c42586$f56a0d30$a401280a@phx.gbl...
> I have exactly the same problem, except that I'm not able
> to create any user accounts at all.
>
> These are these steps that I took:
>
> 1. Installed Windows Server 2003 Enterprise;
> 2. Installed hardware drivers (for modems, drives etc...);
> 3. Promoted the stand-alone server to a AD DC;
> 4. After reboot, installed/configured DHCP;
> 5. Checked DHCP/DNS was all working ok;
> 6. Created an OU, and two Groups;
> 7. Attempted, unsuccessfully, to create a user account;
> 8. Error regarding password complexity and history appears
> even though I supplied a very complex 20 character
> password;
>
> At step 2 and onwards, I was logged in locally as the
> administrator using a 24 character password, and using the
> default settings for the above steps.
>
> No security policies or permissions were manually changed
> on my part.
>
> Could this be a flaw in the Windows OS; and why has this
> trivial matter of creating user accounts made me so
> irritated already?
>
> Answers on a postcard please.
>
>
>
>
> >-----Original Message-----
> >Is that a Windows 2000 or 2003 domain? Have you installed
> any W2k3 DCs
> >recently?
> >W2k3 by default has password complexity enabled in Default
> Domain Policy. If
> >it is not your case, you can run GP Modelling from GPMC,
> for example, and
> >check which GPO has password policies enabled.
> >
> >--
> >Dmitry Korolyov [d__k@removethispart.mail.ru]
> >MVP: Windows Server - Active Directory
> >
> >
> > "Shailu" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:187C3DE5-8D00-43C2-8B3F-E0724365EAE1@microsoft.com...
> > Hi,
> > I have got a AD running with a single domain test.local.
> > Everything was working fine, was able to create users
> etc.
> > All of a sudden when I try to create a user it gives me
> a error saying"The
> >password doesnot meet the password policy requirements.
> Check the minimum
> >password length,password complexity and password history
> requiements".
> > I do not have any group policy implemented neighter all
> the above settings
> >in Default Domain Controllers Policy and Default Domain
> Policy are not
> >defined.
> > Even I try to define the settings in default plicies
> stil it gives the
> >same problem.
> > Kindly get back to me if anyone has got the solution for
> it.
> >
> > Thanks
> >



Relevant Pages

  • Re: User Creation
    ... to create any user accounts at all. ... default settings for the above steps. ... >W2k3 by default has password complexity enabled in Default ... >password doesnot meet the password policy requirements. ...
    (microsoft.public.windows.server.active_directory)
  • Re: domain log in thinks it is local log in?
    ... Default Domain Policy, applied at the domain level, affects ALL ... computer and user accounts in that domain. ... > Check your Default Domain Policy (and maybe other policies affecting ... Windows Server - Active Directory ...
    (microsoft.public.windows.server.active_directory)
  • Re: What Happened? Passwords all expired...
    ... really explain how the new account policy settingmade it to the DCs. ... I would strongly suggest enabling Success/Failure for Account Management ... >>>post that says "I check my GPO's and password complexity ... >>>>account logon events success and fail ...
    (microsoft.public.win2000.active_directory)
  • Re: GPO - password policy - Urgent
    ... Set password complexity to "disabled" - NOT undefined in Domain ... You can also use the mmc snapin for Resultant Set of Policy [again ... assuming Windows 2003] in logging mode on the domain controller to see what ... problems being that domain controllers are not pointing only to themselves ...
    (microsoft.public.windows.server.security)
  • New recipient policy not applying to mail-enabled user accounts
    ... My company's current standard default email ... I have created a filter in this policy, so it applies to the following: ... 3500 MAIL-ENABLED user accounts which also need to have the new ...
    (microsoft.public.exchange.admin)