The user can change the file associations after logon, because the corresponding UI is not locked down. Thus, there is no need to do anything more than update the XML file with new file associations, and they also apply to the clients. If the file is updated with a new file association, the client will check the content every time someone applies Group Policies. XML file to the machines and apply it from there. Make sure that domain computers can read both from the share and from NTFS. I used a file share in the example above. We then add this file to our OS deployment Task Sequence after installing and restarting Windows. cmd file in that directory with the following content: OFFĭism.exe /online /Import-DefaultAppAssociations:'%~dp0defaultapps.xml' I usually work with the /Online method.įirst, create a package in Configuration Manager that contains the defaultapps.xml file and then create a. You can import the default file associations during OS deployment in Configuration Manager using a Run Command Line step in the Task Sequence, either using DISM /Online when the OS is installed or with DISM /Offline when the Windows image is applied and the computer has not yet started the newly installed OS. Deploying default file associations with SCCM Now you can deploy the default file associations with one of the following methods. In my example below, I removed everything that is not associated with Adobe Reader DC, so we end up with the following XML file: The answer is, yes, you can import just the association you need. People often ask me if it is possible to deploy just one file association or if they must use the entire file, which also contains all the default settings. XML file with all the file associations from that user.

Adobe reader pdf windows 10