Authentication failure or connection to the wrong network when you use Group Policy to deploy 802.1X authentication settings to a client computer that is running Windows Vista or Windows Server 2008
In a network environment, you try to use Group Policy to deploy 802.1X authentication settings to a client computer that is running Windows Vista or Windows Server 2008. In this situation, the client computer incorrectly uses the built-in local default 802.1X profile before the Group Policy profile is applied.
This behavior causes the operating system to start authentication based on the built-in local authentication settings. Therefore, the computer connects to the wrong network or fails authentication instead of successfully connecting to the corporate network.
Note: Disconnecting and then reconnecting the network connection, restarting the Wired AutoConfig (dot3svc) service, or restarting the computer will typically enable the authentication to complete successfully.
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB2583709.