Customize the user experience

You can customize the Cameyo user experience using PowerTags.

Windows environment variables

Some programs rely on Windows environment information such as client name, user name, computer name. Cameyo allows you to virtualize these using PowerTags:

!CLIENTNAME: Client name virtualization.
!USERNAME: User name virtualization.
!COMPUTERNAME: Machine name virtualization.

These settings will set the environment variables accordingly, but will also activate an API virtualization layer which will return the value to the calling app.

Keyboard layout

You can customize keyboard options for individual users or user groups.

Note: For users who have non-US keyboards by default, certain keys like Alt Gr + <Key> don't work on an English Cameyo server because of the default en-US keyboard option.

You can use the following PowerTag to customize keyboard options company-wide, on a cluster server, or on a user or app level:

!KBLAYOUT=de-ch-qwertz

The following values are possible:

en-us-qwerty

en-gb-qwerty

de-ch-qwertz

de-de-qwertz

fr-be-azerty

fr-fr-azerty

fr-ch-qwertz

hu-hu-qwertz

it-it-qwerty

ja-jp-qwerty

pt-br-qwerty

es-es-qwerty

es-latam-qwerty

sv-se-qwerty

tr-tr-qwerty

failsafe

IME keyboard input

Cameyo supports Input Method Editor (IME) languages as keyboard input, by configuring the following pair of PowerTags:

!KBLAYOUT=[KeyboardLayout] !STARTUP_BEFORE_PS1

For example:

!KBLAYOUT=[KeyboardLayout] !STARTUP_BEFORE_PS1=Set-WinUserLanguageList -LanguageList [LanguageId] -force;$P1="HKCU:\Software\Microsoft\Input\Settings";if(-not(Test-Path -Path $P1)){New-Item -Path $P1 -Force};New-ItemProperty -Path $P1 -Name EnableExpressiveInputEmojiMultipleSelection -Value 1 -Force;$P2="HKCU:\Software\Microsoft\CTF\LangBar";if(-not (Test-Path -Path $P2)){New-Item -Path $P2 -Force};New-ItemProperty -Path $P2 -Name ShowStatus -Value 0 -Force;New-ItemProperty -Path $P2 -Name ExtraIconsOnMinimized -Value 1 -Force;New-ItemProperty -Path $P2 -Name Label -Value 0 -Force;Set-WinLanguageBarOption -UseLegacyLanguageBar

[LanguageId] can be:

ja-JP

ko-KR

zh-TW

[KeyboardLayout] can be:

ja-jp-qwerty

ko-kr-qwerty

Example:

!KBLAYOUT=ja-jp-qwerty !STARTUP_BEFORE_PS1=Set-WinUserLanguageList -LanguageList ja-JP -force;$P1="HKCU:\Software\Microsoft\Input\Settings";if(-not(Test-Path -Path $P1)){New-Item -Path $P1 -Force};New-ItemProperty -Path $P1 -Name EnableExpressiveInputEmojiMultipleSelection -Value 1 -Force;$P2="HKCU:\Software\Microsoft\CTF\LangBar";if(-not (Test-Path -Path $P2)){New-Item -Path $P2 -Force};New-ItemProperty -Path $P2 -Name ShowStatus -Value 0 -Force;New-ItemProperty -Path $P2 -Name ExtraIconsOnMinimized -Value 1 -Force;New-ItemProperty -Path $P2 -Name Label -Value 0 -Force;Set-WinLanguageBarOption -UseLegacyLanguageBar

Clipboard

Cameyo HTML5 sessions support clipboard interaction with the user's local machine for text.

By default, users will be prompted to consent to share the clipboard between their devices and virtual apps.

If your server is configured with HTTPS, clipboard interaction is supported by default for most browsers.

You can also access the clipboard using Cameyo server tools, on the bottom right.

Text copied from the remote host appears here.

Taskbar

Cameyo's taskbar allows quick launching and switching between applications. It is an optional feature that appears at the bottom of the screen in app sessions.

To activate the taskbar, add a PowerTag named !TASKBAR_QUICKLAUNCH to the targeted server, cluster, or app configuration and set it as follows:

[name] | [command] | [arguments(optional)]

For example:

Auto-hide taskbar

To auto-hide the task bar, add the following PowerTag, in addition to !TASKBAR_QUICKLAUNCH:

!TASKBARMODE=2

Show only open applications

To only show open applications, set its value to EMPTY; the taskbar will only show if two or more applications are open.

!TASKBAR_QUICKLAUNCH=EMPTY

Toolbar

You can extend Cameyo's toolbar with your own custom buttons.

To do this, set the config PowerTag !EXTRATOOLBTNS using the following syntax:

[name] | [action] | [icon], where:

action can be one of the following action types, depending on the syntax:
URL: http[s]://site.com/..., for example: https://google.com

Cameyo app execution: #msg-app-[appid], for example: #msg-app-636296758959995072

Keypress: #msg-keybd-[keyboard key] emulates a keyboard keypress, following Microsoft's standard as described here. For example: #msg-keybd-%{RIGHT}

icon can be one of the following image types, depending on the syntax:
Picture from any URL: http[s]://site.com/..., for example: https ://online.cameyo.com/Images/Player/help.png

Material Google icon: [icon keyword] one of Google's predefined material icons listed here.

Multiple buttons can be specified, separated by semi-colon (;).

For example:

!EXTRATOOLBTNS=Test|#msg-app-636296758959995072;Notepad|#msg-app-25341625830944;VLC|#msg-app-93544712645557;F11|#msg-keybd-{F11}|tab;Alt+Left arrow|#msg-keybd-%{LEFT}|keyboard_arrow_left;Alt+Right arrow|#msg-keybd-%{RIGHT}|keyboard_arrow_right;CNN|https://cnn.com|https://online.cameyo.com/Images/Player/help.png

Where:

Test|#msg-app-636296758959995072

Notepad|#msg-app-25341625830944

VLC|#msg-app-93544712645557

F11|#msg-keybd-{F11}|tab

Alt+Left arrow|#msg-keybd-%{LEFT}|keyboard_arrow_left

Alt+Right arrow|#msg-keybd-%{RIGHT}|keyboard_arrow_right

CNN|https://cnn.com|https://online.cameyo.com/Images/Player/help.png

Files and storage

Cameyo sessions can be connected to local device folders, allowing users to directly view and edit their local files. Cameyo's file dialog replaces Windows standard file dialog box with a cloud-friendly one, which includes built-in integration with cloud storage, data persistence and drag & drop (for file transfer between the user’s host and the server). This mechanism is HTML5-compliant and secure.

Note: Using Admin > Company Settings > Authentication, you can connect cloud storage options for your users, and request users to connect their cloud drive. See Users and groups.

To customize the Cameyo file dialog, navigate to Admin > Session Settings. The Cameyo file dialog is enabled by default with the PowerTag !STORAGEFILEDIALOG.

Block access to specific files and folders

Cameyo allows you to blocklist files so that they cannot be accessed nor executed during sessions. This can be done using the PowerTag !STOPFILES.

For example, to block cmd.exe and notepad.exe and c:\windows\explorer.exe, add this PowerTag:

!STOPFILES=cmd.exe;notepad.exe;%WINDOWS%\explorer.exe

These files will then be neither accessible nor visible during Cameyo sessions.

Block access to local drives

To prevent users from accessing local drives through Windows Explorer or their browser during Play sessions, follow these steps:

On the Cameyo Admin console, select Dashboard .
Click Servers .
Select your server, and Connect as Admin.
Click the Cameyo shortcut in the taskbar.
Select Run.
In the command window, enter gpedit.msc.
Navigate to User Configuration > Administrative Templates > All Settings.
Select the option Prevent access to drives from My Computer.
Select Enabled and Restrict all drives.
Click OK.

If you would like to also hide these drives, you may repeat the same step for a setting named Hide these specified drives in My Computer.

Integrate with a local file system

You can switch file system integration on and off with the PowerTag !WEBFS.Possible values include:
!WEBFS=1, this means file system integration is allowed (this is the default).
!WEBFS=0, this means file system integration is not allowed.

To let your users connect local folders without having to go through the file dialog, use PowerTag !WEBFS=1 to display on the left-hand side as a shortcut.
To let your users connect local folders without having to go through the file dialog, usePowerTag !WEBFS_TOOLBTN=1 to add this to the toolbar.

HTTPS is required for this feature. If your Cameyo server is self-hosted and you do not have an SSL certificate, contact Cameyo Support to make connections from outside your network HTTPS.

Allow or block specific URLs on Chrome

As an admin, you can allow or block certain websites in Chrome browser within Cameyo. To achieve this, set the following registry keys on your Windows server:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\URLBlocklist] "1"="*" [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\URLAllowlist] "1"="cameyo.com" "2"="chrome://policy"

Tips for managing access to websites:

Create a blocklist entry disallowing everything (*)
Add as many addresses as you want to the URLAllowList, with incremental numbers.
Use the chrome://policy entry to check whether the policies got applied, but remove in production.
Don't use wildcards (*.cameyo.com) and only enter the common part (cameyo.com): cameyo.com will allow cameyo.com, kb.cameyo.com, and so on.
Note: This will not block any forwarders or parts of a page that is drawn from another website, but links to external sites will be blocked.

Set up user files and folders using a provisioning template

Files and folders stored in a user profile template are automatically provisioned to the user's profile directory on session start.

Windows user profile: C:\UserTemplate\AnyUser\%Profile%
Profile directory: C:\Users\RemoteUserX

You can also provision pre-defined registry data in the user profile template, which will be provisioned to HKEY_CURRENT_USER upon session start, by placing registry export file profile.reg.

Steps

To provision pre-defined HKCU data upon temporary session start:

On the Cameyo Admin console, selectServers .
Select your server, and Connect as Admin.
Click the Cameyo shortcut in the taskbar.
Select Run.
In the command window, run regedit.exe.
Set the keys you'd like to be distributed to all user profiles into your HKCU hive.
Export the relevant registry keys to C:\UserTemplate\AnyUser\%Profile%\profile.reg.

Policy settings, such as HKCU://SOFTWARE/Policies, are not allowed (by security) and will be ignored!

Set up printers

Printing with Cameyo can be done directly from the browser to the end user's network or personal printers. There are several methods of providing printing capability to users running applications in Cameyo.

Virtual printer

The virtual printer is a printer that is automatically available in Cameyo application sessions. When a print job is sent to it, it will render the print job to PDF, then send that PDF down to the end user's web browser and request it to print the PDF. The user will then be able to send the print job to any printer they have installed locally on their device.

Server-side printer

Printers may be installed on the Cameyo application servers themselves, which will allow users to print to printers that they may not have installed on their endpoint devices (such as to an office printer while they are working at a café). Printers installed on a Cameyo server will generally come in two main forms - locally-installed TCP/IP printers and print-server-based session printers.

Local TCP/IP printer

If a printer is installed directly onto the Cameyo server (including printer drivers and printer network ports), that printer will by default be available to all users who run an application on that server. Print jobs that are printed to these printers will be sent over the network directly to the printer devices. In order for this to work, make sure that there is network connectivity between the Cameyo server and the printer device.

Session printer

Session printers are printers that are available in individual user sessions. These printers are generally hosted on a print server, and the printers are made available to users via group policy, login scripts, or third party print management utilities. This configuration will usually be done outside of Cameyo, though login scripts may be set up to be launched using PowerTags or script files.

If you have a printer set up in your Google printing environment, your users will be able to print from their Cameyo apps directly to the registered printer.