Posted on 09-06-2018 06:15 AM
Our corporate network was never set up to use 'standards' for Wi-Fi. We now use EAP-TLS.
I've created a profile that allows users to join the network. This has worked for all users I've tested it with.
All users are standard, mobile network accounts
However, there is one user on the latest build of 10.13.6 that cannot use the profile. When it is installed and I turn Wi-Fi on - it automatically turns off.
The profile requires Ethernet to be connected in order to download the machine certificate from Active Directory.
This system does appear to download the cert - however, despite standard troubleshooting - I can't figure out why it switches off.
Without the profile - the user is able to utilize our guest network
Posted on 09-07-2018 08:35 PM
This issue persists under the local admin account as well as is isolated to this one computer
Posted on 09-08-2018 01:00 AM
Hi @k3vmo
Is it possible that the wireless network or the "SSID" is already configured on the machine somewhere?
Check via CLI with something like;
networksetup -listpreferredwirelessnetworks en0
Or try also if there is an keychain entry that is wiling to fill out username/password for the wireless network and the config profile with EAP-TLS AD Machine certificate can't overwrite?
Cheers,
Thijs.