Citrix Virtual Apps and Desktops (CVAD) Upgrades

Last Modified: Sep 12, 2022 @ 9:26 am

Navigation

Change Log

Citrix Virtual Apps and Desktops (CVAD) Versions

Version Numbering

Citrix Virtual Apps and Desktops (CVAD) is the new name for XenApp and XenDesktop.

The most recent version of Citrix Virtual Apps and Desktops (CVAD) 7 is 2206. The version number is based on YYMM (Year Month) format. References to 7.x versions in this article include the YYMM versions.

XenApp and XenDesktop 7.x versions range from 7.0 through 7.18. 7.18 is the last version of XenApp and XenDesktop. Citrix Virtual Apps and Desktops (CVAD) 2206, 2203, 1912, and 1808 are newer than XenApp and XenDesktop 7.18.

Release Notifications

Follow my Twitter or EUC Weekly Digests for new release notifications.

Sometimes release notifications are posted to Citrix Blogs, but this is not comprehensive.

Watch Citrix Discussions and Citrix Support Knowledgebase to learn about known issues that are fixed in a later release.

Release Classifications – LTSR, CR

Image from Citrix Blog Post What’s New in XenApp, XenDesktop and XenServer November 2017.

There are three classifications for on-premises releases:

  • LTSR (Long Term Service Release) – these releases get 5 years of mainstream support from the release date, plus up to 5 more years of paid extended support
  • CR (Current Release) – 6 months support from the release date. Updated quarterly.
  • LTSR Compatible Components – non-LTSR components running in a LTSR implementation. This classification provides exceptions to the requirement that all components must be LTSR versions.

Citrix Virtual Apps and Desktops (CVAD) is a bundle of components. Long Term Support requires the components to be specific versions. Any deviation from the required versions results in loss of Long Term Support, and instead is classified and supported as a Current Release. Use Citrix LTSR Assistant tool to confirm LTSR compliance.

LTSR Programs

There are three different LTSR programs:

LTSR Licensing requirement

LTSR requires you to be on Customer Success Services Select, formerly known as Software Maintenance.

LTSR vs CR

Support Duration

LTSR is supported for 5 years from the LTSR release date, plus 5 more years of optional, paid extended support.

  • LTSR Cumulative Updates (similar to service packs) are released periodically. Cumulative Updates for LTSR are installed exactly like upgrading to a newer Current Release, except you don’t get any new features.
    • Cumulative Updates are released only for LTSR versions. To patch a Current Release, upgrade to the newest Current Release.
  • Be prepared to install these LTSR Cumulative Updates every 6 months. Workspace app LTSR (or Receiver LTSR) too.

Current Releases are end-of-maintenance after 6 months, and end-of-life after 18 months.

  • Be prepared to upgrade to a newer Current Release every 6 months. Workspace app too.

See Lifecycle Milestones for Citrix Virtual Apps & Citrix Virtual Apps and Desktops for an explanation of support durations for each release classification.

In either case, you are expected to perform some sort of upgrade or update approximately twice per year.

Release Frequency

New LTSR versions are released every 18-24 months.

There are three supported LTSR releases: LTSR 2203, LTSR 1912, and LTSR 7.15.

Cumulative Updates (CU) for LTSR are released every few months. Don’t forget to install these patches. I’ve seen CUs fix LTSR issues.

  • Cumulative Updates do not include new features.
  • Citrix has released one Cumulative Updates for LTSR 2203, bumping up the version to 2203.1000.
  • Citrix has released four Cumulative Updates for LTSR 1912, bumping up the version to 1912.5000.
  • Citrix has released nine Cumulative Updates for LTSR 7.15, bumping up the version to 7.15.9000.
  • Citrix will continue to release Cumulative Updates for all currently supported LTSR versions.

You can upgrade directly to the latest Cumulative Update. It is not necessary to upgrade to the base version before upgrading to the latest Cumulative Update.

New Current Release versions are released every quarter. Sometimes longer for Workspace app.

Some Citrix Virtual Apps and Desktops (CVAD) components are released on a separate schedule from the main LTSR or Current Release releases:

  • App Layering
  • Workspace Environment Management

Citrix Provisioning version numbers don’t line up with Citrix Virtual Apps and Desktops (CVAD) LTSR Cumulative Update version numbers:

  • Citrix Virtual Apps and Desktops (CVAD) 2203 LTSR CU1 comes with Citrix Provisioning 2203 CU1
  • Citrix Virtual Apps and Desktops (CVAD) 1912 LTSR CU5 comes with Provisioning Services 1912 CU5
  • XenApp/XenDesktop 7.15.9000 (LTSR 7.15 CU9) comes with Provisioning Services 7.15.39

Current Release cons

New Current Releases add new features, and new bugs. For example:

  • The initial release of Citrix Virtual Apps and Desktops (CVAD) Current Release 1906 had some upgrade issues and disconnect issues which required it to be pulled and re-released.
  • The initial release of Citrix Virtual Apps and Desktops (CVAD) Current Release 1808 had some upgrade issues which required it to be pulled and re-released.
  • The initial release of XA/XD Current Release 7.14 had some issues which required it to be pulled and re-released.
  • Current Release 7.13 had issues (e.g., VDA registration error message), that weren’t fixed until 7.14.
  • Receiver 4.10 has some issues with drop-down boxes that requires a newer version of Workspace app to fix.

No hotfixes will be released for Current Releases. To get hotfixes, upgrade to the newest Current Release.

LTSR cons

Features not in LTSR – Some features are not included in the LTSR program. In other words, these features don’t get 5 years of support, and might not even be included in the LTSR installer.

  • Personal vDisk and AppDisks – these are replaced by User Personalization Layers.
  • Framehawk

Features in Current Release but not LTSR:

  • Upcoming CVAD Current Release Version 2209 will have new features that are not in 2203 LTSR. Will you upgrade to CVAD 2209, which puts you on the Current Release upgrade train? Or will you wait until the next LTSR, probably released sometime in 2024?
    • Another option is to remain on 2203 LTSR (with latest cumulative update) until you see a Current Release with new features that are desirable enough to upgrade to. You can then upgrade directly from 2203 LTSR to the latest Current Release (e.g., 2212). There’s no need to upgrade to intermediary versions.

Don’t mix Current Release and LTSR components – As soon as you upgrade one LTSR component to Current Release, upgrade all other LTSR components to Current Release and keep them updated with new Current Releases every 6 months.

  • When the next LTSR is released, you can stop upgrading (except for Cumulative Updates).
  • Or deploy Current Release in a separate environment.
  • Use Citrix LTSR Assistant tool to confirm LTSR compliance.
  • Some app vendors require you to remain on LTSR.

LTSR “compatible” components require frequent upgrades – Some components, like App Layering, are LTSR “compatible”, meaning there’s no LTSR version, but it’s OK to use them in an LTSR environment. Since they’re Current Release and not LTSR, you’re expected to update the Current Release components to the latest release every 6 months.

  • There’s no LTSR version of Citrix Licensing. Instead, always upgrade Citrix Licensing to the latest Current Release version.
  • There’s no LTSR version of App Layering. Instead, always upgrade App Layering to the latest Current Release version.
  • There’s no LTSR version of Citrix Workspace Environment Management. Instead, always upgrade Citrix Workspace Environment Management (WEM) to the latest Current Release version.

Windows 11 is supported in CVAD 2109 and newer. Windows 11 is not supported in CVAD 1912 LTSR.

Windows 7 and Windows Server 2008 R2 support: 7.16 VDA and newer, including 1912 LTSR VDA, are not supported on Windows 7 or Windows Server 2008 R2. For these operating system versions, install 7.15 LTSR VDA. The 7.15 LTSR VDA can register with newer Delivery Controllers. However, the 7.15 LTSR VDAs cannot take advantage of the newer features in the newer releases.

Citrix Virtual Apps and Desktops (CVAD) Supported versions

The most recent release of Citrix Virtual Apps and Desktops (CVAD) is version 2206.

There are three supported LTSR versions of Citrix Virtual Apps and Desktops (CVAD): LTSR 2203, LTSR 1912, and LTSR 7.15.

  • Cumulative Update 1 has been released for LTSR 2203, resulting in version number 2203.1000.
  • Cumulative Update 5 has been released for LTSR 1912, resulting in version number 1912.5000.
  • Cumulative Update 9 has been released for LTSR 7.15, resulting in version number 7.15.9000.

You can directly install the latest Cumulative Update of any LTSR version. It is not necessary to install the base version of the LTSR version before you upgrade to the latest Cumulative Update.

Examples of non-supported versions:

  • Citrix Virtual Apps and Desktops (CVAD) 1909 is not LTSR, and is more than six months past release date, so Citrix will not provide any code fixes. Once 18 months have elapsed, Citrix will not support it at all.

Workspace app Supported Versions

Starting in August 2018, Receiver have been renamed to Workspace app. Also, versioning has changed from 4.x to a YYMM (year month) format.

The most recent release of Workspace app is version Workspace app 2209, which is a Current Release.

The LTSR version of Workspace app is version 2203.1 LTSR.

  • Browser Content Redirection does not work in LTSR Workspace app because Embedded browser is removed due to infrequent updates of LTSR versus frequent updates of the embedded browser.

Citrix Virtual Apps and Desktops (CVAD) Component Version Dependencies

Citrix Virtual Apps and Desktops (CVAD) is a collection of installable components:

  • Citrix Licensing Server
  • Delivery Controller
  • Citrix Studio
  • Virtual Delivery Agent
  • Director
  • StoreFront
  • Federated Authentication Service
  • App Layering
  • Citrix Provisioning
  • Citrix Group Policy Management Plug-in
  • Profile Management
  • Workspace Environment Management
  • Session Recording
  • Workspace app for Windows, Linux, Mac, iOS, and Android
  • Workspace app for HTML5
  • Skype for Business HDX RealTime Optimization Pack
  • Citrix ADC (aka NetScaler) Load Balancing
  • Citrix Gateway

Component behaviors:

  • Each component can be installed separately.
  • Some components can be combined onto the same machine.
  • Some components are completely standalone with no dependency on other components.
  • Some components communicate with other components, and thus are dependent on those other components.

The fewest components that make up a Citrix Virtual Apps and Desktops (CVAD) site/farm are License Server + Delivery Controller + Studio + VDA + SQL Databases.

  • A farm/site is a collection of Delivery Controllers that share the same SQL databases.
  • The official term is Citrix Virtual Apps and Desktops (CVAD) Site. However, since the word “site” has multiple meanings, this article instead refers to a Citrix Virtual Apps and Desktops (CVAD) Site as a Farm, which is the same terminology used in XenApp 6.5 and older.

Some of the components can be used with multiple sites/farms.

  • Citrix Licensing Server can be used by multiple sites/farms.
  • StoreFront can pull icons from multiple sites/farms, including XenApp 6.5. This enables multi-farm capabilities for the following components that are dependent on StoreFront:
    • Federated Authentication Service can be used by multiple StoreFront servers.
    • Workspace app for Windows, Linux, Mac, iOS, and Android can connect to multiple StoreFront stores, which can be on different StoreFront servers.
    • Each StoreFront server has its own Receiver or Workspace app for HTML5
    • Citrix Gateway connects to one StoreFront server
  • Citrix Studio can connect to multiple sites/farms.
  • Virtual Delivery Agent can register with only one site/farm at a time, but the farm registration can be easily changed by modifying the ListOfDDCs registry key.
  • Director can display monitoring data from multiple sites/farms.
  • App Layering has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
  • Citrix Provisioning has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
  • Citrix Group Policy Management Plug-in can be used to create Citrix Policies that can apply to multiple sites/farms.
  • Profile Management has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them. The profiles are usually tied to a VDA operating system version.
  • Workspace Environment Management has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
  • Session Recording has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
  • Skype for Business HDX RealTime Optimization Pack has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them. This component only cares about the RealTime Connector that is installed on the VDA.

The Citrix components that don’t have any relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms can be used with XenApp 6.5 too.

Some components communicate with other components, and thus are dependent on the versions of those other components.

  • Citrix Licensing Server should always be the newest version. Citrix Virtual Apps and Desktops (CVAD) Components will verify the Licensing Server version.
  • StoreFront can usually work with any Delivery Controller version, including XenApp 6.5.
  • Citrix Studio should be the same version as the Delivery Controllers it is managing.
  • Virtual Delivery Agents can be any version, including older or newer than the Delivery Controllers.
  • Director uses the Citrix Monitoring Service that is installed on the Delivery Controllers.
  • Workspace Environment Management (WEM) – newer WEM can configure newer Profile Management features. Otherwise, WEM is independent from Citrix Virtual Apps and Desktops (CVAD).
  • Workspace app – Many newer Citrix Virtual Apps and Desktops (CVAD) features require a specific version of Workspace app.
    • The newest Workspace app along with the newest VDA supports the latest Teams optimization (offload) features. LTSR versions of these components might not support the latest Teams optimization features.
    • If you are deploying Current Releases, then deploy the newest Current Release Workspace app.
    • If you are deploying LTSR, then deploy the latest LTSR Workspace app or LTSR Receiver.
      • If you need Browser Content Redirection, then deploy the latest Current Release Workspace app since LTSR Workspace app does not support Browser Content Redirection.
  • Citrix Gateway – Some Newer Citrix features require newer Citrix ADC firmware. For example:
    • EDT (Enlightened Data Transport) / Adaptive Transport
    • Gateway Configuration export/import with StoreFront
  • Citrix ADC builds have bug fixes that affect the Citrix Virtual Apps and Desktops (CVAD) experience.

7.x Upgrade Overview

7.x Components

Citrix Virtual Apps and Desktops (CVAD) 7 is composed of multiple Components, each of which is upgraded separately.

Newer versions of Citrix components enable Customer Experience Improvement Program (CEIP) automatically. If you wish to disable CEIP, see https://www.carlstalhood.com/delivery-controller-cr-and-licensing/#ceip.

Component Upgrade Process

In-place upgrades – 7.x components can be upgraded in-place. No need to rebuild like you did in XenApp 6.5 and older.

  • For LTSR releases, you can upgrade directly to the latest Cumulative Update. It is not necessary to install the base LTSR version first.
  • For Current Releases, you can upgrade directly to the latest Current Release.

Here’s the general, in-place upgrade process for each component. Detailed instructions for each component are detailed later.

  1. In-place upgrade one (or half) of the component’s servers.
  2. Upgrade the component’s database. Requires temporary sysadmin permission on SQL Server. Not all components have databases.
  3. In-place upgrade the remaining component’s servers.
  4. In-place upgrade the agents.
    1. Rebuilding of master images might be preferred, assuming you have time to automate it.

Mix and match VDA/Controller versions – You can upgrade VDAs without upgrading Delivery Controllers. Or vice versa.

  • Newer VDA features sometimes require Citrix Policy to enable or configure. The newest Citrix Policy settings are included in Delivery Controller / Citrix Studio upgrades. Or, if you haven’t upgraded your Delivery Controllers yet, you can simply upgrade the Citrix Group Policy Management component.

VDA Operating System version Upgrade – Considerations when upgrading the VDA operating system version:

  • Operating System Version – VDA 7.16 and newer no longer support Windows Server 2008 R2, Windows 7, or Windows 8/8.1. If you need these older operating system versions, then install VDA 7.15 instead. VDA 7.15 can register with 1912 Delivery Controllers.
    • Windows 11 – VDA 1912 LTSR does not support Windows 11, but CVAD 2109 and newer do support Windows 11
  • App compatibility – Verify app compatibility with the new OS version. For compatibility with a Server OS version, check compatibility with the equivalent Desktop OS version.
    • Windows Server 2012 R2 = 64-bit Windows 8.1
    • Windows Server 2016 = 64-bit Windows 10 1607
    • Windows Server 2019 = 64-bit Windows 10 1809
    • Windows Server 2022 = 64-bit Windows 10 21H2
  • Start Menu in published desktop – If you publish desktops, is the Windows 2012 R2 Start Menu acceptable to the users? Windows 2012 R2 Start Menu is the same as Windows 8.1 Start Menu.
    • Windows Server 2016 Start Menu is the same as Windows 10 1607 Start Menu.
    • Windows Server 2019 Start Menu is the same as Windows 10 1809 Start Menu.
    • Windows Server 2022 Start Menu is the same as Windows 10 21H2 Start Menu.
  • GPO settings– Newer OSs have newer Microsoft GPO settings.
  • Profile version – Newer OS means newer profile version. Older profile versions do not work on newer operating system versions. For example, you can’t use Windows 7 profiles on Windows 10. This means that an OS upgrade results in new profiles for every user.
    • Write a script to copy profile settings from the old profiles to the new profiles.
  • Remote Desktop Services (RDS) Licensing – if you are building RDSH (Server OS) VDAs, then every user that connects must have an RDS License for the RDSH operating system version. If RDSH is Windows 2016, then every user needs a Windows 2016 RDS License. Windows 2008 R2 RDS Licenses won’t work.
    • RDS Licensing Server – RDS Licensing Server is a built-in Windows Server Role. It must be installed on servers with the same or newer operating system version than the RDSH VDAs.
  • Windows 10 Branches – Windows 10 Semi-Annual Channel Targeted (aka Current Branch) is only partially supported. Semi-Annual Channel Broad (aka Current Branch for Business), and LTSB are fully supported. See CTX224843.
  • Upgrade Windows 10 Version – In-place upgrade of Windows 10 versions is not recommended. For example, upgrading from Windows 10 1511 to Windows 10 1607 broke several features. Rebuild is cleaner.
    • App Layering – However, due to dependencies between App Layers and OS Layer, you might have to in-place upgrade your OS Layer.
  • Citrix Virtual Apps and Desktops (CVAD)Component Agents – ensure the Citrix component agents (WEM Agent, Profile Management, Session Recording Agent, App Layering Tools, etc.) are supported on the new OS version.

Considerations for upgrading the operating system version on component servers:

  • Do not in-place upgrade the operating system version. Instead, build new VMs, and join them to the existing infrastructure.
  • New OS version requires newer component versions. The required component version might be newer than what you’re currently running.
  • When adding a server to the existing component farm/site, the new server must be running the same component version as the existing servers. That means you might have to in-place upgrade your existing component servers before you can add new component servers running a newer operating system version.
  • For example:
    • Existing Delivery Controllers are version 7.9 on Windows 2012 R2.
    • You desire to migrate to new Windows 2016 Delivery Controllers.
    • Only Delivery Controller 7.11 and newer can be installed on Windows 2016. But you can’t add Delivery Controller 7.11 to a Delivery Controller 7.9 farm/site.
    • Upgrade the existing Delivery Controllers to 7.11 or newer first.
    • Then you can add the new Windows 2016 Delivery Controllers VMs to the existing farm/site.

Here are general instructions to upgrade component server OS version. Detailed instructions for each component are detailed later.

  1. In-place upgrade the existing component servers to a version that supports the new OS. Check the System Requirements documentation for each component to verify OS version compatibility.
  2. Build new machine(s) with desired OS version.
  3. On the new machines, install the same component version as the existing component servers.
    • The new machines must be the same component version as the existing machines. You can’t add machines with newer component versions.
  4. Add the new component servers to the existing farm/site/server group.
  5. Migrate load balancer, VDAs, Targets, etc. from old to new. See below for detailed instructions for each component.
  6. Decommission old servers.

Upgrade Guidelines

Test farms – Test Citrix infrastructure upgrades in separate test environments (separate test farms):

  • Due to forwards and backwards compatibility, VDA upgrades can usually be tested in production.
  • Everything else requires global server-side upgrades first, so you can’t test them in production.
  • Upgrade procedures for High Availability components (e.g. multiple Delivery Controllers) are different than upgrade procedures for singe, standalone components. The Test environment should look like production, which means HA too.
  • The separate Test environments should include multi-datacenter capabilities (StoreFront icon aggregation, GSLB, etc.) so those multi-datacenter features can be tested.

Known upgrade issues – Read Citrix Discussions, or ask your Citrix Support TRM, for known upgrade issues. Don’t upgrade production immediately after a new version is released.

  • Read the release notes, especially the known issues.

Smart Check the environment before upgrading. It’s free. Access it at https://smart.cloud.com.

Backup/snapshot – Backup databases, snapshot machines, etc. before starting the in-place upgrade.

  • Have a rollback plan, including the databases.

Citrix Licensing Server – Always upgrade the Citrix Licensing Server before upgrading anything else.

  • Check Subscription Advantage (SA) date on the installed licenses. Some components require SA expiration date to be later than the component’s release date.

In-place upgrade preparation:

  1. Make sure other admins are logged off before starting the upgrades.
  2. Close all consoles and PowerShell.
  3. Snapshot the machines.

Upgrade Citrix Virtual Apps and Desktops (CVAD) 7.x

All 7.x components can be upgraded in-place.

  • Current Release upgrades are cumulative. You can skip intermediary versions.
  • LTSR Cumulative Updates are also cumulative, hence the name.
  • LTSR Cumulative Updates are performed using the same process as Current Release upgrades. The only difference is that you don’t get new features with LTSR updates.

Some components (Delivery Controllers, Citrix Provisioning, Session Recording, WEM, etc.) require the person doing the upgrade to have temporary sysadmin permissions on the SQL server so the database can be upgraded.

Upgrade order – For the most part, upgrade order doesn’t matter. That’s because there are few dependencies between each component, as detailed earlier.

  • Before upgrading anything else, upgrade the Citrix Licensing Server.
    • Install updated license files with non-expired Subscription Advantage dates.
  • VDAs and Delivery Controllers can be different versions.
    • VDAs can be upgraded before Controllers, or vice/versa.
  • If Zones, upgrade all Delivery Controllers in all zones at the same time.
  • For Director, upgrading Director won’t do you much good if the Controllers aren’t upgraded, since Director uses the Monitoring service that’s installed on the Controllers.
    • Director 7.16 and newer will warn you if your Delivery Controllers are not the same version as Director.
  • For Citrix Provisioning, the Citrix Provisioning servers must be upgraded before you upgrade the Target Device Software.
  • For Session Recording, the Session Recording server(s) must be upgraded before you upgrade the Session Recording agent.
  • For WEM, the WEM server(s) must be upgraded before you upgrade the WEM agent.

If you upgrade to a version that has CEIP functionality, decide if you want to disable CEIP, or leave it enabled.

After upgrading, configure new functionality.

Additional general upgrade guidance can be found at Upgrade a deployment at Citrix Docs.

Citrix Licensing Server

It’s a simple in-place upgrade.

  • After upgrading, download the latest license files from http://mycitrix.com, and install the license files on the license server. Make sure the Subscription Advantage date hasn’t expired.

To upgrade the Licensing Server Operating System version:

  1. Build a new VM with desired OS version.
  2. Install the latest Current Release License Server.
  3. At http://mycitrix.com, reallocate licenses to the new case-sensitive hostname, and install the license file on the new Licensing Server.
  4. For 7.x sites/farms, in Citrix Studio, go to Configuration > Licensing, and change the License Server to the new Licensing Server.
  5. For XenApp 6.5, in AppCenter > Policies, or a GPO with Citrix Policies, find the Citrix Policy that defines the Licensing Server name, and change it.
    1. Or, run the XenApp Server Role Manager on each server and change Licensing configuration.

Delivery Controllers

Both of the following types of upgrades/updates use the same upgrade process:

  • Install latest LTSR Cumulative Update
  • Upgrade to latest Current Release

To in-place upgrade Delivery Controllers:

  1. If High Availability is configured correctly, then Delivery Controllers can be upgraded during the day.
  2. Upgrade the Citrix Licensing Server if you haven’t already. Install current licenses if you haven’t already.
  3. Ask a DBA for temporary sysadmin permission to the SQL server.
  4. Prepare: run Smart Check, logoff other admins, close consoles.
  5. If upgrading from 7.15 to 2203, then 7.15 must be Cumulative Update 5 or newer.
  6. In-place upgrade one (or half) of the Delivery Controllers. Upgrade to one of the following:
    1. Delivery Controller 2206
    2. Delivery Controller LTSR 2203 CU1
    3. Delivery Controller LTSR 1912 CU5
    4. Delivery Controller LTSR 7.15.9000 Cumulative Update 9
  7. Launch Studio. Upgrade the database when prompted.
  8. In-place upgrade the remaining Delivery Controllers.
  9. Run Smart Check again.
  10. Temporary sysadmin permissions can now be removed.
  11. For Citrix Studio that’s installed on administrator machines other than Delivery Controllers, in-place upgrade Studio by running AutoSelect.exe from the Current Release or LTSR CVAD ISO.

To upgrade the operating system version of the Delivery Controllers:

  1. In-place upgrade the existing Delivery Controllers to a version that supports the new operating system version.
    1. For Windows Server 2016, upgrade Delivery Controller to version 7.15 or newer.
    2. For Windows Server 2019, upgrade Delivery Controller to version 1912 or newer
      • CVAD 1912 does not support Windows 2008 R2 Controllers so you might have to upgrade to Windows Server 2016 first.
    3. For Windows Server 2022, upgrade Delivery Controller to version 2203 or newer.
      • CVAD 1912 does not support Windows Server 2022.
  2. Build one or more new virtual machines with the new operating system version.
  3. Install Delivery Controller software with the same version as the other Delivery Controllers.
  4. Run Citrix Studio and join the new machines to the existing farm/site.
  5. Reconfigure VDAs to point to the new Delivery Controllers. Edit the ListOfDDCs registry key.
  6. Reconfigure Director server > IIS Admin > Default Web Site > Director > Application Settings > Service.AutoDiscoveryAddresses to point to the new Delivery Controllers.
  7. Reconfigure StoreFront console > MyStore > Manage Delivery Controllers to point to the new Delivery Controllers.
  8. Secure Ticket Authorities:
    1. Add the new Delivery Controllers to firewall rules between Citrix ADC SNIP and STAs.
    2. In Citrix Gateway > Edit Virtual Server > scroll down to the Published Applications section > click the line to edit the Secure Ticket Authorities. Add the new Delivery Controllers as Secure Ticket Authorities. Don’t remove the old ones yet.
    3. In StoreFront Console, go to Manage Citrix Gateways > edit each Gateway > on the Secure Ticket Authority page, add the new Delivery Controllers as Secure Ticket Authorities, and remove the old ones.
    4. In Citrix Gateway > Edit Virtual Server > scroll down to the Published Applications section > click the line to edit the Secure Ticket Authorities. Remove the older Controllers as Secure Ticket Authorities.
  9. In Citrix Studio, at Configuration > Controllers, remove the old Delivery Controllers.
    1. Note: if this doesn’t work, then you might have to manually evict the old Delivery Controllers from the SQL database.
  10. Decommission the old Delivery Controllers.

An alternate method of upgrading the operating system on the Delivery Controllers while preserving the machine’s identity:

  1. The new server will have the same Citrix version as already installed. You might have to in-place upgrade Citrix to get to a version that supports the new operating system version. For example, CVAD 1912 can run on Windows Server 2019 but it cannot run on Windows Server 2022.
  2. Export any certificates that you want to keep and put them on a different machine.
  3. Record the IP Address and hostname of the machine you want to replace.
  4. Record the database connection strings. PowerShell Get-BrokerDBConnection shows the main database connection. Get the Logging and Monitoring database names from Citrix Studio > Configuration.
  5. Shut down a Delivery Controller and never power it on again. Don’t remove this machine from the domain to avoid accidentally deleting the Active Directory computer object.
  6. Build a new machine with an operating system version supported by the Citrix version running on the other Delivery Controllers. Give it the same name and IP address. Join it to the domain using the existing Active Directory computer object.
  7. Install the same version of Delivery Controller as was running previously. Don’t run Citrix Studio.
  8. Use the PowerShell commands at https://www.carlstalhood.com/delivery-controller-cr-and-licensing/#changedbstrings to connect the new machine to the SQL database.
  9. Run Citrix Studio. It might ask you to upgrade the database but it’s merely finishing the database connection and not actually upgrading anything.

App Layering

To in-place upgrade Citrix App Layering:

  • In-place upgrade the ELM appliance.
    • From 4.2 and newer, newer versions should be downloaded automatically. Just click the link to start the upgrade.
    • From 4.1 and older, download the upgrade package and upload it to the ELM.
  • Upgrade the App Layering Citrix Provisioning Agent by uninstalling the Citrix Provisioning Agent and re-installing it.
  • Create a new OS Layer version and install the latest OS Machine Tools.
  • When the images are published, the drivers will be updated automatically by the ELM.

Workspace Environment Management (WEM)

There is no LTSR version of Citrix Workspace Environment Management (WEM) so you should always deploy the latest version of WEM.

To in-place upgrade Citrix Workspace Environment Management (WEM):

  1. In-place upgrade the Citrix Licensing Server if you haven’t already.
    1. Ensure the installed licenses have a non-expired Subscription Advantage date.
  2. Ask a DBA for temporary sysadmin permission to the SQL server.
  3. In-place upgrade the first WEM Server. Consider removing it from load balancing before performing the upgrade.
  4. Use the Database Maintenance tool to upgrade the WEM database.
  5. Run the WEM Broker Configuration Tool on the upgraded Broker to point to the upgraded database.
  6. In-place upgrade the remaining WEM Servers. Consider removing them from load balancing before performing the upgrade.
  7. Temporary sysadmin permissions can now be removed.
  8. In-place upgrade the WEM Console on all non-server machines where it is installed.
  9. In-place upgrade the WEM Agents.
  10. If you are upgrading from WEM 4.2 and older, in the WEM Console, add the WEM Agents (computer accounts) to Configuration Sets instead of the old WEM Sites.

To upgrade the operating system version of the Workspace Environment Management servers, it’s easier if you have a custom DNS name, or load balanced DNS name for WEM, instead of using a server name :

  1. In-place upgrade the existing WEM servers to a version that supports the OS you intend for the new WEM servers.
  2. Build new WEM servers with the same version as the existing WEM servers.
  3. Configure the new WEM servers to point to the same database as the old WEM servers.
  4. Cutover options:
    1. If you have a load balanced DNS name for WEM, reconfigure the load balancer to point to the new WEM servers.
    2. If you have a custom DNS name for WEM, change it to resolve to the new WEM server’s IP address.
    3. If you were previously using the actual server name, then you can either change the WEM Agent group policy to point to the new WEM server name, or delete the old WEM server and rename the new WEM server, or delete the old WEM server and reconfigure the old DNS name as a custom DNS name for the new WEM server.
  5. Decommission the old WEM servers.

Session Recording

To in-place upgrade Session Recording:

  1. In-place upgrade the Citrix Licensing Server if you haven’t already.
    • Ensure the installed licenses have a non-expired Subscription Advantage date.
  2. Ask a DBA for temporary sysadmin permission to the SQL server.
  3. In-place upgrade the first Session Recording server to one of the following.
    1. Session Recording 7.14 and newer are on the main Citrix Virtual Apps and Desktops (CVAD) ISO.
    2. Only Session Recording 7.16 and newer fully support load balancing. Consider removing the Session Recording server from load balancing before performing the upgrade.
    3. Session Recording 2206
    4. Session Recording LTSR 2203 CU1
    5. Session Recording LTSR 1912 CU5
    6. Session Recording LTSR 7.15 Cumulative Update 7
  4. The upgrade of the first Session Recording server should automatically upgrade the database.
  5. In-place upgrade the remaining Session Recording Servers. Consider removing them from load balancing before performing the upgrade.
  6. Temporary sysadmin permissions can now be removed.
  7. In-place upgrade the Session Recording Agents.
  8. In-place upgrade the Session Recording Player on all machines where it is installed.

To upgrade the operating system version of the Session Recording servers, it’s easier if you have a custom DNS name or load balanced DNS name for Session Recording, instead of using a server name:

  1. In-place upgrade the existing Session Recording servers to a version that supports the OS you intend for the new Session Recording servers. Windows 2016 support was added to Session Recording 7.11 and newer.
  2. Build new Session Recording servers with the same version as the existing Session Recording servers.
  3. Configure the new Session Recording servers to point to the same database as the old Session Recording servers.
  4. Configure the new Session Recording servers to store recordings on the same UNC path as the old Session Recording servers.
  5. The certificate on the Session Recording servers or load balancer must match the DNS name used by the Session Recording Agents and Player.
  6. Cutover:
    1. If you have a load balanced DNS name for Session Recording, reconfigure the load balancer to point to the new Session Recording servers.
    2. If you have a custom DNS name for Session Recording, change it to resolve to the new Session Recording server’s IP address.
    3. If you were previously using the actual server name, then you can either: change the Session Recording Agents and Players to point to the new Session Recording server name, or delete the old Session Recording server and rename the new Session Recording server, or delete the old Session Recording server and reconfigure the old DNS name as a custom DNS name for the new Session Recording server.
    4. If the Session Recording DNS name changed, reconfigure Director to point to the new Session Recording DNS name.
  7. Decommission the old Session Recording servers.

Citrix Provisioning

Citrix Provisioning servers must be upgraded before you can upgrade Target Devices.

To in-place upgrade Citrix Provisioning servers:

  1. Make sure Citrix Provisioning High Availability (HA) is working for target devices. If HA is functional, in-place upgrade can be done during the day.
    • In the Citrix Provisioning console, you should see an even distribution of Target Devices across all Citrix Provisioning servers.
    • Check the WriteCache folders on Citrix Provisioning servers to make sure they’re empty. If any Target Device is caching on Server, then those Target Devices will not failover to another Citrix Provisioning server.
  2. Get temporary sysadmin permissions to the SQL Server that hosts the Citrix Provisioning database.
  3. Get the one of the following installation media:
    1. Citrix Provisioning 2206
    2. Citrix Provisioning LTSR 2203 CU1
    3. Citrix Provisioning LTSR 1912 CU5
    4. Citrix Provisioning LTSR 7.15.39 from LTSR 7.15 Cumulative Update 8
  4. On the first Citrix Provisioning Server:
    1. In-place upgrade Citrix Provisioning Console by running the 2206, LTSR 2203 CU1, LTSR 1912 CU5, or LTSR 7.15.39 Citrix Provisioning Console installer.
    2. Re-register the Citrix.PVS.snapin.dll snap-in:
      "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe" "c:\program files\citrix\provisioning services console\Citrix.PVS.snapin.dll"
    3. In-place upgrade Citrix Provisioning Server by running the 2206, LTSR 2203 CU1, LTSR 1912 CU5, or LTSR 7.15.39 Citrix Provisioning Server installer
    4. Run the Citrix Provisioning Configuration Wizard. The farm should already be configured, so just click Next a few times and let it upgrade the database and restart the services.
  5. In-place upgrade the Console and Server software on the remaining Citrix Provisioning Servers. After installation, run the Citrix Provisioning Configuration Wizard, and click Next until the end.
  6. Temporary sysadmin permissions can now be removed.
  7. Target Device Software can now be upgraded.

There are several methods of upgrading the Citrix Provisioning Target Device Software that’s inside a vDisk:

  • If Target Device Software is version 7.6.1 or newer, in-place upgrade the Target Device Software while doing your normal vDisk update process.
  • Completely rebuild the vDisk. An automated build process like MDT is recommended.
  • If Target Device Software is 7.6.0 or older, then you must reverse image.
    • To upgrade VMware Tools (or any software that modifies the NIC), you must reverse image.

To in-place upgrade Target Device software 7.6.1 and newer:

  1. Create a new vDisk Maintenance version, or put the vDisk in Private Image mode. Then boot an Updater Target Device. This is the normal process for updating a vDisk.
  2. Run the 2206, LTSR 2203 CU1, LTSR 1912 CU5, or LTSR 7.15.21 Target Device software installer to upgrade the software. The Target Device software must be the same version or older than the Citrix Provisioning Servers.
  3. Shut down the Updater. Promote the Maintenance version to Production, or change the vDisk to Standard Image mode. This is the normal process for updating a vDisk.

Reverse image methods:

  • Boot from VHD – Build a VM. Copy Citrix Provisioning vDisk VHD/VHDX to VM. Boot from VHD/VHDX.
  • Hyper-V can boot from a VHD directly. Copy Citrix Provisioning vDisk VHD/VHDX to Hyper-V host. Create a VM that boots from VHD/VHDX.
  • Once VHD/VHDX is updated, copy the VHD/VHDX back to Citrix Provisioning, import to a Citrix Provisioning Store, which creates a new vDisk, and assign the new vDisk to target devices. Takes effect at next Target Device reboot.

If using Citrix Provisioning Accelerator, keep XenServer patched.

To upgrade the operating system version of the Citrix Provisioning Servers:

  1. In-place upgrade the existing Citrix Provisioning Servers to a version that supports the new operating system version. For Windows 2016, upgrade to version 7.11 or newer.
  2. Build one or more new virtual machines with the new operating system version.
  3. Install Citrix Provisioning Server software with the same version as the other Citrix Provisioning Servers.
  4. Run Citrix Provisioning Configuration Wizard and join the new machines to the existing Citrix Provisioning farm and Citrix Provisioning database.
  5. Copy the vDisk files from an existing Citrix Provisioning Server to the new Citrix Provisioning Servers. Check Replication Status of each vDisk.
  6. Install the App Layering Citrix Provisioning Agent.
  7. In Citrix Provisioning Console, reconfigure Bootstrap to point to the new Citrix Provisioning Servers. Go to Sites > MySite > Servers > right-click each server, and click Configure Bootstrap.
  8. Reconfigure DHCP Options or BDM to point to the new Citrix Provisioning Servers. Do one or more of the following:
    • Reconfigure TFTP load balancing to point to the new Citrix Provisioning Servers.
    • Change DHCP Scope Options 66/67 to the new Citrix Provisioning Servers.
    • Create a new Boot ISO with the new Citrix Provisioning Servers.
    • Use the Citrix Provisioning Console to update the BDM Partition on each Target Device.
    • Start the PXE Service on the new Citrix Provisioning Servers and stop the PXE Service on the old Citrix Provisioning Servers.
    • Reboot some Target Devices to make sure they work.
  9. In Citrix Provisioning Console, delete the old Citrix Provisioning Servers.
  10. Decommission the old Citrix Provisioning Servers.

Virtual Delivery Agents (VDA)

To in-place upgrade the Virtual Delivery Agent software:

Instead of in-place upgrading the VDAs, you can also rebuild them with the new software versions. If rebuilding, use an automated method, like MDT.

To upgrade the operating system version of the Virtual Delivery Agents, it’s recommended to rebuild the VDA. But keep in mind the following:

  • Windows 11 is not supported by VDA 1912 LTSR but Windows 11 is supported with VDA 2109 and newer.
  • Windows 10 version upgrades should be a rebuild, not an in-place upgrade.
    • If you in-place upgrade, uninstall VDA software, upgrade Windows, then reinstall VDA software.
    • Citrix App Layering might require in-place upgrade of Windows 10 due to other layers being linked to the OS Layer.
  • Newer VDA operating system versions use newer profile versions, which means older profiles will not work.
  • Newer RDSH operating system versions require newer RDS Licensing Servers and newer RDS Licenses.
  • GPO settings– Newer OSs have newer Microsoft GPO settings.

StoreFront

StoreFront is the most problematic component to upgrade so be prepared to roll back.

  • Newer versions of StoreFront installer are adding pre-upgrade checks to prevent known upgrade issues – e.g. stop SCOM Service

Citrix does not support mixing StoreFront versions within a single Server Group, and they instead prefer that you do this: (source = Upgrade StoreFront at Citrix Docs)

  1. It’s critical that you snapshot the StoreFront machines before beginning the upgrade.
  2. Remove a StoreFront sever from the Server Group and load balancing.
  3. Prep: close consoles, close PowerShell, logoff other admins, stop SCOM Agent.
  4. Upgrade the removed server by installing one of the following:
    1. StoreFront LTSR 2203 CU1. There is no StoreFront 2206.
    2. StoreFront LTSR 1912 CU5
    3. StoreFront LTSR 3.12.9000 from XenApp & XenDesktop 7.15.9000 Cumulative Update 9
    4. If upgrade fails, review the install logs to determine the cause. Once the cause is determined, revert the VM to prior snapshot, and try the upgrade again.
    5. Upgrade the HTML5 Workspace app installed on StoreFront. The instructions for StoreFront LTSR 2203 CU1, StoreFront LTSR 1912 CU5, and StoreFront LTSR 7.15.9000 (3.12.9000) are the same.
  5. Swap out the upgraded server on the load balancer so all traffic goes to the new server.
  6. Uninstall/reinstall StoreFront on the remaining StoreFront servers and join the first server that was already upgraded.

To upgrade the operating system version of the StoreFront Servers:

  1. Build one or more new virtual machines with the new operating system version.
  2. Install StoreFront software.
  3. Do one of the following: (Note: Citrix does not support mixing operating system versions in the same StoreFront server group)
    • Export the StoreFront configuration from the old servers and import to the new servers. This only works if the older servers are StoreFront 3.5 and newer.
    • Manually configure the new StoreFront Server Group to match the old StoreFront Server Group. This configuration includes: Base URL, entries under Manage Delivery Controllers (case sensitive), SRID (c:\inetpub\wwwroot\Citrix\Roaming\web.config), export/import subscriptions, Beacons, Gateways, Icon Aggregation, etc.
    • This option is probably unsupported: In-place upgrade the existing StoreFront Servers to the same version as the new servers. Run StoreFront Console on the new servers, and join the new machines to the existing Server Group. This causes configuration and subscriptions to replicate to the new server.
  4. Upgrade the HTML5 Workspace app installed on StoreFront. The instructions for StoreFront LTSR 2203 CU1, StoreFront LTSR 1912 CU5, and StoreFront LTSR 7.15.9000 (3.12.9000) are the same.
  5. Reconfigure the load balancer to point to the new StoreFront servers instead of the old StoreFront servers.
  6. In StoreFront console, remove the old StoreFront servers.
  7. Decommission the old StoreFront servers.

Workspace app for HTML5

Workspace app for HTML5 is usually released on a different schedule than StoreFront and is upgraded out-of-band.

  • There is no LTSR version of Workspace app for HTML5 so you should upgrade to the latest Workspace app for HTML5, especially for the newer features (e.g. multi-monitor, USB redirection).

To in-place upgrade Workspace app for HTML5:

  1. Upgrade the HTML5 Workspace app installed on StoreFront. The instructions for StoreFront LTSR 2203 CU1, StoreFront LTSR 1912 CU5, and StoreFront LTSR 7.15.9000 (3.12.9000).
  2. For VDA machines that are version 7.15 or older, upgrade the HTML5 Citrix PDF Printer software that’s installed on the VDA.
    • VDA 7.16 and newer install the PDF Printer automatically, so you don’t have to install the Citrix PDF printer yourself.
  3. Upgrade the Chrome File Access software that’s installed on the VDA machines.

Director

To in-place upgrade the Director servers:

  1. Ensure the Delivery Controllers are already upgraded. There’s no point in upgrading Director if Delivery Controllers aren’t upgraded.
  2. In-place upgrade to one of the following versions:
    1. Director 2206
    2. Director LTSR 2203 CU1
    3. Director LTSR 1912 CU5
    4. Director LTSR 7.15.9000 Cumulative Update 9
  3. Upgrading Director overrides modifications to LogOn.aspx (e.g., default domain name), so you’ll have to reapply them.
  4. Repeat for the remaining Director servers.
  5. Upgrade the StoreFront Probes.

To upgrade the operating system version of the Director servers, it’s easier if you have a custom DNS name or load balanced DNS name for Director instead of using a server name :

  1. Make sure Delivery Controllers are running a version that supports the OS you intend for Director. For Windows 2016, Delivery Controllers must be version 7.11 or newer.
  2. Build new Director servers with the same version or newer than the Delivery Controllers.
  3. Configure the new Director servers to point to the same Delivery Controllers as the old Director servers.
  4. Copy the Director data files from the old Director servers to the new Director servers. Or point the new Director servers to the existing UNC path.
  5. Cutover:
    1. If you have a load balanced DNS name for Director, reconfigure the load balancer to point to the new Director servers.
    2. If you have a custom DNS name for Director, change it to resolve to the new Director server’s IP address.
    3. If you were previously using the actual server name, then you can either inform users of the new Director server name, or delete the old Director server and rename the new Director server, or delete the old Director server and reconfigure the old DNS name as a custom DNS name for the new Director server.
      1. Also reconfigure the StoreFront probes to point to the new Director name.
  6. Decommission the old Director servers.

Citrix Group Policy Management Plug-in

On any machine that has Group Policy Management installed, in-place upgrade the Citrix Group Policy Management Plug-in by running the installer from the Citrix Virtual Apps and Desktops (CVAD) 2206, CVAD LTSR 2203 CU1, CVAD LTSR 1912 CU5, or XenApp/XenDesktop LTSR 7.15.9000.

Profile Management Group Policy Templates

Profile Management service is included with Virtual Delivery Agent. Upgrading the VDA also upgrades Profile Management.

New templates don’t break existing functionality – Upgrading the Profile Management group policy templates (.admx files) will not affect existing functionality. The templates do nothing more than expose new settings that can be configured.

To in-place upgrade the Profile Management Group Policy Templates:

  1. Copy the newer Profile Management Group Policy Templates to the PolicyDefinitions folder: either Sysvol, or C:\Windows on every group policy editing machine.
  2. Look for older versions of the templates and delete them. The template files have the version number in their name (e.g. ctxprofile7.19.0.admx). Older Profile Management versions will have different template files with different names (e.g. ctxprofile5.8.0.admx).
  3. Edit the VDA GPOs that have Profile Management settings configured. Review the new settings, and configure them, if desired. Review the Profile Management release notes for the list of new features.

Workspace app Group Policy Templates

New templates don’t break existing functionality – Upgrading the Workspace app group policy templates (.admx files) will not affect existing functionality. The newer templates do nothing more than expose new settings that can be configured.

To in-place upgrade the Workspace app Group Policy Templates:

  1. Copy the newer Workspace app Group Policy Templates to the PolicyDefinitions folder: either Sysvol, or C:\Windows\PolicyDefinitions on every group policy editing machine. Overwrite existing template files.
    1. LTSR Workspace app and Current Release Workspace app have different versions of the group policy template files.
    2. Current Release Workspace app template files include all of the LTSR Workspace app settings, plus new settings that don’t apply to LTSR Workspace app.
  2. If you are deploying a newer Current Release Workspace app version, edit the GPOs that have Workspace app settings configured, review the new settings, and configure them, if desired. Review the Workspace app release notes for the list of new features.

Workspace app

To in-place upgrade Workspace app:

  1. SCCM – Use SCCM or similar to push one of the following versions:
  2. StoreFront delivery of Workspace app – If Workspace app is offered directly from StoreFront servers, copy the newer Current Release Workspace app to StoreFront 3.12+.
    • If StoreFront is configured to tell users to download Workspe app from citrix.com, then note that it defaults to downloading Receiver 4.12 instead of Workspace app. You can configure StoreFront to download Workspace app instead of Receiver. Note: Receiver 4.12 is not LTSR and is no longer supported by Citrix.
    • StoreFront, by default, does not offer Workspace app upgrades to users but it can be enabled. If Workspace app upgrades are not offered, then Workspace app is provided by StoreFront only if there’s no Workspace app installed on the client device.
      • In StoreFront 3.5 and newer, enable Upgrade plug-in at logon at the same place you upload the Workspace app files.
      • For StoreFront 3.0 and older, edit C:\inetpub\wwwroot\Citrix\StoreWeb\web.config and set upgradeAtLogin  to true.
  3. Auto-update – In Workspace app, if Auto-Update is enabled, then users with permissions will receive an update notification. Users can then manually initiate the Workspace app upgrade.
    • You can configure group policy or an install switch to only update to LTSR versions of Workspace app.
  4. Manual update – Inform remote users to upgrade their Workspace app by downloading the Current Release version from http://workspace.app.
    • If Workspace app was initially installed as an administrator, then only an administrator can upgrade it.
    • If Workspace app was initially installed without administrator permissions, then each non-admin user on the same machine has a different Workspace app installation, and each user has to upgrade it separately.

Skype for Business HDX RealTime Optimization Pack

The Skype for Business HDX RealTime Optimization Pack is usually released separately from the main Citrix Virtual Apps and Desktops (CVAD) releases.

To in-place upgrade HDX RealTime Optimization Pack:

  1. On the VDAs, install the HDX RealTime Connector.
    • 2.9 is the last version of Skype for Business HDX RealTime Optimization Pack.
  2. On each Workspace app machine, install the HDX RealTime Media Engine normally.

Federated Authentication Service (FAS)

To in-place upgrade the Federated Authentication Service (FAS) servers:

  1. On the existing FAS servers, run AutoSelect.exe from the Citrix Virtual Apps and Desktops (CVAD) 2206 ISO, the LTSR 2203 CU1 ISO, the LTSR 1912 CU5 ISO, or the LTSR XenApp/XenDesktop 7.15.9000 ISO, and click the button to install Federated Authentication Service. It’s a simple Next, Next, Next process.
  2. Newer versions of FAS might have newer group policy templates. If so, copy them to Sysvol, or C:\Windows\PolicyDefinitions on all group policy editing machines.

To upgrade the operating system version of the FAS servers:

  1. Build one or more new FAS servers.
  2. Request a Registration Authority certificate for each of the FAS servers.
  3. Change the group policy object for FAS to point to the new FAS servers. Run gpupdate on StoreFront and VDAs.
  4. Decommission the old FAS servers.

Customer Experience Improvement Program (CEIP)

Newer versions of Citrix Virtual Apps and Desktops (CVAD) components automatically enable Customer Experience Improvement Program (CEIP). To disable, see the following:

Citrix ADC Firmware

Test appliances – Ideally, Citrix ADC firmware upgrades should be tested on separate test appliances. VIPs on the test appliances should then be tested.

Downtime if no High Availability – If you only have a single Citrix ADC appliance, then upgrading the firmware will cause downtime while the appliance is rebooting.

GSLB and mixed versions – If GSLB Metric Exchange Protocol (MEP) is enabled, then the Citrix ADC appliances on both sides of the MEP connection can run different versions of firmware.

To in-place upgrade Citrix ADC Firmware:

  1. Save the config. Then download a copy of the ns.conf file, or perform a backup of the appliance and download the backup file.
  2. On the secondary appliance, install the newer firmware.
  3. To test the new firmware, perform an HA failover.
    1. Configuration changes made on the primary appliance will not be synchronized to the secondary appliance until the firmware on the secondary appliance is upgraded.
    2. You can failover HA again to revert to the older firmware.
    3. To downgrade, on the appliance you’ve already upgraded, you can perform the firmware upgrade process again, but this time upload the older firmware.
  4. On the primary appliance, install the newer firmware. A HA failover occurs automatically.

Migrate From XenApp 6.5 to Citrix Virtual Apps and Desktops (CVAD) 7

XenApp 6.5 is End-of-life in June 30, 2018. End-of-maintenance (no new patches) after December 31, 2017. See the Lifecycle Announcement.

Citrix has a website devoted to 6.5 to 7.x migrations.

6.5 to 7.x Migration Considerations

Current Release or LTSR?

Will you deploy Current Release 7.x? Or LTSR 7.x? See above for a comparison between Current Release and LTSR.

Some vendors (e.g., Epic) strongly recommend LTSR. Today, there are three supported LTSR options: CVAD LTSR 2203 CU1, CVAD LTSR 1912 CU5, and XenApp/XenDesktop LTSR 7.15.9000.

Citrix XenApp licensing

Subscription Advantage Expiration date needs to be the same or newer than the 7.x release date.

Software Maintenance or Customer Success Services – Select is required for LTSR.

XenApp licenses can be traded up to Citrix Virtual Apps and Desktops (CVAD) licenses.

  • XenApp Enterprise doesn’t have Citrix Provisioning, but XenDesktop Enterprise does get Citrix Provisioning.
  • XenDesktop licenses add virtual desktops capability.

Mixed license types – In 7.13 and newer, you can mix license types, but not editions, in the same 7.x farm/site.

Director licensing – Some Director functionality requires Premium Edition – e.g. alerting, custom reports, and StoreFront Probes.

VDA/Worker Operating System Version

Stay with Windows 2008 R2? – Are you staying with Windows 2008 R2 on the 7.x VDAs? If so, you can uninstall 6.5 from the XenApp worker, and install VDA 7.x instead. No need to rebuild.

  • Staying with Windows 2008 R2 allows you to reuse your existing profiles instead of requiring new profiles.
  • VDA 7.15 LTSR is the last version to support Windows 2008 R2. See the list of Deprecated Features.
    • VDA 7.15 can register with 2203 LTSR CU1 Delivery Controllers or 1912 LTSR CU5 Delivery Controllers.

Upgrade operating system version – If you are upgrading the workers to a newer operating system version:

  • Every user will get new profiles.
  • Applications must be compatible with the new operating system version.
  • If you are publishing a desktop, then Windows 2012 R2 Start Menu is quite different than other operating system versions.
    • Windows Server 2016 has the same Start Menu as Windows 10 1607.
    • Windows Server 2019 is the same as Windows 10 1809.
    • Windows Server 2022 is the same as Windows 10 21H2.
    • Windows Server 2016 is supported with CVAD LTSR 2203 and newer, CVAD LTSR 1912 and CVAD LTSR 7.15.
    • Windows Server 2019 is supported with CVAD LTSR 1912 and CVAD LTSR 2203 and newer, but not CVAD LTSR 7.15.
    • Windows Server 2022 is supported with CVAD LTSR 2203 and newer, but not CVAD LTSR 1912 or older.
    • Windows 11 is supported in CVAD LTSR 2203 and newer. Windows 11 is not supported in CVAD LTSR 1912 and older.
  • The VDAs with newer operating system must be rebuilt from scratch.
  • Make sure you own Remote Desktop Services CALs that match the newer operating system. Windows 2008 R2 RDS CALs cannot be used with Windows 2012 R2 or newer VDAs.
    • RDS Licensing Server must be the same OS version or newer than the VDAs.

You can mix and match operating system versions in the same 7.x farm/site. Primarily VDAs. But also infrastructure servers.

  • One option is upgrade most of your VDAs to a newer OS version, but leave some at 2008 R2 so they can run apps that are not supported in the newer OS versions.
  • For 16-bit apps, you can publish them from VDAs running 32-bit Windows 7.

New functionality in 7.x not available in 6.5

The following a selected list of new features in 7.x that wasn’t available in 6.5. Which of these would you like to enable after the upgrade?

  • Hypervisor connection (e.g. vCenter) – for virtual machine power management
  • Machine Creation Services (MCS):
    • Requires knowledge of hypervisor storage, clusters, etc. And Capacity Planning. Need to work with your hypervisor team.
  • VDAs hosted in IaaS Clouds like Azure or AWS
    • CVAD 2003 and newer no longer support VDAs in Azure or AWS. To broker sessions to VDAs in Azure, AWS, or Google Cloud, Citrix now requires customers to instead subscribe to Citrix Cloud CVAD Service .
  • Virtual Desktops
  • App-V integration with Citrix Studio
  • EDT protocol (UDP-based ICA)
  • GPUs
  • Generic USB Redirection in RDSH
  • SAML authentication
  • Client IP/Client Name access restrictions
  • AppFlow
  • Remote PC
  • Browser Content Redirection

6.5 to 7.x Changes

Link:

Single product – In 7.x, XenApp and XenDesktop were merged into a single product. It’s the same installer for both. The only difference is the licenses. You can use the terms XenApp and XenDesktop interchangeably.

Delivery Controllers – XenApp 6.5 Controllers are now called Delivery Controllers in 7.x.

Virtual Delivery Agents – XenApp 6.5 Workers are now called Virtual Delivery Agents (VDAs) in 7.x. These are the machines that apps are installed on and users actually connect to. They’re called VDAs because you install Virtual Delivery Agent software on those machines.

Controller and VDAs are separate software – In XenApp 6.5, you install the same software on both Workers and Controllers. In 7.x, Delivery Controller software and VDA software are completely different.

VDA types – 7.x supports three types of VDAs: Remote Desktop Session Host (RDSH aka Server OS), virtual desktops (Desktop OS), and Remote PC (physical PCs). XenApp 6.5 primarily only supported one type of worker: RDSH.

  • RDSH is the new name for Terminal Services.
  • XenApp 6.5 administrators tend to think of the XenApp workers as “XenApp Servers“. Actually, it’s more accurate to call them Microsoft Windows Remote Desktop Session Hosts. Apps run on top of Windows (RDSH), not Citrix. XenApp is installed on top of RDSH. XenApp merely provides ICA connectivity to RDSH, instead of RDP.
  • In 7.x workers, Virtual Delivery Agent replaces XenApp.

SQL/Licensing communication – In XenApp 6.5, every XenApp machine, including Workers, connects to database and licensing. VDAs in 7.x no longer talk to database or licensing. VDAs rely on Delivery Controllers to do that. This makes 7.x sites/farms much more scalable than 6.5.

Farm vs site – In XenApp 6.5, all Controllers/Workers that share a database belong to a single Farm. In 7.x, all Delivery Controllers that share a database belong to a single XenApp/XenDesktop site. The terms site and farm can be used interchangeably. However, the term “site” might not clearly indicate that it’s the same as a “farm”.

  • VDAs belong to Delivery Controllers in a single site/farm. You use registry values (ListOfDDCs) to control which Delivery Controllers (and site/farm) a VDA registers with.

SQL availability is more important in 7.x. If SQL is down, then the 7.x farm is down. XenApp 6.5 did not have the same level of dependency on SQL.

  • Local Host Cache in CVAD LSTR 2203, CVAD LTSR 1912 or XenApp/XenDesktop LTSR 7.15 can maintain most functionality after a database outage.
  • AlwaysOn Availability Groups (or Basic Availability Groups or Mirroring) is the preferred SQL HA method.

Zones vs Multiple sites/farms:

  • In XenApp 6.5, it was very easy to stretch a farm to multiple datacenters by putting different XenApp 6.5 machines in different zones. That’s because access to SQL database was not particularly important.
  • In 7.x, SQL database access is critical, making it difficult to stretch a site/farm across datacenters. Current Release 7.7 and newer added zones, which were greatly enhanced in Current Release 7.12 with the addition of Local Host Cache and Zone Preference. Current Release 7.14 enhanced Local Host Cache even more. There are still some scalability limitations, and missing virtual desktop functionality. And it adds complexity with no savings in the number of machines other than SQL.
  • Zones and Local Host Cache are available in CVAD 2206, CVAD LSTR 2203, CVAD LTSR 1912 or XenApp/XenDesktop LTSR 7.15.
  • The alternative for 7.x is to build a separate XenApp/XenDesktop site/farm in each datacenter, and use StoreFront to aggregate the icons.

Citrix Studio – In XenApp 6.5, you manage the farm using AppCenter. In XenApp/XenDesktop 7.x, you manage the site/farm using Citrix Studio. Both are MMC based consoles.

Director – In XenApp 6.5, help desk uses AppCenter to manage user sessions. In XenApp/XenDesktop 7.x, help desk uses a web-based tool called Director.

  • Shadowing from Director uses Microsoft Remote Assistance.
  • Director is also used by administrators to view historical performance and usage data.
  • Director is similar to EdgeSight, but the monitoring service is built into Delivery Controller, and the monitoring agent is built into the VDA software.

Catalogs / Delivery Groups / App Groups can be confusing concepts.

  • You first add VDA machines to a Catalog. You either add existing VDA machines to a Catalog, or MCS/PSS creates VDA machines and puts them in a Catalog.
  • You add VDA machines from one or more Catalogs to a Delivery Group.
  • You publish apps and desktops from one or more Delivery Groups.
  • You aggregate multiple applications into an App Group. App Groups lets you configure identical settings across multiple published app icons. It also controls Session Sharing.

Tags in 7.x simulate Worker Groups in 6.5. You assign a single tag to multiple VDAs. Then you publish an app to a tag, or publish an app to an App Group that has the tag selected. The published app launches on only the VDAs that have the tag. This lets you publish apps on a subset of machines in a Delivery Group, instead of load balancing across every VDA machine in the Delivery Group.

PowerShell commands in 7.x are different than 6.5. All 7.x configuration is performed using PowerShell. Changes made in Studio are actually performed using PowerShell. This focus on PowerShell makes it easy to automate XenApp/XenDesktop tasks (e.g. add a new VDA machine to Catalog and Delivery Group).

XenApp Streamed Applications was removed from 7.x.

  • If you want to keep the Application Streaming functionality, then you’ll to need to repackage the streaming applications using Microsoft App-V or similar.
  • If you don’t need app isolation, then App Layering Elastic Layers are another option since they are essentially streamed.

Session Recording – XenApp 6.5 Platinum Edition had SmartAuditor. Citrix Virtual Apps and Desktops (CVAD) 7.x Premium Edition has Session Recording. The latest Current Release version of Session Recording can do the following, which weren’t available in SmartAuditor:

  • Record both RDSH and Desktop VDAs.
  • Integrate with Director – can enable or disable recording from Director.
  • More policy options for starting recording.
  • Load balance multiple Session Recording servers.
  • Tag recordings when USB devices are inserted.
  • Web-based Session Recording Player.

XenApp 6.5 functionality missing from CVAD

The following 6.5 functionality is still not available in 7.x:

  • Custom ICA files:
  • SmartAccess per published application:
    • In 7.x, you enable Access Control filters at the Delivery Group level. It’s not possible to configure Access Control at the individual published application.
  • Director is quite different from EdgeSight.
    • To get full Director functionality, you need Citrix Virtual Apps and Desktops (CVAD) Premium Edition, and the latest Current Release.
  • Single Sign-on (aka Password Manager)
    • Self Service Password Reset is available. However, the rest of the Single Sign-on functionality is missing from 7.x.

Migrate from Web Interface to StoreFront first

A challenging aspect of migration from 6.5 to 7.x is the StoreFront/Citrix Gateway migration. But once on StoreFront, there should be no more need for major migrations on the client side.

Since StoreFront can connect to both 6.5 farms and new 7.x farms, you should migrate to StoreFront before you migrate the Workers and Controllers to 7.x. StoreFront has features that can help with farm migration:

  • StoreFront can aggregate identical icons from multiple farms/sites.
  • StoreFront can use AD Group Membership to control access to a farm/site.
  • StoreFront can control access and routing to farm/sites and 7.x zones across multiple datacenters.

StoreFront vs Web Interface

StoreFront, Receiver Self-Service, and Citrix Gateway are a major architectural change from Web Interface/Secure Gateway.

Receiver Self-Service vs PNAgent – If you are currently running PNAgent clients (aka Receiver Enterprise, aka pnagent.exe), then you will have to deploy a newer Workspace app that has Self-Service capability. Self-Service is the client side of StoreFront.

  • If you install Workspace app on a machine that has PNAgent installed, then newer versions of Workspace app should be able to remove PNAgent and install Self-Service instead. But this isn’t always successful, and you might have to manually remove PNAgent before Self-Service installs correctly.

Favorites – In StoreFront, users can mark icons as Favorites. The selected Favorites are stored on a database that is replicated to each StoreFront server. Web Interface never had this capability. Do you want to leave Favorites enabled? Or disable it so it’s not too much of a change for migrated users?

HTTPS – Receiver Self-Service and StoreFront require HTTPS.

Discovery – Receiver Self-Service downloads a XML-based discovery document from StoreFront, and uses the XML document to configure itself.

Beacons – Receiver Self-Service uses Beacons to determine if the client machine is internal or external. If external, Receiver Self-Service uses Citrix Gateway to connect.

  • Single FQDN – If you use the same DNS name for both internal and external, then DNS caching might affect machines that roam from internal to external and back again. Another option is to use different DNS names for internal StoreFront and external Citrix Gateway.

StoreFront Server Group – Multiple StoreFront servers can be combined into a Server Group, which automatically replicates Favorites between each other.

  • Configurations can be manually replicated from the StoreFront Console.
  • Citrix does not support stretching a single StoreFront Server Group across datacenters. Each datacenter should be a separate Server Group.

Multiple Stores – StoreFront can host multiple Stores, which are somewhat like Web Interface sites.

  • Some StoreFront components, like the Base URL, are shared across multiple Stores.
  • When Receiver Self-Service performs Discovery, if the StoreFront server has multiple stores, then the user is prompted to select a store. Stores can be hidden (not advertised).

Citrix Gateway required – For external access,Receiver Self-Service and StoreFront require Citrix Gateway ICA Proxy instead of Secure Gateway.

Workspace app configuration methods – There are multiple methods of configuring Receiver Self-Service: registry, group policy, StoreFront Account Services, and installer command line arguments.

Challenges of cutover – Because Receiver Self-Service is so different from PNAgent, cutovers are difficult. Workspace app behaves differently when connected to StoreFront Stores vs PNAgent URLs.

HDX Optimal Routing – StoreFront supports sending ICA traffic for each site/farm to a non-default Citrix Gateway URL. If a user launches an icon from Datacenter A, then you probably want ICA traffic to go through the Citrix Gateway that is in Datacenter A. This is called HDX Optimal Routing and was never available in Web Interface. This feature requires datacenter-specific DNS names.

SAML Authentication – StoreFront and Citrix Gateway support SAML authentication. Deploy Federated Authentication Services to support SAML.

LTSR or Current Release – If you intend to build LTSR CVAD, then StoreFront should be the LTSR version, and Workspace app should be the LTSR version.

  • LTSR Workspace app and LTSR VDA might not support the latest Teams optimization features.
  • LTSR Workspace app does not support Browser Content Redirection (BCR). Current Release versions of Workspace app do support Browser Content Redirection.

Citrix Gateway vs Secure Gateway

Not free – Citrix Gateway is not free.

Networking skills – Citrix is a networking device, which requires different skills than the server-based Secure Gateway.

PNAgent vs Self-Service through Citrix Gateway – Workspace app can’t connect to PNAgent stores through Citrix Gateway. StoreFront stores (Receiver Self-Service) do work through Citrix Gateway.

AppFlow – If ICA traffic is going through Citrix Gateway, you can enable AppFlow, and send it to Citrix Application Delivery Management (ADM) and Director for monitoring and reporting.

  • You can deploy Citrix Gateway internally to get internal ICA traffic through Citrix ADC for AppFlow reporting.
  • Only newer versions of Citrix Workspace app support Single Sign-on through Citrix Gateway by enabling a group policy setting.

Build StoreFront and Citrix Gateway

Follow the guides on this site to build StoreFront, and configure Citrix Gateway:

  1. Build two or more StoreFront 2203 LTSR CU1, StoreFront 1912 LTSR CU5, or StoreFront 7.15.9000 (3.12.9000) LTSR, servers in each datacenter. There is no StoreFront 2206.
  2. Configure StoreFront Console’s Manage Delivery Controllers to connect to existing XenApp 6.5 farm(s).
  3. Configure a load balancer to load balance Storefront in each datacenter.
  4. Configure Citrix ADC GSLB to load balance a single DNS name to StoreFront Load Balancing VIPs in both datacenters.
  5. Configure Citrix Gateway in both datacenters.
    1. Create an internal Citrix Gateway vServer for AppFlow reporting?
    2. Configure StoreFront Console > Manage Citrix Gateways, and enable Remote Access on the Store. See the instructions for StoreFront 3.12 and newer.
  6. Configure HDX Optimal Routing. See the instructions for StoreFront 3.12 and newer.
  7. Configure Citrix ADC GSLB to load balance a single DNS name to Citrix Gateway VIPs in both datacenters.
    1. Configure Citrix ADC GSLB active/passive for the HDX Optimal Routing DNS names.
  8. Import a Citrix Application Delivery Management (ADM) virtual appliance.
    1. Use Citrix ADM to enable AppFlow on the Citrix ADC appliances.

Migrate from Web Interface to StoreFront

Cutover DNS? – If you cutover an existing DNS name from Web Interface to StoreFront:

  • StoreFront user interface and Citrix Gateway user interface are different than the Web Interface user interface. A cutover might result in help desk calls from users that are not accustomed to the new user interface.
  • If you cutover an existing DNS name, how do you reconfigure Receivers to use Receiver Self-Service Stores instead of PNAgent URLs? You’d have to ask every user to remove existing Receiver accounts and re-add them.
  • Are you migrating from HTTP to HTTPS? It’s difficult to reconfigure Receivers and Browser Favorites to point to HTTPS instead of HTTP.
  • Cutover night would have many changes. Be prepared for many support issues the next day.

New DNS names – A preferred alternative is to use a new DNS name(s) for StoreFront and Citrix Gateway.  This lets you run Web Interface and StoreFront in parallel, and you can migrate users (and Receiver) at your leisure.

  • Use group policy to point Receiver Self-Service to the StoreFront DNS name. This group policy setting does not apply to PNAgent (pnagent.exe).
  • Deploy one of the following Workspace App versions to company-managed machines.
    • Current Release – Workspace app 2209
    • LTSR Workspace app 1912 Cumulative Update 7 (aka 19.12.7000)
  • Inform users of new external DNS name. StoreFront can be configured to offer Receiver upgrades.
  • Inform users to remove existing accounts from mobile Receiver (iOS, Android), and re-add using the new DNS name. This changes the mobile Receiver to use StoreFront Store instead of PNAgent (Legacy).

6.5 to 7.x Migration Plan

This section assumes users have already been migrated to StoreFront/Receiver.

New 7.x Infrastructure

  1. Upgrade Citrix License Server, and upgrade license files with Subscription Advantage date that has not expired.
    1. Alternatively, you can build a new license server and reallocate the licenses to the new license server. Point the 7.x farm/site to the new license server.
    2. You can either leave the 6.5 farm on the old license server, or reconfigure the 6.5 farm to use the new license server. If you use both old and new license servers, then the assumption is that you will migrate all users to the new 7.x farm/site in a timely manner so you don’t exceed your license count.
  2. Build highly available SQL Servers. Typically AlwaysOn Availability Groups (or Basic Availability Groups in SQL 2016 Standard Edition).
    1. Separate SQL in each datacenter?
  3. Build Delivery Controllers – at least two per datacenter. Connect them to the Highly Available SQL Servers.
    1. Delivery Controller 2206Delivery Controller LSTR 2203 CU1, Delivery Controller LTSR 1912 CU5, or Delivery Controller LTSR 7.15.9000.
    2. Separate sites/farms in each datacenter?
    3. Or are you stretching and configuring zones instead? Zones are available.
    4. Mixed license types are available.
  4. Connect Citrix Studio to your hypervisor (e.g. vCenter). Import the vCenter certificate first.
    1. If using MCS, create Hosting Resources in Studio. These are a combination of hypervisor cluster, hypervisor storage, and hypervisor network.
  5. Install Citrix Director and configure them to point to the Delivery Controllers.
    1. Director 2206, Director LTSR 2203 CU1, Director LTSR 1912 CU5, or Director LTSR 7.15.9000
  6. If Citrix Provisioning, and if using the Citrix Provisioning Citrix Virtual Desktops Setup Wizard, then either in-place upgrade Citrix Provisioning servers to the same version as Citrix Virtual Apps and Desktops (CVAD) 7 or build new Citrix Provisioning servers with the same version as Citrix Virtual Apps and Desktops (CVAD) 7.
    1. If new Citrix Provisioning servers, then they can be in a new Citrix Provisioning farm with a new database.
  7. If you are upgrading the VDA OS version, then you might have to upgrade the App-V infrastructure.
  8. If you intend to use Citrix App Layering, import and configure the ELM appliance.
  9. Build Citrix Workspace Environment Management servers.
  10. Build Citrix Session Recording servers. See the instructions.
  11. Configure group policies and profiles for newer OS version.
    1. Move Citrix Policy settings from AppCenter to a group policy object (GPO) instead of Citrix Studio.
    2. If new profiles, create scripts to copy settings from old profiles to new profiles.
  12. Implement Citrix and hypervisor monitoring tool(s)

New 7.x VDAs

  1. Create a master VDA – either VDA LTSR 2203 CU1, VDA LTSR 1912 CU5, or VDA LTSR 7.15.9000.
    1. If remaining on Windows 2008 R2, you can uninstall XenApp 6.5 (and all related components), and then install Virtual Delivery Agent LTSR 7.15.9000. LTSR VDA 1912 will not install on Windows 2008 R2.
    2. If upgrading the OS version, then you must build from scratch.
    3. If App Layering, import the OS Layer to ELM with only Windows installed.
    4. If not App Layering, then install Applications, VDA, and Security software (e.g. antivirus) on the Master VDA.
  2. If App-V, upgrade App-V packages, or create new App-V packages.
    1. CVAD can integrate App-V into Citrix Studio.
  3. If Layering, use ELM to create Platform Layer and App Layers. Then push an image to Citrix Provisioning, or your hypervisor.
  4. Use Citrix Provisioning or MCS to create Catalogs. Both options create new VDA machines, and put them in a Machine Catalog. If Citrix Provisioning,
    1. Convert the master VDA to a new vDisk.
    2. Use the Citrix Provisioning Virtual Desktops Setup Wizard to create multiple Target Devices that boot from the vDisk.
  5. Configure scheduled reboots of RDSH VDAs. Citrix Studio has some reboot options. Or write a script.

Publish Icons, Pilot, Rollout, and Operations

  1. Create Delivery Groups and Publish Applications/Desktops from the Delivery Groups.
    1. See the XenApp 6 migration tool.
    2. See App/Desktop publishing.
    3. See limit application usage.
    4. Create App Groups.
    5. Publish apps to anonymous users?
    6. Create Published Content.
    7. Use Tags to publish apps on a subset of machines in a Delivery Group.
    8. Enable multiple sessions from one user?
    9. Use Keywords to control icons in Receiver. You can even use Keywords to hide applications from StoreFront.
  2. Add the 7.x farm/site to StoreFront > Manage Delivery Controllers
    1. Configure StoreFront user farm mapping (Map users to Controllers) so only members of an AD Group can see icons from the 7.x farm/site? See the instructions for StoreFront 3.12 and newer.
  3. Help Desk:
    1. Add Help Desk users to Citrix Studio > Configuration > Administrators so they can use Director.
    2. Teach Help Desk how to use Director. 2206 Director, LTSR 2203 Director, LTSR 1912 Director, and LTSR 7.15 Director have different capabilities.
  4. Conduct pilot:
    1. Assign users to the apps and desktops published from 7.x. Since users are already using StoreFront, the new icons should show up in Workspace app automatically.
    2. Solicit feedback and fix issues.
  5. Rollout:
    1. Assign users to 7.x published apps/desktops, and unassign the users from the 6.5 published apps/desktops
  6. Decommission the 6.5 farm.
  7. Backup 7.x SQL databases, vDisks, master images, and Citrix ADC configurations.
  8. Build test 7.x farm(s) so you can test Citrix infrastructure upgrades.

143 thoughts on “Citrix Virtual Apps and Desktops (CVAD) Upgrades”

  1. I am planning to upgrade ddc.
    Does upgrading from ddc 1912 to 1912cu5 disconnect existing azure hosting? There is an issue with connecting to azure hosting on cu5 in a known issue.

    1. All Citrix services are disconnected while the database is upgraded.

      I’m not aware of any issues with upgrading Citrix and Azure connections.

      1. Look at the known issues
        Attempts to create a hosting connection to Azure in Citrix Studio might fail with an exception.
        Here’s how it came out.

        In 1912, is there any problem when upgrading cu5 while connected to hosting?

        1. It seems to indicate that only when creating a new connection, not for existing connections. And I don’t think it applies to every attempt to create new connections or else I would hear customers complaining.

          I’ve never seen a problem with hosting connections when upgrading.

  2. Hi, Hopefully a simple question here, apologies if it has already been asked…. When following the upgrade path from 7.15 to 2203 will there be any downtime or outages for the users? We have multiple Delivery Controllers and VDA’s so can take them offline individually without affecting users, but is there a point when the DC’s have been upgraded but before the database when users would not be able to connect? Presumably whilst the database is actually being upgraded new connections will not be able to be made (I’m assuming any existing connections would be OK)? Thanks.

    1. Correct. When the Delivery Controllers are disconnected from SQL then launches probably won’t be possible. Already logged in won’t be affected.

  3. Hello, I’m a long time follower and first time commenter looking for some advice on how to proceed. I currently have a small Citrix farm that consists of two servers and one Netscaler virtual appliance. Both of the servers are currently running Windows 2012 R2 and I am looking for the best way to replace these with a newer Windows version. What would be the best way to proceed?

    1. Do you want to rebuild everything, including the database? If so, then start from scratch. You can cutover your FQDN to your new StoreFront servers.

      Keeping the database takes more effort. The official method is to add more servers and then remove the old ones as I detailed in this guide. Another option is to shut down a server and rebuild it with new OS but same CVAD version and then use PowerShell commands to connect it to SQL. When you remove the old server, do not delete it from AD or else it won’t be able to connect to SQL.

      I recommend engaging a consultant to help you.

  4. I need to upgrade a customers CVAD 7.8 to 7 1912 LTSR CU5. Should I do this directly (Delivery Controllers) or with a step between with 7.15 LTSR?

    regards, Stefan

  5. Hi Carl,

    We’ve upgraded the StoreFront Servers from 1912 LTSR CU2 straight to CU5 and followed this step:

    – Remove a StoreFront sever from the Server Group and load balancing.

    Upgrading is fine but don’t get the option to add it back to the server group post upgrade – would you know the reason for this?

    Thanks in advance.

    1. I think they want you to build new StoreFront servers, add them the new Server Group, then swap them out on the load balancer.

      1. I am guessing this is not the right area for my question but I am going to give it a go. We are planning to upgrade from 7.15 CU3 to 1912 Cu5 or which ever is the latest build. Do you see any issues with that? How long does the upgrade of the DB typically take?

        Second we want to deploy Citrix on AWS but not using Citrix Cloud service. For all practical purposes it would be similar to on-prem using EC2 instances for the management plane and managing EC2 instances for the workloads. Is this possible, or is it better to have the management plane on-prem with a direct connect to AWS and manage workloads that way… This will be primarily for DR and use when upgrading.

  6. I see High Availability mentioned here. I’ve been searching for a definitive answer on how to set it up and how it works for a while and can’t find anything. We’re setup with 2 DCs and 2 storefront servers, but high availability definitely isn’t working.

    1. What exactly isn’t working? You typically load balance StoreFront. StoreFront points to both Delivery Controllres.

      1. This part of in place upgrades for Delivery Controllers is what I’m referencing, “If High Availability is configured correctly, then Delivery Controllers can be upgraded during the day.” I’ve attempted this before, but brought down citrix completely. What does a typical highly available configuration look like for CVAD? I haven’t been able to find definitive documentation about it anywhere. We have our storefront servers load balanced. We have 2 delivery controllers. Any time I shut down one DC Citrix is inaccessible. I see local host caching and SQL DB high availability, but nothing about how high availability for Storefront and Delivery Controllers should work or be configured.

Leave a Reply to Carl Stalhood Cancel reply