OASOpen
Architecture
Systems
Back to insights
Citrix & Virtualisation

Citrix CVAD 2607 LTSR: An Upgrade Planning Checklist

Citrix 2607 LTSR is the current long-term release of Virtual Apps and Desktops, and 2203 LTSR reaches end of life in March 2027. A planning checklist for on-premises Citrix sites.

OAS Editorial Team

· 6 min read

Most on-premises Citrix Virtual Apps and Desktops sites in South Africa run a Long Term Service Release. An LTSR gets security and stability fixes through cumulative updates for years without the feature churn of a Current Release. The trade-off is that it eventually ages out, and the upgrade that follows touches every component in the site.

Citrix released 2607 LTSR in August 2026. This checklist sets out what we review with a customer before an LTSR upgrade, in the order we review it.

1. Know where your release sits in the lifecycle

The Citrix product matrix gives these end-of-life dates for Virtual Apps and Desktops: 2203 LTSR on 23 March 2027, 2507 LTSR on 18 August 2028, 2402 LTSR on 15 April 2029 and 2607 LTSR on 17 August 2029. Current Releases reach end of maintenance six months after general availability and end of life eighteen months after it, so the 2511 Current Release left maintenance on 29 June 2026 and ends on 29 June 2027.

A site still on 2203 LTSR has about four months of support left and should treat the upgrade as a dated project. A site on 2402 LTSR can plan the move around a quiet period, bearing in mind that 2607 LTSR carries protocol efficiency work and Microsoft Entra single sign-on for Entra hybrid joined session hosts that 2402 will never receive.

2. Settle licensing before anything else

Since 15 April 2026 the License Activation Service is the only way to activate on-premises Citrix components, and Citrix lists the minimum LAS-compatible releases as 2203 LTSR CU7, 2402 LTSR CU3, 2411 and 2507 LTSR. If your site has not yet left file-based licensing, that comes first; our article on the Citrix LAS deadline covers it.

Citrix's preparation guidance adds three checks. Your Customer Success Services date must be valid for the target release and at least 15 November 2021. The License Server must be compatible with the target release, which the installer on the product ISO verifies. If your licences carry Hybrid Rights, update the License Server before deploying a licence file with the SaaS attribute, or the site upgrade is blocked.

3. Check the version intersect

An LTSR is a snapshot, and a cumulative update on the older LTSR you run today may be newer than it. Citrix asks you to compare the release date of your current CU with that of the target LTSR or its latest CU. If yours is later, Citrix recommends waiting for the next CU of the new LTSR, because moving to older code can overwrite security fixes you already have. It is the usual reason an otherwise ready upgrade waits a few weeks.

4. Back up and test the database layer

Back up the site, monitoring and configuration logging databases before you begin. Confirm that your SQL Server version is supported by the target release: an unsupported version stops the upgrade, and the command-line option that ignores database check failures does not bypass it. Sites on Citrix-installed SQL Server Express must install a supported Express version and migrate the databases to it.

Run the preliminary site tests the installer offers. They confirm that the site database is reachable and backed up, that the Citrix services connect and that the License Server and configuration logging database can be reached, and they write their results to PreliminarySiteTestResult.html. Resolve every failure rather than ignoring it.

5. Clear out what the new release will not accept

Personal vDisks, AppDisks and host connections to Azure Classic and CloudPlatform are unsupported. Remove the machines, catalogues and connections that depend on them, and remove the PvD and AppDisk components from VDAs. Back up each StoreFront store's App_Data folder, because customised files such as default.ica are easy to lose. Close consoles and PowerShell sessions, stop and disable third-party monitoring agents on the machines you are upgrading, and use an account that is a domain user and local administrator, with db_owner or equivalent rights if the installer is to upgrade the database.

6. Follow the component order

Citrix publishes a fixed sequence, and the order matters:

  • License Server, if a newer version is available
  • StoreFront
  • Director
  • Citrix Provisioning, from its own media, if you use it
  • Half of the Delivery Controllers
  • Studio, followed by a restart of Studio
  • The database and site
  • The remaining Delivery Controllers
  • VDAs, then the machine catalogues and delivery groups
  • Other components such as Session Recording and Profile Management

Leaving half the Controllers on the old version lets users keep reaching the site while the first half is upgraded, at reduced capacity. It does not remove the outage entirely: during the database upgrade the product services are disabled and no Controller can broker a new connection, which Citrix describes as a brief interruption in the final steps, and the upgraded Controllers cannot process requests until the whole site is upgraded. Citrix's stated best practice is still to upgrade all Controllers in the same maintenance window, and a site with a single Controller is unavailable while it is upgraded. Every provisioning and delivery group task waits until all Controllers and the database are done.

7. Plan the VDA rollout as its own project

Every VDA upgrade restarts the machine. For Machine Creation Services catalogues the VDA is upgraded on the master image and rolled out through an image update; Citrix Provisioning follows its own documentation. Citrix advises against mixing VDA versions within a catalogue, and a VDA older than the catalogue's functional level cannot register at all. Use one installer type, full product or standalone, throughout a single-session VDA's life.

Citrix also notes that you can almost always upgrade directly to the latest version, so a site on 2203 LTSR need not pass through 2402 or 2507. Measure logon times before the change, as our guide to diagnosing slow Citrix logons describes, so you can tell afterwards whether the new release helped.

Where this fits

An LTSR upgrade is also the moment to revisit the platform choice itself, which our VDI buyer's guide lays out. For most regulated South African organisations we support, on-premises Virtual Apps and Desktops remains the right answer, and this checklist is how we keep it on a supported release.

Sources

Have your LTSR upgrade planned and run as part of a Citrix assessment from OAS.

Keep exploring

All insights