G
Gabe Knuth
This old battle again...
We've got an AD (previously used only Netware for the PC's) with 1200 or so
users in it. About 100 of those are laptop users that are rarely in the
office.
In the past, the users would log on to their local machine, connect via
Contivity VPN, then authenticate to a Windows file share in a domain that
pretty much only servers were in by using their domain credentials. Their
passwords were set to never expire and were synched manually with their
Novell and local machine passwords.
Now we're adding them to AD. We've got a corporate SOX policy in place, so
each user is required to change their password afte x-number of days.
Problem is, these users don't connect to the network with their laptops
before their password expires. That works OK for the local machine, it'll
just cache it until they plug in again, but if they log on with their cached
password (after connecting to the VPN), they won't be able to connect to the
file share.
What's everyone else doing in situations like this? I've been trying to
find a way to have their dial-up client and their VPN client launch before
the logon to the box. That should fix this. It seems to me there is a
simpler way, and I'm just mucking it up and over thinking it.
Any thoughts are appreciated.
Thanks,
Gabe
We've got an AD (previously used only Netware for the PC's) with 1200 or so
users in it. About 100 of those are laptop users that are rarely in the
office.
In the past, the users would log on to their local machine, connect via
Contivity VPN, then authenticate to a Windows file share in a domain that
pretty much only servers were in by using their domain credentials. Their
passwords were set to never expire and were synched manually with their
Novell and local machine passwords.
Now we're adding them to AD. We've got a corporate SOX policy in place, so
each user is required to change their password afte x-number of days.
Problem is, these users don't connect to the network with their laptops
before their password expires. That works OK for the local machine, it'll
just cache it until they plug in again, but if they log on with their cached
password (after connecting to the VPN), they won't be able to connect to the
file share.
What's everyone else doing in situations like this? I've been trying to
find a way to have their dial-up client and their VPN client launch before
the logon to the box. That should fix this. It seems to me there is a
simpler way, and I'm just mucking it up and over thinking it.
Any thoughts are appreciated.
Thanks,
Gabe