Windows 10 and LANProfiles on 802.1X networks

Hi,

As an originally, this problem is linked to Microsoft Surface Hub devices, where it is running Windows 10 Teams edition. But I believe this could be universal question...

So I have a network where I do have 802.1X network, meaning to be able to join to network the certificate for machines is not enough. My idea for the Surface Hub device was to use OneXEnabled/OneXEnforced configurations and disable both of them ("false") using the LANProfile on the provisioning package. Then I could use exception rules on the network.

What I have been seen working so far, has been if I have disabled OneX on the LANProfile I have been able to get device up to network, if the device has been on 802.1X free network during the startup. When the startup is over, I could connect the device to 802.1X enabled network and that is still working smoothly.

Either I have not understood something correctly, or there could be problem on the Windows platform, but if the device is on the 802.1X network all the time, I'm unable to get the device online. For me it feels like, if the network is preventing device to come connected (like 802.1X does), then the LANProfile gets never uploaded and the devices stays disconnected.

I was not able to found too many hits from DuckDuckGo searches, so I though if I could reach some others from here who have been working around this topic. Any thoughts what is on-going? Why the device must be in 802.1X network to get LANProfile enabled?