wilbywilson Posted July 2, 2014 Report post Posted July 2, 2014 I'm working on building an Office 2013 application in SCCM 2012 R2, and due to the way that Office 2010 was rolled out in this corporation, I can't do a simple "upgrade." I am having to do a complete "uninstall" of Office 2010, following by the installation of Office 2013. I am using the Supersedence tab in the Office 2013 application, and I'm telling it to uninstall Office 2010 (I made an SCCM package for Office 2010, just so that we could do an uninstall of it.) For the most part, it seems to be working. However, after the uninstallation of Office 2010, the machine reboots itself. When it comes back up, the Office 2013 install does *not* resume itself automatically. I have to go into the Software Center, and click on "Install" again. Right now, this is an optional application, as opposed to required. Is what I'm seeing normal? Would any behavior change if I made it "required"? I'd obviously prefer if the installation of Office 2013 kicked itself after the machine reboots, as opposed to having to go back into the Software Center and "force" it to continue. Thanks for any input. Quote Share this post Link to post Share on other sites More sharing options...
