Some RDM clients cannot use offline mode

Some RDM clients cannot use offline mode

avatar

We are experiencing a problem where some clients cannot work in offline mode. Others behave as expected when trying to reproduce the problem internally.

Client version: 13.5.6.0 (enterprise edition)
Server version: 5.0.2.0

Symptoms:

User can start in online mode just fine.
When user switches to offline mode, a login prompt is displayed, only allowing a password to be entered (no username). Expected behaviour is that the treeview remains available and user can continue working.
When starting offline, again the same prompt is shown, only allowing a password to be entered (no username).

As a work-around we have asked users whom are affected by these symptoms to check off the "always prompt for a username" in the datasource connections settings, and fill in their username there instead. This allows them to continue working in offline mode.

Settings have been checked between users who are and who are not experiencing this problem, but no differences where found. The users affected by this problem, also had this problem before we (recently) updated to 13.5.6.0. This problem has not been introduced to new users since upgrading to 13.5.6.0.

Could this be due to some residue of their old installation that needs to be manually cleaned after uninstalling / reinstalling / updating the client? (e.g. registry setting, or some locally cached files?). In order to rule that out, I would like to know how to completely eradicate any trace of RDM ever being on their workstations, and use a realy clean install.


Please advise on how to proceed.

All Comments (2)

avatar

Hello,

A few enhancements have been made in the latest release of RDM regarding the offline mode.

Could you try this latest release, which is 13.5.9.0? You can download it here
https://remotedesktopmanager.com/home/download#Beta

Best regards,

Jeff Dagenais

avatar

Thanks for the information. User feedback from the first tests is that this problem has been resolved in this version.

EDIT: one user (who applied the workaround) now reports that if the workaround (which he previously applied) is disabled, version 15.3.11.0 (which is / was currently available as beta download, not 13.5.9.0) is still giving the same behaviour. The first user reporting back test results from the beta version did not apply the work around and there the issue seems resolved by installing beta version 15.3.11.0.