The Netsweeper Client Filter 10.50 GA is now available for all customers. This release builds on the stability and proven features of the Netsweeper Client Filter and provides customers with some major improvements for all operating systems. Customers running a 10.x EA release should strongly consider upgrading to the 10.50 GA release while customers running the 9 GA can now consider their migration plan to the Client Filter 10.
Netsweeper will be moving to the Chrome Client Filter v3 manifest over the next few Sprint cycles. Google has extended the V2 Manifest for enterprise policies until January 2024 due to a lot of the changes and problems many developers have been running into. We are committed to making sure the new V3 manifest is available before customers can no longer use the V2 manifest version. More information from Google can be found here.
If you have any questions or concerns about planning an upgrade to this release, please contact Netsweeper Technical Support (support@netsweeper.com).
Downloads
Windows
Mac
- MacOS Client Filter 10.50.53
- Mobile Config-Configedit_mobileconfig 10.50.53.53
- Netsweeper Client Filter - 10.50.53.53 mac64-tp_crt.pem
- Netsweeper Client Filter - 10.50.53.53 mac64-tp_app_proxy.mobileconfig
- Client Filter - 10.50.53.53 mac64-nmonitor_config.mobileconfig
- Netsweeper Client Filter - 10.50.53.53 mac64-configedit.mobileconfig
iOS
- Client_Filter_iOS_mdm-tunnel-10.50.1.unsigned.mobileconfig
- Client_Filter_iOS_mdm-tunnel-vendor-10.50.1.plist
- Client_Filter_iOS_mdm-tunnel-root-ca-10.50.1.pem
Android
- Netsweeper-android-10.50.53.53-work.apk
- Netsweeper-android-10.50.53.53-settings.txt
- Netsweeper_android-10.50.53.53-ca-root.pem
Chrome Web Store
Client Filter 10.50
Issue Type |
Ticket |
Summary |
|---|---|---|
|
Improvement |
CF-68 |
When upgrading the Windows MSI, we will not run the generic ConfigEdit configuration. A new Property has been added for CONFIGEDIT_UPGRADE and NMONITOR_CONFIG_UPGRADE which can be set to be run during an upgrade of the Windows Client. |
|
Improvement |
CF-70 |
The Windows Client Filter performance has been improved. This experimental feature can to be enabled with the flags -f 1048576 for ring buffer support, and -f 2097152 for improved proxy performance. |
|
Improvement |
CF-117 |
A filter-version-brand.xml has been released for any build made for the Chrome Client Filter. This allows administrators to pin the version they wish to rollout and manually control when updates occur. |
|
Improvement |
CF-122 |
The Client Filter Browser for iOS has been upgraded to the latest Firefox and security builds in the 10 release. |
|
Bug |
CF-134 |
Windows/Mac Client Filter/Android/iOS 10.10 to 10.30 did not work when configured to talk to the policy service over HTTPS or SSL as it did not validate the remote server certificate. |
|
Bug |
CF-141 |
The Client Filter when used with http://policy.server.example.com or https://example.com did not handle all protocol error cases. |
|
Bug |
CF-146 |
The nMonitor keyword parsing engine could over-detect complex phrases and words with OR in a word. The OR was treated like a Boolean operator and not part of the word in some cases. |
|
Improvement |
CF-148 |
Android nFilter Client libraries have been updated to the latest release. |
|
Improvement |
CF-151 |
When upgrading the MacOS PKG, we will not run the generic ConfigEdit configuration. A new launchctl environment variable has been added for CONFIGEDIT_UPGRADE and NMONITOR_CONFIG_UPGRADE which can be set to be run during an upgrade of the MacOS Client. |
|
Bug |
CF-157 |
Android added a Route/IP for IPv6 even if there was no IPv6 connectivity. |
|
Bug |
CF-160 |
The MacOS Client Filter, can lookup the wrong username and use the 'root' user in builds 10.10 to 10.30. The 10.40 and above now lookup the username of the running process instead of relying on getlogin() or the environment. |