2 XMLs causing eachother to disable - StartLayout and DefaultApps

[Obee1]

Hi all

 

We have an issue whereby we have created a start layout in Windows 10 1803. We have exported the layout via Powershell and set the users to use this layout.

USER CONFIGURATION>POLICIES>ADMINISTRATIVE TEMPLATES>START MENU AND TASKBAR>START LAYOUT

This works fine.

 

However another issue that we have is that Windows 10 likes to use Edge as the default PDF viewer. Additionally if this default app is changed it likes to give users the opportunity to select which app to use. We need to use Adobe Reader for this rather than Microsoft Edge due to some of the functionality.

I have managed to fix this issue by creating a further xml to set the default app to Adobe Reader.

COMPUTER CONFIGURATION>POLICIES>ADMINISTRATIVE TEMPLATES>WINDOWS COMPONENTS>FILE EXPLORER>SET THE DEFAULT ASSOCIATIONS CONFIGURATION FILE

This also works fine.

 

The problem arises that by using the Default Associations File, it stops the start menu layout file from working.

 

I have tried merging all into one file, but that doesn't seem logical and doesn't work.

 

 

 

Does anyone know if there is a limitation to how many xml files you can apply via GPO. If so is it one, and the reason this isn't working?

Anyone had the same issue and know any way around it?

[SystemsAd]

May sound silly and don't shoot me for this, but are you applying computer and user policies via the same GPO?

 

I am deploying both start menu and default file associations to the user and PC respectively. Although I am using 1809...

[bald_pig]

have you run gpresult? should tell you the cause of the conflict.