InTouch licensing in RDS and non-RDS environments
- Last UpdatedSep 25, 2024
- 1 minute read
If an InTouch application is running on a server node enabled with Remote Desktop Services (RDS), the console will behave the same as an RDS client session. Each session will consume a license. Each session will also consume a separate InTouch development license.
In this case, the InTouch application's ReadWrite capability is defined by its remote access configuration and confirmed by the consumed license. For example, if an application with ReadOnly remote access configuration is launched in WindowViewer in an RDS client session, it will look for a ReadOnly InTouch license. If an RDS ReadOnly license is not available in the License Server, startup license validation will fail.
On a node without RDS enabled, you can also login with a RDS client session that is allowed by the operating system. If an InTouch application is running in this non-RDS environment, the client session will behave the same as a console. In this case, the application's remote access configuration does not determine the ReadWrite access. ReadWrite access is determined only by the license in non-RDS environments.
In non-RDS environment, when application is running in free mode, it will always run in Read/Write mode.