For us, we always get a message when trying to connect that the ‘SSID is not in range’ if the person is onboarding off campus. But the clients don’t need to attempt multiple times. the devil is in the details. What operating system are you seeing this with? We are currently in Big Sur hell, but it looks like SecureW2 is testing a ‘big fix’ that should be ready next week.
Ryan Turner Head of Networking, ITS The University of North Carolina at Chapel Hill +1 919 274 7926 Mobile +1 919 445 0113 Office On Jun 18, 2021, at 5:51 PM, Marsen Nuzi <[email protected]> wrote: Hello All, How is the user experience when trying to onboard remotely with securew2? We are still in the testing phase and when users try onboarding remotely they get a difficult experience. Since it is looking for an SSID that is not available at the time of the process the onboarding keeps failing until after a few times then it gets to the last step. Looking to make the onboarding process a little easier and less painful for the end users. Thanks Marsen Nuzi Information Technology 71 5TH AVE, ROOM 913C, NEW YORK, NY 10003 [email protected]<mailto:[email protected]> ********** Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the person who sent the message, copy and paste their email address and forward the email reply. Additional participation and subscription information can be found at https://www.educause.edu/community ********** Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the person who sent the message, copy and paste their email address and forward the email reply. Additional participation and subscription information can be found at https://www.educause.edu/community
