I have an odd situation. When doing some AD work for a remote user I ran into a snag I haven't had before. Whenever we make changes to an AD users profile we ask them to VPN into our internal network so that they can cache their new AD information and then lock their machine and re-login to complete the cache process. This has worked all but this one time. When this particular remote user locks their machine after using the VPN client. The AD info doesn't cache and he cannot log in with new credentials. When logging in with the old credentials I found out it is because Cisco VPN terminates with a very unhelpful "This session has been terminated" and no return code.
This is on a Dell Latitude E6520 with Windows 7 x64
The client is Cisco VPN 5.0.07
The VPN profile has been tested on other user's machines and is confirmed working and I have disabled and enabled fastuserswitching in the registry.