Launch Preferences
From Launch Preferences, you can choose which launch options are made available to the users when they open their store in a web browser. These settings do not apply when using Citrix Workspace app. For more information about launch options, see User access options.
To modify launch options, go to Edit Receiver for web site and select the Launch preferences tab.
Launch option
You can choose from one of the following options:
- Select Always use Receiver for HTML5 if you want the user to always to access resources through a web browser without prompting the user to download and install Citrix Workspace app locally. With this option selected, Workspace for HTML5 users always access resources directly through their browsers.
- Select Use Receiver for HTML5 if local Receiver is unavailable if you want the store web site to prompt the user to download and install Citrix Workspace app locally, but fall back to accessing resources through a browser if Citrix Workspace app cannot be installed. Users without Citrix Workspace app are prompted to download and install it every time they log on to the site.
- Select Install locally if you want the site always to access resources through a locally installed Citrix Workspace app. Users are prompted to download and install the appropriate Citrix Workspace app for their platform. Users can continue to access the store through a web browser but when the launch a resource it opens in the locally installed Workspace app.
Launch applications in the same tab
If you have chosen Always use Receiver for HTML5 or Use Receiver for HTML5 if local Receiver is unavailable, by default, resources launched in the browser open a new browser tab. If you want your resources to open in the same tab, replacing Workspace app for HTML5, select Launch applications in the same tab as Receiver for Web.
Show the Already installed option on the client detection page
Note:
This setting is applicable only for Windows, MacOS, and Linux devices. If a user has installed Workspace web extensions, then the client detection and launch is handled by the web extensions. In such cases, this setting is not applicable.
When end users open a store in their browser for the first time on Windows, macOS, or Linux, the website attempts to detect the locally installed app using the Citrix Workspace launcher. Subsequently, when a user launches a resource, the Citrix Workspace launcher communicates with the locally installed Citrix Workspace app. If users click the Already installed option, the client detection process is skipped. As a result, when the user launches a resource, an .ica
file is downloaded that users can open with their locally installed Citrix Workspace app. This does not support features such as workspace control.
This downloaded .ica
file may pose a security risk. Citrix recommends that you clear Show Already installed link on the client detection page.
Prevent Ica downloads on all platforms
This provides an additional level of protection by completely blocking .ica
downloads across all platforms. As Citrix Workspace launcher is not available on iOS, Android or Chrome, users must either select Use Light version if available, or they must add their store to their locally installed Citrix Workspace app.
Important:
This option should not be used in conjunction with the Show Already installed option on the client detection page.
PowerShell SDK
To configure these settings using the Powershell SDK, use cmdlet Set-STFWebReceiverPluginAssistant.
To configure Prevent ICA Downloads, use cmdlet Set-STFWebReceiverUserInterface with parameter PreventIcaDownloads
.
Progressive Web App [Technical Preview]
The Progressive Web App (PWA) feature allows you to install the store website so that it can be launched from your start menu or desktop, similar to a native app. This is available only in the old UI.
Prerequisites
To use Progressive Web App version, ensure that you have the following:
- The minimum required version of StoreFront is 2411.
- Configure StoreFront for SSL.
- Use Google Chrome or Microsoft Edge browser on Windows, Mac, or Linux.
- You must set the deployment option to Always use Receiver for HTML5.
Note:
This feature is disabled by default.
Known limitations
- When you set single tab mode on the StoreFront deployment, it does not apply to PWA launches.
- Clicking the shortcut icon opens a new window that hosts the store page.
- Hybrid scenarios during session-shared app launches are not supported. For example, launching an app from the PWA and then trying to launch a session-shared app in the browser does not work.
- Switching from the PWA session window to the browser window does not work.
Configuration
This feature is disabled by default. Admins can enable the functionality as follows:
-
From the StoreFront management console, go to Manage Receiver for website and set the deployment option to Always use HTML5 receiver. For more information about the setting, see Deployment option.
-
Run the PowerShell command Set-STFWebReceiverUserInterface
$receiver = Get-STFWebReceiverService Set-STFWebReceiverUserInterface -WebReceiverService $receiver -ProgressiveWebAppEnabled $true <!--NeedCopy-->
Install Progressive Web App using Google Chrome
Users can install the store website as follows:
- Open the store in the Google Chrome browser.
-
Click the following icon in the toolbar:
The option to install PWA appears.
-
Click Install to add your store as PWA to your desktop and Start menu:
If you have multiple StoreFront stores, you can install each store website separately. Each installation will generate a shortcut named
<Store website name>
, which can be renamed as required.
Install Progressive Web App using Microsoft Edge
Users can install the store website as follows:
- Open the store in the Microsoft Edge browser.
-
Click the following icon in the toolbar:
The option to install PWA appears.
-
Click Install to add your store as PWA to your desktop and Start menu:
If you have multiple StoreFront stores, you can install each store website separately. Each installation will generate a shortcut named
<Store website name>
, which can be renamed as required.