Installing JCS in an RDS environment
Note that in JCS version 35.002.17 tsinstall.vbs (a VBScript file) was replaced by rdsinstall.ps1 (a PowerShell file). This is to prepare for the End of Life of VBScript.
The way our RDS (Remote Desktop Services) support works is that the JCS installer puts the frontend MSAccess database JCS16.accde and associated files in the install path (normally C:\JCS). This should be on a local disk connected to the RDS server.
At the end of the installation the installer runs a script called rdsinstall.ps1 that is put into the install path. This script copies the frontend, along with some supporting files, into every user's %LOCALAPPDATA% folder. This is because two users should not run the same frontend at the same time, as it may cause errors/undefined behaviour.
Adding users after running the installer
If a new Windows User is created (or logs into the RDS server for the first time) after the installer has been run, they will not have the frontend files in %LOCALAPPDATA% . This can be resolved by running rdsinstall.ps1 manually.
Run Get-Help C:\JCS\rdsinstall.ps1 with PowerShell, or open rdsinstall.ps1 with a text editor for more information.
FSLogix
If you are using FSLogix users will not have a %LOCALAPPDATA% folder present when the installer runs. (This gets created when a user logs into the RDS server, and removed when they log off). In this case you can run the rdsinstall.ps1 script on each user login, with a command like:
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -File C:\JCS\rdsinstall.ps1 -LogPath "%localappdata%\JCS\rdsinstall_log.txt" -Silent -CurrentUserOnly
Run Get-Help C:\JCS\rdsinstall.ps1 with PowerShell, or open rdsinstall.ps1 with a text editor for more information.