Citrix Virtual Apps & Desktop 7 1912
Citrix have released a new version of Citrix Virtual Apps and Desktop 7 1912.
Release is now available for download, December, 2019.
Citrix Virtual Apps (former name: XenApp) Citrix Virtual Desktop (former name: XenDesktop)
Citrix raises the bar of for user experience and new product release of following technologies:
- Director 1912
- Virtual Delivery Agents 1912 for ServerOS and ClientOS
- Virtual Delivery Agent 1912 for Linux
- Citrix Licensing 11.16.3
- Citrix Federated Authentication Service 1912
- Storefront 1912
- Provisioning 1912
- Profile Management 1912
- Workspace Environment Management 1912
- Session Recording 1912
- Workspace App 1912 Techpreview for Windows
- Workspace App 1912 for Linux
- Workspace App 1912 for Chrome
- Workspace App 1912 for Android
- Workspace App 1912 for HTML5
- Workspace App 1912 for ChromeOS
What’s new in Citrix Virtual Apps and Desktop 7 1912
Important notice about upgrading VDAs
If the Personal vDisk (PvD) component was ever installed on a VDA, that VDA cannot be upgraded to version 1912 LTSR or later. To use the new VDA, you must uninstall the current VDA and then install the new VDA.
This instruction applies even if you installed PvD but never used it.
Learn if you’re affected
How PvD might have been installed in earlier versions:
- In the VDA installer’s graphical interface, PvD was an option on the Additional Components page. The 7.15 LTSR and earlier 7.x releases enabled this option by default. So, if you accepted the defaults (or explicitly enabled the option in any release), PvD was installed.
- On the command line, the
/baseimageoption installed PvD. If you specified this option, or used a script that contained this option, PvD was installed.
If you don’t know whether your VDA has PvD installed, run the installer for the new VDA (1912 LTSR or later) on the machine or image.
- If PvD is installed, a message appears, indicating there is an incompatible component.
- For the graphical interface, click Cancel on the page containing the message, and then confirm that you want to close the installer.
- From the CLI, the command simply fails with the displayed message.
- If PvD is not installed, the upgrade proceeds.
What to do
If the VDA does not have PvD installed, follow the usual upgrade procedure.
If the VDA has PvD installed:
- Uninstall the current VDA. For details, see Remove components.
- Install the new VDA.
If you want to continue using PvD on your Windows 7 or Windows 10 (1607 and earlier, without updates) machines, VDA 7.15 LTSR is the latest supported version.
Install and upgrade: New user personalization layer component in single-session VDAs
When installing or upgrading a single-session VDA, you can include the user personalization layer component. This feature is powered by Citrix App Layering, On non-persistent machines, the feature preserves users’ data and locally installed applications across sessions.
This feature replaces Personal vDisk, which has been deprecated. If you are upgrading a VDA that previously had PvD installed, see Important notice about upgrading VDAs.
Install and upgrade: Microsoft Visual C++ Runtime 2017 prerequisite
When installing a Delivery Controller or Windows VDA, Microsoft Visual C++ Runtime 2017 is installed automatically if it (or a later supported version) is not already installed. This is a newer Visual C++ Runtime version than the version installed in earlier Citrix Virtual Apps and Desktops releases.
Install and upgrade: SQL Server Express version
When installing the first Delivery Controller, you can choose to have Citrix install Microsoft SQL Server Express on the same machine, for use as the site database. As of this release, for new installations, we install SQL Server Express 2017 with Cumulative Update 16. This is a newer version than in earlier Citrix Virtual Apps and Desktops releases. For upgrades, we do not upgrade any SQL Server Express version that is already installed.
When you install a Controller, Microsoft SQL Server Express LocalDB is installed automatically for use with Local Host Cache. (This installation is separate from the SQL Server Express used for the site database.) For a new installation, we install SQL Server Express LocalDB 2017 with Cumulative Update 16. This is a newer version than in earlier Citrix Virtual Apps and Desktops releases. For upgrades, we do not upgrade any SQL Server Express LocalDB version that is already installed.
Install and upgrade: Supported Windows 10 versions for VDAs
This release supports Windows 10 32-bit (x86) and 64-bit (x64) OSs. The 32-bit Windows 10 OS is not supported in the 1909 Current Release, There are currently no plans to support it in Current Releases after 1912 LTSR. For Windows 10 machines, Citrix recommends using 64-bit (x64).
Install and upgrade: Prevent pending reboot check
When installing or upgrading core components, the installer stops if it detects that a restart is pending from a previous Windows installation on the machine. Now, when using the command-line interface, you can prevent the check for a pending restart by including the
/no_pending_reboot_check option in the command. For more information, see During installation of any component.
VDAs and machine catalogs: Operating system name changes
Operating system names for VDAs and machine catalogs have changed.
- Multi-session OS (formerly Server OS): The multi-session OS machine catalog provides hosted shared desktops for a large-scale deployment of standardized Windows multi-session or Linux OS machines.
- Single-session OS (formerly Desktop OS): The single-session OS machine catalog provides VDI desktops ideal for a variety of different users.
Component version number: Change to on-premises value
In a product and component version number (YYMM.c.m.b), the value of c is 0 for an on-premises release. For example, in Apps & features, this version appears as 1912.0.0.build number.
In earlier on-premises releases, and in Citrix cloud releases, the value of c is 1.
Operating system name changes
Operating system names on the Create Machine Catalog > Machine Catalog Setup > Operating System page have changed:
- Multi-session OS (formerly Server OS):
The multi-session OS machine catalog provides hosted shared desktops for a large-scale deployment of standardized Windows multi-session or Linux OS machines.
- Single session OS (formerly Desktop OS):
The single session OS machine catalog provides VDI desktops ideal for a variety of different users.
Support for provisioning Linux machines on Amazon Web Services
Citrix Studio now supports using Machine Creation Services (MCS) to provision Linux machines on Amazon Web Services (AWS). For more information, see Use MCS to create Linux VMs.
Operating system name changes
Operating system names on the Director pages have changed:
- Multi-session OS (formerly Server OS)
- Single session OS (formerly Desktop OS)
Configure on-prem Sites with Citrix Analytics for Performance
You can now configure your on-prem Citrix Virtual Apps and Desktops Site with Citrix Analytics for Performance (currently under Limited Technical Preview) to access advanced performance analytics and actionable insights.
Ensure that you have an activated Citrix Cloud account. To connect your Site to Citrix Analytics for Performance, follow a simple process starting from the Analytics tab in Director. A unique registration code is generated to help register your Site with Citrix Cloud. After registration, you can view the analytics related to the performance of your Site on the Citrix Analytics for Performance dashboard. This feature is available on Delivery Controller and VDAs version 1906 or later. For more information, see the Configure on-premises Sites with Citrix Analytics for Performance article.
Version 1912 of the VDA for Multi-session OS and the VDA for Single-session OS includes the following enhancements (in addition to the VDA installation and upgrade items listed previously in this article):
Although VDA version number displays indicate “Citrix Virtual Apps and Desktops 7 1912 LTSR”, the VDAs are supported for LTSR and CR deployments.
Support for Local Security Authority (LSA) protection
We now support the use of Local Security Authority (LSA) protection on a multi-session server OS and a single-session desktop OS for standard authentication, Federated Authentication Service (FAS) authentication, and Smart Card authentication. For more information about LSA protection, see the Microsoft article Configuring Additional LSA Protection.
This release introduces an add-on feature that enhances security when using Citrix Workspace app. New policies provide anti-keylogging and anti-screen-capturing capabilities in a session. The new policies along with Citrix Workspace app 1912 or later for Windows can help protect data from keyloggers and screen scrapers. For more information, see App protection.
Virtual Delivery Agents (VDAs) 1912 for Linux
Version 1912 of the Linux VDA includes the following new feature and enhancements:
Support for MCS on the AWS platform
You can use Machine Creation Services (MCS) to create Linux VMs on the AWS platform. For more information, see Use MCS to create Linux VMs.
A currently running VDA can be used as the template
When using MCS to create Linux VMs, you can use a currently running VDA as the template and inherit all its existing configurations. This running VDA can be installed manually or using easy install. For more information, see Use MCS to create Linux VMs.
Client drive mapping: Support for large file transfers
Client drive mapping now supports transfers of files with the size of 4 GB and larger between the Linux VDA and your client device. This enhancement requires your client to be running Citrix Workspace app for Windows 1808 or later.
Citrix Federated Authentication Service (FAS) 1912 contains new features.
Citrix Storefront 1912
StoreFront 1912 includes the following new features. For information about bug fixes, see Fixed issues.
StoreFront Protocol Handler Support now includes Chrome devices with Workspace app for Android
When users on Chrome devices open a Citrix Receiver for Web site, with Citrix Workspace App for Android 1912 or higher installed, the browser automatically opens ICA files using Citrix Workspace App for Android at launch.
The client detection work flow for Android—which determines whether Citrix Workspace App for Android is installed—is now identical to Citrix Workspace App for Windows and Citrix Workspace App for MAC clients when the Chrome browser is used on Chrome devices. In previous releases, users on Chrome devices were required to manually open a downloaded ICA file first.
Support for app protection policies
StoreFront 1912 supports app protection policies to enhance security when other Citrix components, such as Citrix Workspace app and Citrix Virtual Apps and Desktops delivery controllers, also support the app protection feature. App protection policies are set at the Delivery Group level, and Citrix Virtual Apps and Desktops determines whether app protection policies are used. You do not need to manually enable the app protection feature within StoreFront. When StoreFront receives requests containing the HTTP header X-Citrix-AppProtection-Capable from a Citrix Workspace app that supports app protection policies, StoreFront automatically sends a smart access tag to Citrix Virtual Apps and Desktops indicating that it supports app protection policies. For details of configuring Delivery Groups with app protection policies, see App protection.
Desktop Appliance sites no longer supported
StoreFront support for users to access desktops on Desktop Appliance sites was announced as deprecated in Citrix Virtual Apps and Desktops 7 1811. At this release, Desktop Appliance sites are no longer supported, and we recommend using Citrix Workspace app Desktop Lock for all non-domain-joined use cases.
When you upgrade to StoreFront 1912, any Desktop Appliance sites in your deployment are automatically removed. See Upgrade StoreFront.
StoreFront PowerShell SDK
The StoreFront PowerShell SDK has been republished as version 1912. You can no longer create or manage Desktop Appliance sites using PowerShell.
Citrix Provisioning 1912
Support for Microsoft SQL 2017
Citrix Provisioning adds support for Microsoft SQL Server 2017.
Citrix Provisioning supports Citrix Hypervisor 8.1 functionality, guest UEFI boot, and secure boot. This functionality enables VMs running Windows 10 (64-bit), Windows Server 2016 (64-bit), or Windows Server 2019 (64-bit) to boot in UEFI mode. UEFI boot provides a richer interface for the guest operating systems to interact with the hardware, which can significantly reduce Windows VM boot times. See the Citrix Hypervisor documentation for more information.
This release of Citrix Provisioning introduces updates to provisioning server performance statistics. These statistics allow other Citrix applications to determine the state of provisioned servers by introducing a performance counter provider that generates dynamic information about the provisioning server.
How it works
This version adds a performance counter provider that captures dynamic information about the provisioning server by using an external application running on a server or a remote machine. This application queries the performance data of the server using Windows Performance Counter. The provider does not duplicate information obtained from the system using standard Windows objects, such as CPU, memory, disk, or network configuration information.
- New Windows events containing database and stream services restart events are written to the Windows event log.
- The state of provisioned servers is obtained from the Citrix Provisioning object oriented PowerShell API.
- The Citrix Provisioning server installer registers the newly installed performance counter provider.
Updated performance counters
Installing this version adds and registers an updated performance counter on each provisioned server as part of the standard installation and upgrade process. The following image illustrates the counter as part of the StreamProcess:
The updated StreamProcess includes the following extra performance counters:
CounterSet: Citrix Provisioning StreamProcess
The provider creates the
PVS_VDisk WMI objects in the
root/Citrix/PVS namespace. Each provisioned target device has a single instance of the
PVS_Target object. The
PVS_Target object provides information about the installed Citrix Provisioning version, and statistics for the latest boot operation.
|Total Target Login Attempts
|The total number of target device login attempts.
|Total Target Reconnect Count
|The total amount of target device reconnects.
|Rejected Login Count – Device Not Found
|The number of target device logins that were rejected because the device was not found in the database.
|Rejected Login Count – virtual disk Not Available
|The number of target device logins that were rejected because the virtual disk was not available for the device.
|Rejected Login Count – Server Busy
|The number of target device logins that were paused because the maximum number of devices a server allows to boot was reached.
|Rejected Login Count – Server Not Available For virtual disk
|The number of target device logins that were rejected because no servers were available for the virtual disk.
The StreamProcess writes the following new events to the Windows Event log:
- DB online to offline with offline database support enabled
- DB online to offline with offline database support disabled
- Offline database support enabled event
- Offline database support disabled event
The StreamService writes the following new events to the Windows Event log:
- Stream process restart event
- Management daemon restart event
- Notifier restart event
- Inventory restart event
To provision a VDA on an opaque network, use the Citrix Virtual Apps and Desktop Setup Wizard. See Deploying virtual desktops to VMs using the Citrix Virtual Apps and Desktops Setup Wizard for more information.
Create the hosting unit and associate the opaque network to it using Citrix Studio. See Connections and resources for more information.
Use Citrix Studio to select an opaque network
In Citrix Studio, access the Add Connection and Resources page. In the Networksection, select the resource representing the opaque network, then click Next:
After creating a hosting unit with the opaque network, use it in the Citrix Virtual Apps and Desktop Wizard in the provisioning console.
Provision VDAs to a specific resource pool
Citrix Provisioning 1912 supports provisioning VDAs at a specific resource pool in an on-premises ESX hypervisor. You can provision this VDA using the Citrix Virtual Apps and Desktops Setup Wizard in the Citrix Provisioning console.
Create a hosting unit with the resource pool using Citrix Studio before using the Setup Wizard in the provisioning console.
- The provisioned target device installer registers the WMI and performance counter providers. No additional installation options require configuration on the provisioned target device.
- The current
CVhdMpperformance counter provider only supports VHDX for target devices using Cache in device RAM with overflow on hard drive. Configure the resource pool. In Citrix Studio, launch the Add Connection and Resources Wizard. From the Add Connection and Resources page, select Storage Management. In the Select a cluster field, click Browse:
Select the appropriate cluster, and click Next. Select the
Compute-ResourcePool or any of the child resource pool options under
Use the Citrix Virtual Apps and Desktops Setup Wizard in the provisioning console to select the hosting unit with the resource pool. Click Next:
To provision at the root cluster level, select the Ignore resource pool info, create VM at cluster level check box.
The cluster and the resource pool info appear in the Summary page of the Citrix Virtual Apps and Setup Wizard:
Using PowerShell to provision VDAs at the resource pool level
Citrix Provisioning 1912 includes a new switch parameter,
UseResourcePool, added to
StartPvsProvisionXdMachines in the
To provision machines at the resource pool level, use the
Start-ProvisionXdMachines with the
-UseResourcePool switch parameter.
Start-PvsProvisionXdMachines -DdcAddress <ddcAddress> -BootType <bootType> -CatalogName <catalogName> -CatalogDescription <catalogDescription> -SessionSupport <sessionSupport> -AllocationType <allocationType> -PersistUserChanges <persistUserChanges> -Scope <scope> -VdaLevel <vdaLevel> -XenDesktopHostResource <hostname> -HostResourcePassword <hostPassword> -TemplateName <templateName> -NetworkPath <networkPath> -StoreId <storeId> -SiteId <siteId> -DiskLocatorId <diskLocatorId> -Domain <domain> -OrganizationalUnit <organizationalUnit> -NamingScheme <namingScheme> -VmCount <vmCount> -DeviceMemory <deviceMemory> -DeviceCpu <deviceCPU> -DeviceWriteCacheSize <deviceWriteCacheSize> -NameSuffixType <nameSuffixType> -VmPvdSize <vmPvdSize> -VmPvdDrive <vmPvdDrive> -UseResourcePool
If the parameter
-UseResourcePoolis not included, the VDA is provisioned at the root cluster level.
Citrix Profile Management 1912
Citrix Workspace Environment Management 1912
Workspace Environment Management 1912 includes the following new features. For information about bug fixes, see Fixed issues.
Replacing Microsoft SQL Server Compact (SQL CE) with SQLite
The Workspace Environment Management (WEM) agent can work in offline mode. In earlier releases, the agent relied on Microsoft SQL Server Compact to synchronize with SQL Server to facilitate offline mode. Microsoft SQL Server Compact 3.5 Service Pack 2 is the last version that supports this functionality. Versions 4.0 and later do not support synchronization with SQL Server. However, SQL Server Compact 3.5 Service Pack 2 reached End of Life (EOL) in 2018. Starting with this release, the agent relies on SQLite for offline mode to work.
How this change impacts you
If you do not want to use Microsoft SQL Server Compact 3.5 Service Pack 2, upgrade the infrastructure services, the administration console, and the agent to the latest version. For information about upgrading these components, see Upgrade a deployment.
If you continue to use Microsoft SQL Server Compact 3.5 Service Pack 2, this replacement does not require action on your part.
Support for exporting and importing configuration sets
Starting with this release, WEM supports exporting and importing configuration sets using the administration console. To export configuration sets, use the Backup wizard, where the Configuration set option is available on the Select what to back up page. To import configuration sets, use the Restore wizard, where the Configuration setoption is available on the Select what to restore page. You can export and import only one configuration set at a time. For more information, see Ribbon.
Option to reset actions
Starting with this release, WEM supports resetting assigned actions (purging action-related registry entries in the user environment). The feature also provides the flexibility to reset assigned actions. You can reset all assigned actions by using the administration console or let users decide what to reset in their environment. The feature might be useful in scenarios where actions you assign to users or user groups do not take effect. For more information, see Advanced settings.
The administration console user interface has changed:
- The Advanced Settings > UI Agent Personalization > UI Agent Options tab introduces an “Allow Users to Reset Actions” option. Use that option to control whether to let current users specify what actions to reset in their environment.
Agent administrative templates
There are now two policies associated with the WEM agent cache synchronization:
- Cache synchronization port
- Cached data synchronization port
Starting with this release, the WEM agent relies on Cached data synchronization port to keep the agent cache in sync with the WEM infrastructure service. If you have Workspace Environment Management 1909 or earlier deployed in your environment, you cannot not use Cached data synchronization port. Instead, use Cache synchronization port. For more information, see Configure group policies.
This release simplifies the process of upgrading the WEM database. In earlier releases, to upgrade the database, you needed to remove the database from the availability group if the database was deployed in a SQL Server Always On availability group. Starting with this release, you can upgrade the database without removing it from the availability group.
Note that you still need to back up the database before you perform the upgrade. For more information about upgrading the database, see Upgrade a deployment.
Workspace Environment Management (WEM) PowerShell SDK modules
This release includes enhancements to the PowerShell modules in the WEM SDK. You can now use the PowerShell SDK to:
- Create, update, query, and delete configuration sets and user-level and machine-level AD objects
- Export and import configuration sets or user-level or machine-level AD objects
Citrix Session Recording 1912
This release includes the following new features and enhancements:
Session Recording web player
Previously available as an experimental feature, Session Recording web player is now fully supported. The web player adds support for Internet Explorer and load balancing scenarios, and provides a new event filter to search for custom events in recordings. For more information, see Session Recording web player.
Enhanced event logging
Session Recording can now log top-most window activities and tag the events in the recording. The process name, title, and process number are logged. Session Recording also enhances app monitoring. When you add a process to the App monitoring list, applications driven by the added process and its child processes are all monitored. For more information, see Log events and see Event logging policies.
Citrix Workspace App 1912 Tech preview for Windows
Note: This is an Early Access Build shared for the purpose of testing/validation with the intent to make organizations ready for the upcoming release and is NOT advised to be deployed in production environments. (GA Q1 2020)
Quality fixes and enhancements
• Enhancement to admin installation
In earlier versions, if an administrator tried to install the Workspace app in a system that has a user-installed instance of the app, the admin installation was blocked. With this release, the administrators can now override the user-installed instance of the Workspace app.
• Enhancement to Citrix Workspace Updates
In earlier versions, you could not update the Citrix Workspace app as a user if there is an admin-installed instance of the app. With this release, you can update the Citrix Workspace app on an admin-installed instance of the app by right-clicking the Workspace app icon in the notification area and selecting Check for Updates.
Note: Check for Updates is now available for both user-installed and admin-installed instances of the Workspace app.
• App protection
This release introduces enhanced security when using Citrix virtual Apps and Desktops. With the new app protection feature, Citrix Workspace app provides anti-keylogging and anti-screen-capturing capabilities in a session. The feature can help protect data from keyloggers and screen scrapers.
Note: This feature is supported only on Microsoft Windows Desktop operating systems such as Windows 10, Windows 8.1, and Windows 7.
Citrix Workspace App 1912.5 for iOS
What’s new in 1912.5
This release addresses issues that help to improve overall performance and stability.
Citrix Workspace App 1912 for Linux
Transparent User Interface Enhancement
Version 1910 introduced the transparent user interface (TUI) feature, including the VDTUI flag. The feature helps the client system to receive the TUI packets sent by the server, and the client can access the UI related components. However, with the flag set to Off, the “Starting <Application>” dialog box overlay would render on top of other application windows, covering the login prompt.
Starting with this release, the VDTUI flag, located in the module.ini file, is set to On by default. As a result, the “Starting <Application>” dialog box no longer appears when you attempt to launch a seamless app session. Instead, a “Connecting <Application>” dialog box appears with a progress bar. The dialog box also displays messages pertaining to the progress of the application launch.
GStreamer 1.x Support [Experimental]
In earlier releases, GStreamer 0.10 was the default version supported for multimedia redirection. Starting with this release, you can configure GStreamer 1.x as the default version.
- When you play a video, forward and backward seek might not work as expected.
- When you launch the Citrix Workspace app on ARMHF devices, GStreamer 1.x might not work as expected.
For more information, see Enabling GStreamer 1.x.
Chromium Embedded Framework (CEF) for Browser Content Redirection (BCR) [Experimental]
The BCR feature redirects contents of a web browser to a client device, and creates a corresponding browser that embeds within the Citrix Workspace app.
In earlier releases, BCR used a WebkitGTK+ based overlay to render the content. However, on thin clients, there were performance issues. Starting with this release, BCR uses a CEF based overlay. This functionality enriches the user experience for BCR. It helps offload network usage, page processing, and graphics rendering to the endpoint.
For more information, see Enabling CEF based BCR.
For information about BCR, see Browser content redirection in the Citrix Virtual Apps and Desktops documentation.
- The pacexec binary is removed from the x86 version of Citrix Workspace app.
- Citrix Files might not work with the “Workspace with Intelligence” feature.
Citrix Workspace App 1912.5 for Android
USB device redirection
Generic USB redirection allows redirection of USB devices from client devices into virtual desktop sessions. With this feature, end users can utilize a wide selection of generic USB devices in their Citrix Virtual Desktops sessions as if the USB devices were physically plugged into the clients.
Generic USB redirection works at a low level and redirects USB request and response messages between client machines and virtual desktops. The feature prevents the need for compatible device drivers on the client machine and the server’s ability to support them.
By default, this feature is set to Off.
This feature is available only on demand.
- Only one USB device is supported at a time.
- Audio and video USB devices are not currently supported.
Auto-launch of ICA file
In earlier releases, you had to manually launch the Workspace app session from the downloaded ICA file to start a session.
Starting with Version 1912.5, you can launch your published apps and desktops by clicking the resource. This feature requires StoreFront (on-premises) Version 1912 or later.
- This feature is supported only on Chromebook devices and only for HTTPS store URLs.
- When you select an app or desktop, do not select the Remember my choiceoption in the prompt.
Enhanced session launch
In earlier releases, published app and desktop sessions launched in the store enumeration window itself. To interact with the store enumeration window, you had to disconnect or sign off from the session.
Starting with Version 1912.5, published apps and desktops launch in a separate window. This helps you to use and interact with the store enumeration window without having to disconnect or sign off from the session.
- This feature is supported only on Chromebook devices.
- This feature is not supported on tablets, phones, and Samsung DeX.
- After changing any user settings, you must relaunch the session for the changes to take effect.
- Apps and desktop are named ‘Workspace’ in the taskbar – not after the session.
- Only one session can be used at a time.
Citrix Workspace App 1912 for Chrome
Support for Asset ID
Starting with this release, Citrix Workspace app for Chrome uses an Asset ID that administrators set through the Google Admin Console as a client name for sessions launched from enrolled Chromebooks.
By default, Citrix Workspace app continues to generate a unique client ID for enrolled Chromebooks, which is similar to earlier versions. To use this feature, you must set a policy for Citrix Workspace app. For more information, see Asset ID.
Citrix Workspace App 1912 for HTML5
This release addresses a number of issues that help to improve overall performance and stability.