![]() ![]() Device/Vendor/MSFT/Policy/Config/Citrix~Policy~ICAClient~DPI/Policy_DPI Device/Vendor/MSFT/Policy/Config/Citrix~Policy~ICAClient~AutoUpdate/Policy_EnableAutoUpdatePolicy Name: AutoUpdate ltsr 7 days from release Device/Vendor/MSFT/Policy/Config/Citrix~Policy~ICAClient~Storefront/Storefronts Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Citrix/Policy/ReceiverADMX ![]() Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Citrix/Policy/CitrixBaseADMX So follwoig this I was able to set the following Open, or restart, the CWA and the discovery process should start. Sync the client, check "HKLM\Software\Policies\Citrix\Receiver" and you should have a 'Sites' key with a 'Store0' item and value as per above. OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Citrix~Policy~ICAClient~Storefront/Storefronts So the value to be put into the Intune OMA-URI entry for setting a Store is: Storefront string = SAMLStore On Appstore via MDM In my case I am configuring remote devices so will be using a Gateway URL format, with a Store name of SAMLStore, and a description of "Appstore via MDM" so I can follow it in the registry and CWA app. So we start with our Store index value (which becomes the name of the registry item), separated by the above string, and then our usual Storefront store value as per. Effectively, it wants a 'grid' structure so two 'columns' separated by the Unicode character 0xF000 which we need to enter as the string  You can then stick in OMA-URI items in the same Device Configuration Profile.Īll the info you need to decipher it all is fortunately documented by Microsoft here:įor specifying the Store (the most common i guess), we can deduce from the ADMX that the element needs to be of the type 'List-ID' which has a specific syntax (see MS links above). These will correspond to the entries you can see in the ADMX files and should help with formatting the OMA-URI paths. After a short period of time for the ADMX's to be processed you should then see your potential configuration items under "HKLM\Software\Microsoft\PolicyManager\ADMXDefault\xxx\Citrix-Policy-ICAClient". ![]() Once you sync a client and look in "HKLM\Software\Microsoft\PolicyManager\ADMXInstalled\.\Citrix\Policy" you should see both CitrixBase and Receiver entries as per your naming in the ingestion policy entries in Intune. With that section removed, you can then paste the remaining content of receiver.admx into it's ADMX Ingestion item. I got a load of 912 events in the DeviceManagement-Enterprise-Diagnostics-Provider/Admin log on the client, and working through them got me to this point. The CitrixBase ADMX you can copy/paste straight in, but crucially before you copy/paste in the contents of receiver.admx you need to remove the 'ica-file-signing' section. This took me some time to figure out - but as is the way with these things, is quite straightforward once you know :).įirst you need to ingest both the citrixbase.admx and the receiver.admx - you can do these both, and the OMA-URI configuration items, in a single Device Configuration Profile. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |