08-22-2020 02:15 AM
Hello,
we are currently working to implement dot1x / NAC and have a problem with USB C-Dock´s.
My colleauge from our client team wants to rollout the supplicant configuration via script that activates dot1x on every network card adapter in Windows 10.
Nevertheless as people move around with their notebook they connect to different USB C-Dock´s
Everytime when this happens a new Network Card Adapter is created without dot1x configuration.
The script must triggered again to apply the configuration on the newly created adapter.
Is there anybody facing the same issue or has an idea how to solve it ?
How did you rollout dot1x configuration ?
Best regards,
steffen bodensohn
08-22-2020 09:31 AM
If you use AD GPO's to push out the supplicant configuration, then the config applies to all ethernet interfaces. That is the recommended way of pushing it out.
08-23-2020 01:17 AM
08-23-2020 07:56 PM
It sounds like the Win10 PC is creating new connection profiles (possibly with a different pass-through MAC address) for each new dock that is connected. The supplicant for that connection would then have to be configured for 802.1x.
This is likely a function of the driver for the docking station. If you have not done so already, I would suggest opening a support case with the dock vendor to see if there as advanced setting in the driver that will mitigate this issue (or request an enhancement to the driver if it does not exist).
With more and more enterprise customers deploying Wired 802.1x, I would think vendors will need to consider this caveat in their driver designs.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide