Serge Deiss

Are there any workarounds to be had until we have an update to install, this is killing my servers ;/ Rollback to Version prior to 2026.2.x ? We run currently 80 Users over multible servers but only some users are killing the cpu and the more connections the more ressources they need aswell.

rdm 2026.2.11.0 64-bit / dvls 2026.2.9.0 on windows server 2022 -2025 RDS. All the same issues.

You can clearly see when we shipped the Update. And that is on all servers.

But not in SQL datasource?

We do have DVLS and MS SQL as Database Server.

But as we will Update coming week it might make sense to just Update first and then use the Official Migration tool if available for this Purpose.

Hi Richard,

Thank you for your Message, do you mean once we Updated to the newest Version we would be able to use the Migrate Accounts Tool for this Purpose ? Because we will Update next Tuesday to the new Version and if it would make more sense we could also just cleanup after the Upgrade and use this Path.

Best Regards

Damian

Hi Richard,

I'm in the same predicament, i would like to cleanup our Users without having to delete them first.

We have currently a mix of sAMAccountName / userPrincipalName im Updating to a version where we can finally use Powershell to Script. But do you have an SQL Script that will not Purge all Private Vaults and Settings from the Users?

Datasource: DVLS Version 2020.3.22.0 / Database Version: 669

Best Regards

Damian