10-12-2015 06:00 AM
just updated a couple of Nexus devices and onboard doesn't seem to work. Everything looks ok in the tracker so it seems it's the fault is in the Quickconnect-app. I even tried making the app device-admin with no luck.
Running Clearpass 6.5.2
App version 1.0.71027
Anyone else tried and got it working?
10-12-2015 06:01 AM
--Give Kudos: found something helpful, important, or cool? Click Kudos Star in a post.
--Problem Solved? Click "Accepted Solution" in a post.
10-12-2015 11:39 PM
Please open a TAC case for tracking. I experienced the same, and found out that QuickConnect cannot delete the WLAN profile in Android 6.0, and that is supposed to be changed by Google 'by design'. An App may only delete or modify WLAN profiles that it created itself. Engineering is aware of this and working on it. Please send send me a personal message with the TAC case number if you want me to have a look at your TAC case.
As a workaround for now, you can Onboard over another SSID (Guest SSID may work), and delete the SSID that you are Onboarding to (typically the Corporate SSID) before Onboarding. In my own testing, I succesfully onboarded two Nexus devices running Android 6.0.
If you have urgent issues, please contact your Aruba partner or Aruba TAC.
10-13-2015 12:26 AM
I've opened a TAC case and have sent them the logs from the quickconnect-app.
And the workaround works, i successfully onboarded using ourguest SSID. I guess we can use that for now. I'd rather have the same SSID-onboard working though, since people tend to forget to delete the connection to the guest-network and call helpdesk to complain that it isn't working the next day.
11-24-2015 05:02 AM
My team reports that ours is now working for the Android 6 users with the new quick connect app but I don't think its a very smooth process. Based on what I am reading the user has to go through our onboard process installs the app and gets the profiles but then gets a pop-up as shown below:
After following the steps of forgetting the network and hitting the back button the user then has to follow a few other prompts which I am not 100% clear if its a complete reboard again or if the Onboard process just starts again with the profiles push but what ever it is, its working.
Only other report I had from the team is the new quick connect does not work for Android 5.1.