Problem: If your environment has load balanced Unified Workspace servers, you cannot use the load-balancer DNS name in the Single Sign-On Server field for wnSSOclient.
Cause: Single Sign-On Server field is used for communicating instructions between the wnSSOclient and server with longer instructions. A load-balancer cannot be between the wnSSOclient and the server.
Solution(s): Make instructions to application short enough that the Single Sign-On Server field is not required. This includes shortening the application path, but still including some instructions like {logoffonexist} and {notimeout}. This is also helpful for situations where you have multiple versions of same software.
Shorten the Application Path:
- Check if the application has an App Path to the EXE file in registry
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths
- If not, add an entry to registry on all RDS servers for the application
Example configuration for application called Cinema4D:
- Registry Key for "Cinema4D.exe"
- Default REG_SZ "C:\Program Files\MAXON\CINEMA 4D R17\CINEMA4D.exe"
- UW Start Program: Cinema4D.exe
- UW Single Sign-on Script: {logoffonexit}|{notimeout}
- UW Single Sign-On Server: (leave it blank)
- UW wnSSOClient Path: whatever path it should be
Reference(s):