Pro/Con: Are you using ADMX Templates for CTX Policies or Studio?

For DaaS I do web studio as you'll always have the latest

Studio, if only because you can make real-time changes without having to wait for any sort of replication. Haven't done ADMX for Citrix in like a decade, I think.

As I'm a fan of CR over LTSR, I'm using Studio as well. We started this discussion in our team and I'm curious about your opinion.

Pros: • Quicker turnaround time for applying/changing/deleting settings • No need to manage templates Cons: • Management overhead (looking in two consoles to get a full RSoP)

I always use studio; I don't want to give Citrix Admins permissions on GPO MGMT Console

ADMX templates mostly with a few Studio policies. We have a lot of clients and managing in Studio would be very difficult to tell which policy applied where. GPO I can see links to OUs and know who the policy will apply to (for the most part). We use AGPM from Microsoft to manage who can make changes to Policies and have an approval process, but change tracking and ability to revert changes quickly if needed. We have multiple Citrix sites and managing policies often would require duplicating work in every site, depending on the scope. Some settings need to be set via registry entry and aren't in Studio, so it is more consistent to have most things in GPO. It's mostly a matter of trying to use the best tool for the situation. I have a pretty good mix.

Either get the job done, I prefer setting Citrix policies in Studio. I would suggest using one or the other, to avoid conflict and confusion.

I second that - pick one and use that exclusively. I had somebody at a previous job use both, and after the first time we ran into policy issues, I forced them to move all settings to Studio (since we agreed to use that over GPO).

I set my security baseline, device redirection, audio and graphic policies via studio. All the rest has to be done via GPO or WEM. Certain policies like session limits for multi session are only available via GPO.

the danger of putting citrix policy inside group policy is that if you go to look at the group policy without the snapin installed you won’t see any of the citrix policies. I’ve had admins delete entire policies because they thought they were blank…