Cameyo's SessionSync data persistence mechanism synchronizes user profile files and registry keys between sessions. Here is how to configure which files get synchronized.

By default, all user's profile files are included within the synchronization mechanism, except the default exclusion list shown at the end of this article.

To extend or modify the list of synchronized files, you can create a file named C:\RemoteAppPilot\Settings\Upcs.filters, of which an example is shown here:

# Upcs.filters: list of inclusion and exclusion rules for files synchronization

+ AppData/Local/My App/**
- *.jpg

You can also define these filters as PowerTags, making them variable according to clusters, servers, apps and/or users.

Follow the following syntax:

  • Lines beginning with + indicate additional paths to include.
  • Lines beginning with - indicate paths to exclude.
  • {Defaults} refers to Cameyo's default built-in rules (which are used by default if this filters file does not exist).
  • Lines beginning with # are ignored, reserved for comments.
  • Empty lines are ignored.
  • Cameyo's service on the server needs to be restarted for changes to take effect.

Rules are processed from the top to the bottom, the first match wins. For example in the following case, *.xyz files are excluded, but is still included:

- *.xyz {Defaults}

Another example

# Upcs.filters: list of inclusion and exclusion rules for files synchronization

- 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 included in data synchronization. The rest of Cameyo's default filters are then taken into account


As of April 2020 {Defaults} corresponds to the following:

- Shared/**
- Outbound/**
- GDrive/**
- GDriveSvc/**
- GTeamDrive/**
- GTeamDriveSvc/**
- MS/**
- Dropbox/**
- DropboxSvc/**
- RapData/**
- Links/**
- CCPTmp/**
- Windows/**
- AppData/LocalLow/**
- AppData/Local/**
- AppData/Roaming/Microsoft/Protect/**
- AppData/Roaming/VOS/**
- AppData/Roaming/Microsoft/Windows/SendTo/**
- AppData/Roaming/Microsoft/SystemCertificates/**
- AppData/Roaming/Microsoft/Search/Data/Applications/**
- *.lnk
- Desktop.ini
- SessionInfo.*
- Cameyo.log


You can configure data persistence filters using the PowerTags !UPCS_INCLUDE, !UPCS_EXCLUDE or the more advanced !UPCS_FILTERS variable:


These PowerTags allow you to define inclusion & exclusion filters in a simplified way, separated by semicolon (';') form. Their matching order of precedence is: EXCLUDE is checked first, then INCLUDE, then EXCLUDE2. Example:

!UPCS_INCLUDE=Documents/Adobe/Premiere Pro/**;AppData/Roaming/Adobe/Premiere Pro/**

!UPCS_FILTERS (advanced)

The !UPCS_FILTERS PowerTag uses the same syntax as the Upcs.filters file described above, but replacing newlines with '|' (pipe). Example:

!UPCS_FILTERS=- *.docx|- *.bat|{Defaults}

In the above example, .docx and .bat files will be excluded from synchronization for the configured app.

You can disable data persistence for a specific cluster, server, app and/or user by setting the PowerTag !UPCS_ENABLED=0