![]() VPN Client network adapter matches: HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Group Policy\History\NetworkName and the DC's are reachable. I have read more about how NLA works here: and I have verified that the connection-specific dns name of the Cisco ![]() When using the Cisco VPN client: the network identification process is never initiated when the client connects and the network is not identified with a domain profile - which means that GPO is not Is identified with a domain profile, and GPO is processed. When using the PPTP VPN: the connection triggers NLA, and the network I have compared the behavior of a Windows 7 PC using a PPTP connection vs the behavior of a Windows 7 PC using the Cisco VPN client. Not triggered when the Cisco VPN client connects. I am having an issue in which Group Policy (computer policy) is not applied to Windows 7 Computers when they connect to the network via the Cisco VPN client (versionĪs far as I can tell: The problem seems to be that Windows 7 network location awareness (NLA overview: ) does not detect the presence of a domain controller because NLA is I am administering a Server 2003 AD environment with a mix of XP and Windows 7 Clients.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |