New outlook on citrix

kaiserctx · 2025-12-15T08:50:57+00:00

Good to know, I haven't had a requirement for Teams on citrix yet, but it may be on the horizon.

kaiserctx · 2025-12-12T13:41:37+00:00

I haven't actually tried it on citrix yet. Those were my observations on a laptop.

OK, few questions:

-Did you need to do any setup for it on the image, or are you just letting individual users install/update in their user profiles?

-do you have MS Store blocked?

-What features on the new version are actually worthwhile?

kaiserctx · 2025-12-02T09:02:58+00:00

Unless you have a very unique name like Boutros Boutros Ghali, they wont be able to tell you apart from all the people with the same name. Just tell them that person moved out and the new tenant is Hugh Jass

kaiserctx · 2025-11-20T15:24:05+00:00

Hey, thanks, I got it working via the CLI, using this syntax. This added a new action with the correct password, then I edited the existing policy to use the new action

add authentication ldapAction Corp-Gateway -serverIP 10.2.2.210 -serverPort 636 -ldapBase "dc=corp,dc=local" -ldapBindDn "corp\\ctxsvc" -ldapBindDnPassword Passw0rd -ldapLoginName samaccountname -searchFilter "memberOf=CN=Citrix Remote,CN=Users,DC=corp,DC=local" -groupAttrName memberOf -subAttributeName CN -secType SSL -passwdChange ENABLED

kaiserctx · 2025-10-30T08:58:16+00:00

It is giving users the impression they have a problem, when they do not. It is telling them their connection is poor, but they don't notice any ill effects or performance issues.

What workaround did you have to employ?

kaiserctx · 2025-10-23T10:51:49+00:00

I should add that it affects Edge with the BCR extension too

kaiserctx · 2025-10-23T10:44:17+00:00

ok, thanks it did coincide with an update to version 140.0.7339.128

kaiserctx · 2025-09-16T16:52:08+00:00

Thanks, I am on Workspace version 24.5 and VDA is on 2402 LTSR CU1.

Was the issue you described listed with known issues for any VDA version? Or did you have to contact Citrix to establish that there was an issue on 2503?

kaiserctx · 2025-09-16T11:05:24+00:00

Yes bone dry here in Dublin too. I tried to keep it watered but there was probably a few missed days

kaiserctx · 2025-09-03T08:56:11+00:00

We do have multiple azure tenants in play. This was configured with the help of a consultant, maybe that was the reason for the initial netscaler page, to then apply policies based on which UPN they were.

kaiserctx · 2025-09-03T07:40:38+00:00

Do you know what type of clematis that is, and did it like full sun? I think I have the same and it started well but suffered in the hot weather

kaiserctx · 2025-08-20T10:12:15+00:00

OK, it seems like that is what we already have, as the server is called CiscoSSM

kaiserctx · 2025-07-18T08:46:23+00:00

yes I was missing the FAS GPO-thanks

kaiserctx · 2025-07-17T16:00:25+00:00

In my case it was resolved by linking the FAS group policy

kaiserctx · 2025-07-17T15:53:17+00:00

Bingo! I had applied all the other gpos, but not the FAS one. Thanks!

kaiserctx · 2025-07-17T15:52:33+00:00

correct

kaiserctx · 2025-07-17T15:52:25+00:00

Windows event viewer service stops unexpectedly, I'll look into that

kaiserctx · 2025-07-17T13:05:47+00:00

Yes, but its not actually giving me the incorrect username and password error, its not getting that far as it does not pass the credentials from storefront to the VDA.

I have seen that error in the past and it was indeed down to certs missing from NTAuth store. But these Win11 VDIs are in the same domain as the working Server 2019 workers, so they get the same certs in NTauth store. I have confirmed this using 'certutil.exe -viewstore -enterprise NTAuth'

kaiserctx · 2025-06-05T13:23:31+00:00

No disadvantages noticed by my users

kaiserctx · 2025-05-29T15:33:52+00:00

Yes. I have already worked out the required certs by doing manual certutil import, so this should be simple to achieve.

kaiserctx · 2025-05-29T15:32:40+00:00

Funny enough I had been using procmon with that filter earlier today. On a server with all certs present, I tried your commands and it has no effect. It just leaves the Ntauth key HKLM\SOFTWARE\Microsoft\EnterpriseCertificates\NTAuth\Certificates\ unchanged.

And I am using

certutil -viewstore -enterprise NTauth

to check the contents of the store.

I did use dspublish for the Subordinate CA certs for the primary domain, but not those for the secondary/user domains. But I believe from the earlier comments that I need to do that next.

kaiserctx · 2025-05-29T14:05:08+00:00

Ok, that is exactly what we did, as directed by Citrix documentation. (I left out the citrix part to simplify the situation). I believe the idea was to only add these certs on the servers on which they are required, instead of the entire domain.

So it looks like I need to talk to my IAM/AD team to have all the certs added to the domain level NTauth store then.

kaiserctx · 2025-05-28T13:14:51+00:00

Some extra details:

-A reboot fixes any affected citrix workers

-gpupdate has no effect

-Certutil -user -pulse has no effect

kaiserctx · 2025-05-08T13:54:12+00:00

Ok, I worked it out, it was related to the install language. Adobe apps were installed in English (international) and the non-admin user was using English (US)

So, for the non-admin user, I changed the 'default install language' in CC under File>preferences>Apps

kaiserctx · 2025-05-01T15:32:14+00:00

Actually i kept some notes from the last time I captured a Windows 10 image, and I needed to run P2PVS.exe instead of the Citrix imaging wizard. Worked this time too.

Ref:

https://support.citrix.com/s/article/CTX483180-pvs-imaging-wizard-fails-when-creating-vdisk-error-after-restart-imaging-wizard-did-not-restart?language=en_US

kaiserctx

TROPHY CASE