What's new
The following new features and enhancements are available in Citrix Virtual Apps and Desktops™ 7 2507 LTSR Cumulative Update 1 (CU1):
Integration with Nutanix Prism Central on AHV
You can now connect Citrix Virtual Apps and Desktops 2507 CU1 and later to Nutanix AHV clusters through Nutanix Prism Central using a new host connection, Nutanix AHV Prism Central.
The benefits of using Nutanix AHV Prism Central host connection are:
-
Supports machine catalogs with both power managed only and MCS provisioned VDAs.
-
Enables MCS master VM sharing across AHV clusters using template version.
-
Simplifies certificate trust on host connection.
-
Eliminates the need to separately install the plug-in on Cloud Connectors.
For more information, see:
Automated LocalDB installation for Delivery Controller upgrades
When you upgrade Delivery Controllers, the metainstaller automatically installs the latest supported SQL Server Express LocalDB version. This enhancement streamlines your upgrade process. It ensures compatibility for the Local Host Cache database without manual LocalDB installation. For more information, see Automatic update.
WIA Redirection enhancements
Admins can now enable and configure WIA redirection inside HDX sessions through a single Studio policy—no additional registry key configuration on the VDA required.
Virtual Delivery Agents (VDAs)
New Meta Installer for Single Session Core Service Virtual Delivery Agent
A new lightweight Single-Session VDA Meta Installer is now available for Windows 365 Cloud PC and Remote PC deployments. This installer is built on the existing Remote PC installer and serves as a streamlined version of the full Single-Session VDA, delivering essential VDA components along with Profile Management, deviceTRUST, uberAgent, WEM, Backup and Restore, and the VDA Upgrade Agent. It significantly reduces package size and improves installation reliability for cloud-based workloads. Designed for modern Remote PC scenarios, this installer provides a simplified and high-performance option for deploying Citrix workloads on Windows 365 and Remote PC.
Citrix Always on Tracing
Citrix AOT for all CVAD components
The latest update introduces a major expansion of Always-On Tracing (AOT), making it easier to collect, centralize, and analyze logs across the entire Citrix environment. A new configuration experience in Web Studio lets admins define the log server, control the logging scope, and enable Director access from one place, with all settings automatically propagated through the Site database. Director now includes a dedicated Logs view, giving admins real-time visibility into AOT events with search, time filters, categories, severity filters, and machine-level filtering. AOT coverage has been extended to more Citrix components, including all core components with Mac VDAs, Linux VDAs, FAS, and Session Recording Server and more, enabling true end-to-end tracing across control and data plane workflows.
The AOT Log Server has been enhanced with improved ingestion performance and more efficient storage using LZ4 compression. The architecture supports a single Log Server per environment, capable of handling up to 128,000 active component connections and 10,000 log events per second, which is sufficient for most deployments. Updated sizing guidance and performance baselines help administrators plan capacity and tune storage and IOPS based on their environment. Standalone components can now send logs to the Log Server using simple PowerShell commands, aligning them with the centralized logging model. Learn more and start your deployment here.
Exclude draining machines from autoscale calculations
You can now exclude machines undergoing draining due to reboot schedules from Autoscale capacity calculations. This prevents over-provisioning, helping you optimize resource usage. To activate this behavior, set the
ExcludeNaturalRebootDrainingFromAutoscale property to True on your multi-session delivery groups.
This feature applies only to:
-
Multi-session OS delivery groups.
-
Reboot schedules configured with Graceful restart for Cloud or "Re-start all machines after draining session" for On-premises deployments.
For example, consider a delivery group with 10 active sessions. Two machines are draining for a scheduled reboot. Previously, Autoscale might count these two draining machines as available, potentially leading to over-provisioning of new machines. With this feature, Autoscale recognizes and ignores the draining machines. It only counts the truly available capacity. This ensures your Autoscale policy accurately provisions resources, preventing unnecessary infrastructure costs.