For a week or so, we are unable to connect to SQL Data Source hosted in azure, Desktop clients connects fine. Mobile Client shows "Database upgrade is required". I clicked the update button - shows successful and listed as DB version 1.414 TCP Secured in desktop client.
Is this a bug or something?
Thank you
Hello,
The latest version of RDM iOS works with the latest version of RDM, which is 13.9.4.0. This means that you would need to upgrade your RDM Windows first, perform the database and then, RDM iOS will work.
Firstly, please consult this help article to perform the database upgrade properly.
https://help.remotedesktopmanager.com/database_upgrade.htm
Secondly, RDM 13.9.4.0 can be downloaded here
https://remotedesktopmanager.com/home/download#Beta
In conclusion, RDM iOS will then get access to the database again.
Best regards,
Jeff Dagenais
So you pushed stable client for mobile with the requirement to use beta software? Is that correct?
Hello,
This is correct. If you don't upgrade RDM Windows, it would not be possible for you to authenticate on the database using RDM iOS.
Best regards,
Jeff Dagenais
No thank you, I won´t be using unstable build in a production environment, "thumbs up" for one that agreed on this approach.
So I would have to agree with everyone else, who made the bonehead decision to require a beta release of the desktop product to be required to use the mobile version.
Hi Jeff,
Is this something that development is taking into consideration in the future?
Its very easy for an enterprise to control the update pace of a Windows application (and the database), but it's nearly impossible to control the update pace of mobile applications. If we push RDM iOS via MDM, it will automatically be updated to the latest version. Many users also have automatic updates enabled on their devices.... so as soon as you release a new update for iOS, you're essentially crippling everyone who hasn't had the opportunity to test and verify the latest desktop app and database versions.
Ideally the iOS apps (and the desktop versions too) should have backwards compatibility built in for at least one or two versions to allow smooth upgrades within enterprise environments. Step 1: clients get upgraded to the latest stable version but still connect to pre-existing back-end. Step 2: sys admin updates back-end database during scheduled down-time.
Hello,
Thank you for your feedback.
I have transferred your message to our engineering department.
Best regards,
Jeff Dagenais