By the designated date. Top posted for your confusion. On Tue, Jun 15, 2010 at 3:17 PM, Jonathan Link <jonathan.l...@gmail.com>wrote:
> Yes, it will interfere with accessing resources. > I had to schedule a day in our office so everyone knew well in advance. > Those that couldn't or chose not to be at work that day had an > administratively assigned password (in the event that they needed access), > or change their password in advance of the date. > I believe I only had one person who didn't change their password on the > designated date. > > > > On Tue, Jun 15, 2010 at 3:11 PM, Ben Scott <mailvor...@gmail.com> wrote: > >> Hello, list, >> >> After years of lobbying on my part, I have finally gotten top >> management at %WORK% to approve a company password policy, complete >> with enforcement via Active Directory/Group Policy. (And there was >> much rejoicing!) >> >> I know we have people who have never changed their password since >> they were hired in 2001. When we suddenly go from "No password >> expiration" to "X days", at their next logon, they'll be prompted to >> change their password. However, until they logoff/logon, the system >> won't prompt them. My question is: Will they have trouble accessing >> resources until they change their password? I've never tried to use a >> Windows domain with an 8-year-expired password before. >> >> Win 2000 AD server, Win XP Pro SP3 clients. >> >> (Yes I know Win2K has five weeks until EOL. I'm working on it. >> Budget priorities, bad economy, yadda yadda.) >> >> -- Ben >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
