r/Citrix

We got our renewal today. We actually cut 100 licenses from our count and the costs still went up near 30 percent from last year. We use Citrix Universal for Hybrid Multi Cloud. They are attempting to lock a 3 year deal to keep pricing "low" but still 30 percent more than last year. When we reached out to the rep at Arrow, he asked "why do we need to meet"... Broadcom all over again. Sad our worlds have come to this. Anyone else seeing this issue now?

Hi everyone,

We are currently creating a new golden image for server 2025 for VDA services. Our current production runs a pool of 2019 VDAs.

We run on-premise Citrix Virtual Apps and Desktops (CVAD) 2507 LTSR (Upgrading to CU1 tomorrow)

We have added the new 2025 VDAs to the existing OU / Device collection in Studio. So same policies and environment rules apply everywhere.

the issue:

When any user connects to the 2025 VDA, disconnects and reconnects, the user gets a new / duplicate session instead of being reconnected to the existing session. This ofcourse causes a miriad of issues.

the symptoms:

-> Get-brokersession -username does not return any session on the VDA. Works fine for session on the 2019 environment

-> Citrix Studio shows connections on the machine, but the username field is empty

-> Citrix Director shows the session(s) aswell, but also shows the username correctly

-> When logging in through RDP instead of ICA, Studio also does not show a username, it does see the connection itself like with ICA connections

-> We upgraded the VDA client with CU1 as test, no dice

-> WMI issues has been pointed out by Citrix article as possible issue, but WMI is brand new & clean (we generate a full new windows installation / golden image each change with Ivanti Automation)

-> No error messages found in eventviewer or citrix director

-> The VDA itself shows as registered in Studio

-> Antivirus / ctxuvi exclusions are in place (and the same for 2019 image)

-> FastReconnect and EnforceUserPolicyEvaluationSuccess regkeys did not help

-> Citrix support has not been helpful so far

Id really appreciate any advice. Thanks!

Hey everyone,

Looking for a reality check on offshore VDI performance, specifically regarding the laws of physics.

Our Setup:

• Company: Large, highly regulated enterprise.
• Infrastructure: Citrix Gateway Service with optimized HDX policies for low bandwith.
• VDI Location: mainly US West Coast, some centralus. We try to put them in west coast if we know they are in India but we dont always get that info.
• User Base: Massive offshore contractor workforce (primarily India via Accenture, Wipro, etc.).

The Problem: Management loves this model because it avoids hardware logistics and keeps data in the US. However, the users constantly complain about "VDI slowness." When we dig into the metrics, they are consistently pulling 600ms+ ICA RTT.

To be clear, not everyone from India has that high of RTT, but I would say 350-400ms is pretty standard for these users. The ones that complain are 600+ though.

To make it worse, most of these contractors are using their own firm-issued endpoints, routing through their corporate VPNs or ZTN clients before even hitting our gateway, despite us explicitly telling them this impacts performance.

We constantly get the classic lines: "It’s slower here than at other clients" or "We don't have this issue anywhere else."

I think it's BS. Unless those "other places" are hosting VDI workloads locally in India cloud landing zones or regional datacenters, you cannot bypass the physical distance between India and the US.

My Questions to the Community:

1. If you host VDI in the US for offshore users in Asia/India, are you seeing these same astronomical RTT numbers?
2. If your latency is actually decent, how are you defeating physics?
3. How do you successfully force third-party vendors (Accenture/Wipro) to bypass their internal security stacks/VPNs for the Citrix connection?

Thanks!

EDIT: We have a document we deliver to them about our requirements, including stating that the GWS POP FQDN's need to be excluded from inspection and routed direct. They don't listen, a lot of these IT departments with these firms dont care and or just wont do it but we get blamed for it. All we can do is try to communicate it to our management.

https://preview.redd.it/kfv1nxa7wa2h1.png?width=1023&format=png&auto=webp&s=3b7907dbc4d9fe37768354368d1c6801157105e2

Is anyone facing a high CPU issue with Citrix Workspace 26.3.1.194? This updated on 5/16.

Good evening

We are running a Citrix cloud daas licence which expires in the coming months

Has anyone ran a subscription down past the expiration date?

Do you get any sort of grace period or is it instant termination of service from that point?

Thank you!

Citrix (very belatedly) released this article: https://docs.citrix.com/en-us/provisioning/current-release/advanced-concepts/secure-boot-cert-expiration-ca-updates.html

I'm interested in this part of the article specifically:

"The CA certificate which is used to validate the Windows boot loader. When using Citrix Provisioning, the Windows boot loader is validated by the Citrix Provisioning Network Boot Program which has the CA certificate embedded. Currently, shipping versions of Citrix Provisioning only include the old CA certificate but there will be releases that include the new one as well - Citrix Provisioning will try both old and new certificate when loading the Windows Boot Loader."

As far as I can tell, the version of PVS I'm using (2203 CU7) does NOT contain the new 2023 secure boot cert in the Network Boot Program. But over a year ago, I updated the windows boot loader on all my PVS images so that it was signed by the new 2023 certificate. I also updated the .NVRAM file to include the new 2023 certs on each virtual machine that ISO boots from PVS. They still boot fine, whereas the article suggests they shouldn't, as the version of the Network Boot Program I'm using doesn't trust the new 2023 cert.

Am I missing something here in terms of how this works?

Ever since this morning, I'm unable to open Citrix. I've tried redownloading, waiting, and contacting my IT department but they say they can just login fine. Any idea on how to fix this issue?

https://preview.redd.it/hbiirq2gh42h1.png?width=414&format=png&auto=webp&s=b8eafd580f47c2942d81841ca99626a4fbf9e94c

We're currently rolling out a new Citrix VDA build on server 2025 with VDA version 2511. We're coming off server 2016 and compared to those VDAs we are seeing a huge amount of latency and lag when accessing office client apps as well as new outlook and issues within edge browser tabs. I've been digging into a lot of information and tuning regarding hardware acceleration as well as edge webview2. Unfortunately I have yet to find the best configuration and we're still having pretty noticeable and frustrating issues with the session. Our virtual VDAs are sized pretty well , 8 vcpu and 48 gb of ram so I don't think it's a compute resource issue but can't yet figure the best configuration between GPO's and Citrix policy's to get it running clean. Anyone have any experience running multi session strictly seamless virtual app sessions on sever 2025 with good results that can share any tuning or config changes that helps? Biggest issues are freezing screen or windows not rendering correctly or fully or clicking within the screen taking a few seconds to register.

Well it looks like Citrix pulled the plug on any non LAS activated system last night, at least those running a recent license server.
The license servers checked out all file based licenses permanently, and show 0 file licenses available. LAS continues to function fine.

We had a client who had a left over 715 farm finally die - just a few users on it.
I'm reading of a few others in various channels. I think the fact that there not has been MORE noise is a success for Citrix.
I did see some reports of ancient farms with old license servers continue to function, though I have no evidence. My bet is the license servers are on versions pre LAS and didnt get the memo to shut it down.

Anyone else have a straggler affected?

All my controllers fell into grace licensing for a period of around six hours last night, between around 8PM-2AM ET. It resolved without any action on our part. The error on the controllers suggests they were unable to contact the LAS license server, but the license server was online and accessible. The license server itself had a error that stated it was unable to connect to the License Activation Service. At the same time, the Citrix download site was not functioning, which makes me think this was a Citrix side issue rather than anything on our side. Just wondering if anyone else saw the same thing?

Today, we're excited to announce Citrix Platform Flex.

Citrix Platform Flex is a persona-based platform that delivers secure access and managed infrastructure services through a flexible, predictable credit-based licensing model. No more over provisioning. No more one-size-fits-all. Just the right delivery for each type of worker, with the ability to scale up or down without disruption.

The first product we're announcing under this platform is Citrix DaaS Flex, a managed infrastructure service, powered by Azure. More services will be released over the coming months. The announcement is at: https://www.citrix.com/blogs/2026/05/11/introducing-citrix-platform-flex/ and we've created some webpages with more information starting here: https://www.citrix.com/platform-flex/

We'll be answering questions about it on the Citrix Community site, in a forum dedicated to this topic. Feel free to ask us questions over there: https://community.citrix.com/forums/forum/1654-platform-flex/

Anybody here work at Citrix and can provide insight or current culture?

We've set up a new Citrix Cloud tenant and are trying to work out the process to get it integrated with our Microsoft tenant for our administrative logins.

Our team doesn't have Global Admin in our Microsoft tenant, and we would prefer not to create a Citrix ID for someone on that team that has those rights.

I see an option for an alternative connection method by creating an admin consent URL, but the instructions seem a little unclear.

This is what the documentation says to run: https://login.microsoftonline.com/<tenant url>/adminconsent?client_id=f9c0e999-22e7-409f-bb5e-956986abdf02&redirect_uri=https://portal.azure.com

It's asking for a 'tenant url' (or ID) and the client ID. I'm confused as to where I get these IDs from. Citrix Cloud console? AAD Console? Some documentation says the tenant URL should be the app ID in Azure, but that App ID hasn't been created as I assumed this was supposed to do that part.

Anyone with any experience in this able to point me in the right direction? Or the process of how this is supposed to be done?

Thanks!

Enabled one “recommended” setting in Citrix.
Now half the VDAs unregistered, OneDrive stopped syncing, Teams broke, and users opened 14 tickets before coffee ☕

Looking for design suggestions from others who have dealt with OneDrive in seamless Citrix published apps.

Environment:
- Citrix published seamless applications (NOT full desktop)
- Multi-user server - Windows Server 2019
- FSLogix profiles - most recent version
- OneDrive Files On-Demand enabled
- Users need access to their OneDrive files from within the published app
- Goal is bidirectional sync between local laptop OneDrive and Citrix session

Current behavior:
If a user saves a file from the Citrix app into OneDrive, it syncs up to the cloud and appears on their laptop quickly.

But if a user saves a file from their laptop into OneDrive, the Citrix session does not seem to notice the cloud-side change immediately. It feels like the Citrix OneDrive client is not actively detecting remote cloud changes unless local activity in the session wakes it up.

What we’ve tried / considered:
- Launching OneDrive as part of the app launch script
- Launching OneDrive only when user opens file dialogs
- PowerShell wrappers
- Hidden launcher concepts

Question:
How are others handling OneDrive in seamless Citrix published apps where true bidirectional sync is needed without moving to full desktop delivery?

Is there a supported / sane pattern here, or are we fighting OneDrive’s intended design?

Hello, anyone has migrated from VMware to Hyper-V recently? Any good tools we can use to make the migration seamless? Best practices or lessons learned?

Thanks

I hope everyone is well. We currently use Citrix VDI (2203 CU5) and use UniPrint Infinity v10.0.4 (by Process Fusion) as our universal print solution. We’re having a sporadic printing issue with our VDIs. Users report that at random times throughout random days nothing prints out whenever they submit a print job. They could be printing fine for hours and then it suddenly stops for them. They get no error or warnings. They have to right click the UP agent and hit refresh printers in order for printing to start working again. We have the printers mapped to the thin client device that the VDIs launch from. We also have all virtual channels allowed in our Citrix policies.

On some machines, I see the UniPrint application folder missing. Our AV hasn’t quarantined the folder, there’s no errors in event viewer, we only use one VDI image, and it’s only affecting a single department. I’m so lost.

Vendor help is no good and the process to get client side logs is freaking terrible. Can anyone please offer advice?

Big news coming from Citrix tomorrow. I'll hang out here to answer questions once we go live.

Update2: I can RDP or directly access the VDA via VM console after a reboot, but I see a TermService error in the event logs after an app launch is initiated. Once the error occurs, most of the Windows OS becomes unresponsive. I see other people have run into this issue and Citrix suggests configuring a FastReconnect registry setting (didn't seem to work for me). Looks like I will potentially be building a fresh master image.

---

Update1: At this point I don't believe it is MCSIO related.

I rolled back the template VM to before I installed 2507, used VDA cleanup tool to remove 2203, installed 2507 with default settings (except for adding cloud connectors), and experienced the same issue without the MCSIO option enabled. I'll attempt to reproduce the issue in an isolated machine/delivery group and then add my findings to the original post.

The Logs in DaaS Monitor/Logs showed the affected VDAs successfully registering the AD object (paraphrasing), but nothing else, so I'll need to reproduce the issue and attempt to login to the affected VDA.

======================

Original post:

I upgraded an MCS image from 2203 CU5 to 2507 CU1, I used the latest VDA cleanup tool in the process. When installing 2507 I enabled MCS I/O because I was planning to move to an Image Definition (DaaS if that matters), which requires MCS I/O to be enabled.

I did not immediately move to an Image Definition, I updated the master image to my new 2507 image straight through the machine catalog using MCS. My machine catalog does not have the storage optimization MCS I/O option enabled... I am guessing that is where I got in trouble.

The VDAs would reboot and register, then become unregistered, seemed to become unresponsive because I couldn't gracefully restart them, and would cause Workspace to show "retrieving the ica file" instead of loading the application. Fortunately the service group's scheduled reboot halted itself after 50% of the machines failed to launch and I was able to rollback the image.

I cleaned and re-installed 2507CU1 without the MCSIO option enabled and it will go out again during the next scheduled reboot. I upgraded other machine catalogs to 2507CU1 without any problem but those did not have MCSIO enabled on the VDA side, so I'm assuming that's where my issue was.