Re: 'password policy' on Windows XP

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Darrell Gorter[MSFT] (Darrellg_at_online.microsoft.com)
Date: 07/17/04 

Date: Sat, 17 Jul 2004 22:33:16 GMT

Hello,
You can set some of these password options with the net command.
Open a cmd prompt ( Start - Run - CMD)
Then run "net help accounts" and "net help user" to get the syntax and
descriptions correct.
This allows you set some of the user password options from the commandline.
This should be available on Home if I recall properly.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>From: "Miha Pihler" <miha-news@atlantis.si>
>References: <O93lkFCbEHA.3692@TK2MSFTNGP09.phx.gbl>
<OVHAvKCbEHA.3820@tk2msftngp13.phx.gbl>
<OPgJ#XDbEHA.1652@TK2MSFTNGP09.phx.gbl>
>Subject: Re: 'password policy' on Windows XP
>Date: Sat, 17 Jul 2004 21:57:41 +0200
>Lines: 102
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
>X-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409
>Message-ID: <uStNThDbEHA.3524@TK2MSFTNGP12.phx.gbl>
>Newsgroups: microsoft.public.windowsxp.general
>NNTP-Posting-Host: pilot.atlantis.si 193.189.177.66
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.windowsxp.general:1015067
>X-Tomcat-NG: microsoft.public.windowsxp.general
>
>Hi David,
>
>sorry, I missed the XP _Home_ edition part :-).
>
>Default XP policy allows creating users without password (minimum password
>length = 0 characters). This can change e.g. once computer joins the domain
>if domain policy is set differently (e.g. requires password to be at least
8
>characters long)...
>
>The other setting that is affected by this policy is use of users account
>without a password to console logon only. If someone is trying to logon to
>your computer over network using local user account without a password set
>it will fail. This is again set in local policy and can be changed.
>
>Mike
>
>"David Cook" <(unknown)> wrote in message
>news:OPgJ%23XDbEHA.1652@TK2MSFTNGP09.phx.gbl...
>> Miha -
>>
>> There is no such policy editor on Win XP HOME (it only exists on Win
>XP
>> Pro)
>> as evidence both by fact that I can't find one on the XP Home machine and
>> because
>> other msgs in this newsgroup and elsewhere explicitly SAY that this
>> policy-editor
>> you speak of exists only on XP Pro.
>>
>>
>> And, unfortunately for me, the machine I care about is the Win-XP Home
>> machine.
>> (Sorry I even mentioned that I also HAVE an XP Pro machine. The reason
>that
>> I did mention it is that I have existing accts on that PRO machine too,
>and
>> they
>> have no passwords. And, I can assure you that no one has NEVER used this
>> 'policy-editor'
>> on that machine, yet I was able in the past to setup user accts that have
>no
>> passwords.)
>>
>> Other ideas?
>>
>> Dave
>>
>>
>>
>>
>> "Miha Pihler" <miha-news@atlantis.si> wrote in message
>> news:OVHAvKCbEHA.3820@tk2msftngp13.phx.gbl...
>> > Hi David,
>> >
>> > you can set your local policy by going to Group Policy (GP) Editor.
>> >
>> > Click on Start > Run > gpedit.msc > once your GP Editor is loaded drill
>> down
>> > Computer Configuration > Windows Settings > Security Settings > Account
>> > Policies. Here you have two options
>> > * Password Policy and
>> > * Account Lockout
>> >
>> > Be careful what you set. Settings will also apply to Administrator and
>> other
>> > accounts with administrative privileges.
>> >
>> > Mike
>> >
>> > "David Cook" <(unknown)> wrote in message
>> > news:O93lkFCbEHA.3692@TK2MSFTNGP09.phx.gbl...
>> > > I have two Windows XP machines here at home, one XP Pro and
>> > > one XP Home. All users have 'administrative' priv on their accounts.
>> > >
>> > > On both machines, it NOW seems that any NEW user accounts that
>> > > I create MUST have passwords. Yet, my EXISTING user accounts
>> > > either have no passwords or else have very minimal (e.g. 3-char
>> > passwords).
>> > >
>> > > Did the rules change (e.g. by some Windows Update patch) or am I
>> > > just not seeing/finding some 'policy' admin program to control this?
>> > >
>> > > (As an aside, I googled this issue and see people mentioning
>> > > to look under
>> > > 'Control panel, administrative tools, local security policies,...'
>> > > but, I don't have a choice of 'local security policies' on either of
>my
>> > > two systems.)
>> > >
>> > > What gives?
>> > >
>> > > Cheers...
>> > >
>> > > Dave
>> > >
>> > >
>> >
>> >
>>
>>
>
>
>

Relevant Pages

  • 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)
  • Re: Password expires for no apparent reason
    ... policy that has set the values to what you see below meaning that users ... So I would define the password age and configure a value in there. ... As Harj said Account lockouts could potentially be a problem as perhaps ... Password expires for no apparent reason ...
    (microsoft.public.windows.server.active_directory)