|
Posted by Anthony [MVP] on February 26, 2008, 12:16 pm
Please log in for more thread options
OK, I hope it goes well,
Anthony
> You are right, not a lot to test on this side. However I did sort of want
> to play around with scripting to give my managers a real easy way to reset
> passwords and unlock users. That's the kind of testing I had in mind.
>
> Thanks,
> Linn
>
>> There's not a lot to test. The user's password will not be affected until
>> it expires, or you set it to be changed at next logon, so you can
>> introduce it that way and change it back if you don't like it.
>> Anthony,
>> http://www.airdesk.co.uk
>>
>>
>>
>>> Thanks for the help Anthony. But man, that means it's all or nothing, I
>>> can't even test this before forcing it on everyone? I don't like that a
>>> bit.
>>>
>>> Thanks,
>>> Linn
>>>
>>>> You need to set the account policy in the root of the domain.
>>>> There's a good article about it here:
>>>>
http://technet2.microsoft.com/windowsserver/en/library/cda0eee3-a52e-4c1b-a9d7-0c70f122ada91033.mspx?mfr=true
>>>> and here:
>>>>
http://technet2.microsoft.com/windowsserver/en/library/b04678d1-510f-48d3-8d10-dce2e61972d71033.mspx?mfr=true
>>>> Hope that helps,
>>>> Anthony
>>>> http://www.airdesk.co.uk
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> I've been asked to force our users to use strong passwords with user
>>>>> lockouts after a number of wrong attempts. So I started small and
>>>>> setup a new OU and created a test user in it. I then created a goup
>>>>> policy, associated it to my new OU and set the Account Lockout
>>>>> Threshold to 3, which in turn set the duration and Reset Account
>>>>> Lockout Counter After to 30 minutes. The policy is linked to my OU
>>>>> and I'm filtering on Domain Users.
>>>>>
>>>>> Now when I look at the settings of my group policy it doesn't show my
>>>>> lockout settings and when I login as the test user it doesn't show
>>>>> this policy in GPResults I've done a GPUPDATE but that didn't help.
>>>>> So what am I missing? I suspect it's something obvious but I'm
>>>>> stumped once again.
>>>>>
>>>>> Thanks in advance,
>>>>> Linn
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|