Jump to content


  • 0
anyweb

USMT 4 Update Released to Support Office 2010 Migrations

Question

Microsoft has created an update for USMT 4.0 that adds support for Office 2010. USMT 4.0 migrations of Office 2010 are now supported .

 

You can get the update here: http://support.microsoft.com/kb/2023591

 

Here are some things you should be aware of:

 

* Certain settings and customizations in MS Word won’t migrate from any version to Word 2010, because of with the way Word is designed and how data is stored in “HKEY_CURRENT_USER\software\Microsoft\Office\<OfficeVersion>\Word\Data".

* Many Office settings (across all Office apps) won’t migrate when going from 32-bit Office to 64-bit Office. This is due to the way that the settings are stored in 64-bit Office installations.

* If you’ve launched Office on the destination PC as a user before doing the migration of that user’s profile, most of your settings won’t migrate. This happens because Office relies on some code that only runs the first time that an Office app is launched to migrate settings.

* This update isn’t a magic bullet. You may still need to do some customization to make USMT fit your particular configuration.

 

The update also fixes a couple of issues around hard-link migration performance when copying a folder with a huge number of files and an issue that affected certain time zones.

 

This post was contributed by David Hornbaker, a Senior Consultant with Microsoft Services - U.S. East Region.

 

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use

 

via > http://blogs.technet.com/b/deploymentguys/archive/2011/02/04/usmt-4-update-released-to-support-office-2010-migrations.aspx

Share this post


Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

You have to be aware that you need to change a line in the ZTIUserstate.wsf script in the MDT package, if you don't your USMT will be screwed from XP to Win7, it won't locate the manifest files.

 

Look for that section in the file:

 

' Workaround for USMT bug in Windows 7 AIK

If oEnvironment.Item("DeploymentMethod") = "SCCM" and oEnvironment.Item("OSVersion") = "XP" and oFSO.GetFileVersion(sFoundScanState) = "6.1.7600.16385" then

oUtility.RunWithHeartbeat "cmd.exe /c xcopy /iesryh """ & sUSMTPath &"\DlManifests"" """ & oEnv("SystemRoot") & "\system32\DlManifests" &""" 1>> " & oLogging.LogPath &"\zticopyUSMT.txt 2>>&1 "

End if

 

 

 

and make sure you change the file version to this: 6.1.7601.21645

 

 

Microsoft teams don't talk to each other it seems. :rolleyes:

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.