BromleyTech

Webscreen works well for the schools I'm involved with. For the majority of schools we've just set up 2/3 policy groups - IP policy for students & then user list policies for staff to allow authenticated access to YouTube etc. I think the trick is to keep it simple & not try and over complicate, unless really needed. There may be some limitations with Webscreen but the other products we've looked at in the past also had shortcomings and there was little point in paying for another product when the one bundled with LGfL does the job well

Personally I haven't heard of any schools jumping ship from LGfL 2.0 & most of the schools I'm involved in have already renewed in advance. The turn around time on port changes seems much better than we used to have it with Capita. When I put in a request, as long as it's clear from the request what I'm trying to receive & it's 'sane' (under LGfL policy) I haven't had any issues. If you're having difficulties it may be worth linking the support guys to the documentation that details the port requirements or provide a capture. Or if you want more control, & an increase in workload , look into the option 2 route.

Hi Scottauto I've had some limited experience with LGfL WiFi at a similar sized school. I remember seeing that they sell Unifi as well, as a budget alternative to the Cisco kit - so could be worth giving them a call to see what they can offer you.

RAv3 is usually the simplest way, with category 2 via TeamViewer etc for 3rd parties. Below is the document previously mentioned. http://files.lgfl.net/LGfL/Policies/LGfL%20Security%20Guidance.pdf

I would recommend blocking facebook.com & https://173.252.64.0-173.252.127.255 through WebScreen. If Chrome presents an IP address to the filtering system, Facebook may be accessible. Particularly if the categories social networking & host is an IP are allowed for the relevant policy.

With LGfL the default filtering policies do enforce safe search. Google safe search can be far from perfect though...

The following works at the school I support. From the user guide: "It is possible to stop Google image searches but the only way to do this is through the use of 'Regular Expressions'. The regular expressions created for this purpose must be added to the Local Block list of each policy where Google image searches should be blocked. The quick method of doing this is by going to the Local URLs and Keywords page and clicking the New URL or Keyword button. Then add the regular expressions listed below, one at a time, and specify which filtering policies they should be included in. Please copy and paste the following regular expressions into your filtering policies (they must appear exactly as shown with brackets, etc): (www\.google\..+/.+\&site=imghp) (www\.google\..+/images/) (www\.google\..+/imghp) (images\.google\..+/) (tbm=isch) (tbs=img:1) (tbs=isch) https://support.atomwide.com/secure/guide/WebGuide/Help.html?ws2_faq.html For this to work though I would expect that the LGfL DNS would need to be used. I assume with Yahoo, I haven't tested it, that you can simply keyword block images.search.yahoo.com Hope this helps?

I found my School's transition to LGfL 2.0 went relatively smoothly and I imagine a number of other schools have had issues with the service due to a lack of forward planning. Remote access is abit of a pain though.

Sorry Searle, going to have to agree with everyone else. I feel generic accounts for this purpose are a bad idea and the traceability is critical.