Windows 10 1703 - Default App Association for Migrated Users (USMT)

%3CLINGO-SUB%20id%3D%22lingo-sub-113568%22%20slang%3D%22en-US%22%3EWindows%2010%201703%20-%20Default%20App%20Association%20for%20Migrated%20Users%20(USMT)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-113568%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anybody%20had%20issues%20deploying%201703%20with%20USMT%20and%20deploying%20default%20file%20associations.%20What%20we%20are%20trying%20to%20achive%2C%20is%20to%20deploy%20IE%20as%20the%20default%20browser%2C%20this%20works%20for%20new%20users%20who%20login%2C%20however%20migrated%20user%20profiles%20still%20have%20edge%20as%20the%20default.%3C%2FP%3E%3CP%3Ehave%20tried%20the%20new%20method%20of%20use%20the%20(clip%20from%20xml)%3A%3CBR%20%2F%3E%3CASSOCIATION%20identifier%3D%22%26quot%3Bhttps%26quot%3B%22%20progid%3D%22%26quot%3BIE.HTTPS%26quot%3B%22%20applicationname%3D%22%26quot%3BInternet%22%20explorer%3D%22%22%3E%3C%2FASSOCIATION%3E%3C%2FP%3E%3CP%3Ebut%20it%20looks%20to%20be%20an%20issue%20with%20USMT%20and%20default%20file%20associations.%3C%2FP%3E%3CP%3EAnyone%20experienced%20this%20issue%20before%20and%20got%20a%20fix%20for%20it%3F%20We%20are%20not%20keen%20on%20applying%20the%20GPO%20to%20force%20the%20file%20associations.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159737%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20101703%20-%20Default%20App%20Association%20for%20Migrated%20Users%20(USMT)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159737%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Dale%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20the%20tip%20it%20worked!!%3C%2FP%3E%0A%3CP%3EBTW%20Im%20doing%20all%20this%20on%20the%201709%20version.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20applied%20the%20reg%20key%20in%20the%20re-image%20task%20sequence%2C%20and%20user%20data%20is%20restored%20during%20the%20task%20sequence.%20When%20the%20user%20logs%20in%20file%20associations%20are%20all%20OK.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20did%20notice%20if%20a%20re-image%20is%20done%20on%20the%20same%20PC%20again%2C%20and%20if%20user%20data%20is%20captured%20then%20restored%2C%20the%20file%20associations%20break%20again.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20the%20key%20you%20mentioned%20exists%20on%20the%20PC%20before%20a%20user%20logs%20in%2C%20then%20the%20same%20key%20then%26nbsp%3Bgets%20created%20under%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHKCU%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CFileAssociations%5CUpgradeChoice%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20causes%20the%20file%20associations%20to%20break%20on%20a%20capture%20and%20restore.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIf%20i%20delete%26nbsp%3BHKCU%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CFileAssociations%5CUpgradeChoice%20before%20the%20capture%20then%20its%20works%20again.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EDid%20Microsoft%20explain%20why%20this%20is%26nbsp%3Brequired%3F%20As%20you%20mentioned%20before%20trying%20this%20the%20ApplyOnUpgrade%20and%26nbsp%3BOverwriteIfProgIdIs%20didnt%20help%20either.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20also%20noticed%20on%20a%201709%20Pro%20version%2C%20non%20Domain%20joined%20PC%20the%20HKLM%20and%20HKCU%20keys%20already%20exist.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThanks%20again%20for%20all%20your%20help%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EMo%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158166%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%201703%20-%20Default%20App%20Association%20for%20Migrated%20Users%20(USMT)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158166%22%20slang%3D%22en-US%22%3E%3CP%3ELet%20me%20know%20how%20you%20go.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158163%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%201703%20-%20Default%20App%20Association%20for%20Migrated%20Users%20(USMT)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158163%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mo%2C%3C%2FP%3E%0A%3CP%3EI%20ended%20up%20getting%20a%20response%20from%20MS.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ELog%20on%20one%20Windows%201703%20client.%3C%2FLI%3E%0A%3CLI%3ERun%20regedit.exe%2C%20locate%20key%20HKLM%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CFileAssociations%5CUpgradeChoice%20(if%20the%20key%20does%20not%20exist%2C%20create%20one%20with%20the%20name.)%3C%2FLI%3E%0A%3CLI%3ECreate%20a%20DWORD%20value%20named%20AppUpgradeVersion%2C%20set%20it%20to%202.%3C%2FLI%3E%0A%3CLI%3EMigrate%20a%20user%20to%20this%20client.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EI%20still%20had%20issues%20with%20associating%20PDFs%20with%20Adobe%20Reader%2C%20but%20MS%20came%20back%20and%20said%20that%20it%20was%20an%20adobe%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158130%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%201703%20-%20Default%20App%20Association%20for%20Migrated%20Users%20(USMT)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158130%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Dale.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDid%20you%20resolve%20this%20issue.%20I%20am%20experiencing%20the%20same%20problem%2C%20wondering%20if%20maybe%20there%20is%20a%20way%20to%20exclude%20file%20associations%20from%20USMT%20capture%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethanks%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Has anybody had issues deploying 1703 with USMT and deploying default file associations. What we are trying to achive, is to deploy IE as the default browser, this works for new users who login, however migrated user profiles still have edge as the default.

have tried the new method of use the (clip from xml):
<Association Identifier="https" ProgId="IE.HTTPS" ApplicationName="Internet Explorer" ApplyOnUpgrade="true" OverwriteIfProgIdIs="AppXz8ws88f5y0y5nyrw1b3pj7xtm779tj2t" />

but it looks to be an issue with USMT and default file associations.

Anyone experienced this issue before and got a fix for it? We are not keen on applying the GPO to force the file associations.

4 Replies

Hi Dale.

 

Did you resolve this issue. I am experiencing the same problem, wondering if maybe there is a way to exclude file associations from USMT capture

 

thanks

 

Hi Mo,

I ended up getting a response from MS.

 

  1. Log on one Windows 1703 client.
  2. Run regedit.exe, locate key HKLM\Software\Microsoft\Windows\CurrentVersion\FileAssociations\UpgradeChoice (if the key does not exist, create one with the name.)
  3. Create a DWORD value named AppUpgradeVersion, set it to 2.
  4. Migrate a user to this client.

I still had issues with associating PDFs with Adobe Reader, but MS came back and said that it was an adobe issue.

Hi Dale 

 

Thank you for the tip it worked!!

BTW Im doing all this on the 1709 version.

 

I applied the reg key in the re-image task sequence, and user data is restored during the task sequence. When the user logs in file associations are all OK.

 

I did notice if a re-image is done on the same PC again, and if user data is captured then restored, the file associations break again.

 

If the key you mentioned exists on the PC before a user logs in, then the same key then gets created under

HKCU\Software\Microsoft\Windows\CurrentVersion\FileAssociations\UpgradeChoice

 

This causes the file associations to break on a capture and restore.

If i delete HKCU\Software\Microsoft\Windows\CurrentVersion\FileAssociations\UpgradeChoice before the capture then its works again.

 

Did Microsoft explain why this is required? As you mentioned before trying this the ApplyOnUpgrade and OverwriteIfProgIdIs didnt help either.

 

I also noticed on a 1709 Pro version, non Domain joined PC the HKLM and HKCU keys already exist.

 

Thanks again for all your help

Mo