You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem:
On a Remote Desktop Server deployment (tested on Windows Server 2019/2022), no more than 1 non-Administrator and 1 Administrator user can have Tabby opened. When other users attempt to open the application, 2 processes will spawn and then terminate, until another user has closed Tabby.
To Reproduce:
On a Windows Server 2019/2022 non-VDI deployment
Install TabbySSH
Under 2 non-Administrator users, attempt to open TabbySSH
The second user will fail here
Observe Task Manager
Run TabbySSH as Administrator
A second instance will open in this case
As a separate Administrator user, run TabbySSH as Administrator
The second Administrator user will fail here
Observe Task Manager
We have tested this outcome with the portable installation of Tabby (in both %PROGRAMFILES% and %LOCALAPPDATA%), as well as user-based and machine-wide installations of Tabby. We've also tested creating several copies of the Tabby portable files and editing the NTFS permissions to explicitly block other users from viewing the contents, to no avail.
Are there some arguments we can pass to Tabby, to allow multiple instances on the same machine?
The text was updated successfully, but these errors were encountered:
Describe the problem:
On a Remote Desktop Server deployment (tested on Windows Server 2019/2022), no more than 1 non-Administrator and 1 Administrator user can have Tabby opened. When other users attempt to open the application, 2 processes will spawn and then terminate, until another user has closed Tabby.
To Reproduce:
We have tested this outcome with the portable installation of Tabby (in both %PROGRAMFILES% and %LOCALAPPDATA%), as well as user-based and machine-wide installations of Tabby. We've also tested creating several copies of the Tabby portable files and editing the NTFS permissions to explicitly block other users from viewing the contents, to no avail.
Are there some arguments we can pass to Tabby, to allow multiple instances on the same machine?
The text was updated successfully, but these errors were encountered: