Password Policy Change - When Into Effect

client is running SBS 2003 SR2 SP2
This is a new environment and I want password policies in effect now but I
don't want it happening to every user on the same day. Since the SBS wizard
to manage policies will reset all passwords from immediately to 7 days I used
GPO to change the Server Domain password Policies.

Am I correct in understanding this will bypass the all-at-once change and
put the requirements in effect based on when the password was last changed -
in relation to maximum password age? When I go back and look at the wizard,
it now has the history length requirement displayed, and still sow 3 days to
go into effect.

Thanks

Hello Perry,

Thanks for your post.

In Windows Server 2003 group policy, we can set a maximum password age. A
common misconception is that the current age for each user's password is
reset when this value is changed. Actually, Windows operating system does
not actually store the age of the user's password, but rather the last time
it was set.

The process of checking whether a user password expires:

1. The user account password is not set to Password Never Expires. If it
is set as Never Expires, the 'Maximum Password age' setting will be ignored.
2. Get the 'Maximum Password age' value dictated by domain policy,
'pwdLastSet' value of the user account and current domain time.
3. If 'pwdLastSet' + 'Maximum Password age' > = current domain time, the
password expires. Before it expires, you will always be prompted to change
password.

Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last time
you changed your password), and all users should not be forced to renew
password on the same day.

Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.

Thank you for your time and cooperation.


Best regards,
Robbin Meng(MSFT)
Microsoft CSS Online Newsgroup Support

Hi,

I would like to change the complexity settings, because now the length is only 4 characters. But will people have to change immediatly their password? Or do they have to meet the complexity rules only when they change their password?
It is a windows 2003 domain.

Thanks in advance,
Mieke



v-robme wrote:

Hello Perry,Thanks for your post.
10-Oct-08

Hello Perry,

Thanks for your post.

In Windows Server 2003 group policy, we can set a maximum password age. A
common misconception is that the current age for each user's password is
reset when this value is changed. Actually, Windows operating system does
not actually store the age of the user's password, but rather the last time
it was set.

The process of checking whether a user password expires:

1. The user account password is not set to Password Never Expires. If it
is set as Never Expires, the 'Maximum Password age' setting will be ignored.
2. Get the 'Maximum Password age' value dictated by domain policy,
'pwdLastSet' value of the user account and current domain time.
3. If 'pwdLastSet' + 'Maximum Password age' > = current domain time, the
password expires. Before it expires, you will always be prompted to change
password.

Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last time
you changed your password), and all users should not be forced to renew
password on the same day.

Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.

Thank you for your time and cooperation.


Best regards,
Robbin Meng(MSFT)
Microsoft CSS Online Newsgroup Support

Previous Posts In This Thread:

On Thursday, October 09, 2008 4:44 PM
Perr wrote:

Password Policy Change - When Into Effect
client is running SBS 2003 SR2 SP2
This is a new environment and I want password policies in effect now but I
don't want it happening to every user on the same day. Since the SBS wizard
to manage policies will reset all passwords from immediately to 7 days I used
GPO to change the Server Domain password Policies.

Am I correct in understanding this will bypass the all-at-once change and
put the requirements in effect based on when the password was last changed -
in relation to maximum password age? When I go back and look at the wizard,
it now has the history length requirement displayed, and still sow 3 days to
go into effect.

Thanks

On Friday, October 10, 2008 7:14 AM
v-robme wrote:

Hello Perry,Thanks for your post.
Hello Perry,

Thanks for your post.

In Windows Server 2003 group policy, we can set a maximum password age. A
common misconception is that the current age for each user's password is
reset when this value is changed. Actually, Windows operating system does
not actually store the age of the user's password, but rather the last time
it was set.

The process of checking whether a user password expires:

1. The user account password is not set to Password Never Expires. If it
is set as Never Expires, the 'Maximum Password age' setting will be ignored.
2. Get the 'Maximum Password age' value dictated by domain policy,
'pwdLastSet' value of the user account and current domain time.
3. If 'pwdLastSet' + 'Maximum Password age' > = current domain time, the
password expires. Before it expires, you will always be prompted to change
password.

Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last time
you changed your password), and all users should not be forced to renew
password on the same day.

Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.

Thank you for your time and cooperation.


Best regards,
Robbin Meng(MSFT)
Microsoft CSS Online Newsgroup Support


Submitted via EggHeadCafe - Software Developer Portal of Choice
Preventing extra HTML Content in File Downloads
http://www.eggheadcafe.com/tutorials...-html-con.aspx

Hi - the change will not affect users until it's time to change their
passwords. I suggest you *not* enable complex password enforcement, but
instead just force a long (e.g., 15-char) password length and show users how
to use passphrases. It's then more likely they will remember their
passwords, rather than writing them on sticky notes and calling you all the
time when they can't set them. A passphrase can use spaces (they don't count
as characters, but they help create long ones) - a good example to tell your
users might be something like this:

the mean sysadmin made me use a long password




OT, but please don't use the Egghead cafe forum, Techarena or Google Groups
to work with the MS public newsgroups. The interface doesn't quote properly,
and you're replying to a post which is no longer on the news server, so it's
unlikely that anyone will know what you're talking about.

Try using a news client, such as Forte Agent, Thunderbird, or even Outlook
Express, instead. It's a lot easier to do nearly everything that way. You
can mark messages to be watched, filter the views so you can see replies to
your posts easily, and search.

The Microsoft public news server is msnews.microsoft.com and you can
subscribe to as many groups as you like; no authentication is required.

The following is from a post by MVP Malke ...

-------------------------------------------------------
Here's information on Usenet and using a newsreader:

http://www.elephantboycomputers.com/page3.html#12-09-02 - a brief
explanation of newsgroups
http://michaelstevenstech.com/outlo...ssnewreader.htm
http://rickrogers.org/setupoe.htm
http://support.microsoft.com/defaul...wto/default.asp
- Set Up Newsreader

http://www.dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html
http://aumha.org/nntp.htm - list of MS newsgroups
microsoft.public.test.here - MS group to test if your newsreader is
working properly
http://www.mailmsg.com/SPAM_munging.htm - how to munge email address
http://www.blakjak.demon.co.uk/mul_crss.htm - multiposting vs.
crossposting

Some newsreaders for Windows
http://www.forteinc.com/agent/index.php - for Forte
http://www.mozilla.org (Thunderbird does newsgroups)
http://gravity.tbates.org/

-------------------------------------




mieke hoogeveen wrote:
> Hi,
>
> I would like to change the complexity settings, because now the
> length is only 4 characters. But will people have to change
> immediatly their password? Or do they have to meet the complexity
> rules only when they change their password? It is a windows 2003
> domain.
>
> Thanks in advance,
> Mieke
>
>
>
> v-robme wrote:
>
> Hello Perry,Thanks for your post.
> 10-Oct-08
>
> Hello Perry,
>
> Thanks for your post.
>
> In Windows Server 2003 group policy, we can set a maximum password
> age. A
> common misconception is that the current age for each user's password
> is
> reset when this value is changed. Actually, Windows operating system
> does
> not actually store the age of the user's password, but rather the
> last time
> it was set.
>
> The process of checking whether a user password expires:
>
> 1. The user account password is not set to Password Never Expires.
> If it
> is set as Never Expires, the 'Maximum Password age' setting will be
> ignored.
> 2. Get the 'Maximum Password age' value dictated by domain policy,
> 'pwdLastSet' value of the user account and current domain time.
> 3. If 'pwdLastSet' + 'Maximum Password age' > = current domain
> time, the
> password expires. Before it expires, you will always be prompted to
> change
> password.
>
> Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last
> time
> you changed your password), and all users should not be forced to
> renew
> password on the same day.
>
> Hope this helps. Also, if you have any questions or concerns, please
> do not
> hesitate to let me know.
>
> Thank you for your time and cooperation.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Previous Posts In This Thread:
>
> On Thursday, October 09, 2008 4:44 PM
> Perr wrote:
>
> Password Policy Change - When Into Effect
> client is running SBS 2003 SR2 SP2
> This is a new environment and I want password policies in effect now
> but I
> don't want it happening to every user on the same day. Since the SBS
> wizard
> to manage policies will reset all passwords from immediately to 7
> days I used
> GPO to change the Server Domain password Policies.
>
> Am I correct in understanding this will bypass the all-at-once change
> and
> put the requirements in effect based on when the password was last
> changed -
> in relation to maximum password age? When I go back and look at the
> wizard,
> it now has the history length requirement displayed, and still sow 3
> days to
> go into effect.
>
> Thanks
>
> On Friday, October 10, 2008 7:14 AM
> v-robme wrote:
>
> Hello Perry,Thanks for your post.
> Hello Perry,
>
> Thanks for your post.
>
> In Windows Server 2003 group policy, we can set a maximum password
> age. A
> common misconception is that the current age for each user's password
> is
> reset when this value is changed. Actually, Windows operating system
> does
> not actually store the age of the user's password, but rather the
> last time
> it was set.
>
> The process of checking whether a user password expires:
>
> 1. The user account password is not set to Password Never Expires.
> If it
> is set as Never Expires, the 'Maximum Password age' setting will be
> ignored.
> 2. Get the 'Maximum Password age' value dictated by domain policy,
> 'pwdLastSet' value of the user account and current domain time.
> 3. If 'pwdLastSet' + 'Maximum Password age' > = current domain
> time, the
> password expires. Before it expires, you will always be prompted to
> change
> password.
>
> Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last
> time
> you changed your password), and all users should not be forced to
> renew
> password on the same day.
>
> Hope this helps. Also, if you have any questions or concerns, please
> do not
> hesitate to let me know.
>
> Thank you for your time and cooperation.
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft CSS Online Newsgroup Support
>
>
> Submitted via EggHeadCafe - Software Developer Portal of Choice
> Preventing extra HTML Content in File Downloads
> http://www.eggheadcafe.com/tutorials...-html-con.aspx

Then there is the one about the new computer user whose password was:

SnowWhiteSleepySneezyDopeyDocHappyBashfulGrumpy

becuase company policy required 8 characters.

<g>

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


> Hi - the change will not affect users until it's time to change their
> passwords. I suggest you *not* enable complex password enforcement,
> but instead just force a long (e.g., 15-char) password length and show
> users how to use passphrases. It's then more likely they will remember
> their passwords, rather than writing them on sticky notes and calling
> you all the time when they can't set them. A passphrase can use spaces
> (they don't count as characters, but they help create long ones) - a
> good example to tell your users might be something like this:
>
> the mean sysadmin made me use a long password
>
>
>
> OT, but please don't use the Egghead cafe forum, Techarena or Google
> Groups to work with the MS public newsgroups. The interface doesn't
> quote properly, and you're replying to a post which is no longer on
> the news server, so it's unlikely that anyone will know what you're
> talking about.
>
> Try using a news client, such as Forte Agent, Thunderbird, or even
> Outlook Express, instead. It's a lot easier to do nearly everything
> that way. You can mark messages to be watched, filter the views so you
> can see replies to your posts easily, and search.
>
> The Microsoft public news server is msnews.microsoft.com and you can
> subscribe to as many groups as you like; no authentication is
> required.
>
> The following is from a post by MVP Malke ...
>
> ------------------------------------------------------- Here's
> information on Usenet and using a newsreader:
>
> http://www.elephantboycomputers.com/page3.html#12-09-02 - a brief
> explanation of newsgroups
> http://michaelstevenstech.com/outlo...ssnewreader.htm
> http://rickrogers.org/setupoe.htm
> http://support.microsoft.com/defaul...wto/default.asp
> - Set Up Newsreader
> http://www.dts-l.org/goodpost.htm
> http://www.catb.org/~esr/faqs/smart-questions.html
> http://aumha.org/nntp.htm - list of MS newsgroups
> microsoft.public.test.here - MS group to test if your newsreader is
> working properly
> http://www.mailmsg.com/SPAM_munging.htm - how to munge email address
> http://www.blakjak.demon.co.uk/mul_crss.htm - multiposting vs.
> crossposting
> Some newsreaders for Windows http://www.forteinc.com/agent/index.php -
> for Forte http://www.mozilla.org (Thunderbird does newsgroups)
> http://gravity.tbates.org/
>
> -------------------------------------
>
> mieke hoogeveen wrote:
>
>> Hi,
>>
>> I would like to change the complexity settings, because now the
>> length is only 4 characters. But will people have to change
>> immediatly their password? Or do they have to meet the complexity
>> rules only when they change their password? It is a windows 2003
>> domain.
>>
>> Thanks in advance,
>> Mieke
>> v-robme wrote:
>>
>> Hello Perry,Thanks for your post.
>> 10-Oct-08
>> Hello Perry,
>>
>> Thanks for your post.
>>
>> In Windows Server 2003 group policy, we can set a maximum password
>> age. A
>> common misconception is that the current age for each user's password
>> is
>> reset when this value is changed. Actually, Windows operating system
>> does
>> not actually store the age of the user's password, but rather the
>> last time
>> it was set.
>> The process of checking whether a user password expires:
>>
>> 1. The user account password is not set to Password Never Expires.
>> If it
>> is set as Never Expires, the 'Maximum Password age' setting will be
>> ignored.
>> 2. Get the 'Maximum Password age' value dictated by domain policy,
>> 'pwdLastSet' value of the user account and current domain time.
>> 3. If 'pwdLastSet' + 'Maximum Password age' > = current domain
>> time, the
>> password expires. Before it expires, you will always be prompted to
>> change
>> password.
>> Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last
>> time
>> you changed your password), and all users should not be forced to
>> renew
>> password on the same day.
>> Hope this helps. Also, if you have any questions or concerns, please
>> do not
>> hesitate to let me know.
>> Thank you for your time and cooperation.
>>
>> Best regards,
>> Robbin Meng(MSFT)
>> Microsoft CSS Online Newsgroup Support
>> Previous Posts In This Thread:
>>
>> On Thursday, October 09, 2008 4:44 PM
>> Perr wrote:
>> Password Policy Change - When Into Effect
>> client is running SBS 2003 SR2 SP2
>> This is a new environment and I want password policies in effect now
>> but I
>> don't want it happening to every user on the same day. Since the SBS
>> wizard
>> to manage policies will reset all passwords from immediately to 7
>> days I used
>> GPO to change the Server Domain password Policies.
>> Am I correct in understanding this will bypass the all-at-once change
>> and
>> put the requirements in effect based on when the password was last
>> changed -
>> in relation to maximum password age? When I go back and look at the
>> wizard,
>> it now has the history length requirement displayed, and still sow 3
>> days to
>> go into effect.
>> Thanks
>>
>> On Friday, October 10, 2008 7:14 AM
>> v-robme wrote:
>> Hello Perry,Thanks for your post.
>> Hello Perry,
>> Thanks for your post.
>>
>> In Windows Server 2003 group policy, we can set a maximum password
>> age. A
>> common misconception is that the current age for each user's password
>> is
>> reset when this value is changed. Actually, Windows operating system
>> does
>> not actually store the age of the user's password, but rather the
>> last time
>> it was set.
>> The process of checking whether a user password expires:
>>
>> 1. The user account password is not set to Password Never Expires.
>> If it
>> is set as Never Expires, the 'Maximum Password age' setting will be
>> ignored.
>> 2. Get the 'Maximum Password age' value dictated by domain policy,
>> 'pwdLastSet' value of the user account and current domain time.
>> 3. If 'pwdLastSet' + 'Maximum Password age' > = current domain
>> time, the
>> password expires. Before it expires, you will always be prompted to
>> change
>> password.
>> Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last
>> time
>> you changed your password), and all users should not be forced to
>> renew
>> password on the same day.
>> Hope this helps. Also, if you have any questions or concerns, please
>> do not
>> hesitate to let me know.
>> Thank you for your time and cooperation.
>>
>> Best regards,
>> Robbin Meng(MSFT)
>> Microsoft CSS Online Newsgroup Support
>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>
>> Preventing extra HTML Content in File Downloads
>>
>> http://www.eggheadcafe.com/tutorials...cf-4f4f-917e-f
>> 3dcccf496ad/preventing-extra-html-con.aspx
>>

Ha, I thought it was:
SnowWhiteSleepySneezyDopeyDocHappyBashfulGrumpySac remento

because the policy required 8 characters and at least 1 capital


"Larry Struckmeyer[SBS-MVP]" <> wrote in message
news: m...
> Then there is the one about the new computer user whose password was:
>
> SnowWhiteSleepySneezyDopeyDocHappyBashfulGrumpy
>
> becuase company policy required 8 characters.
>
> <g>
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
>
>
>> Hi - the change will not affect users until it's time to change their
>> passwords. I suggest you *not* enable complex password enforcement,
>> but instead just force a long (e.g., 15-char) password length and show
>> users how to use passphrases. It's then more likely they will remember
>> their passwords, rather than writing them on sticky notes and calling
>> you all the time when they can't set them. A passphrase can use spaces
>> (they don't count as characters, but they help create long ones) - a
>> good example to tell your users might be something like this:
>>
>> the mean sysadmin made me use a long password
>>
>>
>>
>> OT, but please don't use the Egghead cafe forum, Techarena or Google
>> Groups to work with the MS public newsgroups. The interface doesn't
>> quote properly, and you're replying to a post which is no longer on
>> the news server, so it's unlikely that anyone will know what you're
>> talking about.
>>
>> Try using a news client, such as Forte Agent, Thunderbird, or even
>> Outlook Express, instead. It's a lot easier to do nearly everything
>> that way. You can mark messages to be watched, filter the views so you
>> can see replies to your posts easily, and search.
>>
>> The Microsoft public news server is msnews.microsoft.com and you can
>> subscribe to as many groups as you like; no authentication is
>> required.
>>
>> The following is from a post by MVP Malke ...
>>
>> ------------------------------------------------------- Here's
>> information on Usenet and using a newsreader:
>>
>> http://www.elephantboycomputers.com/page3.html#12-09-02 - a brief
>> explanation of newsgroups
>> http://michaelstevenstech.com/outlo...ssnewreader.htm
>> http://rickrogers.org/setupoe.htm
>> http://support.microsoft.com/defaul...wto/default.asp
>> - Set Up Newsreader
>> http://www.dts-l.org/goodpost.htm
>> http://www.catb.org/~esr/faqs/smart-questions.html
>> http://aumha.org/nntp.htm - list of MS newsgroups
>> microsoft.public.test.here - MS group to test if your newsreader is
>> working properly
>> http://www.mailmsg.com/SPAM_munging.htm - how to munge email address
>> http://www.blakjak.demon.co.uk/mul_crss.htm - multiposting vs.
>> crossposting
>> Some newsreaders for Windows http://www.forteinc.com/agent/index.php -
>> for Forte http://www.mozilla.org (Thunderbird does newsgroups)
>> http://gravity.tbates.org/
>>
>> -------------------------------------
>>
>> mieke hoogeveen wrote:
>>
>>> Hi,
>>>
>>> I would like to change the complexity settings, because now the
>>> length is only 4 characters. But will people have to change
>>> immediatly their password? Or do they have to meet the complexity
>>> rules only when they change their password? It is a windows 2003
>>> domain.
>>>
>>> Thanks in advance,
>>> Mieke
>>> v-robme wrote:
>>>
>>> Hello Perry,Thanks for your post.
>>> 10-Oct-08
>>> Hello Perry,
>>>
>>> Thanks for your post.
>>>
>>> In Windows Server 2003 group policy, we can set a maximum password
>>> age. A
>>> common misconception is that the current age for each user's password
>>> is
>>> reset when this value is changed. Actually, Windows operating system
>>> does
>>> not actually store the age of the user's password, but rather the
>>> last time
>>> it was set.
>>> The process of checking whether a user password expires:
>>>
>>> 1. The user account password is not set to Password Never Expires.
>>> If it
>>> is set as Never Expires, the 'Maximum Password age' setting will be
>>> ignored.
>>> 2. Get the 'Maximum Password age' value dictated by domain policy,
>>> 'pwdLastSet' value of the user account and current domain time.
>>> 3. If 'pwdLastSet' + 'Maximum Password age' > = current domain
>>> time, the
>>> password expires. Before it expires, you will always be prompted to
>>> change
>>> password.
>>> Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last
>>> time
>>> you changed your password), and all users should not be forced to
>>> renew
>>> password on the same day.
>>> Hope this helps. Also, if you have any questions or concerns, please
>>> do not
>>> hesitate to let me know.
>>> Thank you for your time and cooperation.
>>>
>>> Best regards,
>>> Robbin Meng(MSFT)
>>> Microsoft CSS Online Newsgroup Support
>>> Previous Posts In This Thread:
>>>
>>> On Thursday, October 09, 2008 4:44 PM
>>> Perr wrote:
>>> Password Policy Change - When Into Effect
>>> client is running SBS 2003 SR2 SP2
>>> This is a new environment and I want password policies in effect now
>>> but I
>>> don't want it happening to every user on the same day. Since the SBS
>>> wizard
>>> to manage policies will reset all passwords from immediately to 7
>>> days I used
>>> GPO to change the Server Domain password Policies.
>>> Am I correct in understanding this will bypass the all-at-once change
>>> and
>>> put the requirements in effect based on when the password was last
>>> changed -
>>> in relation to maximum password age? When I go back and look at the
>>> wizard,
>>> it now has the history length requirement displayed, and still sow 3
>>> days to
>>> go into effect.
>>> Thanks
>>>
>>> On Friday, October 10, 2008 7:14 AM
>>> v-robme wrote:
>>> Hello Perry,Thanks for your post.
>>> Hello Perry,
>>> Thanks for your post.
>>>
>>> In Windows Server 2003 group policy, we can set a maximum password
>>> age. A
>>> common misconception is that the current age for each user's password
>>> is
>>> reset when this value is changed. Actually, Windows operating system
>>> does
>>> not actually store the age of the user's password, but rather the
>>> last time
>>> it was set.
>>> The process of checking whether a user password expires:
>>>
>>> 1. The user account password is not set to Password Never Expires.
>>> If it
>>> is set as Never Expires, the 'Maximum Password age' setting will be
>>> ignored.
>>> 2. Get the 'Maximum Password age' value dictated by domain policy,
>>> 'pwdLastSet' value of the user account and current domain time.
>>> 3. If 'pwdLastSet' + 'Maximum Password age' > = current domain
>>> time, the
>>> password expires. Before it expires, you will always be prompted to
>>> change
>>> password.
>>> Therefore, the SBS 2003 server will not reset the 'pwdLastSet' (last
>>> time
>>> you changed your password), and all users should not be forced to
>>> renew
>>> password on the same day.
>>> Hope this helps. Also, if you have any questions or concerns, please
>>> do not
>>> hesitate to let me know.
>>> Thank you for your time and cooperation.
>>>
>>> Best regards,
>>> Robbin Meng(MSFT)
>>> Microsoft CSS Online Newsgroup Support
>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>
>>> Preventing extra HTML Content in File Downloads
>>>
>>> http://www.eggheadcafe.com/tutorials...cf-4f4f-917e-f
>>> 3dcccf496ad/preventing-extra-html-con.aspx
>>>
>
>

Isn't it required to include at least one word of 'leet speak?
'course, your spelling of the capital of CA may qualify...

(I've a machine which can't be reached via the 'net whose admin password
is:

Bill Gates is leaving the building.

(The period is part of the password.)

It is too darn long--I have to re-type it about every 4th attempt.


"M. Murphy" <> wrote in message
news:...
> Ha, I thought it was:
> SnowWhiteSleepySneezyDopeyDocHappyBashfulGrumpySac remento
>
> because the policy required 8 characters and at least 1 capital
>
>
> "Larry Struckmeyer[SBS-MVP]" <> wrote in
> message news: m...
>> Then there is the one about the new computer user whose password was:
>>
>> SnowWhiteSleepySneezyDopeyDocHappyBashfulGrumpy
>>
>> becuase company policy required 8 characters.
>>