Have an open student forum, perhaps done in conjunction with your student government. I find this the best way to get feedback, then follow it up with a basic survey (not more than 10 questions), and have an incentive tied to completion of the survey e.g. Free printing block, free coffee (we have a student run coffee house), etc.
In the basic survey, ask if the respondent would like to participate in an more in-depth survey and/or discussion group. Once you get the basic survey, so the in-depth survey and/or discussion group. The difficulty with wireless is that even when the problem is the client, you still get the blame. In addition, it would be really important to ask about things you may perceive as beneficial, but the students do not e.g. On-boarding, registering device, multiple SSIDs, etc. Jeff On 10/22/15, 7:06 AM, "The EDUCAUSE Wireless Issues Constituent Group Listserv on behalf of Frank Sweetser" <[email protected] on behalf of [email protected]> wrote: >Others have already covered most of the same ground I would on collecting SNMP >data sets and actively looking where users are stubbornly sulking ("why didn't >anyone fix this problem I didn't tell anyone about!?"), but if you have at >least a little budget and some time you could put a decent system together >yourself. Most of the fancy tools out there aimed at this problem like >7signals and NetBeez are just fancy agents running on Raspberry Pis. If I >were in your situation, and wanted to gather hard data, here's what I would do: > > * Get hold of a few of them, and set them up in some of your higher profile >locations (libraries, student centers, larger classrooms, etc) with a wireless >adapter > > * Use a wired connection for backhaul and management. If you can put them >on a PoE port, you can get a splitter that will allow you to power the Pi off >of PoE, making deployment a little simpler. > > * Use a combination of smokeping and regularly scripted iperf tests, dumped >into something like graphite. Throwing in some tests for common services >(school web site, email, etc) wouldn't hurt either. > >These can give you some hard metrics on latency and throughput, which can go a >long way in figuring out whether wireless complaints are really about >wireless, or something else in the chain. > >Frank Sweetser fs at wpi.edu | For every problem, there is a solution that >Manager of Network Operations | is simple, elegant, and wrong. >Worcester Polytechnic Institute | - HL Mencken > >On 10/22/2015 07:04 AM, Williams, Matthew wrote: >> I have been instructed that I need determine a metric that reasonably >> guestimates the end user experience of our wireless networks, without >> procuring a system(s) that does it. I readily admit that my head kind of >> exploded when this directive was given. Have any of you done this exercise >> or >> have any ideas/formulas to try to calculate something like this? Thanks for >> any ideas that you care to share. >> >> Respectfully, >> >> Matthew Williams >> >> Manager, Network and Telecommunications Services >> >> Kent State University >> >> Office: (330) 672-7246 >> >> Mobile: (330) 469-0445 >> >> ********** Participation and subscription information for this EDUCAUSE >> Constituent Group discussion list can be found at >> http://www.educause.edu/groups/. >> > >********** >Participation and subscription information for this EDUCAUSE Constituent Group >discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
