Administrator Guide

In earlier version of ThinOS, when the broker times out, the user session is disconnected and the user is logged out from the broker.

From ThinOS 8.2 release, ThinOS disconnects the user session from the broker, but does not force user logout. This is because the

user has local connections other than the broker desktop, and these connections are active when the broker timeout is reached.

PCoIP session NUM/CAP keyboard status synchronizes with session instead of thin client—This is applicable for session startup

only. The PCoIP session keyboard NUM/ CAP status synchronizes from remote session to client, whereas RDP/ ICA synchronizes

status from local to remote session.

For example:

1. Set keyboard NUM=off in current PCoIP session.

2. Disconnect the session.

3. Set client keyboard NUM=on.

4. Reconnect to the PCoIP session.

5. The keyboard NUM status in both session and client is updated to NUM=off.

RDS desktop through PCoIP—You can view and connect to the Remote Desktop Service (RDS) desktop through the PCoIP

protocol in the broker using PCoIP enabled the ThinOS clients. In VMware Horizon View 6.0 and later versions, the RDS desktop has

RDP and PCoIP connections based on server congurations.

NOTE: The Horizon application is supported on both PCoIP and Blast. RDP is not supported.

The RDS desktop protocol switch message dialog box is provided in this release. A typical user scenario is as follows:

1. Connect to the RDS desktop through protocol. For example, RDP.

2. Disconnect from the desktop.

3. Connect to the same RDS desktop through another protocol. For example, PCoIP.

The message dialog box is displayed, allowing you with an option to continue.

The options available are:

• Cancel—You can end the PCoIP connection, and connect to the desktop in RDP again.

• Log Out and Reconnect—You can connect to the desktop through PCoIP, and the earlier session in RDP is logged out.

USB redirection RDS desktop through PCoIP—This feature is supported.

Using unauthenticated access—You can anonymously log in to the VMware session with application remoting.

To use the unauthenticated option, do the following:

1. On your AD server, create two anonymous users, for example, anonymous1 and anonymous2.