Just to follow-up on this, I found the loadstate.vbs file that we used. Here is
the snippet of code that runs to clear the problem of the USMT breaking Outlook
2013:
Command = "%ComSpec% /c del /f /q ""C:\Program Files (x86)\Common
Files\System\MSMapi\1033\MSMapi32.dll"""shell.Run command, 1, TrueCommand =
"msiexec /fm {90150000-0012-0000-0000-0000000FF1CE}"shell.Run command, 1, True
Hope that helps close the loop on this for you.
Regards,-S
From: [email protected]
To: [email protected]
Subject: RE: [MDT-OSD] USMT Breaks Outlook 2007 to 2013
Date: Fri, 31 Oct 2014 12:06:42 +0000
What I've found is that uninstalling all applications that have outlook addins
on the target machine prevents this problem. Now I'm trying to just exclude the
addins registry key to see if that works.
From: [email protected] [mailto:[email protected]]
On Behalf Of s kissel
Sent: Monday, October 20, 2014 9:24 AM
To: [email protected]
Subject: RE: [MDT-OSD] USMT Breaks Outlook 2007 to 2013
That should work. I didn't actually exclude it so if that doesn't work for you,
let me know and I'll ping some colleagues who actually did.
Regards,
-S
From:
[email protected]
To: [email protected]
Subject: RE: [MDT-OSD] USMT Breaks Outlook 2007 to 2013
Date: Mon, 20 Oct 2014 12:25:39 +0000
Is this how you excluded it?
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/allfiles";>
<component type="Documents" context="System">
<displayName>Test</displayName>
<role role="Data">
<rules>
<unconditionalExclude>
<objectSet>
<pattern type="File">% COMMONPROGRAMFILES %\System\MSMAPI\*
[*]</pattern>
</objectSet>
</unconditionalExclude>
</rules>
</role>
</component>
</migration>
From:
[email protected] [mailto:[email protected]]
On Behalf Of s kissel
Sent: Friday, October 17, 2014 5:13 PM
To: [email protected]
Subject: RE: [MDT-OSD] USMT Breaks Outlook 2007 to 2013
Yes, I've seen it.
I went looking through some old emails for resolution to this issue and this is
the most conclusive thing I could come up with without reaching out to my
colleagues:
Exclude the % COMMONPROGRAMFILES %\System\MSMAPI from the USMT backup process.
The MSMAPI folder becomes messed up after USMT restore, deleting it and
repairing office resolves the issue,
but not restoring the data to that directory should prevent it from happening.
Outlook should automatically recreate the MSMAPI and use it successfully.
Give it a try and let us know if that resolves it. If not, I'll ping my good
buddy.
Regards,
-S
From:
[email protected]
To: [email protected]
Subject: [MDT-OSD] USMT Breaks Outlook 2007 to 2013
Date: Fri, 17 Oct 2014 20:21:02 +0000
A subset of my users cannot open Outlook after I restore user state onto
Windows 7 x64 with x86 Office 2013 from Win7 x86 with Office 2007. I have a
case open with CSS. Has anyone ever seen
this before? The first time these users open outlook they get this dialog but
Outlook opens:
Subsequent launches of outlook fail with the following error message:
John Marcum
MCITP, MCTS, MCSA
Desktop Architect
Bradley Arant Boult Cummings LLP
Confidentiality Notice: This e-mail is from a law firm and may be protected by
the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and then
delete it from your computer.
Confidentiality Notice: This e-mail is from a law firm and may be protected by
the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and then
delete it from your computer.
Confidentiality Notice: This e-mail is from a law firm and may be protected by
the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and then
delete it from your computer.
Confidentiality Notice: This e-mail is from a law firm and may be protected by
the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and then
delete it from your computer.
Confidentiality Notice: This e-mail is from a law firm and may be protected by
the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and then
delete it from your computer.
