The Netsweeper Client Filter 11.30 EA is now available. This release improves verification of HTTPS site certificates on Windows, MacOS, and iOS, with more improvements coming in future releases. The 11.30 release has focused on memory usage when nMonitor is enabled trying to lower memory consumption. Customers should upgrade to the 10 GA release. For those waiting for the improvements listed in the release notes for 11.30 EA, they can consider testing these improvements and rolling them out to their production networks.
We anticipate rolling out many advancements and improvement to the Client Filter 11 over the next few months.
- Windows Update Service allowing customers running Windows to keep the Client Filter up-to-date from the WebAdmin interface
- Improvement to memory usage on all platforms
- Automated Client Filter device registration with the WebAdmin interface allowing for improved functionality
- Improved internationalization support allows customers to easily install Windows in different languages
Return to the Client Filter 11x Release Notes page.
Downloads
Windows
Mac
- MacOS Client Filter 11.30.54.54
- Mobile Config-Configedit_mobileconfig 11.30.54.54
- Netsweeper Client Filter - 11.30.54.54 mac64-tp_crt.pem
- Netsweeper Client Filter - 11.30.54.54 mac64-tp_app_proxy.mobileconfig
- Client Filter - 11.30.54.54 mac64-nmonitor_config.mobileconfig
- Netsweeper Client Filter - 11.30.54.54 mac64-configedit.mobileconfig
Android
- Netsweeper-android-11.30.54.54-work.apk
- Netsweeper-android-11.30.54.54-settings.txt
- Netsweeper_android-11.30.54.54-ca-root.pem
Chrome Web Store
Client Filter 11.30
|
Issue Type |
Ticket |
Summary |
|---|---|---|
|
Improvement |
CF-105 |
The Chrome zlib library has been upgraded from version 1.2.12 to version 1.2.13. |
|
Improvement |
CF-128 |
Added keyboard input monitoring support to nMonitor for the Chrome Client Filter. |
|
Bug |
CF-142 |
Chrome startup tabs and new tabs were inadvertently being sent to the Policy Server. |
|
Bug |
CF-163 |
All Clients could crash if the policy server field was empty. |
|
Improvement |
CF-164 |
Improved how NSProxy verifies root certificates on all platforms. |
|
Bug |
CF-173 |
Systray Dock icon stayed visible after closing the 11.30 Client Filter Settings on MacOS. |
|
Bug |
CF-181 |
ConfigEdit Export would include the default value for Windows Filtering Priority unnecessarily. |
|
Improvement |
CF-225 |
We now store the nMonitor configuration in the Chrome Enterprise Storage. This improves nMonitor configurating loading, data processing, and will allow for easier debugging. |
|
Improvement |
CF-226 |
We have reduced the memory usage for Chrome Client Filter extension, improving overall performance. |
|
Improvement |
CF-228 |
Made improvements to how nMonitor data is handled during reload events by the Chrome Client Filter, ensuring more efficient data processing. |
|
Bug |
CF-230 |
Fixed a layout issue with the nMonitor configuration window. |
|
Bug |
CF-232 |
nMonitor 'getconfig' settings were being ignored when downloading via Chrome. |
|
Bug |
CF-235 |
Changing the Policy Server through the Chrome Client’s browser icon would not trigger a getconfig event. |
|
Bug |
CF-238 |
Resolved an issue where certain conditions, such as losing connection to a Policy Server, could cause nMonitor to temporarily stop scanning keywords. |
|
Bug |
CF-239 |
Resolved an issue with HTTP_GET and HTTP_POST on MacOS. |
|
Bug |
CF-242 |
Initial nUpdate service is now included. It is only available by setting the MSI property NUPDATE_ENABLED when installing. |
|
Bug |
CF-244 |
nUpdate service must pause logging before upgrade is complete to allow the upgrade process to complete successfully. |