This article communicates new features and bug fixes in this release of School Zone.

Importantly, with this release School Zone provides key integration with the broader Family Zone platform. In particular this release fixes some small bugs and builds on the initial phase of integration to the Mobile Zone solution providing a visual representation of the student population’s level of engagement in Family Zone Cyber Safety as well as statistics and reporting on the installation of Apps across student devices (whether used at school, at home or when mobile) including highlighting risky apps.


This is a General Availability (GA) release incorporating bug fixes to Sonar 5.0.2 and new features to MyNet 1.0.1.


This product has been tested on the following Base Operating Systems:

  • CentOS 6.8


  • A server compatible with the listed base Operating Systems

  • At least 24 GB RAM available to the host Operating System (32 GB RAM is recommended)

  • 300 (min) GB HDD space is required.


As always, we recommend performing a backup_os and a backup_logs prior to upgrading your system. The specific component versions are as follows: 

Sonar v5.0.2

  • sonar-5.0.2-13570

  • sonar-tools-1.0.1-16

  • sonar-info-daemon-2.0.0-49_gb816c

Requirements: A current version of Sonar 3.5.3 GA ( or newer) must be installed. 

NOTE: If upgrading from Sonar 3.5.3, we recommend following the process outlined in our MyNet Preparation guide to ensure a seamless transition to the new MyNet platform.

MyNet v1.0.1

  • mynet-1.0.1-2.g3839d

  • mynet-api-1.0.1-2.ge1edd

  • mynet-core-1.0.1-6.g0779d

  • mynet-sonar-1.0.1-2.gcda83

  • mynet-ui-1.0.1-3.g4a5c5


The following new features appear in this release:

ClamAV Improvements
Added the ability to scan files as streams as well as improved connection and socket efficiency.
ClamAV Allow Content Types
Added the ability to configure which types of content ClamAV Scans
Increased MyNet/Sonar Logging
Increased logging granularity for MyNet and Sonar services.


The following bug fixes appear in this release:

Bug Fix
Bug with ‘username’ MyNet login parameter enabled
Fixed issue when users configured to login with their username (rather than email address), would fail to authenticate.
Remove Keep-Alive Categorisation Requests
Removed multiple categorisation requests for keep-alive connections.
Username Not Displaying Correctly
This fixed the issue where users logged into MyNet would not see their account names rendering correctly.
Bypass Ticket Field Not Appearing
This resolves a bug where the bypass ticket field would not appear on a block page, even if it was set to do so.
Group Firewall Rules not Applying
This resolves a bug where firewall rules on a group did not apply as expected.
Services Unavailable Via Apache over SSL
All Sonar servlets and static HTML are now available via Apache for access over HTTPS.
Cache Module Checkbox Does Nothing
The checkbox has been removed.
Not Syncing All Email Aliases
This resolved an issue where Sonar would only sync the first email alias (alphabetically) for an AD user. It now syncs all SMTP aliases.
Sonar Services MyNet Protocol Dependency
This resolved an issue where MyNet wasn’t logging correctly to the reporting database because of protocol mismatches.
Site Filtering Not Effective In Conjunction With SSL Inspection Exceptions
This bug caused domains blocked by Site Filtering to be allowed if they were in SSL Inspection Exceptions, rather than just not being decrypted.
Block Uncategorised Not Effective when SSL Inspection is Disabled
This bug caused the ‘Block Uncategorised’ option to be ineffective unless SSL Inspection was enabled.
Category-Based QoS Browsing
This fixed the Issue where, in certain conditions, unauthenticated users would be able to browse the internet when specific QoS rules were applied.
Sonar Not Logging Reporting Data
This fixed the issue where MyNet logging intermittently stopped working.
Block Page Not Showing Data
This fixed the issue where block pages were failing to  show the block reason.


  • Apache logs not rolling properly: There is a known issue, whereby Apache’s logs (https-access.log and https-error.log) are rolling accordingly and are gaining in size, albeit slowly.