Old version not finding new version

Hello,

There's an option in File -­­> Options -> Application Start to check for updates.

For more information, please refer to this help article;
https://help.remotedesktopmanager.com/file_options_general_applicationstart.htm

If the option doesn't work either, it might be possible that the old version doesn't detect new releases correctly.

In that case, please download the installer manually;
https://remotedesktopmanager.com/Home/Download

Best regards,

Yes, I already have it set to check for updates and I manually went to the menu and clicked Check for Updates. It simply comes back and says that it is already up to date.

Can you verify if something changed on the back end that is preventing this older version from updating itself? I'd rather not have to go track down anyone with an older version manually and have them update...

Hello,

If you select "All updates including beta" do you get a prompt?

Is it possible that you have a firewall rule or proxy that might prevent the application from checking for updates?

Our links are using HTTPS now.

Best regards,

I have it set to include Beta. We haven't changed anything on our side. I am able to update an install that was on 11.5.x just fine. The people who have an old version (11.0.1.0) installed do not get any sort of prompt at all.

We have changed our url for https. Could it be possible that your firewall block the check for update?

Regards

I am able to check for updates from some machines that are running a more current version of RDM. I only cannot check for updates from machines running the old 11.0.1.0 version.

Is that old version not able to check via HTTPS? Our network works fine as I have other machines finding updates without any problems. Is there a log file that will show anything I can look at?

We have verified and https should not be a problem. Could you verify if it's related to the version or a policy? By example you can try to manually upgrade it to a newer version but not the latest and see if it works.

Regards

I created a new custom installer thing and used that instead. That installed fine and then upgraded to 12.x with no problems. Only had the problem with that 11.0.1.0 version but I think I got everyone updated by hand so we're good.

Could test it by installing the 11.0.1.0 version and then trying to check for updates. That will tell you if it's just me or not. :)

Good point :) I will ask the QA to test it tomorrow

Hello,

I think that I have been able to reproduce your issue. It seems to come from the way that the custom installer has been created. Here is the explanation:

When the application prompts for the update, you have the choice to "Skip the version". If this option has been chosen in the version from which the custom installer come from, it has been saved in the installer configuration.

When you install the customized version, there is a conflict between the two configurations (the one from the custom installer and the local one). Since the update check is done before this conflict happens, it will be prompted if the local configuration allowed it before installing the customized version.

When your colleague's machine has been re-imaged, the local configuration has been lost and the custom one took its place without any conflict when installed.

I would suggest to update the custom installer you are using. Then the update check should be displayed with installer configuration.

Best regards,