https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Host_page/Reinstall_and_upgrade_an_access_agent

Server updates can be manual or automatic (in the case of cloud instances), but updating your agents must be done via the Host page or via their original deployment method (for example, GPO).

Simon,

Yes, we will be able to do Tokyo at the same time as Australia moving forward. Thanks for the suggestion!

As far as I know, Google Authenticator does not support push notifications, but their phones do.

https://www.howtogeek.com/260369/how-to-set-up-google%E2%80%99s-new-code-less-two-factor-authentication/

If this changes, we will consider adding push.

Jay, It was great working with you yesterday. We will be looking at expanding support for Duo to include hardware tokens, but we do not have a timeframe on when we may make that available.

Also, I want to make it clear that this issue was not a Control vulnerability, but instead, the Duo App on the affected users phone was out of date. Once the Duo App was updated, the issue was resolved.

Thanks!

Sean White

Thank you for your request, our SSO team is currently investigating this issue.

In our 19.3 release, we have added the ability to select a session and hold shift+double click to open the 'Specify Join Options' dialog. Additionally, we added an app.config option  'IsBackstageDefault' which when configured will go to backstage by default.

More here:

https://docs.connectwise.com/ConnectWise_Control_Documentation/Release_notes/ConnectWise_Control_2019.3_Release_notes