Re: Per room wireless

Since August 2013 we have deployed about 1680 AP702W's into undergrad residence rooms. Since we enable and support the wired access ports on these APs, we also relocated all outlet boxes to just above desk height. Eriks Rugelis --- Manager, Network Development York University **

RE: [WIRELESS-LAN] TLS Onboarding Vendors

Curtis, Curtis, I'm just asking questions and thinking out loud. Of course there will be infrastructure, but in my mind, a student logging into our student portal to get their personal key _once_, which they then use on all of their devices, is intrinsically less overhead (and less time spent)

Re: [WIRELESS-LAN] TLS Onboarding Vendors

Curtis, Yeah, 5 minutes was my nonprecise way of saying it doesn't take long :). For Windows and iPhones, it is lightening fast. For OSX, it is pretty quick (but the user is annoyingly asked to enter their root credentials multiple times) with android being the most problematic. I am sure

Re: [WIRELESS-LAN] TLS Onboarding Vendors

Hi Jeff, I'm wondering what product you have found that facilitates PPSK to group levels with no administrative overhead and no infrastructure requirements. I mean assuming you don't want every user in the organization to be using the same key and every device in the same VLAN - there has to

RE: [WIRELESS-LAN] TLS Onboarding Vendors

Interesting enough, just with eduroam, I have probably reduced my onboarding time just in the past year by a factor of 6 because so many places I go to are eduroam enabled. So, the initial time onboarding for a federated SSID will be more than made up for the time they would either 1) not have

RE: [WIRELESS-LAN] TLS Onboarding Vendors

Numbers at scale can be misleading. I am not going to be concerned about the 5 minutes once a year for onboarding any more than I am going to worried about the bathroom breaks my employees take, or the 5 minutes they take multiple times in the day to get a coffee. Managing productivity at

Re: [WIRELESS-LAN] TLS Onboarding Vendors

Based on your data, this is what I ran in my head. 58,000 devices on TLS – Say 5 minutes each to provision based on your comments. WAP2-Ent TLS: 5 minutes x 58000 clients = 4833 hours spent by the community connecting to WiFi. 4833 hours each and every year given the expiration on the cert.

Re: [WIRELESS-LAN] Per room wireless

We have started down this road in several of our residences here at Western. M On Nov 4, 2016, at 10:48 AM, Michael Blaisdell > wrote: How many on the list have moved to a per room model for wireless for student residence halls? Michael

RE: [WIRELESS-LAN] Per room wireless

We’re getting ready to deploy almost 900 of the Cisco 1810W (hospitality AP’s) with the cradles in the residence halls. We’re using 802.1x in order to allow students to make use of the additional LAN ports in the cradles. Our design is a high density 5Ghz deployment with some 2.4Ghz radios

Re: [WIRELESS-LAN] Per room wireless

For refurbishments we specify one high level data point per room so that we have flexibility when installing APs near completion of project. AP locations are determined first by predictive design and then later using APoaS survey. After final installation we'll do another survey to tweak power

Re: [WIRELESS-LAN] Per room wireless

We just completed half our dorms and did an AP approximately every other room (installed 2,000). We used the "hospitality" ap's so they are mounted on the wall at jack height. We mounted them where ever jacks where, which created some "interesting" designs. We have many on outside walls,

RE: [WIRELESS-LAN] Per room wireless

Our last two dorms we placed an AP in every third room staggered above and below so no client should be no more than one wall away. We were fortunate enough to get Ethernet drops for APs to every room just in case. I say fortunate but we really pushed it as insurance for the future. Coverage is

RE: [WIRELESS-LAN] Per room wireless

We have moved to a per room model for student residence halls. It has worked well. / Stephen Belcher Assistant Director of Network Operations WVU Information Technology Services One Waterfront Place / PO Box 6500 Morgantown, WV  26506 (304) 293-8440 office (681) 214-3389 mobile

Re: [WIRELESS-LAN] Per room wireless

It depends on the construction, but we typically have 1 AP to 2.5 rooms. The APs are placed inside the rooms, but they're not 1-to-1. On Fri, Nov 4, 2016 at 9:53 AM, Adam T Ferrero wrote: > We have an AP in nearly every suite. That is what made things work well > for us. > >

RE: [WIRELESS-LAN] Per room wireless

Depending on the layout of the Dorm, we are moving to Aruba wireless and we are going to a every other room for the dorms that are long halls and Ap per suite for the Suite Dorms Peppino Muraca Sr. Network Administrator Stonehill College 508-565-1193 pmur...@stonehill.edu

Re: [WIRELESS-LAN] Per room wireless

We've moved partially to that, though not completely. Suite based dorms (typically a common room, bathroom, and two or three bedrooms) and apartments get a single AP per suite/apartment. Drywall or thinner brick construction, we typically do every other room. We were able to get a drop in

RE: [WIRELESS-LAN] Per room wireless

We have an AP in nearly every suite. That is what made things work well for us. Adam -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Sullivan, Don Sent: Friday, November 4, 2016 10:52 AM To:

RE: [WIRELESS-LAN] Per room wireless

For Samford University, depending on the dorm construction, we have a per room or every other room model. Don Sullivan Network Administrator 205-726-2111 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On

Per room wireless

How many on the list have moved to a per room model for wireless for student residence halls? Michael Blaisdell Director of Network Services IT Services Learning Commons/Library Saint Francis University 117 Evergreen Drive Loretto, PA 15940 814-472-3242 http://www.francis.edu The best way to

Re: [WIRELESS-LAN] 802.1x (eduroam) Win10 - no prompt for new password after credential change

>The first was that even using username@domain, the Windows client still passed >netbiosdomain\user to the RADIUS server. By default, Windows will set "Automatically use my Windows logon name and password" for PEAP connections, that is why you see netbiosdomain\user is passed to RADIUS

RE: TLS Onboarding Vendors

We do, too. I really wasn’t even thinking of those types of devices in the initial response because our belief has been for any device that doesn’t support TLS to just use PSK. Yesterday we had 58,000 devices on eduroam (using TLS) and 9000 on our PSK network. Ryan -Original

RE: [WIRELESS-LAN] TLS Onboarding Vendors

Well, in truth I was referring to portable devices. Of your list, I guess I forgot about the fire. We run a PSK network for those devices. -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Jeffrey

Re: [WIRELESS-LAN] 802.1x (eduroam) Win10 - no prompt for new password after credential change

Thanks for the replies. We've run into 2 issues with using username@domain for login. The first was that even using username@domain, the Windows client still passed netbiosdomain\user to the RADIUS server. It's my assumption that this would not work for remote users. The second issue that we

RE: TLS Onboarding Vendors

Those devices do not support 802.1X. That is why we currently have a separate SSID for those devices. PPSK *may* be a more secure solution for those devices that do not support TLS much like WPA2-Personal (PSK) is currently a solution for devices that do not support WPA2-Enterprise (802.1X).

RE: 802.1x (eduroam) Win10 - no prompt for new password after credential change

I may be wrong, but wouldn't the proper solution be to use the full "username@domain" for login as Microsoft recommended when AD was introduced? You could then have the network caching turned off. We do not use EDUROAM but only use the network caching for non-domain (usually student owned)