Deploying default file type associations WITHOUT Group Policy? Defaultapps.xml
How can I deploy File Type Associations/Defaultapps.xml using SDA?
I see many guides on how to do this using Group Policy, but that would override end users being able to set their own associations.
I tried loading my Defaultapps.xml as a post installation task and uploading the xml as the installer, and then using this command:
Installation fails on this command.
Also tried saving the command as a cmd file and zipping that with the defaultapps.xml and uploading the zip file as the installer (this has worked for some other apps like Alertus) which seemed to work but did not set any defaults.
How else can I set the default apps in a way that the users can change them if they desire? Local Group Policy? Another method of applying the XML?
Answers (2)
I run a batch file to sysprep my masters and one line exports the app asso. I use a mid level task to re-import after sysprep
Dism /Online /Export-DefaultAppAssociations:c:\temp\AppAssoc.xml
powershell Export-Startlayout -path c:\temp\layout.xml
start /wait notepad.exe C:\Windows\w2d\tmccimageversion.reg
start /wait regedit /s C:\Windows\w2d\tmccimageversion.reg
start /wait regedit /s C:\Windows\w2d\sus.reg
cd\windows\system32\sysprep
sysprep /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\adminw10x64.xml
NOTE: this is a custom deployment but it is same for system images
I ended up making a post installation task and got that to work. I had to include both the cmd and xml in the zip file and just called the cmd in the full command line box.