andyire

Ah that makes sense . I suspect we will have some how decide not to subscribe. Also some users may decide to bring additional devices such as laptops. It's a shame you can't prevent apps being installed. Could you remove the App Store? Blacklisting apps is a fair workaround . How would you use the smooth wall with the ruckus? The user connects to open SSID and gets redirected to smooth wall captive portal for authentication ? How does the student WLAN and auth each day work? I had heard that ZeroIT was a bit flaky for non iOS stuff would be interesting to see if the update fixes it a little. The supplier I am working with said there were some improvements but unfortunately I am past the testing stage. How have you found Ruckus in your environment? What made you choose Ruckus over other brands? Thanks Andy

Hi Sagima for you post. Glad to hear your experience has gone well so far, though I suppose it is early days. How have you found them config wise? Is the cli & UI easy to get your head round?

Hi Peter , Thanks for your response. It's good to hear that it works well with airwatch. I think we will end up factoring the cost of airwatch into the purchase of iPads but this is not set in stone. When you say you haven't put the BYOD's on to airwatch do you mean additional devices which pupils decide to bring to school I.e their windows laptops or MacBooks? As regards VPN apps.. Would it be possible to prevent the install of VPN apps via Airwatch to stop them circumventing the proxy/filters ? Out of interest how are you managing access to the WIFI? Are you using Radius for BYOD SSID? Or ZeroIT feature? Cheers Andy

Hi we are looking to upgrade our wireless infrastructure and Ruckus is looking like the front runner after some testing. Before deciding on this as the solotuin I am interesting to find out what experiences people have had with using Ruckus wireless solutions with Airwatch for BYOD iOS deployments. ? Also how are you managing & restricting student access to the WIFI ? Cheers Andyire

10Gig network upgrade - Dell N2000 series edge switch N4032F Core switch ? Any good ?

they are N2000 series edge and N4032F Core which are Dell Networking as far as I can tell.? The cli seems very similar to the Cisco cli. they are on par with the 2920HP stuff as far as I can tell

We are looking at refreshing the wired and wireless networking hardware here over the summer break. After testing various WAP vendors I have decided that Ruckus wireless is likely to be the most suitable option. I am however torn between wired switching vendors. We are currently using 10/100 Cisco catalyst hardware but I have decided against replacing with new Cisco hardware. I have had great experience in the past with HP procurve gear so initially said to the resellers I am working with that, this is what I am after. They have all come back with varying configurations at various costs and interestingly have fired a Dell quote into the mix just for comparison. The HP kit is coming in at roughly £10,000 more expensive than the Dell kit and has been specced at 1G (although capable of 10G) throughout compared to 10G core and Edge switching with Dell !!! This is where I have a dilema. Historically I have found HP support to be excellent, however Dell on the other hand have been at times less satisfactory. I must admit however that the last time I dealt with Dell was some years ago. I am really interested in finding out peoples thoughts on current Dell switching hardware. Should I go with a more expensive HP at 1G or invest in Dell 10G hardware at a lower price point ? Will I regret Dell should I need to deal with Dell support or is this a thing of the past ? Cheers

Why don't you just setup a test SSID on the Ruckus AP I.e. WirelessSurvey.... attach the ruckus AP to a mic stand. Place the AP in a classroom, plugin using PoE injector, long cat5 cable etc.... Then walk away from the AP to adjacent classes etc.. Then using insider you can find the SSID test signal strength (-60db or less) and bandwidth ...

I can confirm Impero does work for PC, but I didnt have success with OS X when I set this up at my last school. Also although it was initially described as possible it was later admitted by an Impero Tech that in fact it isn't possible to wake OS X up from sleep remotely. Their advice was to walk to the suite and move mouse or .. etc.. Things to check RE power management would be Client wise - Client BIOS settings (wake on LAN allowed) - I have seen this setting referred to as many things. - NIC settings via device manager in Windows (magic packet listening) Switch wise - As mentioned above if you have multiple subnets or VLANS on your network you will need to check if the WOL broadcast (typically UDP packets sent to port 7 or port 9) is allowed/forwarded between them. (IPHelpers) Other things to consider are - Virus protection / firewall on the Impero Server - Are users powering the PC down and then turning off wall switches/ unplugging the units If you struggle after you have tried these things and had no luck after contacting Impero Support, it could be an option ( although slightly crude ) to write a simple batch script along the lines of -------------- @echo off shutdown -r :EXIT ------------- and create a scheduled task to run it on each PC at a certain time each evening. There is also some power management control which can be had via group policy.

E-Learning Technician. Redland Green School is a high performing comprehensive school serving the local area of Redland in north Bristol. We are an 11-19 school with about 430 in our Post-16 learning community. We offer outstanding opportunities and CPD development for staff to contribute to the school’s continuing development. Redland Green School is a very special place to work and we are looking to recruit a suitably qualified and motivated E Learning Technician. To provide technical, creative and organisational assistance to staff and students in their use of ICT and web based systems to improve learning in all areas. Deadline is : Wednesday, 9th July at midday Salary Details: Term time only + 5 INSET days; Permanent; Full Time (37 hours per week) + 5 Additional Days Bristol Grade 8 (£10.27 - £11.26 per hour) Start Date: ASAP Please find a link to apply here: Redland Green School - E Learning Technician

Hi mprice, I would suggest the following as a place to start; 1) creating a test user 2) on the ADDS test users profile tab, add the path \\server.local\profiles$\students (you could use something like \\server.local\profiles$\testAccount, and change it up later if you wanted) 3) log on to your test Windows 7 machine with your test user account. 4) make any necessary profile customizations you require (i.e changing the desktop background), 5) log off the PC and windows will upload the profile to your profile server and create the folder \\server.local\profiles$\students.V2 for you. I suggest doing it this way because, if you simply copy the profile from the local PC up to the profile server you will end up with unnecessary directories in your mandatory profile (i.e C:\Users\Username\AppData\Local). 6) Change the NTUSER.MAN to NTUSER.DAT in the freshly generated .V2 Then just leave the users profile path on the AD DS profile tab to \\server.local\profiles$\students (or whatever you use). When you log on XP it will use the "students" folder. When you log on to Windows 7 , Windows will look for the "students.V2" If you change the profile path on the AD DS profile tab to \\server.local\profiles$\students.V2, windows will expect the profile to exist at \\server.local\profiles$\students.V2.V2. I suggest having a play about with this until you are confident on the whole process and see what gives. I like to break things in Virtual Box before going wild on the production environment, but maybe thats just me. Good Luck

Yep you can have mandatory profiles working for both XP and Windows 7, just edit the NTUSER.DAT in the .V2 folder just like in XP and change the extension to .MAN. Both profiles should continue to work fine alongside each other. Creating a Mandatory User Profile When a user logs on at a Windows XP machine their XP profile should be picked up, when a User logs on at an Win 7 machine their .V2 profile should be picked up. We were running XP and win7 together for a while because we had to gradually roll out in some areas. Keep in mind that the 2 profiles will be completely separate though. Also the Win7 profile is quite a lot larger in size than the windows XP profile. Keep this in mind if you have any unlocked profiles and perhaps have a quota per user on profile folders. You will run into roaming profile issues, with .CC and TEMPS showing up.

In case anyone else gets this error and they have tried both increasing the port range and tweaking the UDPportPolicy setting via the registry, I have found another possible cause and solution. In the past I have found that either "increasing the port range" or "tweaking the UDPportPolicy via the registry" sorts any problems that I have had with WDS and client computers displaying the PXE - tftp open timeout errors when attempting to download images. Naturally these were the first things I tried when I came to work today and found that other techs were reporting clients displaying the infamous open timeout error. Unlucky for me this didn't work. Solution 1)Looking in the "Application and Services Log> Deployment-Services-Diagnostics" -on the WDS Server, I could see that the client was booting and talking to the WDS server successfully. IP on the clients PXE boot screen tallied with the IP logged on the WDS server with this event below; Event ID: 4096 The Following Client PXE Booted: MAC: 00000000000000BLAHBLAH IP: 123.123.123.50 I could see however that the server wasn't logging any of the following normal events to signify that the client managed to get the boot wim. Event ID's: 4099 or 4100 The Following Client started the TFTP Download 2) Looking in "Windows Logs> Application" I discovered this lovely error message, indicating trouble with UDP port 69 when setting up the TFTP endpoint. Event ID: 772 An error occurred while trying to create the UDP endpoint for WDSTFTP provider on interface 123.123.456.26:69. This can happen if the network interface was disabled or changed, or some other application is already using the port. The provider will not be able to receive requests on this interface. Error Information: 0x2740 3)Next, I dumped the info about ports running using; netstat -abn >> NewFile.txt Searching the output for port 69 I discovered that javaw.exe was the culprit. UDP 123.123.456.26:69 *:* [javaw.exe] As it turns out there had been an update for java a few days before this, after a restart javaw.exe decided it wanted to use port 69, which WDS requires for TFTP. Javaw.exe managed to nab the port before WDS got a chance, thus our lovely open timeout error. 4) I killed the javaw.exe process 5) Restarted the WDS service & boom, back in action, no more TFTP open timeout errors. OK, I hope this helps someone else.