Roadmap
Changelog
Windows Roaming Client v1.6
new
Windows Roaming Client
Action Required: Update Windows Roaming Client
What is changing?
As part of good security practice, DNSFilter rotates our “certificate of authenticity” for our Windows applications every three years. This certificate gives you validation that no tampering has taken place in the code, and you can safely install them on your systems.
Because the old certificate expires on March 15th, 2021 at 2pm EDT, it is important that you are running the newest version of these tools to maintain continuity.
It is imperative that you utilize the latest version of the Roaming Client so that Windows continues to recognize them as trusted applications.
What do I need to do?
The Windows Roaming Client is set to update automatically by default.
If auto-update is enabled for your account, you do not need to take any action
. You can click here to verify your auto-update setting (Or navigate in the dashboard to Deployments > Roaming Clients > Settings).
However,
if you have disabled auto-update
, you must either turn auto-update ON by March 11th for your organization(s), or download Windows Roaming Client v1.6 and install it.
Thank you for keeping your organization secure, and partnering with us to make the internet a safer place for your users.
Windows Roaming Client 1.5.3
improved
Windows Roaming Client
  • resolves issues with restoring original DNS settings after certain VPNs or other applications modify them
Windows Roaming Client Auto-Upgrade from 1.4.3 -> 1.5.2
new
Windows Roaming Client
  • 1.5.0: Released Web AppUI LocalDomains
  • 1.5.1: VPN Handling improvements, support for IgnoreVPNInterfaces Registry settings
  • 1.5.2: Improved ordering of AppUI LocalDomains above DHCP DNS Search Suffix
Windows Roaming Client 1.4.3
new
Windows Roaming Client
We have released a new version of the Windows roaming client. This version resolves an issue causing network bandwidth spikes in customers with large Active Directory installations. No action is needed for this update. Your clients will perform a rolling auto-update in the next 24-48 hours.
Windows Roaming Client v1.4.2
improved
Windows Roaming Client
  • Improved information gathering of current logged in user using WMI
Windows Roaming Client v1.4.1
improved
Windows Roaming Client
  • Improved information gathering of current logged in user
  • Improved debug messages
Windows Roaming Client v1.4.0
improved
Windows Roaming Client
  • Improved support for multiple interfaces working at the same time
  • Improved local domains per interface settings
Windows Roaming Client v1.3.8
new
improved
Windows Roaming Client
  • Improved reachability test code to prevent race conditions
  • Implemented requests failure count that forces a network change check
  • Reduced DNS query timeout from 10000ms to 1980ms AND that value is divided by the number of configured servers
  • Changed failure count logic, now it does a reachability test followed by a network change check if needed (after 30 failed requests, it triggers a check)
  • Updated installer to NOT override modified files on update (e.g.: config file)
Windows Roaming Client v1.3.7
new
Windows Roaming Client
  • Network change events now triggers a quicker process to update system configuration
  • Fewer registry reads to build interface configuration info, now they are on a single place
  • Added some guards that could be causing unhandled exceptions
  • Added a "catch all unhandled expections" callback to at least write in log file what happened
  • Better handling of local domains PER interface
  • Windows service recovery options forced to restart service in case of crashes
Windows Roaming Client v1.3.5
fixed
Windows Roaming Client
  • Client automatic reactivation fix
  • 1.3.6 (debug version, not published)
  • Added version number to MSI file in the "comments" field
  • Client custom release channel support
  • Implemented restoration retries on system boot to retry multiple times in case of failure (mostly due to OS still getting things up and ready, like network interfaces)
  • ARPSYSTEMCOMPONENT flag are now preserved on auto-updates
  • Flush DNS cache on client start
Load More