How to configure it in an RDS/RDP/terminal services environment (with some notes/guidance for IT teams doing mass deployment)
- Install it on both the server and the client. Automatic deployment can be done using the /S command line switch (for silent/unattended installation, and it is case sensitive).
- On the server side, navigate to the "Misc" tab in the SOTA Hub settings and tick the "Bridge Over RDS" option
- The server side is now set to just "passthrough" bridge information to the client. No other settings matter on the server side when Bridge Over RDS is enabled. Bridge Over RDS enabled also disables the server from talking to any connected devices, so you can run multiple sessions without interference, so don't pass anything through.
- On the client side, configure any settings you'd like as needed (i.e. app mode (recommended ON), Use Edge Browser, etc.). You can copy the .ini file you configured to help automate deployment to other clients as needed, just drop it in or write a batch file to make the edits that you can deploy with you DM software.
- Restart the hub or Server
TL;DR: tick the Bridge Over RDS option on the server, install as normal on the client, and you are good to go.
We have a couple of customers now in the last week or so in multi-session terminal services environments running this release candidate successfully.