Hi,
In DEM 9.10 there is now support for File Type Associations and Protocols.
The documentation however does not specify the syntax to be used.
Whilst it is easy to set up a FTA in DEM (see below screenshot), I am not sure what the syntax is to use for protocol associations.
Currently I am pushing the config via group policy through a DefaultAssociations.xml file (see attached file), but I would prefer to use DEM for both FTA and Protocol associations
Is there somewhere a good explanation on how to perform protocol associations?
Thanks,
Lieven
Accepted Solutions
Hi Lieven,
There's no fancy UI (yet?) to create protocol associations, but you can do it by creating/tweaking an XML file and applying that via predefined settings or Files and Folders settings.
When DEM persists default app settings via the Default applications Windows Common Setting, it performs a "normal" registry export, but it also creates a Registry\Default Applications.xml file. That file ties file extensions and protocols to specific ProgIDs, very similar to the approach used by DefaultAssociations.xml.
The easiest approach is probably to create a personalization config file to capture Default applications, set up everything to your liking, log off, and take a look at the Registry\Default Applications.xml file from the profile archive that was created. Just remove everything that's not relevant, making sure that the overall structure and file encoding are left intact.
Then create a new predefined setting or Files and Folders setting (manually creating the Registry sub folder among all the other pre-created profile folders that you don't need 
), and drop your Default Applications.xml file into the Registry sub folder.
For Chrome, it would look like something like this:
Hi Lieven,
There's no fancy UI (yet?) to create protocol associations, but you can do it by creating/tweaking an XML file and applying that via predefined settings or Files and Folders settings.
When DEM persists default app settings via the Default applications Windows Common Setting, it performs a "normal" registry export, but it also creates a Registry\Default Applications.xml file. That file ties file extensions and protocols to specific ProgIDs, very similar to the approach used by DefaultAssociations.xml.
The easiest approach is probably to create a personalization config file to capture Default applications, set up everything to your liking, log off, and take a look at the Registry\Default Applications.xml file from the profile archive that was created. Just remove everything that's not relevant, making sure that the overall structure and file encoding are left intact.
Then create a new predefined setting or Files and Folders setting (manually creating the Registry sub folder among all the other pre-created profile folders that you don't need ), and drop your Default Applications.xml file into the Registry sub folder.
For Chrome, it would look like something like this:
