Workaround for using Passbolt CE for users on Terminal Servers

Checklist
[x ] I have read intro post: https://community.passbolt.com/t/about-the-installation-issues-category/12
[x ] I have read the tutorials, help and searched for similar issues
[x ] I provide relevant information about my server (component names and versions, etc.)
[x ] I provide a copy of my logs and healthcheck
[x ] I describe the steps I have taken to trouble shoot the problem
[x ] I describe the steps on how to reproduce the issue

Hello,

i have installed passbolt in our enviroment and we started to use it in our IT administration for some months where we work on full client systems. This works absolutely fine with no issues at all. Now we wanted to share our experience with the other people working here and rollout passbolt in the entire company. Unfortunately the users work on terminal servers which are divided in nine different systems with their own user disks mounted to their session. Since the management uses loadbalancing the user gets connected to a different terminal server every day and somehow passbolt starts the initial procedure to login every day eventhough the cache gets stored in the user disk (GPO enabled for own path for Google Chrome Userdata).

Is there any workaround for using passbolt on terminal servers directly? I guess it detects the user is working on other systems every day?

Thanks for your help!

Tell me, which information you need and i can share them to you.


Hi Patrick,

I hope you are still active on the forum.

Have you ever found a solution for the problem below?

We have the same setup with 3 RDP servers (RDP1, RDP2, RDP3), and our end users also have to enter their recovery key occasionally. We suspect that this happens after the end users end up on one of the other RDP servers.

We also use User Profile Disks, and there is no GPO active that cleans up Chrome or Edge.

Kind regards,

Michel

Hi Michel,

unfortunately i need to tell you that we couldnt fix the problem yet. I can have a look today if the problem could be resolved because we integrated Chrome Roaming Profiles and maybe this is more stable. If passbolt still recognizes a different device, then it might not work out.

We are using two GPO which manage the memory consumption of the Roaming Folder and clean up a bit if it goes above 1024MB.

I will give you an update if it works here.

Kind regards,

Patrick

Hi Patrick,

We also have one dedicated RDP server for a group of employees.

They are not experiencing any problems.

The Google Chrome & Microsoft Edge data from the user profile is properly included in the User Profile Disks (appdata\local & appdata\roaming).

We are curious whether your solution provides any new insights.

Kind regards,

Michel