lots of known issues, I have gotten it to work on single laptop, everyone else is having some issues,to get it to work in normal environment, I'm assuming that you are going to have roaming users and therefore will be using roamin profiles and probably login scripts, you need to make sure that you have sp 4 or the patch for dot1x, so that the authentication tab show up on your ip properties, for roaming profiles and login scripts to work you have to check machine authentication and be using active directory, this authenticates machine and assigns it to a default vlan that can reach login servers before a user logs in, I also believe that a certificate has to be loaded in local machine store for this to work, haven't tried it without certificate, but works with certificate, the next issues is that once it logs in with user credentials there is another issue, it doesn't release and renew for new vlan, this has been addressed with ms patch q822596, I've gotten this to work successfully on one laptop, although from other posts it appears that there are some issues with patch, another issue is that if you are trying to do single login, and after user logs of, no eapol logoff frame is sent, this is fixed by setting a ms registry of supplicantmode = 3, this is the default value for a wireless interface, but for wired interface it is for some reason set to 2. finally last issue is that there seems to be some issue with stablility, seems that some people have had issues with bluescreens and the svchost.exe process locking up computers. hope this helps, any other feed back from people implementing this and actually having this working in a lan environment would be greatly appreciated. I'll take opposing opinions and possible solutions. thanks
