none
File associations are lost when user account is migrated from one domain to another domain (SID changes)

    Question

  • Hello,

    Currently we are in the middle of a migration project. We are migrating users from child domains to the root domain of one organization.

    The user accounts are migrated with powershell using Move-ADObject cmdlet. This works as expected. The SIDHistory attribute is updated correctly.

    Recently we received complaints from some *migrated* users - they lost their default/custom file associations. This happens only on Windows 8/Windows 8.1.

    What happens:

    1. the user is migrated and logs on
    2. her profile loads and everything's preserved (as expected)
    3. the user clicks on a .jpeg file (previously associated with program XYZ)
    4. OS asks the user to choose a program to open the file with
    5. the user chooses a default program XYZ and the file opens
    6. when the user clicks on a .jpeg file again - OS asks to choose a program again

    i.e. the settings are not preserved.

    Our investigation shows that it is connected with the UserChoice registry key and the HASH value under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.SomeExt

    According to this blog  the HASH is calculated based on user's SID. But after the migration the user has new SID and the HASH becomes invalid and we hit this:

    "However In Win 8, the registry changes are verified by a hash (unique per user and app)  that detects tampering by apps. In the absence of a valid hash, we ignore the default in the registry."

    Currently deleting the UserChoice key for all associations solves the problem. But the user has to make all her customizations again which is undesirable.

    Is there any supported way to fix this? Why the OS doesn't update the HASH after the first logon when the SID has changed as it updates the SID for the ProfileList key? 

    This could become big issue in large migrations.


    Wednesday, April 8, 2015 10:57 AM

Answers

  • Hello Petar K. Georgiev,

    Please check the following article to change the registry key to change back to the default file type associations.
    http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html

    Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best regards,
    Fangzhou CHEN


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, April 9, 2015 8:26 AM
    Moderator

All replies

  • Hello Petar K. Georgiev,

    Please check the following article to change the registry key to change back to the default file type associations.
    http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html

    Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best regards,
    Fangzhou CHEN


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, April 9, 2015 8:26 AM
    Moderator
  • This is a known issue bug on Windows 8, Windows 8.1 and Windows 10 computers prior to RS1.
    A fix exists in RS1 builds after 14821.
    Those needing a fix on Windows 10 TH2 should verify the fix in RS1 and request a backport of the RS1 fix for TH2.

    Wednesday, March 23, 2016 4:10 PM
  • Good day, Peter K. Georgiev.
    I was faced with an identical problem. Only kachetstve migration using Quest manager 8.10. You got to find a solution, in addition to removing UserHoitse?
    Saturday, March 26, 2016 7:42 AM
  • Hello.
    How to solve this problem in Windows 8.1, not removing UserHoitse?
    • Proposed as answer by k-boy Thursday, March 31, 2016 2:38 PM
    • Unproposed as answer by k-boy Thursday, March 31, 2016 2:38 PM
    Saturday, March 26, 2016 7:44 AM
  • A work around is to backup all user files not on the network drive as well as bookmarks and then delete the user's related logon profile, and after that user can now login with a new profile.

    I'm having the same problem and have managed to solve it for some users by deleting the profile but now i have one complicated profile which i won't want to use this method.

    Is there any quick fix for this on windows 8.1?

    • Proposed as answer by k-boy Thursday, March 31, 2016 2:39 PM
    Thursday, March 31, 2016 2:39 PM