Sync issue with VPN when users change password locally. Safe Boot is also used on laptops.

I am working with a customer who has field agents with laptops. The field agent is offline about 95% of the time. They connect to the VPN maybe twice a month, which then gets them on the corporate network.  The customer wants to implement a 60 day password change policy.  The issue is that the agents will already have booted their laptops up and made a password change which is cached locally.  They may run like this for 2 weeks. When they try to connect to the VPN (which uses the same AD password for login), they will not be able to connect because they are attempting to use their new password.  The VPN is expecting the old password because AD server has not been updated yet.  How can we manage password changes and sync issues for these field agents who are offline most of the time but are still required to change their password every 60 days?
opie51Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Rob WilliamsConnect With a Mentor Commented:
Are you using the Windows VPN client by any chance? If so, and the machines are members of the domain, at logon there is a check box option to allow the user to use a dial up connection. Selecting this will then allow the user to connect to the VPN, which completes and allows the user to have a proper network connected session, rather than one using cached credentials. If the user then changes their password during this session it is changed in AD and on the local machine.

It is a common problem, and this is one option.
0
All Courses

From novice to tech pro — start learning today.