PowerTags are a powerful feature for customizing virtualized application environments. PowerTags are metatags that can be assigned to various entities within a virtualized environment, including users, user groups, apps, servers, clusters, or the entire account (global). For example, you can use a PowerTag to define custom behavior for sessions or to inject environment variables directly into the Windows session.
Custom behavior with PowerTags
PowerTags offer granular control and can be applied at different levels:
- Individual users
- User groups
- Individual apps
- Specific servers
- Server clusters
- Company account
How to use a PowerTag
To use a PowerTag to customize a feature or a component, you locate the relevant option on the Cameyo Admin console and add a line to the input field.
CLOSECONFIRM PowerTag- On the Cameyo Admin console, click Servers
.
- To open the Details page of your chosen server, click the hyperlinked server name.
- Navigate to General > PowerTags.
- On a new line, enter
!CLOSECONFIRM=1to set a server-wide setting. - At the bottom, click Save.
- Restart your Cameyo server for the new PowerTag value to take effect for apps running on that server.
Once CLOSECONFIRM is switched on, every time a user closes a tab, a message displays prompting them to click Leave to confirm that they do want to close the tab, or Cancel to return to the app.
!CLOSECONFIRM=0/1 can be placed at an application, server, cluster, user, usergroup or company-wide level.Supported PowerTags and their functions
These are the supported PowerTags that you can use to control various aspects of the virtualized environment and user sessions.
Users and Cameyo portal
| PowerTag | Description |
|---|---|
|
|
Delete or report inactive users (company-level PowerTag only). |
|
|
Number of inactivity days after which to automatically delete users (minimum allowed: 14), or 0 for never. |
|
|
Number of inactivity days after which to report users as inactive. Report is submitted by email, or 0 for never. |
|
|
Disables the ability for end users to access My Profile. |
|
|
Cameyo logins only passwords expire after X number of days, after which they must be changed. |
|
|
Cameyo logins only regular expression for password strength validation. |
|
|
Ukraine-supportive theme and colors for the portal, to be applied at the company level. |
|
|
Changes browser icon from Cameyo icon to an online ICO file, for example, |
|
|
Company-level PowerTag for setting the authentication cache cookie duration after which the user is logged off and re-authentication is necessary (by default 10 days). Note: This takes effect after a sign-in (so if you're already signed in, sign out and sign in again after applying this PowerTag). |
File dialogs and storage for user groups
| PowerTag | Description |
|---|---|
|
|
Controls the Cameyo File Dialog, set to either "1" (enable) or "0" (disable). |
|
|
Virtual drive letter for user profile. |
|
|
Virtual drive letter for the Public dir. |
|
|
Controls Session Sync for data persistence and cloud-based user profile synchronization. |
|
|
Controls data persistence and its include and exclude filters. |
|
|
Defines the minimum hard-drive space when caching data persistence locally (C:\UserData). See Session Sync data persistence. |
UPCS_EXCLUDE2 |
Controls data persistence and its include and exclude filters.
|
UPCS_FILTERS |
Controls data persistence and its include and exclude filters. |
Windows and app behavior
| PowerTag | Description |
|---|---|
|
|
Block access to specific files and executables. For example: |
|
|
Client, user and machine name virtualization. |
|
|
Sets Chrome as the default browser. |
|
|
Defines the starting directory for the session app's execution. |
|
|
Substitutes the execution of an app from a specified directory path. For example, if you want to specify to run |
|
|
Blocks hard-disk Explorer navigation and basic system commands. |
|
Requires !USERPROFILE_DRIVE to be set (for example, !USERPROFILE_DRIVE=X). |
|
|
Has to be set at the server level (or cluster or company) but cannot be on a single app or user, as it's a server-global security feature and not per-session. |
|
|
Requires service restart to be applied, for the same reason. |
|
|
|
URLs launched by the session's app will be redirected directly as a new tab within the user's browser, outside the session itself. The url_prefix is in the form: |
|
|
Controls whether Cameyo allows file system integration. |
|
|
File handling using PWA's (File Association) |
|
|
USB redirection using WebUSB |
|
|
Using SILOs (Persistence) |
Session behavior and appearance
| PowerTag | Description |
|---|---|
|
|
Controls Cameyo's task bar. |
|
|
Controls extra tool bar buttons. |
|
|
Enables or disables clipboard support (from session to client - client to session is always permitted) |
|
|
Defines a fixed session width and height. |
|
|
When in full screen mode, session will capture all system keyboard keys including the Windows key, Alt-Tab as well as certain reserved control keys. |
|
|
Controls user's cloud drives virtualization, if configured. |
|
|
Controls accidental tab closure. |
|
|
Setting Cameyo keyboard layout. |
!GRACEFULDISCOSECSTARTUP_GRACEFULDISCO_PS1 |
See Graceful application closing. |
!STARTUP_AFTER_xxxx |
Controls session scripting. |
!STARTUP_BEFORE_SYNC_xxx |
Controls session scripting. |
!STARTUP_GLOBAL |
Controls session scripting. |
Session connectivity and initiation
| PowerTag | Description |
|---|---|
|
|
Switches Cloud Tunneling on or off. |
|
|
Sends a notification email to the technical contacts every time an Admin session is initiated on a Cameyo server, for increased account security. |
|
|
This is an allow-list of countries from which sessions can be requested (2-letter ISO country codes), at a company-wide, application, server, cluster, user or usergroup level. For example, |
|
|
This is list of IP addresses, separated by semicolon, from which sessions can be requested. Takes precedence over !ALLOW_COUNTRY so the two PowerTags can be used together to allow specific IP addresses from blocked countries. |
Session token security
| PowerTag | Description |
|---|---|
|
|
Timeout in seconds after which a session's token can no longer be used. Note that this also neutralizes connection resiliency after the timeout expires. |
|
|
Revokes a session's token a few seconds after session authentication. |
|
|
Prevents a session's token from being used from an IP different than the initial one. Note that this also neutralizes connection resiliency if the user's IP changes during session time. Also note that this prevents a session's token from being used from an IP different than the initial one when the Cameyo server uses direct connections, not cloud tunneling. |
|
|
Hides the session token out of the URL bar. In some cases people like to hide the token ID, either because they project or share their screens, or because they feel better this way. Take into account though that this makes page refresh (F5) not be able to reconnect to the session. |
Server properties
| PowerTag | Description |
|---|---|
|
|
Blocks server access to Cameyo's support team.
|
|
|
Time, in seconds, to keep sessions alive in case of disconnection. Equivalent to Windows RDS' MaxDisconnectionTime parameter. Cameyo's default is 120. |
|
|
Maximum idle time in minutes. Overrides the session policy settings. Requires service restart. |
|
|
Custom cloud tags and labels, VPC and subnets for created instances. |
|
|
Forces Secure Boot to be enabled on created instances. |
|
Specifies a custom machine type. For more information, see Google Cloud's General-purpose machine family for Compute Engine.
|
!CLOUDCPUGEN |
Specifies the CPU generation type. |
!CLOUDSERIES |
Specifies the CPU series type. C4D VMs are available as predefined configurations in standard, highcpu, and highmem sizes ranging from 2 vCPU to 384 vCPUs and up to 3,024 GB of memory. |
!CLOUDIP |
Specifies the IP format, IPv4 or IPv6. |
Configuration and order of precedence
PowerTags are dynamic, meaning they can vary from one session to another and take effect immediately, without requiring service nor server restart (except server-level PowerTags).
The order of precedence, from highest priority to least, is:
- User
- User group
- App
- Server
- Cluster
- Company (Account)
Example 1:
If a user has the tag 'MY_NAME=John' defined while the server has 'MY_NAME=Server' defined, a session run by this user on that server will have 'MY_NAME' defined as 'John'.
Example 2:
If the server has tag 'MY_NAME=SERVER' defined while the server's cluster has 'MY_NAME=CLUSTER' defined, sessions will run on this server with 'MY_NAME' defined as 'SERVER'.
Example 3:
If an application has tag 'MY_NAME=SomeApp' while the same global Cameyo account's PowerTag is defined as 'MY_NAME=CameyoAccount' then a session running this app will have 'MY_NAME' defined as 'SomeApp'.
Multiple tags
When multiple tags exist for a given session (for example, cluster + server + user + app), the session will be started with the combination of all relevant tags.
Multiple tags can be defined on each line, for example:
MY_VAR1=Some value
MY_VAR2=Some other value
Custom PowerTags
You use PowerTags to inject custom values into Cameyo sessions as environment variables. For more advanced control, sticky PowerTags can be used to create persistent, server-wide environment variables.
'+' sticky PowerTags: persistent server-wide environment variables (advanced): apply globally to an entire server, including system processes outside of a Cameyo session, and are defined by adding a + prefix.
- Function: To create global system variables. For example, +MY_GLOBAL_VAR=Some value creates a system variable named "MY_GLOBAL_VAR" with the value "Some value" on the affected servers.
- Scope: These tags can be set for servers, clusters, or entire accounts.
- Activation: A sticky PowerTag only takes effect after the server's Cameyo service (re)starts.
- Removal: To remove a sticky tag, you must set it to an empty value (for example, +MY_GLOBAL_VAR=). The removal takes effect after the Cameyo service restarts and the system is rebooted, which is a Windows requirement.