Re: Group Policy Need help !!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Thanks a lot..

"kj" wrote:

You may be having a problem applying updated group policies.

try running;

gpresult /z > gpresult.txt

then examing gpresult.txt for something like;

Account Policies
----------------
GPO: Default Domain Policy
Policy: LockoutBadCount
Computer Setting: 50

....if you are not seeing the changes you expect, then review the workstation
and server event logs for group policy errors.

--
/kj
"Eric" <Eric@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4BBC4BA9-5EE8-4C5E-BC9A-985E6FFA2D6F@xxxxxxxxxxxxxxxx


"Dave Nickason [SBS MVP]" wrote:

Eric - are you saying that the user enters the incorrect password 5 times
and the account is locked out. Then you have to go into the user
properties
in AD and unlock it? So in AD, on the Account page, the check box is
checked for "Account is locked out?" And when you clear the checkbox it
unlocks the account?

YES



And you run rsop.msc on the desktop and on the server, and in all
instances
lockout is showing as "not defined?"

YES


And on the workstation when you go to Control Panel -> Administrative
Tools -> Local security policy, on the Account Lockout Policy page, all
are
"not defined?"

SHOW "NOT APPLICABLE "


On the server, if you open the Group Policy Management Console and expand
your SBS, under Group Policy Objects, do you have a policy called "Small
Business Server Lockout Policy? That's the default place the lockout
policy
is set in SBS.


YES , a policy called "Small Business Server Lockout Policy? BUT SHOW "
NOT
DEFINED" UNDER "ACCOUNT LOGOUT POLICY "

I don't know of any other places to look for a policy that would cause
what
you're seeing. If it's not in a group policy, and it's not in a local
security policy on the workstation, I'm lost. The only other thing I can
think of is that there might be a way to set lockout in the workstations'
registries, but I can't actually find any info on that.

If you're convinced that no group policy or local security policy is
causing
this, I would probably try creating a policy with a higher number of
failed
attempts than 5 - the SBS default is 50. Do a gpupdate /force on the
workstation to apply the new policy, then do an rsop.msc to make sure it
worked. Then see if the new policy is overriding whatever setting is
causing it to lock out after 5 bad passwords.

I CHANGEED THE POLICY TO 20 TIMES BEFORE, BUT NOT WORK, THE SYSTEM STILL
LOCKOUT USER AFTER 5 TIMES...

Thanks a lot for your help...





"Eric" <Eric@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0DDA9DDB-500B-43C9-8370-588B42E37EC9@xxxxxxxxxxxxxxxx
Same the station "not defined" on the account policies
Thanks a lot

"Dave Nickason [SBS MVP]" wrote:

And, you can run rsop.msc on the server as well, to see what's getting
applied there.


"Eric" <Eric@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:52D04424-5E34-4CFD-8FC1-06FA5D808EA7@xxxxxxxxxxxxxxxx
Thanks for the help..
I run the rsop.msc on the ststion, It's show "not defined".
All station has same problem (5 times & logout), I think the problem
is
in
the server. any idea ?



"Dave Nickason [SBS MVP]" wrote:

You didn't find the settings in the GPO called "Small Business
Server
Lockout Policy?" If not, on a workstation go to Start -> Run and
type
"rsop.msc" without the quotes. In the results, find the setting,
and
it'll
tell you what GPO contains the policy.


"Eric" <Eric@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C394C57A-B4BC-43A7-BD05-DA40DDEF7A23@xxxxxxxxxxxxxxxx
After typing 5 times error password system will lockout the user.

I need change the lockout policy for the system, and I checked
"security
setting" for "default domain policy", "SB server domain password
policy,
lockout policy", "Domain controllers policy", & Group policy
objects"
But
the
lockout policy show "not defined" Why? Did I missing something?

Thanks for all help....















.



Relevant Pages

  • RE: Windows Locks out automatically after x minutes
    ... As you mentioned the one pc is on a domain, maiking policy the likely cause ... for the workstation locking itself. ... enter is an account on the host machine. ...
    (microsoft.public.windowsxp.general)
  • Re: GPO causing client security logs to fill?
    ... a virus in play. ... settings to be applied on your client workstations. ... Group Policy is a complex and often misunderstood beast. ... I modified the account ...
    (microsoft.public.windows.server.sbs)
  • Re: The local policy of this system does not permit you to logon i
    ... Security policies were propagated with warning. ... Error 0x534 occurs when a user account in one or more Group Policy objects ... I have checked the security policies & the administrator profile is not ...
    (microsoft.public.windows.server.sbs)
  • Re: GPO causing client security logs to fill?
    ... Unlink the Default Domain Controller Policy (As it was not previously ... settings to be applied on your client workstations. ... I modified the account ... So basically, the Account lockout threshold, account lockout ...
    (microsoft.public.windows.server.sbs)
  • Re: GPO causing client security logs to fill?
    ... Possibly delete the Default Domoan Controller Policy (As it did not ... issues as it was about recoverying from a virus which appears to ... with client logon failures. ... I modified the account ...
    (microsoft.public.windows.server.sbs)