Data Persistence (Session Sync)

Synchronize files and settings across sessions and servers

By default, Cameyo accounts are set up to remove user traces from the server(s) after each Play session is disconnected. If data persistence is desired, Session Sync can be enabled to store changes made to the user's profile directory and registry (HKCU) in a Cameyo Google Cloud Storage bucket. Each time the user signs in and starts a session, the user's data is synchronized back to the server.

This method gives data persistence and keeps the server clean when not in use for better security.

Go to Policy page and click (activation required) next to Data persistence to enable.

 

031 Data persistence on Policy page

Authorization is required through a Google account, which will be used only as a unique secure access key, i.e. no data will be stored on this authorized account.

Once Session Sync is enabled, users will see their profile settings and files as unchanged from one session to the next, from one server to another. Files can be saved and opened within the usual user directories such as Documents, Desktop.

Limitations:

  • Does not support unauthenticated users, i.e. users have to be signed in.
  • If a user from one Cameyo account (Company A) uses an application from another Cameyo account (Company B), his session’s data will be stored on Company B’s cloud storage, for security reasons.
  • Although files are synchronized from the server to the cloud on the fly, registry keys are synchronized only after the user sessions are disconnected. For this reason, setting changes that rely on the registry should be made with only one active session.

Exclude / include filters (advanced)

In RemoteAppPilot\Settings folder you can add two optional files to include and/or exclude files and directories for SessionSync's data persistence:

Exclusion filter

C:\RemoteAppPilot\Settings\Upcs.exclude: text file containing dirs or files to exclude, relative to the base dir (user profile).
Syntax:
RelativeDir/**: excludes %UserProfile%\RelativeDir and all its sub-directories.
*.ext: excludes any file ending with .ext extension.
FileName.*: excludes any file named FileName, regardless of extension.

Exceptions:

-ToExclude: by starting a line with a minus sign ('-'), you can remove certain directories or files from Cameyo's default exclusion list.

Example:
SomeDir/**
Draft.*
*.tmp
Options.ini
-AppData/Local/**

In the above example, folder SomeDir is recursively excluded. Any file named Draft.[anything] is excluded, as well as any file with .tmp extension. Any file named Options.ini will be excluded, regardless of directory. Last, AppData/Local (excluded by Cameyo's built-in rules) is un-excluded, thus included in data synchronization.

Inclusion filter

C:\RemoteAppPilot\Settings\Upcs.Include: same format as Upcs.exclude, without the exception ('-') mechanism.
Note: the inclusion filter takes precedence. So for example if you set inclusion to "Documents/**" and exclusion to "*.docx", the resulting synchronization will be: only files within Documents (and subdirs), except files ending with .docx.
Important: when using the inclusion filter, please add "hkcu**" to it if you'd like to keep user's registry settings (HKCU) synchronized.

Remarks

Changes in Upcs.Exclude or Upcs.Include require a service restart to take effect.