About this release
This Citrix Virtual Apps and Desktops release includes new versions of the Windows Virtual Delivery Agents (VDAs) and new versions of several core components. You can:
Install or upgrade a site
Use the ISO for this release to install or upgrade core components and VDAs. Installing or upgrading to the latest version allows you to use all of the latest features.
Install or upgrade VDAs in an existing site
If you already have a deployment, and aren’t ready to upgrade your core components, you can still use several of the latest HDX features by installing (or upgrading to) a new VDA. Upgrading only the VDAs is often helpful when you want to test enhancements in a non-production environment.
After upgrading your VDAs to this version (from version 7.9 or later), you do not need to update the machine catalog’s functional level. The 7.9 (or later) value remains the default functional level, and is valid for this release. For more information, see VDA versions and functional levels.
- If you are building a new site, follow the sequence in Install and configure.
- If you are upgrading a site, see Upgrade a deployment.
Citrix Virtual Apps and Desktops 7 1909
Install and upgrade: VDAs no longer supported on x86 Windows 10 OSs
As of this release, installing or upgrading VDAs on Windows 10 is valid only on x64 OSs. Windows 10 x86 OSs are not supported.
If you want to upgrade an earlier VDA on an x86 Windows 10 machine (and your hardware supports x64), reimage the machine to an x64 OS and then install the latest VDA.
If you must continue using the x86 machine, use the 1906.2.0 VDA, which is available on the VDA download pages.
Install and upgrade: Delivery Controller hardware check
When you install or upgrade a Delivery Controller, the hardware is checked. The installer (or log) informs you if the machine has less than the recommended amount of RAM (5 GB), which could affect site stability. If you’re using the command-line interface, the installation ends.
- Recommended: Stop the installation. Add more RAM to the machine and then start the installation again.
- Alternatively, continue with the installation. The site might have stability issues.
- Recommended: Add more RAM to the server and then run the command again.
- Alternatively, run the command again with the
/ignore_hw_check_failureoption to override the warning. Your site might have stability issues.
For more information, see Hardware check.
Install and upgrade: Database scripts with preferred rights (PowerShell only)
In enterprise environments, database setup includes scripts that must be handled by different teams with different roles: securityadmin or db_owner. By default, one script contains all tasks, which require different rights.
Using PowerShell, you can now specify the preferred database rights. (This feature is not available in Studio, which supports only the default behavior.)
Specifying a nondefault value results in separate scripts being created. One script contains tasks that require the securityadmin role. The other script requires only db_owner rights, and can be run by a Citrix administrator without having to contact a database administrator.
For details, see Preferred database rights scripts.
Install and upgrade: Prompt for restart when installing core components from the full-product ISO
When installing or upgrading core components (Delivery Controller, Studio, License Server, Director, StoreFront) from the full-product ISO, if the Citrix installer detects that a restart is pending from a previous Windows installation on the machine, the installer stops with exit/return code 9. You are prompted to restart the machine.
This is not a Citrix forced restart. It is due to other components installed earlier on the machine. If this occurs, restart the machine and then launch the Citrix installer again.
Install and upgrade: New registry key to turn off automatic cleanup of App-V packages
A registry key has been added during installation to turn off the automatic cleanup of certain packages. The key is located at HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\AppV\Features. Cleanup is disabled by default and occurs only if you change the value of the key to true (“1”) and no publishing servers are registered with the machine.
Machine catalogs: Tags (PowerShell only)
You can now use PowerShell to apply tags to machine catalogs. For details, see Tags on machine catalogs.
Delivery Groups: Restart schedule maximum delay timer (PowerShell only)
If a scheduled restart of machines in a Delivery Group doesn’t begin because of a site database outage, you can specify how long to wait beyond the scheduled start time. If the database connection is restored during that interval, the restarts begin. If the connection isn’t restored during that interval, the restarts don’t begin.
For details, see Scheduled restarts delayed due to database outage.
Power manage machines in a Delivery Group: Enhanced power policy
In earlier releases, a VDI machine transitioning to a time period where an action (disconnect action=“Suspend” or “Shutdown”) was required remained powered on. This scenario occurred if the machine disconnected during a time period (peak or off-peak times) where no action (disconnect action=“Nothing”) was required.
Starting with this release, the machine is suspended or powered off when the specified disconnection time elapses, depending on the disconnect action configured for the destination time period. For details, see Power manage VDI machines transitioning to a different time period with disconnected sessions.
The health checks feature in Citrix Scout has been enhanced:
- You can now run health checks on Citrix License Servers and StoreFront servers.
- Configuration checks now run on Delivery Controllers.
For details, see Citrix Scout.
SDK: Installed as PowerShell module and snap-in
The Citrix Virtual Apps and Desktops SDK now installs as both a PowerShell snap-in and a PowerShell module.
With the addition of the module functionality, you can use this SDK’s cmdlets without a preceding
For associated components’ SDKs (such as Citrix Licensing, Citrix Provisioning, and StoreFront) that install only as a snap-in, using their cmdlets still requires a preceding
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.
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.
Virtual Delivery Agents (VDAs) 1909
Version 1909 of the VDA for Windows Server OS and the VDA for Windows Desktop OS includes the following enhancements (in addition to the VDA installation and upgrade items listed previously in this article):
Support for AMD hardware encoding
We now support AMD hardware encoding with VDAs for Desktop OS. For more information, see “AMD” in the Use hardware encoding for video section.
Enhanced session reliability logging capability
Several new session reliability event logging messages have been added in this release. The messages are in the Windows event logs. You can use these log messages to help diagnose network issues.
Bidirectional content redirection
You can now link different groups of URLs to different specified published applications instead of to only one published application. This enhancement requires Citrix Workspace app 1909 for Windows. For information about the client-side bidirectional content redirection configuration on the Citrix Workspace app, see Bidirectional content redirection in the Citrix Workspace app for Windows documentation. For information about the server-side configuration, see Bidirectional content redirection policy settings.
Citrix Licensing 11.16
Citrix Federated Authentication Service 1909
Citrix Federated Authentication Service (FAS) 1909 contains new features.
New product names
New product names and version numbers were introduced in Citrix Virtual Apps and Desktops 7 1808. This section provides that information for reference.
If you’ve been a Citrix customer or partner for a while, you’ll notice new names in our products and in this product documentation. If you are new to this Citrix product, you might see different names for a product or component.
The new product and component names stem from the expanding Citrix portfolio and cloud strategy. Articles in this product documentation use the following names.
- Citrix Virtual Apps and Desktops: Citrix Virtual Apps and Desktops offers a virtual app and desktop solution, provided as a cloud service and as an on-premises product, giving employees the freedom to work from anywhere on any device while cutting IT costs. Deliver Windows, Linux, web, and SaaS applications or full virtual desktops from any cloud: public, on premises or hybrid. Virtual Apps and Desktops was formerly XenApp and XenDesktop.
- Citrix Workspace app: The Citrix Workspace app incorporates existing Citrix Receiver technology as well as the other Citrix Workspace client technologies. It has been enhanced to deliver additional capabilities to provide end users with a unified, contextual experience where they can interact with all the work apps, files, and devices they need to do their best work. For more information, see this blog post.
- Citrix SD-WAN: NetScaler SD-WAN, a crucial technology for our customers and partners transforming their branch networks and WANs with cloud technology, is now Citrix SD-WAN.
- Citrix Secure Web Gateway: As the Citrix Networking portfolio expands, we’re proud to offer our robust Citrix Secure Web Gateway service, previously known as NetScaler Secure Web Gateway.
- Citrix Gateway: Our robust NetScaler Unified Gateway, which allows secure, contextual access to the apps and data you need to do your best work, is now Citrix Gateway.
- Citrix Content Collaboration and Citrix Files for Windows: The advanced access, collaboration, workflows, rights management, and integration features of ShareFile are now available in the Citrix Content Collaboration component set in our secure, contextual, integrated Citrix Workspace. Citrix Files for Windows allows you to access your Content Collaboration files directly through a mapped drive, providing a native Windows Explorer experience.
- Citrix Hypervisor: The technology from XenServer for virtualization infrastructure, based on the XenProject hypervisor, is now Citrix Hypervisor.
Here’s a quick recap:
|Citrix Virtual Apps and Desktops||XenApp and XenDesktop|
|Citrix Workspace app||Incorporates Citrix Receiver and extensive enhancements|
|Citrix SD-WAN||NetScaler SD-WAN|
|Citrix Secure Web Gateway||NetScaler Secure Web Gateway|
|Citrix Gateway||NetScaler Unified Gateway|
|Citrix Content Collaboration||ShareFile|
|Citrix Files for Windows||ShareFile Desktop App, ShareFile Sync, ShareFile Drive Mapper|
|Citrix Provisioning||Citrix Provisioning Services|
Implementing this transition in our products and their documentation is an ongoing process.
- In-product content might still contain former names. For example, you might see instances of earlier names in console text, messages, and directory/file names.
- It is possible that some items (such as commands and MSIs) might continue to retain their former names to prevent breaking existing customer scripts.
- Related product documentation and other resources (such as videos and blog posts) that are linked from this product’s documentation might still contain former names.
- For Citrix Hypervisor: The new name will be used on the Citrix website and in informational product materials from September 2018. You will also see the new name in the administrator consoles of some Citrix products, such as Citrix Virtual Apps and Desktops. The XenServer product release and technical documentation materials will continue to use XenServer 7.x until early 2019.
Your patience during this transition is appreciated. For more detail about our new names, see https://www.citrix.com/about/citrix-product-guide/.
New product and component version numbers
In this release, product and component version numbers are displayed in the format: 7 YYMM.c.m.b.
- YYMM = Year and month when the product or component is planned for release. For example, a release planned for the first quarter of 2019 appears as 1903. The actual release date may vary.
- c = Citrix Cloud release number for the month.
- m = Maintenance version (if applicable).
- b = Build number. This field is shown only on the About page of the product, and in the OS’s feature for removing or changing programs.
For example, Citrix Virtual Apps and Desktops 7 1809.1.0 indicates that the product released in September 2018, is associated with Citrix Cloud release 1 in that month, and is not a maintenance version. Some displays show only the version’s year and month: for example Citrix Virtual Apps and Desktops 7 1809.
In earlier releases of this product (XenApp and XenDesktop 7.18 and earlier), version numbers were displayed in the format: 7.version, where the version value incremented by one for each release. For example, the release following 7.17 was 7.18. Those earlier releases will not be updated with the new numbering format.