Last night Citrix released Citrix Receiver 4.3 that includes ADMX templates to manage Citrix Receiver Group Policy settings. Microsoft introduced the ADMX templates when Vista/Server 2008 was introduced in 2006, so it was about time for Citrix to come up with template files in that format instead of the old ADM based files.
After installing the Citrix Receiver 4.3 that can be downloaded from here you’ll find the new ADMX/ADML files in the following location:
“C:\Program Files (x86)\Citrix\ICA Client\Configuration”
But it looks like whoever was in charge of provding the new ADMX templates did not really care about structures. The files are placed all over the place. .
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\HdxFlash-Client.admx”
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\ica-file-signing.admx”
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\receiver.admx”
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\ica-file-signing.adml”
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\receiver.adml”
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\en-US\HdxFlash-Client.adml”
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\en\receiver_usb.adml”
“C:\Program Files (x86)\Citrix\ICA Client\Configuration\en\receiver_usb.admx”
But okay, those familiar with Group Policy templates will know where to place which files. Now comes the next surprise, when opening the Group Policy editor there are multiple nodes for Citrix Components.
When opening any setting, the supported on description is as following: ADMX Migrator encountered a policy that does not have a supportedOn value.
This explains it all, one would assume that by now it should be known that the ADMX migrator is okay for an initial conversion, but that once converted from ADM to ADMX still some manual work is required. To be honest I really like Citrix technology, but I am a bit dissapointed how this was done. I would expect from a Company like Citrix that they would put some effort in getting such things right.
This all has a bit of a bad taste and one might hope that the settings itself all work as expected.
Dear Citrix consider getting this right the next time please.
Hi Alex,
Are you aware of http://www.carlstalhood.com/receiver-for-windows/#admx, which points out how to import the right files into either the sysvol or local policy definitions? This way, you won’t end up with 3 nodes.
I found this as I was researching the same error message. Do the policies still actually work with Receiver? I’m about to start testing and was just curious. Thanks!
I agree with you, come on Citrix…
It’s like the Feature Pack 2 on XenDesktop 7.6.
After downloading it, you see it’s just a bunch of .exe in a zip file. Couldn’t they package it into one installer?
After focusing on client experience, they should also take into account the “Admins experience”…
Briefly looking at the files they, like previous Citrix ADMX files, were converted using the Full Armor tool which doesn’t convert the some elements of the Adm files properly (It leave out the registry key that they entries are meant to change.) I’ve not checked through the new ones but I know the old admx files did not work properly. I have spent the time creating/fixing the Citrix adm/admx file see. http://discussions.citrix.com/topic/280022-icaclientadm-available-as-admx/?p=1851164
Thanks for sharing David and for making the effort to fix this.
I still hope Citrix gets it right, as we would not want to spend hours of fixing templates each time they release a new version of the Receiver. Cheers, Alex
I’ve opened a case at Citrix regarding the new Receiver 4.3. We can’t type the “@” sign in the password field with swiss keyboards (FR-CH / DE-CH). We got a private patch.
I also suggest you guys to read the updated “About” section of the Receiver 4.3 where it talks about slow enumeration of apps. Works like a charm!
Cheers
David