ContentProtect

avoid employee time and resource waste

Multi platform

Content is protected

Website

Product can be marketed better

Documentation needs work

Filtering

Internet Management

Regulatory Compliance

high returns on search

Better user experience

Helps reaching the correct content

The client is relatively light weight and doesn't impact other applications.

The client isn't easily bypassed, so the user's are kept under restrictions.

The configuration is relatively simple and easy to deploy.

Our primary policy is a restricted list, so that does as advertised. We had one location that had blocks based on categories (adult, illegal, etc). We continually had issues with sites getting completely blocked due to unrelated content. For example, Yahoo had a beer ad on the page, alcohol was blocked, so Yahoo became blocked for the period of time that ad was displayed. We had this happen multiple times and eventually switched to a different solution at that location.

I've had issues with their cloud portal not working. I don't have to edit our configuration often, but on numerous occasions, i was unable to get the configuration page to load after login, sometimes for days. The platform just wasn't stable when I needed it to be.

We run many of our remote rooms as frozen (after logoff they reset to the image). This works fine most times, but when content protect needs a configuration change pushed down, someone needs to go 'thaw' the computers, download the updated configuration, and re-'freeze' the computer. It would be nice if that information was just dynamic from the cloud and didn't need to be pulled down.

The categorization used for policies is very limited and not flexible or easily customizable.

I could never get the usage reporting to work.

It was a relatively inexpensive and simple solution when we needed one relatively quickly, which is a positive. The inexpensive price has kept it in the environment.

The lack of reliable reporting has lead to the need for an alternate monitoring solution in a few cases. Network level reporting was used, which is a separate expense, configuration.

Time has been lost waiting on the portal and then troubleshooting support tickets when sites that shouldn't have been blocked have been blocked. It has resulted in changes for locations that needed dynamic category filtering as opposed to a finite list.

The blocking of sites based on add traffic or sub-sites (rather than just blocking that content like other solutions) has resulted in downtime during classes when those sites were listed in the lesson plan and had previously worked.