Hello, I recently had an issue with a customer where Secure Client NAM on some workstations (not all) temporarily selects the wireless profile, when no wireless NICs are present, ie these are wired only workstations. The Secure Client configuration.xml profile is setup for a wired EAP-Chaining profile, and a wireless EAP-Chaining profile, and the workstations go from an authenticated state with the correct wired profile, to attempting to authenticate with wireless that doesn't exist.
The customer is running Secure Client 5.1.2.42, NAM and ISE Posture modules.
ISE is running 3.3 P5, and when this occurs, the Anomalous Endpoint Detection rule is hit and the workstation gets rejected in Context Visibility.
Has anyone seen this, and have an idea where to look?
