The article link provided below, contains information about how to troubleshoot problems that affect the ability to sign in to Microsoft Office apps for Mac, iPad, iPhone, or iPod Touch by using single sign-on (SSO). This article also contains resources for IT administrators to address reports about Active Directory Federation Services (AD FS) issues that are specific to Office for Apple iOS and Mac platforms:

http://support.microsoft.com/kb/3015526

There are three options for upgrading to Office 2013:

•In-place upgrade - The earlier version of Office, such as Office 2010, is still installed on computers and we install Office 2013 on top of it.

•Uninstall upgrade - The earlier version of Office, such as Office 2010, is first uninstalled before we install Office 2013.

•New operating system upgrade - The computers get a new version of the operating system, such as Windows 8.1, and a copy of Office 2013.

We will be discussing the uninstall upgrade process in this blog as that is the situation most environments will be in and is the recommended way of moving from Office 2010 to Office 2013.  

First, we are going to remove Office 2010 from the user machines. We will automate the removal of Office 2010 by using either uninstall command line, the Office 2010 removal Fix It or Offscrub10.vbs. We want to remove the previous version first, then install the new version of Office 2013 for a couple of reasons. If you are going from Office 2010 MSI to Office 2013 MSI, and we simply use the "remove previous versions" feature of Office 2013 to remove Office 2010, we will still be left with Office 2010 and Office 2013 on the machine. The reason for this is SharePoint Designer is not part of the Office 2013 Pro Plus suite but rather a standalone install. Office 2013 will remove all previous versions of apps it will be installing - Word, Excel, etc. However, because there isn't a SharePoint Designer app in the Office 2013 Pro Plus suite, it will not remove the 2010 version of it and thus you will be left with 2010 and 2013 on the machine still. That is another reason we recommend uninstalling Office 2010 completely first, then installing Office 2013 cleanly on the machines. If we go from Office 2010 MSI to Office 2013 365, Office 365 will not remove the previous version and you will have multiple versions of Office on your system which is not recommended.

Here are the three methods of uninstalling Office 2010:

Using the command line to uninstall 2010:

If you are going to use the command line to remove office, it will look similar to the following example:

\\server\share\office2010\setup.exe /uninstall ProPlus /config \\server\share\office2010\proplus.ww\config.xml

If you choose to remove Office 2010 with the command line uninstall option, keep in mind that the uninstallation could fail if the health of the product is poor. IE… if the source cache directory is corrupt, or if cached patches are broken. If you are removing Office 2010 and are wanting to have the uninstallation be silent, and you want to prevent the reboot, you will need to edit the config.xml that contains those options and have it accessible on a share to call via the uninstall command line.

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />

Using the Office 2010 removal “Fix It” tool to uninstall Office 2010:

Obtain the Office removal “Fix It” tool here

Using Offscrub10.vbs to uninstall Office 2010:

Utilizing Offscrub is the best method of removing a previous version of Office. It will call setup.exe and MSIExec to remove the bits. It is best equipped to deal with machine or software corruption and completely removes Office app shortcuts for the previous version. We recommend using Offscrub in almost every situation of moving from
Office 2010 to Office 2013. 
 How to obtain Offscrub
 
Once you have decided what method you are going to use to remove Office 2010, we need to automate the removal of Office 2010, and then the installation of Office 2013.

Automation options:

Here are two example batch files for Volume License media and Click-to-Run that we can use to uninstall 2010, then install either of the two versions of Office 2013 Pro Plus. These examples are using Offscrub as the method of removal for Office 2010. These batch file can be pushed out with a software distribution tool like SCCM, or used as a startup script in Group Policy.
http://technet.microsoft.com/en-us/library/ff602181.aspx

Installing Office 2013 Click-to-Run:

First we need to download the Office 2013 Click-to-Run source media. We will use the Office Deployment Tool (ODT) to download a local copy of the Click-to-Run Source. To use the ODT, follow the steps outlined here:

http://blogs.technet.com/b/odsupport/archive/2014/07/11/using-the-office-deployment-tool.aspx

=====================================================
 setlocal

REM *********************************************************************

REM Environment customization begins here. Modify variables below.

REM *********************************************************************
 
REM Set DeployServer to a network-accessible location containing the Office source files.

set DeployServer=\\server\Share\

REM Set ConfigFile to the configuration file to be used for deployment (required)

set ConfigFile=\\server\share\configuration.xml
 
REM *********************************************************************

REM Deployment code begins here. Only modify Offscrub location below this line.

REM *********************************************************************

:DeployOffice

call cscript \\server\share\Offscrub10.vbs ProPlus /bypass 1 /q /s /NoCancel

start /wait %DeployServer%\setup.exe /configure %ConfigFile%

:End

Endlocal
 =====================================================
 
Installing Office 2013 Volume License:

For Office 2013 Volume License you will get your media from the Volume License Service Center. One thing to note is if you are using a KMS host for your Office 2013 activation, you will need to add the Office 2013 KMS host pack to your KMS server and activate it separately even if you have one set up for 2010 already.

=====================================================
setlocal

REM *********************************************************************

REM Environment customization begins here. Modify variables below.

REM *********************************************************************

REM Set DeployServer to a network-accessible location containing the Office source files.

set DeployServer=\\server\Office2013SourceFiles

REM Set ConfigFile to the configuration file to be used for deployment (required)

set ConfigFile=\\server\Office2013SourceFiles\ProPlus.WW\config.xml

REM *********************************************************************

REM Deployment code begins here. Do not modify anything below this line except for the Offscrub path

REM *********************************************************************

:DeployOffice

call cscript \\server\share\Offscrub10.vbs ProPlus /bypass 1 /q /s /NoCancel

start /wait %DeployServer%\setup.exe /config %ConfigFile%

:End

EndLocal

=====================================================
 
 These batch files are simply examples. There are other methods to automate this process. The biggest take away is to follow the following order:
#1. Uninstall Office 2010 using one of the available methods for automated uninstallation
#2. Wait for the uninstallation to complete.
#3. Install Office 2013 cleanly on the machine.

FAQ

Will user settings still migrate if we are removing Office 2010 prior to installing Office 2013?

A- Any user settings that would migrate during a typical upgrade would still migrate when performing an uninstall-upgrade. The user settings will migrate upon the first user of each Office 2013 application.

We are pushing the uninstall-upgrade using a deployment method that will perform the installation while a user is logged on to the machine. We have elected to use the Offscrub method and hide the CMD prompt window that Offscrub populates, but now find that there is no message to the user that the Office installation is taking place. Can we generate a notice to the users so they know that Office is being installed, and don’t try to shut down or disconnect the PC in the middle of the install?

A- It is not uncommon for folks to want to disable the command prompt window that Offscrub generates, because if that command prompt window is closed by the end user, than Offscrub will not complete. See Offscrub FAQ
http://blogs.technet.com/b/odsupport/archive/2011/04/08/how-to-obtain-and-use-offscrub-to-automate-the-uninstallation-of-office-products.aspx

You can launch a custom IE window or a CMD window to act as the user notification if you wish. As an example, you could add the following to launch a nice notice to the user:

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2013 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"

Then after the install completes, close the CMD notification with:

taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"

So the portion of the install code above would look similar to this:

:DeployOffice

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2013 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"
call cscript \\server\share\Offscrub10.vbs ProPlus /bypass 1 /q /s /NoCancel
start /wait %DeployServer%\setup.exe /config %ConfigFile%
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ ----NOTICE----"
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

A few weeks ago the following update containing a great improvement to the Ospp.vbs script was released:

2883036  August 12, 2014 update for Office 2013 KMS activation component

So, the next time you are troubleshooting a KMS activation issue and run the Ospp.vbs script, please note the addition of two items to the output:

• A ‘notice’ advising you that a KB article is available for the error code generated by the script
• A URL to the section of article 2870357 that is bookmarked specifically for the error code

These items can be seen in the following figure:

In the above example, the URL takes you to the details targeting the 0xC004F038 error:

Prior to this update, you would have to manually search for content related to the 0xC004F038 error and then navigate your way through all the hits on this error to look for your solution. After this update is installed you only need to copy the URL from the Ospp.vbs output, paste it into your browser and then follow the directions provided in the article (for that error).

Background

The June 2014 release (build 15.0.4623.1003 and later versions) of Office Click-to-Run from Office 365 allows you to automate both a quick and online repair of Office 2013.

Note - if using an Office build lower than 15.0.4569.1007 you will need to use integratedoffice.exe to perform a Quick Repair.  Further information on using integratedoffice.exe can be found here, Automating Quick Repairs in Office 365 ProPlus.


More Information

OfficeClicktoRun.exe is the executable that will allow you to automate a repair in Office 2013.  This executable will reside in one of the following locations based on the version of the Operating System:

64-bit OS:
C:\Program Files\Microsoft Office 15\ClientX64

32-bit OS:
C:\Program Files\Microsoft Office 15\ClientX86

Here is the list of variables that can be used with OfficeClickToRun.exe:

For example, to do a silent Online Repair, run the following command from an elevated command prompt:

"C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe" scenario=Repair platform=x86 culture=en-us RepairType=FullRepair DisplayLevel=False

Related Information

For more information on the build versions of Office 2013 Click-to-Run, please see the following KB article
Microsoft Office 2013 Click-to-Run virtualization

Shortly after the release of the July Public Update, we received notification of a potential issue affecting a subset of Office 365 ProPlus users. In some cases, users running Office may not be able to launch Office products after the July 2014 updates are installed.

We have since corrected the issue and will be releasing an updated build 15.0.4631.1004 scheduled to go live by Thursday July 24th. Once the update is available, you can click on “Update Now” from the backstage to get the latest fix.

If you still have issues, then please reboot your computer and try “Update Now.” If you still have issues launching Office applications, as a last resort, please run the Fix It located at http://support.microsoft.com/kb/2739501 to uninstall and reinstall the latest bits.  For more information please see the article http://support.microsoft.com/kb/2989605.

Note: This issue doesn’t affect Volume License customers.