DNSFilter roaming client agent checks for updates every day 12:00 GMT
in progress ( live <90 days )
Greg Gelman
We are wondering why the auto update feature is moving so slow across our fleet of roaming clients and noticed that the roaming client auto update feature has this text about checking for updates every day at 12:00 GMT. Updates from 1.6.2 to 1.8.2 has taken months and we are not fully updated yet across our fleet.
Is this true to understand that updates are only checked at the same hour every day? What if our org is across 6 or more timezones internationally and some of our roaming clients are offline at that hour, will those roaming clients never check for updates? Does a roaming client check for updates as soon as it wakes up with activity?
The feature request I am considering here is a button for us to be able to force updates on selected devices, or all devices if the case of checking for auto updates are only at 12:00 GMT every day.
R
Ryan Poppa
in progress ( live <90 days )
Will be updated when the copy in the product is complete. However, the documentation is accurate.
R
Ryan Poppa
Thanks for sharing this. This copy is incorrect. We've updated our documentation https://help.dnsfilter.com/hc/en-us/articles/1500008108422-Manage-Roaming-Client-settings#roaming-client-settings which has more accurate information on the update cadence. The in-product text will follow soon. However, if you are having issues with clients not upgrading, please reach out to our support team. We're happy to take a look.
chad Pence
I have noticed that also that there are devices that are older than others and they are up and online.