none
make IE11 default browser in windows 10 using GPO RRS feed

  • Question

  • Hi Expertz,

    I am trying to make IE 11 as default browser in windows 10 1511 machine & following link below

    https://technet.microsoft.com/itpro/internet-explorer/ie11-deploy-guide/set-the-default-browser-using-group-policy

    My followed steps are::

     

    1>     1>  Taken a windows 10 1511 reference machine where IE11 was made default browser manually from settingsàsystemsàdefault appàset defaults by app—select IEàset this program as defaultà OK

    2>      2>Exported this default app changes using dism

    >Dism /Online /Export- DefaultAppAssociations:c:\defaultassociations.xml

     

    3>      3>Copied this xml file from ref VM & paste in DC in location

    c:\windows\system32\defaultassociations.xml

    In Domain Controller side

     

    4>     Tools-->Group Policy Management-->default domain Policy-->edit-->computer configuration-->Administrative template-->Windows ComponentsàFile exploreràset a default association configuration file -->enable

    In option tab-->paste-->c:\windows\system32\defaultassociations.xml

    4>

    1>      In client VM verified whether policy has been appliedàwinkey +Ràcmdàgpupdate /force

    Gpresult /scope computer /r

     

    2>      IE11 was not set as a default browser in settings in client windows 10 VM

    Guys I could be missing somewhere, Kindly guide me where I am wrong???


    • Edited by Dhanraj B Thursday, June 9, 2016 9:28 AM
    Wednesday, June 8, 2016 1:22 PM

Answers

  • Sorry, Tang,

    I corrected what wrongly I have typed, and exactly followed what you have shown above,

    & this is where I was mistaking . As I am implementing default file association in my domain I should have put the defaultassociations.xml file in a shared Location. SO, upon policy update the client device can look for that file.

    I renamed the file as default.xml & put in shared location in DC---> \\DC\sharefolder\default.xml

    & it worked.

     




    • Edited by Dhanraj B Thursday, June 9, 2016 10:54 AM
    • Marked as answer by Dhanraj B Thursday, June 9, 2016 10:55 AM
    Thursday, June 9, 2016 9:29 AM
  • Hi,

    Yes, your line of thought is correct.

    Firstly, we export default app association xml file by DISM command on a Windows 10 machine.

    Secondly, copy this xml file into DC’s c:\windows\system32 directory, that’s ok.

    But, according to the content of your post, you next open Local Group Policies Editor from Run dialog, this operation is strange.

    As a DC admin, we need to create a GPO in Group Policy Management for clients, then edit this GPO in the Group Policy Management Editor interface. After these, our configurations on DC can be applied to clients.

    There is no doubt that all your measure are correct, you just forget that you are operating on DC side rather than client side.

    Have a try again.

    Regards


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact tnmff@microsoft.com

    • Marked as answer by Dhanraj B Thursday, June 9, 2016 10:49 AM
    Thursday, June 9, 2016 6:24 AM
    Moderator

All replies

  • Hi,

    Yes, your line of thought is correct.

    Firstly, we export default app association xml file by DISM command on a Windows 10 machine.

    Secondly, copy this xml file into DC’s c:\windows\system32 directory, that’s ok.

    But, according to the content of your post, you next open Local Group Policies Editor from Run dialog, this operation is strange.

    As a DC admin, we need to create a GPO in Group Policy Management for clients, then edit this GPO in the Group Policy Management Editor interface. After these, our configurations on DC can be applied to clients.

    There is no doubt that all your measure are correct, you just forget that you are operating on DC side rather than client side.

    Have a try again.

    Regards


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact tnmff@microsoft.com

    • Marked as answer by Dhanraj B Thursday, June 9, 2016 10:49 AM
    Thursday, June 9, 2016 6:24 AM
    Moderator
  • Sorry, Tang,

    I corrected what wrongly I have typed, and exactly followed what you have shown above,

    & this is where I was mistaking . As I am implementing default file association in my domain I should have put the defaultassociations.xml file in a shared Location. SO, upon policy update the client device can look for that file.

    I renamed the file as default.xml & put in shared location in DC---> \\DC\sharefolder\default.xml

    & it worked.

     




    • Edited by Dhanraj B Thursday, June 9, 2016 10:54 AM
    • Marked as answer by Dhanraj B Thursday, June 9, 2016 10:55 AM
    Thursday, June 9, 2016 9:29 AM