Mustang

Are you sure you are using 172.0.0.11 and other addresses in this range?? As 172.0.0.0 to 172.15.255.255 isn't a private address range and is owned by AT&T. If you are using these IPs you need to change them ASAP. Private address for class B are 172.16.0.0 to 172.31.255.255 you also shouldn't be using the vlan 1 (default_vlan) HP always recommend not using it. I think you should sort these problems out first before you try and get the BYOD working.

We have 110 APs (121 and 330) and had them installed by Lan3 about 2 years ago and are still troubleshooting the problems now. First problem, lazy ass bloke from Lan3 didn't do a proper survey and just guessed where the AP's should go. Meraki and Aerohive use the exact same hardware, get some trial AP's and open them up have a look. Hivemanager and HiveOS are buggy and new releases often get pulled and then re-released within a few days to fix the major bugs. Roaming doesn't work properly, guest access has lots of issues, AP's auto power setting doesn't work, AP's randomly reboot. We do have a very complicated Lan design, we route all the traffic from the edge and this normally confuses a lot of engineering and takes them a while to get there head around it. I suspect this our Lan design hasn't helped with some of the issues but it really isn't anything unique, we have been working with Lan3 and Aerohive to fix most of the issues and things are much better than when it was installed 2 years ago. If you do use Lan3 you want Steve Coles doing the install, he's knows his stuff. I advise you test as many manufactures as you can and focus on the wireless capabilities before you get sucked in by all the features. We tested Aerohive, Meraki, Xirrus, Extricom, Aruba and HP, we would have tested Ruckus kit but couldn't get demo equipment.

I believe 802.11ac got ratified on the 8th of January

As stated above that setting doesn't work, That setting will only effect local account polices on servers and workstations. Fine grained password policies are the only way to do what you require but as stated works on security group not ou. Using adsi edit to do it is fairly simple but could be dangerous if you change the wrong thing. It is even easier using the admin tools in windows 8, 8.1, 2012 and 2012 r2. If you aren't licensed for any of these just download a trial version, once up and running use the Active Directory Admin Centre to create the password policy Creating fine grained password policies through GUI Windows server 2012

If they can't open apps when the server goes down it sounds like your using network homes and not local as you stated. Network homes put a lot of strain on the network. Where in the North West are you based??

@RTFM what Ruckus AP's did you go for??

Well Ruckus so far have managed to price themselves out of the running by being double the cost of everyone else

We are looking at about 75 to 90 AP's from AeroHive Aruba Cisco Extricom HP Merkai Ruckus Xirrus We have also been told around the 50K mark but i think this seems really expensive

Hi everyone i have found your site after a bit of googling round for information on wireless vendors. I have already read a number of topics, which were very useful I am currently looking at replacing our Wireless Lan with another vendor and upgrading to N. We have spoken to a few vendors and sales people but depending on who you speak to cost difference is immense and i think because we are in education they think we can afford anything. I know this is really cheeky but could any of you guys let me know how much you paid for your wireless upgrade in the past year and what kit you had, as i think we are getting taken for a ride. If you don't want to post on the thread thats fine but you are more than welcome to inbox me Thanks Mustang