We are having problems with transparent user authentication. Some users are getting the default policy instead of the policy that the should be getting based on AD security group membership. This only seems to be happening with laptops that are taken home at night, then docked again in the morning. Or, if they are un-docking and moving around the building then docking again. If I have the users turn off their wireless, then reboot and log in again it sometimes works.
We are currently only using the DC agent installed on our policy server. Should I also install the Logon Agent on the policy server as well? Could that help resolve the issue? My other thought is to enable manual authentication as the Additional Authentication Option? It is currently set to computer or network policy.
Any help would be appreciated!