USMT 4.0 Support for Office 2010

re: USMT 4.0 Support for Office 2010

wesley E Batton — Fri, 22 Mar 2013 10:15:55 GMT

<a href="office-2010.iyogi.com/">Office 2010 Support </a> in sage Act!2011

definately office can easily install any operating system whether it is 32 bit or 64 bit.In Act 2011 worked only 32 bit little bit diffrence and the 25 features are added by Microsoft office 2010

Thanks for haring us.

re: USMT 4.0 Support for Office 2010

Markus — Fri, 09 Mar 2012 11:09:50 GMT

It's me again. I found the reason of the problem. The DlManifests folder must be located in the USMT folder - NOT in any subfolder.

re: USMT 4.0 Support for Office 2010

Michael Niehaus — Wed, 02 Mar 2011 17:12:07 GMT

Correct, the fix is only for ConfigMgr-integrated scenarios.

There is a separate fix in ZTIUserState.wsf that is unaffected by the USMT hotfix. (This fix just sets the working directory to the folder containing the USMT binaries.)

-Michael

re: USMT 4.0 Support for Office 2010

JoeZeppy — Wed, 02 Mar 2011 16:38:11 GMT

So I'm unclear here. If I'm just using MDT lite touch deployment, I don't need to modify the ZTIUserState file?

re: USMT 4.0 Support for Office 2010

Michael Niehaus — Mon, 07 Feb 2011 09:09:57 GMT

Good point, I didn't mention which file contained that logic - it's ZTIUserState.wsf. I've updated the article above.

-Michael

re: USMT 4.0 Support for Office 2010

Mike — Mon, 07 Feb 2011 09:06:22 GMT

Thanks for this information. Just one question, which XML file should I edit?

re: USMT 4.0 Support for Office 2010

Michael — Mon, 07 Feb 2011 03:35:28 GMT

I don't suppose one of the fixes includes trying to exclude both local profiles and profiles older than a given age when migrating from WinXP?

re: USMT 4.0 Support for Office 2010

Michael Niehaus — Thu, 03 Feb 2011 07:53:08 GMT

Oops, you're right - that's what I get for not testing the change :-) I've fixed the article above.

Thanks,

-Michael

re: USMT 4.0 Support for Office 2010

Lasse Balsvad — Thu, 03 Feb 2011 07:49:01 GMT

Remember to put in parentheses when using the OR operator. Else the expression will evaluate to true if the fileversion of scanstate i = "6.1.7601.21645". But if the version of scanstate can only be "6.1.7601.21645" on XP. Then it's OK. Else the correct expression should be as follows:

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