Lost my User Vault

Ok, this is getting stranger and stranger. Now I have my User Vault back but my main vault is 'Not connected' but does show 1634 entries?

This will need more attention than a simple Forum post. Can you please open a support ticket by sending your request to ticket@devolutions.net.

Add "Attn: Stefane" to the ticket and I will pick it up from there.

Best regards,

I created a problem report from within the app but haven't heard anything yet. Problem seems to have solved itself so you can close that.

Very strange and very scary for my Vault to get 'lost' somehow but good it's back.

Odd, we received the support ticket and I replied that would like to have a remote session to look over the issue with you. (maybe check your spam folder)

As the issue now looks to have resolved itself, unless you need more assistance, I will be closing the support ticket (DEVO-31562).

Best regards,

Ah, yes, found it. My apologies.

We've had two more instances of the same issue and the common occurence is that in both cases the client version was very old (as well), requiring multiple upgrades or an uninstall/reinstall. After the upgrades we needed to clean the caches before it worked. The uninstall/reinstall path works best as it is fastest to do and cleans up caches, etc, as well.

Hope this helps others!

No worries and thank you for the update.

Still odd that you would need to do all that. It should be as simple as upgrade and that's it, regardless of what version you were on prior to the upgrade.

We will keep this in mind and see if we can't figure out what is truly happening in this case.

Best regards,

I think from a user perspective just triggering a message that a client upgrade is necessary (after this database upgrade) would be great?

Now we panic 'everything is gone', especially because you don't see an error message but just an (almost) empty vault.

We already have the "Version Management" but it has to be modified manually.

https://help.remotedesktopmanager.com/datasourcesettings_versionmanagement.html

However, after an upgrade, it would be helpful to prompt the user if they want to go change the minimum versions.

Something along the lines:

Do you want to configure version management for this version?

• Automatic - RDM simply set the appropriate value
• Yes - open the settings page
• No - do nothing

What do you think?

Yes, we used that setting now, but it's hard for us to predict when it's necessary and we don't want to force users to upgrade every time either. It took me a while to figure out that that was indeed the issue too, as at first it didn't appear to help...

An 'Automatic' switch as you suggest would be great.

Perfect, I will add to our to-do list.

In the meantime, you should try to synchronize them on every major and/or minor change in the version number (format: major.minor[.build[.revision]]). This is where we limit our database upgrades also to make it easier on you.

Best regards,