I am upgrading from Office 2010 Pro to Office 2013 Pro. In my test, we discovered that the MRUs are not getting migrated over from the Office 2010 Pro applications into the Office 2013 Pro applications.   I am using the Microsoft Office 2013 OCT to do the configurations.  In the OCT, I have "migrate user settings" checked, but that did not work for the users MRUs.  I came across the following link

http://social.technet.microsoft.com/Forums/office/en-US/67b3622f-5b7c-4c57-b71d-c8c7de6f7da9/office-2010-pro-to-2013-not-migrating-settings-and-recent-history?forum=officeitpro

That suggests manually creating the Migration key with sub keys like below

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000d
"Lang"=dword:00000409

On the test machine that I was using and had installed Microsoft Office 2013 Pro on, I found the keys listed as follows

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000e
"Lang"=dword:00000000

1) I would like to know which is correct subkey ("UpgradeVersion" and "Lang") to use?

2) Since I am using the OCT, can I add or import them into the OCT add registry entries section?

Thanks for your help.

Since you are doing an uninstall-upgrade the MRU list will not migrate by default.

"UpgradeVersion"=dword:0000000d means Office 14.0, also known as Office 2010

"UpgradeVersion"=dword:0000000e means Office 15.0, also known as Office 2013

"Lang"=dword:00000409 means Locale ID = English_United_States, and the "Lang"=dword:00000000 means default.

In this case, you plan to migrate Office 2010 to 2013. thus, the correct one is

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000e
"Lang"=dword:00000409 (00000000 is ok as well)

Yes, you may import them into OCT registry entries section, or you may deploy these registry keys before migration.

Tony Chen
TechNet Community Support

• Edited by Tony Chen CHNMicrosoft contingent staff, Moderator Friday, February 07, 2014 6:40 AM

Since you are doing an uninstall-upgrade the MRU list will not migrate by default.

"UpgradeVersion"=dword:0000000d means Office 14.0, also known as Office 2010

"UpgradeVersion"=dword:0000000e means Office 15.0, also known as Office 2013

"Lang"=dword:00000409 means Locale ID = English_United_States, and the "Lang"=dword:00000000 means default.

In this case, you plan to migrate Office 2010 to 2013. thus, the correct one is

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000e
"Lang"=dword:00000409 (00000000 is ok as well)

Yes, you may import them into OCT registry entries section, or you may deploy these registry keys before migration.

Tony Chen
TechNet Community Support

• Edited by Tony Chen CHNMicrosoft contingent staff, Moderator Friday, February 07, 2014 6:40 AM

Since you are doing an uninstall-upgrade the MRU list will not migrate by default.

"UpgradeVersion"=dword:0000000d means Office 14.0, also known as Office 2010

"UpgradeVersion"=dword:0000000e means Office 15.0, also known as Office 2013

"Lang"=dword:00000409 means Locale ID = English_United_States, and the "Lang"=dword:00000000 means default.

In this case, you plan to migrate Office 2010 to 2013. thus, the correct one is

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Common\Migration\Word]
"UpgradeVersion"=dword:0000000e
"Lang"=dword:00000409 (00000000 is ok as well)

Yes, you may import them into OCT registry entries section, or you may deploy these registry keys before migration.

Tony Chen
TechNet Community Support

• Edited by Tony Chen CHNMicrosoft contingent staff, Moderator Friday, February 07, 2014 6:40 AM

Tony,

Thank you for responding.  Your instructions on migrating the MRUs did NOT work.  I added the keys to the OCT Tool as show in my image.  Ran the Office2013 install which was customized with OCT.

Is there anything else I can try?  Also, if I am testing the Office 2013 install on the same machine, do I need to delete any registry key or remnants of files before testing the MRUs reg keys again?
Also, one more thing, does it matter if the office install is being done through a shutdown batch file? Can the key migration be done via the batch file?

• Edited by Fox245 Saturday, February 08, 2014 3:47 PM

Is there anything else I can try?  Also, if I am testing the Office 2013 install on the same machine, do I need to delete any registry key or remnants of files before testing the MRUs reg keys again?
Also, one more thing, does it matter if the office install is being done through a shutdown batch file? Can the key migration be done via the batch file?

• Edited by Fox245 Saturday, February 08, 2014 3:47 PM

Is there anything else I can try?  Also, if I am testing the Office 2013 install on the same machine, do I need to delete any registry key or remnants of files before testing the MRUs reg keys again?
Also, one more thing, does it matter if the office install is being done through a shutdown batch file? Can the key migration be done via the batch file?

• Edited by Fox245 Saturday, February 08, 2014 3:47 PM

Anything suggestion?  Any workaround for this?

Hello, 

Did you ever manage to get a solution for this - I am trying to solve the same problem.

Thanks

Hello, 

Did you ever manage to get a solution for this - I am trying to solve the same problem.

Thanks

No, I did not find a solution for this.

Hello,

So I was thinking of doing a very quick and dirty solution. We use a Powershell wrapper around our installation of Office 2013 - so was going to add the following -

Copy-Item -Path 'HKCU:\Software\Microsoft\Office\14.0\Word\File MRU\' -Destination 'HKCU:\Software\Microsoft\Office\15.0\Word\'

Seems to copy over pinned and recent documents and the links work, only tested in Word so far but will give a whirl.

Thanks

Hello,

So I was thinking of doing a very quick and dirty solution. We use a Powershell wrapper around our installation of Office 2013 - so was going to add the following -

Copy-Item -Path 'HKCU:\Software\Microsoft\Office\14.0\Word\File MRU\' -Destination 'HKCU:\Software\Microsoft\Office\15.0\Word\'

Seems to copy over pinned and recent documents and the links work, only tested in Word so far but will give a whirl.

Thanks

That's great.   I had already given up on this limitation, but if you come up with a simple solution it would really help others as well. Keep up posted.

Thanks

Unfortunately it looks like the registry key has completely changed for Office 2013 and includes a user specific ID hash in the key path now for the File MRU.  Still looking for a slick solution to this one...

In my specific case I am installing Office with PowerShell.  I've found that I can force the ID Hash to generate by running the following code for each application I need Recent Files for (Excel, Word, PowerPoint). 

$application = New-Object -ComObject Word.Application

$application.RecentFiles

$application.Quit()

 Unfortunately this only works when running in the particular users context and not in the System context.  

Mushnar,

That's good to know you were able to make some progress.  After all this time, I thought Microsoft Support would have provided some solution for this.  We are deploying without the users MRUs.  Good thing Word was not the primary app all the users were using before. Good luck.

Hi, Just wondering if you can help me...I'm new to PS and am trying to incorporate what you suggest into an existing script which is working, but I'm not clear on how to do it. We were using a batch file to open a doc in word, but it's messy and cumbersome. I like your idea, so I stuck your code at the start of the working PS script below.  Unfortunately it doesn't seem to work....probably because I'm missing something very fundamental.

Be awesome if you can help. Thanks

--------------------------------------------------------------------------------------------------------------------------
$application = New-Object -ComObject Word.Application
$application.RecentFiles
$application.Quit()

$MRULIst = Get-ChildItem "HKCU:\Software\Microsoft\Office\15.0\Word\User MRU\"
#Write-Host "$MRUList"
$MRUListFinal = $MRULIst -replace "HKEY_CURRENT_USER", "HKCU:"
#Write-Host "$MRUListFinal"
$SID = $MRUListFinal.Substring(51)
New-Item -path "HKCU:\Software\Microsoft\Office\15.0\Excel\User MRU\$SID\File MRU" -force
New-Item -path "HKCU:\Software\Microsoft\Office\15.0\Access\User MRU\$SID\File MRU" -force
New-Item -path "HKCU:\Software\Microsoft\Office\15.0\Powerpoint\User MRU\$SID\File MRU" -force

Copy-Item -Path 'HKCU:\Software\Microsoft\Office\14.0\Word\File MRU\' -Destination $MRUListFinal
Copy-Item -Path 'HKCU:\Software\Microsoft\Office\14.0\Excel\File MRU\' -Destination "HKCU:\Software\Microsoft\Office\15.0\Excel\User MRU\$SID"
Copy-Item -Path 'HKCU:\Software\Microsoft\Office\14.0\Access\File MRU\' -Destination "HKCU:\Software\Microsoft\Office\15.0\Access\User MRU\$SID"
Copy-Item -Path 'HKCU:\Software\Microsoft\Office\14.0\PowerPoint\File MRU\' -Destination "HKCU:\Software\Microsoft\Office\15.0\PowerPoint\User MRU\$SID"

Write-Host "File MRU Completed"

#Write-Host "Press any key to continue ..."

#$x = $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")