After enabling Windows 10 Credential Guard (only available on Win10 Enterprise Edition), location awareness rules for configuring ITCM to point at the nearest scalability server, are no longer working as expected.
Client Automation (ITCM) -- any version
Windows 10 Enterprise Edition
The Windows 10 Credential Guard feature adds a new networking adapter, "vEthernet Switch", at the top of the network adapter binding order. As this adapter is at the top of the binding order, CAM binds to it, as revealed in the "camstat -a" output. ITCM communication is successful in this scenario, however, location awareness now uses the vEthernet IP address when processing location awareness rules, instead of the real IP address. The problem here is that LOCATION AWARENESS is now based on the vEnternet adapter at the top of the binding order, rather than the real network adapter.
At this time, we are tracking this conflict between Location Awareness and the Windows Credential Guard Feature, but do not yet have a solution. Please open a support case referencing feature story F19199, so we can add additional sites for tracking and prioritization purposes.
Microsoft information on the Credential Guard feature: