The dormitory is the biggest and most complex setting of the school WiFi. It has a large number of people, long hours, bandwidth sensitivity, and students have little tolerance to use, and it's a little card, a re-run, complaining about its immediate release to their friends. The process of certification of the dormitory scene, if not well designed, will not save the experience.
First authentication to be reduced
The first time a new student goes to the dormitory WiFi is the most vulnerable moment of satisfaction. The ideal process is: go on WiFi's automatic ejection, log in with a school worker's number plus password, tie up equipment, and then stop using this mobile computer. Trouble is that one student has a cell phone, a notebook, a tablet, or a school limit on online equipment, which exceeds the number of hand kicks. We suggest that we do it when you get certified for the first time."Common equipment"The concept is clear, allowing two or three sets to be tied beyond the check-up.
NATHHELL_SEAMLESS_AUTH is more comfortable than Portal
Portal certification pages are re-boarded every time they break the network, and the signal in the dormitory is a tremor. The students are tired. On conditions permitting, we can do Seamless Authentication: after the first student accreditation, the system remembers that the equipment's MAC or it is issued under a single identity, then goes straight to the next level without playing the page. This is a qualitative change in the experience. After meeting a high school on NatsheL_SEAMLES_AUTH, the number of related changes in the dormitory network has dropped by 40%. The certification system is conditional on the support of MAC binding or 802.1x, the equipment capability being confirmed before construction and the equipment being purchased before it is found not to be supported.
We need to get out of line fast. Don't keep the students waiting.
The accommodation WiFi is better and has fluctuations, the AP switchover and DHCP renewals can lead to short breakpages. The authentication process must be designed to automatically reconnect with previous vouchers after a break, not play another page to allow students to lose their passwords. Backstage conversations should be set in a reasonable way, without causing frequent loss of certification. We suggest that sessions remain at least daily, together with Natshell_SEAMLES_AUTH, where students are largely unacknowledged by the existence of certification.
The equipment and people must be right, but not too dead.
The accommodation bill is charged to the student account, and a single account is kept off the floor. It is common to limit the number of items online and the number of meetings that are held up. But this is a good measure: too dead, students are blocked from sharing their cellular hot spots; too loose, accounts are sold widely. We suggest that accommodation be set as many as three separate accounts are online, and that students manage their own list of equipment on self-help pages, and find that strange equipment can kick themselves out.
Night and vacation strategies need to be considered separately.
The housing network has a clear time feature, peaks at night and summer holidays almost empty. Certification and billing processes must match the rhythm: vacations can freeze the package automatically, start school again, and avoid students paying for useless holidays; certification servers should be able to handle and issue them at night peaks, and the days of entry into the system are stress points and the system needs to be pressured ahead. We've seen thousands of people first day of school, first certified, server failed, Portal page was blocked, network broken. This peak is set aside when the process is designed, and leave strategy is aligned with student billing cycles, and not visible."People are leaving, and they're still withholding their money."- It's embarrassing.
The process of certifying the dormitory scenes, not the target."Keep the students in check."Yes."It's like, you know, it's like..."The first deduction, usual unconsciousness, fast reconnection, self-control and elasticity of the equipment were made so that the WiFi billing system in the dormitory could be kept quiet and run quietly, instead of being complained daily.
Self-help unties less than a manager.
Students change their mobile phones, fix computers, sell old equipment, and leave a binding record. If you can only find managers, the dormitory manager's phone is blown up. We strongly recommend that students have a self-help page that looks at their own equipment and that allows them to untie strange devices. This page is best done with check-in bills, which are owned by each student. The more self-help capacity we have, the less manual work there.
Visitors and co-loans need temporary access.
There are often students in the dormitories who come to connect or parents who send things on a temporary basis. It seems unimpressive, liberal and dangerous to move online. We suggest that the dormitory scene be given a short-time visitor code that allows students to generate, time limits, speed limits, and automatic expiry of their maturity. This would take care of both the need for temporary services and not the cost system.