Sometimes there is the need to provide connections that depend on the user (or group of users) rather than on the device. I.e. a user should be able to access specific connections independently from the device he is using. This is called Roaming Profile because the profile will follow the user independently from the device he is using.
To implement this functionality we need essentially two things:
At least one connection profile for users associated to at least one user policy.
A device policy that enables ThinMan Login on specific devices and that applies the user policy previously configured (see How to protect the Thin Client with ThinMan Login).
Since user authentication is needed, be sure to configure an LDAP Server or configure local users).
Configure either LDAP users or groups or local users.
Create a connection profile for users from a template.
Create a user policy that associates users (or groups) to the connection profile. This step is very important because it defines which connections the user will see on the device after the ThinMan Login.
Create a device policy and flag the two attributes Enable ThinMan Login and Enable User Policy. The first parameter tells ThinMan to protect the device with an authentication, the second parameter tells ThinMan to apply a specific user profile depending on the logged user. The device policy must be associated to all the devices on which we need to activate the roaming profile.
With this configuration all the devices associated to the device policy will ask for authentication.
After the authentication ThinMan will apply the corresponding User Policy associated to the logged user (or group who the user belongs to).
The User Policy will give a Connection Profile for Users (i.e. connections) to the device. The user will be able to see on the desktop the received connections.