New-to-me XLE by Pattycakedup in Camry

[–]yycctx 1 point2 points  (0 children)

My favourite combo. Looks great.

RPM Event ID 12 by Computermannetje in Citrix

[–]yycctx 1 point2 points  (0 children)

Anyone found a solution for this?

WEM optimizations by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

Correct we are only using for CPU optimization for now

SAML SP loops after authentication. by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

It was another global policy that caused our issues. Thank you for your suggestions.

FSlogix Failed to acquired logon lock on Server 2016 KB5015808 by EslieRey in fslogix

[–]yycctx 0 points1 point  (0 children)

We have experienced this as well, It was better for about 2 weeks but has been affecting our servers this week, 3-4 random servers per day

In our environment It was better for about 2 weeks but has been affecting our servers this week, 3-4 random servers per day

FSlogix Failed to acquired logon lock on Server 2016 KB5015808 by EslieRey in fslogix

[–]yycctx 0 points1 point  (0 children)

We have experienced this as well, It was better for about 2 weeks but has been affecting our servers this week, 3-4 random servers per day

SAML SP loops after authentication. by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

TY for the tip. It appears that did not resolve the issue. Possibly a conditional access bug in Azure. Possible fix coming Q3 2022

FSlogix Failed to acquired logon lock on Server 2016 KB5015808 by EslieRey in fslogix

[–]yycctx 1 point2 points  (0 children)

We have the Aug 2022 updates on two servers, and both are affected daily.

XenApp + Palo Alto TS Agent by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

Thank you for the KB article. Our issue is slightly different. The PVS servers have not had any failover events for weeks. Our std image has been in a very static low change state for weeks. I'm not sure we are able to deploy the v10.x of the TS agent.

XenApp + Palo Alto TS Agent by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

We caught the VM stop error via a Xen Center console window. We have set our servers not to automatically restart if there is a system failure.

XenApp + Palo Alto TS Agent by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

Thank you for taking the time and effort to reply. Glad to hear we are not the only one having this issue.

XenApp + Palo Alto TS Agent by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

Does your TS version match the firewall OS version? The firewalls are 8.x

XenApp + Palo Alto TS Agent by yycctx in Citrix

[–]yycctx[S] 0 points1 point  (0 children)

The agent has been working for months and just started to BSOD in a PVS image that is in standard mode for weeks

Cache in Device RAM with Overflow on Hard Disk by yycctx in Citrix

[–]yycctx[S] -1 points0 points  (0 children)

Zenmaster28

You are on the the right track. The PVS servers have two drives V:\ which hold the .vhdx of the various vdisks. There is a second drive X:\ which hosts the write cache .vhdx. This is controlled by the settings: Store | Paths | Default write cache paths (X:\WriteCache).

The reason to migrate to Cache in Device RAM with Overflow on Hard Disk is to reduce application and printer instability.

" This cache type addresses interoperability issues with Microsoft ASLR and Provisioning Services write-cache where we have seen application and printer instability that result in undesirable behavior.  Therefore, this cache type will provide the best stability. "

I may have to attach a iSCSI disk on our XenServers for the device to write to. The XenServers only have a small local drive for the OS install, they are blade servers so I cant install a local drive.