The Netsweeper Client Filter 11.20 EA is now available. This release adds the initial version of nUpdate which allows our Windows Client Filter to be kept up to date from the WebAdmin Client FIlter Settings using the Netsweeper 8.2.1 or above server. The 11.20 also fixes shutdown and upgrade problems with our nsdivert.sys driver which has been enabled by default in the 11.x release. The Netsweeper Client Filter 11 will be expanding our stable and proven Client Filter technology and introducing some new features and improvements. Customers should upgrade to the 10 GA release, and for those waiting for the improvements listed in the release notes for 11.20 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
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 11.20.54.54
- Mobile Config-Configedit_mobileconfig 11.20.54.54
- Netsweeper Client Filter - 11.20.54.54 mac64-tp_crt.pem
- Netsweeper Client Filter - 11.20.54.54 mac64-tp_app_proxy.mobileconfig
- Client Filter - 11.20.54.54 mac64-nmonitor_config.mobileconfig
- Netsweeper Client Filter - 11.20.54.54 mac64-configedit.mobileconfig
iOS
- Client_Filter_iOS_mdm-tunnel-11.20.1.unsigned.mobileconfig
- Client_Filter_iOS_mdm-tunnel-vendor-11.20.1.plist
- Client_Filter_iOS_mdm-tunnel-root-ca-11.20.1.pem
Android
- Netsweeper-android-11.20.54.54-work.apk
- Netsweeper-android-11.20.54.54-settings.txt
- Netsweeper_android-11.10.54.54-ca-root.pem
Chrome Web Store
Client Filter 11.20
Issue Type |
Ticket |
Summary |
|---|---|---|
|
Bug |
CF-187 |
The new nsdiver.sys for high speed Windows filter could cause blue screen during shutdown, uninstall or service restart. This new nsdivert.sys is now enabled by default so all Windows platforms can experience line rate high speed filtering performance. |
|
Improvement |
CF-188 |
Client Filter Windows nUpdate Service has been added to 11.20 and works with Netsweeper Server 8.2.1 and above. This allows for the Windows platform to be upgraded to a new version of the Client Filter from the WebAdmin. |
|
Improvement |
CF-189 |
Client Filter did not get notified when there were metadata changes for the nMonitor and nUpdate. |
|
Improvement |
CF-196 |
Monitor downloads would ignore errors on big downloads that timeout causing files not to be updated. |
|
Improvement |
CF-200 |
The nsPDE engine, in the Client Filter, is now enabled by default. A checkbox to disable it has been added to Client Filter Settings. |
|
Bug |
CF-202 |
The Client Filter and Workstation Agent, when put into debug mode, could cause uninstall issues due to in use log files. |
|
Bug |
CF-208 |
The Windows Uninstall prompts for password even when the password field is empty. |
|
Improvement |
CF-210 |
When using Windows with the region set to another language, the Client Filter Settings menu popup gave an 'Invalid Catalog' error message. |
|
Bug |
CF-214 |
Changing the Client Filter nMonitor from server A to server B, with a different serial, would not properly reload the nmonitor data. |
|
Bug |
CF-215 |
There were problems in Windows when moving/loading/saving config files. |
|
Improvement |
CF-218 |
The Chrome Client Filter did not have a workstation name when not enrolled with an asset ID, generate a GUID/WUID for the workstation when no asset ID was available. |
|
Improvement |
CF-219 |
The domain user group timer did not have a ConfigEdit argument to adjust in all places. |
|
Improvement |
CF-220 |
The current cookie in nMonitor is now always loaded when a nMonitor event is triggered. This makes sure we send the proper logged in user when the event was triggered and now a prior cached cookie |
|
Bug |
CF-222 |
The Request Logs/dst ip showed all NSProxy destination IP addresses as 127.0.0.1. |
|
Bug |
CF-223 |
The Chrome extension would only load a single config push from the Client Filter Settings before ignoring all other config updates. |
|
Improvement |
CF-226 |
The Chrome Client Filter extension used 1.4Gbyte with nMonitor and 864Mbytes for nFilter. We have reduced memory usage to 300Mbyte after lo |