This message was deleted.

We have the same issue, the workaround is to expand the citrix computer section first and then the user one.

My workaround was to migrate them all to studio - annoying but solid 😳

not sure that's better

I’m with James - moved everything to Studio and haven’t looked back.

Can confirm that this is happening in my lab setup as well

Not sure why Citrix Admins across the world are still using the GPO policies and not the Studio ones. Am I missing something?

One console for all policies

Yeah but most orgs don’t allow Citrix admins to get gpo objects permissions. So creating a new policy object can require additional actions from AD Admins. In Studio the Citrix Admin can just create the settings and bam! It’s working.

Sure and a valid point :)

We use GPO policies rather than Studio because Citrix Cloud Studio crashes constantly in the Policies section

We’re not on cloud, but one of the biggest benefits for me was instant change capabilities. That bailed us out a few times when we found issues, and would have been a mess had we had to wait for GPO replication and/or reboots. That said, Studio could be a little snappier.

@James Rankin We have a couple of customers on Cloud and we don't have Studio crashing in the Policy section so wondering if one of your Studio policies are making Studio crash

We have a case open with Citrix, I think it is fairly common

The Citrix Cloud environment is far away from being perfect but we had no issues like the one you mentioned, for any of our customers' tenants. We did have others! I smile every time I stumble on one of @Carl Stalhood's posts and see he's controling Citrix Policies from GPOs :)

Pretty common IME for customers to do it that way

There is no right or wrong - in multi site, have fun managing Citrix Policies without them being nested in GPO (unless you are in Cloud), I personally use Studio if it's a single site deployment, but that's typically because i like to have Citrix components managed together - and then you land on the limitations of Cloud where whilst you can have multi site and drive it all in studio, you can't use some policies (like some of the printer ones) as it simply doesn't work and you have to use a combination of both - right place for right architecture with everything, Policies are no exception

Our XA admins use GPO for their stuff in our multi-site environment. I still use Studio, though I do have to duplicate everything. Minor inconvenience as far as I’m concerned, since we don’t have to really do much work there. I can see why that would sway others from it, though.

We also see this issue. We use GPO for Citrix policies because we have templates which are much easier to import than with studio.

I'm happy to report this is fixed with 1912.