Domain Password Policy Not Prompting Windows 7 Clients to Change Password Before Expiry

Posted on 2010-09-22
Last Modified: 2012-05-10

We are a Windows Server 2008 domain and have a password policy set at domain level which was working fine until we upgraded the clients to Windows 7.  Now it no longer prompts the users to change their passwords before expiry - it simply expires, then tells them they need to change the password before they are able to login.

Our password policy is set as follows:
Min Length: 6 characters
Password Complexity is on
Maximum Age: 120 days
Minimum Age: 2 days
Password History: 2
Interactive Logon:Prompt User to Change Password Before Expiration: 14 days

When our clients were running Windows XP they were regularly prompted to change their passwords from 14 days before expiry & they could choose to ignore this prompt or set a new password at that point.  It would appear that the password policy itself is working as paswords are expiring, it's just the prompt which isn't working for users who logon to a Windows 7 machine.  I need this to work as our staff and students connect to our site from home & if their password expires without them realising, they will not be able to login remotely.

Does anyone have any ideas?
Question by:stbernards
  • 4
  • 2
  • 2
LVL 20

Expert Comment

by:Iain MacMillan
ID: 33732873
have you connected to your DC with the Win 7 system with RSAT tools installed, to update the GP files for Win 7 systems, or have a 2008 DC server?

you may need to check that the policy you use, is applicable to Win 7 systems, and not just XP - do you have your Win 7 machine accounts in a separate OU, or are they in among the XP machine accounts?  You could always create a new password policy specifically for Win 7 systems.

you can also run the GPRESULT /H filename.html command (call it whatever file-name you want), to see what policies are being run on your Win 7 system.

Author Comment

ID: 33733410

My domain controllers are both server 2008, but I tend to use RSAT tools on my Windows 7 client machine to do any group policy editing.  However, our password policy is the same one that was in place when our domain controllers were 2003 and the clients were xp - I haven't made any changes to the policy - do I need to?

Our Windows 7 machine accounts are in the same OU as the xp machines.  Are you suggesting that there are new policy settings when configuring a password policy for a windows 7 client machine?  If so what are they?

I have already run GPRESULT /H for my login on my machine & the default domain policy is applying & specifically, the password policies I described above are applying (or so it says!)


Accepted Solution

mszal101 earned 500 total points
ID: 33733786
If I remember correctly we had this same problem when we first started putting windows 7 machines on our network - the problem was that we were using the default setting on the default domain policy, however windows 7 requires it to be manually set in order to take effect.

The default is 14 days which we were happy with - but I had to manually set it in the RSAT under:

Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options

The option in question is "interactive logon: prompt user to change password before expiration"

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

LVL 20

Expert Comment

by:Iain MacMillan
ID: 33733832
yes you need to specifically set it, as mszal101 says.  once you save it, you just need to run GPUPDATE to test it.

OU sorting is a personal preference thing, but given there are far more options to set in GPO for Win 7 and 2008 Server, you might want to keep the 7 machine accounts separate from the XP systems, until such time you have removed all XP presence.

Author Comment

ID: 33735176

I have just checked our setup again & the settings which MSZAL101 suggested configuring are already set that way in GPMC

ie. Computer config > Windows Settings > Security Settings > Local Policies > Security Options
"The Interactive Logon: prompt user to change password before expiration" is already set to 14 days - as I said I haven't changed anything & it has always worked up till now.

This is set in the Default Domain Policy.  Are you saying that I need to create a new OU for only Windows 7 machines & set the policy at that level instead?

I'm sorry to sound thick, but I don't understand why it has stopped working if it as the Domain level

Thanks for your help

Assisted Solution

mszal101 earned 500 total points
ID: 33736845
Is it set by default to 14 days or did you Hard Set it to 14 days?  There is a difference - For some reason windows 7 does not employ it unless it is set manually.

Author Comment

ID: 33752623
Brilliant - that worked, thanks.

I hard set my domain password policy to prompt at 14 days & now I am being prompted by the balloon in the system tray.  I assume this is the normal Windows 7 way now & actually it it better because it is easier to ignore if it is set to a longer time span.

Author Closing Comment

ID: 33752638
Thank you, this solution fixed my problem.  It was the hard setting that did the trick - obviously another Microsoft bug!

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A safe way to clean winsxs folder from your windows server 2008 R2 editions
By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

815 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now