Jump to content

DaultApps XML - Slow to apply or not applying at all


Recommended Posts

Posted

I have Windows 10 Eduation 1607 and set the default apps via a GPO using the setting Computer Configuration > Administrative Templates > Windows Components > File Explorer > Default Associations Configuration File. That XML file is located in a read-only area that everyone can read from (confirmed). However I'm noticing a lot of inconsistencies with the XML deployment, specifically it's taking a long time to deploy or it is not applying at all.

 

The main reason this is causing a problem is because of Edge. We use Impero to block the use of Edge as it cannot be monitored at the moment. So the default associations file sets IE11 as the default browser, as well as other things like Adobe Reader being the default PDF viewer.

 

Examples:

 

1) Newly imaged machine that is in the correct OU and had gpupdate /force and rebooted several times can take up to 60 minutes (longest I've seen so far) for the default associations to apply.

 

2) One of our live Win10 test machines in the library had the associations working fine - IE11 as the default browser. I ran DelProf2.exe on the machine and rebooted. Then the default browser was set as Edge and I don't know why.

 

Has anybody come across this behaviour before?

Posted

I have Windows 10 Eduation 1607 and set the default apps via a GPO using the setting Computer Configuration > Administrative Templates > Windows Components > File Explorer > Default Associations Configuration File. That XML file is located in a read-only area that everyone can read from (confirmed). However I'm noticing a lot of inconsistencies with the XML deployment, specifically it's taking a long time to deploy or it is not applying at all.

 

The main reason this is causing a problem is because of Edge. We use Impero to block the use of Edge as it cannot be monitored at the moment. So the default associations file sets IE11 as the default browser, as well as other things like Adobe Reader being the default PDF viewer.

 

Examples:

 

1) Newly imaged machine that is in the correct OU and had gpupdate /force and rebooted several times can take up to 60 minutes (longest I've seen so far) for the default associations to apply.

 

2) One of our live Win10 test machines in the library had the associations working fine - IE11 as the default browser. I ran DelProf2.exe on the machine and rebooted. Then the default browser was set as Edge and I don't know why.

 

Has anybody come across this behaviour before?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...