Step-by-Step Guide: Upgrading to Citrix 2507 LTSR CU1 (with PVS Architecture)

Upgrading a mission-critical Virtual Desktop Infrastructure (VDI) environment is a high-stakes balancing act. Transitioning your corporate infrastructure to the Citrix Virtual Apps and Desktops 2507 LTSR (Long Term Service Release) platform ensures your enterprise remains under active mainline support while unlocking advanced HDX engine efficiency, integrated analytics, and native support for modern operating systems.

However, if you are running an environment powered by Citrix Provisioning (PVS) rather than Machine Creation Services (MCS), your sequence of execution is vastly different. Because the Delivery Controller depends on PVS to communicate with streaming vDisks, updating the core DDC database schema before upgrading your PVS servers can break communication hooks and crash production target device bootups.

🛑 Phase 1: Infrastructure Prerequisites & Pre-Flight Checks

Before running a single 2507 Cumulative Update 1 (CU1) metainstaller executable, you must verify and lock down these critical minimum environmental requirements:

• 🔑 Citrix License Server Version: Your central License Server must be running Version 11.17.2 Build 47000 or later before upgrading any core controllers. Older licensing daemons will fail to decode 2507 product code strings, dropping user checkouts into a grace-period violation.
• 🗄️ Microsoft SQL Server Engine & Compatibility:
  • Engine Requirement: Your Site Configuration, Logging, and Monitoring databases must be hosted on Microsoft SQL Server 2016 SP3, 2017, 2019, or 2022.
  • The Compatibility Trap: Even if your SQL server engine is updated, you must connect to SQL Server Management Studio (SSMS) and verify that your Database Compatibility Level is manually set to 130 (SQL Server 2016) or higher. Citrix 2507 utilizes modern query functions; leaving compatibility matching legacy database configurations will cause the site schema upgrade to crash immediately.
• 🖥️ Operating System Support: Citrix 2507 has officially dropped support for Windows Server 2016 core roles. Your Delivery Controllers, StoreFront servers, and Provisioning nodes must be running Windows Server 2019 or 2022 before beginning the software upgrade.
• 💾 Infrastructure Backups: Take independent VM snapshots of all infrastructure nodes and execute a complete, cold database backup within your SQL cluster.

🛠️ Phase 2: The Core Upgrade Timeline

Follow this exact component sequence to guarantee a seamless transition across your management, provisioning, and delivery planes:

1. License Server Migration

Step 1

Always target your central License Server first. The incoming 2507 infrastructure components will fail to validate operational session tokens if the underlying licensing daemon is running older software.

2. StoreFront Server Cluster Update

Step 2

Isolate StoreFront nodes from your NetScaler load-balancer pool one by one. Run the 2507 CU1 installer, verify console access, and fully re-propagate the server group before introducing production user traffic.

3. Citrix Provisioning (PVS) Infrastructure Upgrade

Step 3

Mount your dedicated Provisioning 2507 installation media. Run the PVS upgrade utility on your first PVS server to migrate the PVS database schema, update your remote PVS management consoles, and then upgrade the remaining streaming PVS servers in the farm.

4. Primary Delivery Controller (DDC) Upgrade

Step 4

Mount the main Citrix 2507 LTSR CU1 ISO on your primary DDC. Launch the installer to update Studio and local server core components. Reboot the node when requested, but do not open the Web Studio console yet.

5. Automated SQL Site Schema Upgrade

Step 5

Open the newly updated Web Studio console on your Primary DDC. You will be hit with a mandatory site upgrade prompt. Select Automatic Site Upgrade to allow Citrix to safely inject the 2507 table schemas directly into your SQL backend database.

6. Secondary Delivery Controllers

Step 6

Once the primary database configuration updates successfully, run the metainstaller across your secondary backup DDCs to ensure configuration high-availability remains unbroken.

7. Target Device VDA & PVS Client Update

Step 7

Upgrade Citrix Director. Next, boot your master vDisk in PVS Private Image or Maintenance mode. Run the standalone 2507 CU1 VDA installer alongside the updated Target Device software, run the PVS optimizer, shut down, and promote the new vDisk version to production.

⚠️ Known Issue: The Generic Taskbar Icon Bug

Admins deploying 2507 CU1 have flagged a persistent user experience bug in production environments: when users launch a published application via a desktop shortcut or the Workspace App interface, the application loads successfully, but its icon on the Windows taskbar displays the generic black/blue Citrix Workspace icon instead of the application’s actual native icon (e.g., Excel or SAP).

This issue is tied to stub execution changes inside the selfservice.exe engine.

The Temporary Workaround

While awaiting an official patch, you can force the workspace environment to reuse existing app stubs and cache application icons properly by applying a registry key change via Group Policy (GPO) or directly on the end-user endpoints:

1. Open regedit and navigate to: HKEY_CURRENT_USER\Software\Citrix\Dazzle
2. Create a new String Value (REG_SZ) named ReuseStubs.
3. Set its value data to true.
4. Completely exit and relaunch the Citrix Workspace App for changes to apply.

📢 CU2 Update Note: Citrix product management has acknowledged this behavior under ticket tracking. A fix is scheduled to roll out with the upcoming 2507 Cumulative Update 2 (CU2) package. For official tracking and updates, bookmark theCitrix Workspace App for Windows Known Issues Registryand monitor theCitrix Community Forumsfor active admin validation threads.