Apps, including virtual apps, can save data in a defined location so that it can be retrieved and used later, even after the apps have closed or the system has been restarted. Data persistence ensures that data remains intact and accessible across different sessions of an app.
By default, Cameyo's data persistence component synchronizes users' data between servers.
You can configure which global folders and files get synchronized. You can also configure data persistence filters using PowerTags to make them variable according to clusters, servers, apps or users.
Configure data persistence for global folders
- On the Cameyo Admin console, click Servers
.
- On the right of your chosen server, click Action > Connect as admin.
- Click the server you chose and go to Details > General > PowerTags.
- Enter
!UpcsGlobal=1to set a server-wide or cluster-wide PowerTag.Note: By default,
C:\Users\Publicwill be the synchronized directory. If you'd like it to be different, set a PowerTag!UpcsGlobalPath=path (C:\Data). - At the bottom, click Save.
- Restart your Cameyo server or their respective services.
Note: A backup ZIP of the global directory's contents are automatically generated after each server reboot, within that server's directory
C:\RapPrereqs\RClone\Bak.
Configure data persistence for files
Cameyo's SessionSync data persistence mechanism synchronizes user profile files and registry keys between sessions.
By default, all user's profile files are included within the synchronization mechanism, except the default exclusion list.
To configure which files get synchronized, you can create a list of inclusion and exclusion rules for file synchronization.
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.
Note: Inclusion and exclusion rules are processed from the top to the bottom, the first match wins.
Example 1To extend or modify the list of synchronized files, you can create a file named C:\RemoteAppPilot\Settings\Upcs.filters:
# Upcs.filters: list of inclusion and exclusion rules for files synchronization
+ AppData/Local/My App/**
- *.jpg
{Defaults}
In the following example, *.xyz files are excluded, but abc.xyz is still included:
+ abc.xyz
- *.xyz
{Defaults}
In this example:
- The folder
SomeDiris recursively excluded. - Any file named
Draft.[anything]is excluded, as well as any file with.tmpextension. - Any file named
Options.iniwill be excluded, regardless of directory. 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.
# Upcs.filters: list of inclusion and exclusion rules for files synchronization
- SomeDir/**
- Draft.*
- *.tmp
- Options.ini
+ AppData/Local/**
{Defaults}
From March 2025, {Defaults} corresponds to the following excludes:
- /Shared/**
- /Outbound/**
- /GDrive/**
- /GDriveSvc/**
- /GTeamDrive/**
- /GTeamDriveSvc/**
- /MS/**
- /WebFS/**
- /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/**
- /AppData/Roaming/NVIDIA/**
- NTUSER.*
- *.lnk
- Desktop.ini
- SessionInfo.*
- CyoDesktopApps.xml
- /Cameyo.err.log
- /Cameyo.log
- Cameyo.UserTemplateFastSync.dat
- CameyoVOS.log
{Defaults} corresponds to following includes:
- /hkcu-base.dat
- /hkcuclass-base.dat
- /hkcu.reg
- /profile.reg
- /User.Id
- /AppData/Local/Microsoft/IdentityCache/**
- /AppData/Roaming/Cameyo/WinCred/**
- /AppData/Local/Microsoft/Office/16.0/Licensing/**
Configure data persistence filters using PowerTags
You can configure data persistence filters using the PowerTags !UPCS_INCLUDE, !UPCS_EXCLUDE or the more advanced !UPCS_FILTERS variable.
!UPCS_EXCLUDE / !UPCS_INCLUDE / !UPCS_EXCLUDE2
These PowerTags allow you to define inclusion and exclusion filters in a simplified way, separated by semicolon (';') form. Their matching order of precedence is: EXCLUDE is checked first, then INCLUDE, then EXCLUDE2. For example:
!UPCS_INCLUDE=Documents/Adobe/Premiere Pro/**;AppData/Roaming/Adobe/Premiere Pro/**
!UPCS_FILTERS
The !UPCS_FILTERS PowerTag uses the same syntax as the Upcs.filters file described above, but replaces newlines with '|' (pipe). For 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 or user by setting the PowerTag:
!UPCS_ENABLED=0
Google and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.