When deploying Office 2013 as an application in SCCM 2012, some clients fail with "waiting for process xxx to end". Upon further investigation we learned that the process was a popup window from the installer informing the client that it was unable to install Office because of another Office product that has a different architecture than what's being deployed.
So our workaround was to create different deployment types for our application based on architecture requirements however we still have a problem with clients who have an additional Office product installed with a different architecture (ie. Project, Visio, Sharepoint Designer). Because of this mixed architecture of Office application installations, Office 2013 fails until all installed Office applications are the same architecture.
For example:
Client has Office Pro x86 installed on their 64bit system. Client also has Visio installed but is x64 version. Because of this, Office 2013 will not install with x64 or x86 versions until Visio is either removed or reinstalled with x86 version.
Is there any other way around this or do we have to perform multiple uninstalls after identifying the mixed architecture Office application installs?