Cameyo's server page allows you to define the server's behavior. To access a server's configuration page, go to the Servers page (online.cameyo.com/servers) and click on the server you'd like to edit.
•User profiles
This section defines how Windows user profiles are managed during sessions.
o"Temporary user profiles" (default): user profiles are provisioned on the fly with temporary user accounts named RemoteUser1, RemoteUser2, etc. The user's profile is deleted upon session end. This is the most scalable mode as it allows any number of sessions per user. User data is wiped out of the server upon session completion, which also ensures data privacy. You can combine this mode with data persistence and enjoy a 'best of both worlds' approach.
o"Cached user profiles": user profiles are provisioned similarly to the above, but instead of RemoteUserX, each end-user gets their own uniquely-named user profile, which remains on the server from one session to the next.
o"Native Windows accounts": Windows-based authentication. When set, users are prompted for their Windows credentials and authenticated into the server with their persistent Active Directory profile. Unlike with Temporary users, their roaming profiles remain on the server and do not get deleted upon session end. You can also input an authentication domain that will set the domain to which to authenticate. For Windows authentication mode to function, the server needs to be part of the Active Directory domain, or have some local Windows users.
Note: changing the user profiles requires a service restart. Hence, after changing the user profile mode, click "Save changes" and then "Restart service".
•Concurrent sessions: defines the maximum number of overall concurrent sessions on the server. When set to anything other than "unlimited", the server won't allow more than the indicated number of concurrent sessions (including all users and all apps).
•Timezone: defines the server's time zone. This affects both Cameyo's settings (i.e. usage management) and Windows' timezone configuration.
•RDP Port Shield: keeps RDP port closed within Windows Firewall, opening it only when needed (more info here).