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.

With the release of Office 2013 Click-to-Run, Microsoft has created a tool to assist with the deploying of various 2013 Click-to-Run products. This blog walks through how to use and customize the Office Deployment Tool for Click-to-Run.

Step 1.
Download the Office Deployment Tool for Click-to-Run from here:
http://www.microsoft.com/en-us/download/details.aspx?id=36778
Running the officedeploymenttool.exe produces a Setup.exe and a configuration.xml file.

Step 2.
Edit the Configuration.xml file:
Open the configuration.xml file in a word editor. You will see the XML data:
  

   <Configuration>
   <!-- <Add SourcePath="\\Server\Share\Office" OfficeClientEdition="32" >
   <Product ID="O365ProPlusRetail”>
   <Language ID="en-us" />
   </Product>
   <Product ID=”VisioProRetail”>
   <Language ID=”en-us” />
   </Product>
    </Add> -->
    <!--  <Updates Enabled="TRUE" UpdatePath="\\Server\Share\Office\" /> -->
    <!--  <Display Level="None" AcceptEULA="TRUE" />  -->
    <!--  <Logging Name="OfficeSetup.txt" Path="%temp%" />  -->
    <!--  <Property Name="AUTOACTIVATE" Value="1" />  -->
    </Configuration>

Anything between comment marks <!--   --> will not run. So first remove the comment marks around Add SourcePath and the trailing </Add>

Next, edit the “\\Server\Share\Office\” path to represent where you want to download the Office files too. Example – “C:\users\admin\desktop\odt\”

If you are only installing Office Pro Plus, remove <Product ID=”VisioProRetail”> through </Product> to remove Visio from the install. Then save your Configuration.xml file.

If you are wanting to exclude a specific app or apps from your install, you will use the <ExcludeApp ID="x" /> in the configuration.xml file as outlined here:
http://technet.microsoft.com/en-us/library/dn745895(v=office.15).aspx

If you are installing additional products, or a different product, view the following KB article for a full list of product IDs that are supported by the Office Deployment Tool for Click-to-Run:
http://support.microsoft.com/kb/2842297 

If you are adding additional languages to your install or want to further customize your install, please see the Reference for Click-to-Run configuration.xml file TechNet article:
http://technet.microsoft.com/en-us/library/jj219426.aspx

Step 3.
Download the media:
Open a command window and change the directory to the location of your setup.exe file. Next, run Setup.exe /download configuration.xml
 

The software will begin downloading to your machine. This process usually takes 10 or so minutes, but can take as long as an hour or more depending on your internet connection and other factors.
Once the software is done downloading, the command window will return to the C:\ Prompt.

 
Step 4.
Install the software.
If you are installing on the same machine that you downloaded the software too, run the following command to start the install: Setup.exe /configure configuration.xml

If you are planning on adding this download to a network share and having multiple users download Office from that location, make sure that DOMAIN COMPUTERS has Read & execute, List folder contents and Read permission. For more info on Installing from a network share, visit our blog entry on that topic here:
http://blogs.technet.com/b/odsupport/archive/2012/11/20/office-2013-installation-hangs-at-10-percent-when-installing-from-a-network-share.aspx

Background

One of the goals of Office Click-to-Run is to continue to innovate and improve the product with each new update release.  This month is no different.

More Information

With the July 2014 update of Office 2013 for Office 365 the following improvements have been made:

1. Smaller Update Download Package:  Based on feedback from our customers, we have made improvements to the size of the update package that has to be downloaded to each machine being patched.  We now use binary delta compression, so that the amount of data downloaded across the network is reduced by up to 70%.  For example, if you have installed the June 2014 build (version 15.0.4623.1002) and now apply the July 2014 build, the total amount of data downloaded to the computer will be less than 120MB compared to over 310 MB with the traditional update method.
   Note: This holds true only if you apply updates each month.  If you skip months, then the update package size will be larger.
   
   
2. User-mode Streaming:  When installing Office 2013 for Office 365 from a network location, the requirement has been that the local computer accounts need “read” permissions to that network location.  This requirement is documented here.  With the July 2014 update, this is no longer a requirement.

Overview:

The May 2014 update of the Office Deployment Tool  along with the May 2014 update of Office 2013 Click-to-Run (Build 15.0.4615.1001) offers administrators the ability to customize the installation to select which application to not install.

Note: Versions of Office Deployment Tool and Office 2013 Click-to-Run prior to May 2014 do not support Application Selection.

More Information:

The configuration.xml file provided with the Office Deployment Tool supports a new ExcludeApp element.  This element can be set to an application name to keep that application from installing.  A sample snippet of the configuration.xml file would be as follows:

<Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Access" />
      <ExcludeApp ID="Outlook" />
</Product>

A complete list of application names and IDs is as follows:

Once the configuration.xml file has been created with this element added, you can run the command-line:

<path>\setup.exe /configure <path>\<name of the configuration file>.xml

This will install Office 2013 Click-to-Run without the application(s) added to the ExcludeApp element.  If an application needs to be added back, you can edit the configuration.xml to remove the ExcludeApp ID entry for that application and rerun the command-line listed above.

Note: An Online Repair of Office 2013 Click-to-Run will install all the applications on the system, overriding the settings made in the configuration.xml file.

Background:

The SP1 for Office 2013 Click-to-Run introduced some new update capabilities to the product.  In order to manage these new features, four new Group Policy settings were introduced with the April 2014 update for Office 2013 Click-to-Run

Requirements:

In order for these four new policy settings to work, you will need to have at least the April 2014 build of Office 2013 Click-to-Run (Build 15.0.4605.1003) and download the latest Administrative templates files (ADMX/ADML) from the Microsoft Download Center.

More Information:

The four new Group Policy settings being introduced are summarized in the following table:

Related Information:

For more information on the new update related command-line options offered with SP1, please see the blog: The new Update Now feature for Office 2013 Click-to-Run for Office365 and its associated command-line and switches.

For more information about setting the Update Path, Target Version and the Update Deadline by using the Office Deployment Tool, see Reference for Click-to-Run configuration.xml file.  However, you can't set Hide Update Notification by using the Office Deployment Tool.

Update 4/28/14: A new version of the Office Customization Tool (OCT) has been released as part of the Office 2013 Administrative Templates to address this issue.  You can download the OCT from http://www.microsoft.com/en-us/download/details.aspx?id=35554.  Once downloaded double-click the executable to extract the contents which includes the Admin folder.  Copy this folder over the existing \Admin folder in your Office source.

Create an MSP file to deploy Office 2013 w/ Service Pack 1 using the newly downloaded OCT.  If you want to use an existing MSP file you will need to Import the existing MSP file into the newly downloaded OCT and then save the MSP file.  Not importing an existing MSP file may cause the OCT to fail.

 
After installing Office 2013 with Service Pack 1 from the Volume Licensing Service Center (VLSC) with a customized MSP file using the Office Customization Tool (OCT), Lync and OneDrive for Business are not installed.

We are currently investigating the issue and will provide an update soon.  In the meantime, please use one of the following workarounds:
 

1. Use the Updates folder on the original RTM release and the publically available Service Pack 1 MSP files: http://support.microsoft.com/kb/2817430.

For further information on using the Updates folder to install Office updates, refer to the following Microsoft article: Deploying software updates with an initial Office 2013 installation

2. Use the config.xml file to add Lync and OneDrive post install of Office 2013.  To accomplish this, edit the config.xml file to have the following:

<Configuration Product="ProPlus">

               <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
               <OptionState Id="GrooveFiles2" State="local" Children="force" />
               <OptionState Id="LyncCoreFiles" State="local" Children="force" />

</Configuration>

Note - this issue also applies to Excel Add-ins Power Map and PowerPivot.  If there is a need to install these add-ins you can do so by adding the following to the config.xml file:

               <OptionState Id="ExcelAddInPowerMapFiles" State="local" Children="force" />
               <OptionState Id="ExcelAddInPowerPivotFiles" State="local" Children="force" />

Once the install of Office 2013 with SP1 has completed, run the following command-line:

<path>\setup.exe /config <path>\config.xml

For further information on using the Config.xml file in Office 2013, refer to the following Microsoft Article: Config.xml file reference for Office 2013

Background:

The SP1 release of Microsoft Office 2013 Click-to-Run for Office365 offers a new Update Now feature on the File | Accounts (backstage) page of each Office application:

More Information:

This new feature allows users to check for and install updates for Office on demand.  Under the hood, there is a new OfficeC2RClient.exe file that makes this possible.

Outside of this user interface, the OfficeC2RClient.exe can be run from an administrative command-prompt by constructing an appropriate command-line in the following format:

%Program Files%\Microsoft Office 15\ClientX86 | ClientX64\OfficeC2RClient.exe /update user variable1=value variable2=value … variableN=value

Where the variables are optional settings and based on the following table:

If your environment has Office 2010 installed and you install parts of or all of Office 2013, for example Lync 2013, you will not be able to open or create a new Office document from the SharePoint document library. You will get a blank page displayed instead and may see the following URL links:

ms-word:nft|u|http://o15psvr:8080/Shared Documents/Forms/template.dotx|s|http://o15psvr:8080/Shared Documents

Excel Files :  "ms-excel:ofv|u|http://sharePointDocumentlibraryURL"

This problem is related to the new Microsoft SharePoint Foundation Support for Office 2013. Office 2013 installs a new version that Office 2010 is not aware of. This causes a conflict and one of the Foundation Support tools needs to be removed. We generally recommend keeping the most recent SharePoint Foundation Support (2013) but if your environment has Office 2010 and Lync 2013, you will want to remove 2013 and keep the 2010 version.

To fix this issue, we need to do two things, we need to create an MSP file to remove the 2013 SharePoint Foundation Support, and then repair Office 2010.

Create a MSP file to remove SharePoint Foundation Support using the Office Customization Tool for Office 2013 (OCT):

1) Open the OCT tool for the Office version you wish to remove SharePoint Foundation services from. In this example it will be for Office 2013.

2) Path to “Set Feature installation state” on the left, expand Microsoft Office and expand Office tools.

3) Under “Microsoft SharePoint Foundation Support, click the drop down and set the sub tier Microsoft SharePoint Foundation Support to “Not Available, Hidden, and Locked” but keep Microsoft Web Access Datasheet Component turned on. You will see the letter “H” and “L” as well as a red “X” as shown in this example:

4) Save the MSP file and close the OCT

Running a Silent Repair of Office:

1) We will need access to Office source, so find your Office source files on the network.

2) Open the config.xml file located in the ProPlus.WW folder (If you are using a different SKU such as Office Standard, the config file will be located in the Standard.WW folder)

3) Change the first editable line in the config file to look like the following:

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes />

4) Save and close the Config file.

After applying the MSP file to remove SharePoint Foundation Support, run the following to repair Office:

“\\my-server\my-Office-2010-source\setup.exe” /repair ProPlus /config “my-Office-2010-source \proplus.ww\config.xml”

Automating this fix across your environment:

If you need to automate this across your environment there are a few ways you achieve this. You could use SCCM and schedule tasks to push out the MSP file first, then run the repair of Office 2010, or you could use a batch file to do the same thing.

Here is an example batch file that can be used to first install the MSP file, then trigger the repair of Office. (Always test scripts before deploying)

=================================
@echo off

:RUN
%windir%\system32\msiexec.exe /p \\<path to msp file>\my-file.msp
goto REPAIR

:REPAIR
“\\my-server\my-share\setup.exe” /repair ProPlus /config “\\my-server\my-share\proplus.ww\config.xml”

:END

Exit

================================

There are other ways to achieve this fix, but the biggest takeaway is to run the MSP file that removes SharePoint Foundation Support from Office 2013 first, then run a repair of Office 2010.

The Click to Run Version of Office Pro Plus behaves differently than its MSI based counterpart. Tools like Microsoft Update and corresponding MSP files are not involved in software updates. Likewise, management tools like Windows Server Update Services (WSUS) and products controlling WSUS like System Center Configuration Manager 2012 are not distributing software updates to Click-to-Run software.

Instead, The software update process in Click-to-Run functions by first discovering what is already installed, examining the updates being delivered and only applying the differential files.

As far as managing these updates, we have three different options:

#1 – User machines receive automatic updates from Microsoft

#2 – User machines pull updates from an internal location controlled by the admin

#3 – Disable automatic updates

Let’s examine these options further:

#1 User machines receive automatic updates from Microsoft

This setting has the user machines receiving automatic updates monthly directly from Microsoft Servers. Each month, on Patch Tuesday the latest build of Office is made available. User machine’s Office update service runs as a scheduled task daily to check the Office 365 service, http://officecdn.microsoft.com/ for new updates. When the latest update is available, Office will schedule a time randomly over the next few days to download and install the update. When the update triggers, the client performs a delta comparison to determine which pieces have changed and then only retrieves the pieces that have been updated to reduce network traffic. The random scheduling is also done so not all users are downloading from the web at the same time. To enable this type of updates management, in the Configuration.xml file used for install, set the enable updates to true but do not add a specified path. This will default the path to the Office 365 service – http://officecdn.microsoft.com/

<Updates Enabled="TRUE" />

#2 – User machines pull updates from an internal location controlled by the admin

In this scenario, the updates are controlled by the admin. Each month a new build of Office is available to download via the Office Deployment Tool (ODT). Administrators will specify a network location for the client machines to receive their updates from. When the administrator is ready to push out an updated build, he or she will add that build package to the specified network location and the client machines will trigger a pull. The client machines will only pull the delta’s that have changed from the build currently on their machine to reduce bandwidth and like getting updates from Microsoft directly, each machines will pull the delta’s at a random time over a few days to minimize network traffic.

To enable this configuration, when deploying Office 365, remove the XML comment marks <!—and --> from the updates option in the configuration.xml. Then specify the location where the updated versions will be stored: (*NOTE – DO NOT name your updates location folder “Office.” This will create a problem as the BaseURL value in the registry will add an additional Office folder breaking the path.)

<Updates Enabled="TRUE" UpdatePath="\\My-server-name\Office-Share-location\New-Office-build-location" />

Much like setting automatic updates in scenario one, the Office update service will run daily as a scheduled task and once the administrator adds the latest build to this specified location, Office will install the new deltas.

In this model, the user will not see software updates being applied or forced to close applications – unless instructed to do so by the administrator distributing and automating the update. Updates are applied in the background and simply by normal use of closing and re-opening the Office program, updates are applied to Office.

#3 – Disable automatic updates

In this scenario, User machines will never look for updates via Microsoft CDN Servers or from internal network shares. If this method is used, upgrading the build of Office will require manual upgrading. To achieve this, first download the latest build of Office, or the version you wish to update to. Then add the full version number to the configuration.xml file as such:

<Add SourcePath=”\\server\share\odt\" Version=”15.0.xxxx.xxxx” OfficeClientEdition="32" >

Once this is added, make any other changes to the configuration.xml file you wish, then save it. Next run setup.exe /configure configuration.xml and Office will upgrade to the latest build.

Here is a link to the sustained Engineering blog with a list of all patches that are included in the most recent and past updates:

http://blogs.technet.com/b/office_sustained_engineering/

Here is a link to using the Office Deployment Tool for Click-to-Run:

http://blogs.technet.com/b/odsupport/archive/2013/06/19/using-the-office-deployment-tool.aspx

Here is a link that lists the version history for Office 2013 Click-to-Run:

http://support.microsoft.com/gp/office-2013-click-to-run

ISSUE:

When attempting to activate Microsoft Office running on Windows 8.1 or Windows Server 2012 R2 clients using KMS activation, the activation fails with an error code 0xC004F074.

Running ospp.vbs /dstatus shows the following output:

LICENSE NAME: Office 15, OfficeProPlusVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15,VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004F00C
ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the valid grace period.
REMAINING GRACE: 29 days (43178 minute(s) before expiring)
Last 5 characters of installed product key: GVGXT

Running ospp.vbs /act shows the following output:

LICENSE NAME: Office 15, OfficeProPlusVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: GVGXT
ERROR CODE: 0xC004F074
ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.

The application event log will show an event ID 12288 containing an error 0x8007000D.  You can also run the following command-line from an administrative command-prompt to determine the issue:
x86:
cscript "c:\Program Files\Microsoft Office\Office15\ospp.vbs" /dhistorykms

x64
cscript "c:\Program Files (x86)\Microsoft Office\Office15\ospp.vbs" /dhistorykms

MORE INFORMATION:

This issue occurs due to a change made to the activation engine of Windows 8.1 and Windows Server 2012 R2 that prevents KMS host running on down-level operating systems from activating these clients.  Microsoft has published a hotfix to address this issue.  This hotfix has to be applied to all down-level operating systems that are running KMS Host.  No update to hosts running on Windows 8.1 or Windows Server 2012 R2 is needed.

RESOLUTION:

Download and install the appropriate hotfix from the Microsoft Knowledge Base Article:
http://support.microsoft.com/kb/2885698

After installing Office 2010 Service Pack 2, you may receive the following error when attempting to Internet activate Office 2010:

This activation error is currently being investigated.  To activate Office 2010, please use one of the following workarounds:

1. Activate Office 2010 by using OSPP.VBS.

a. Open an administrative command-prompt
b. Run one of the following command-lines based on your Operating System:

x86
cscript "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act
x64
cscript "C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs" /act

2. Open any Office 2010 program using Run as Administrator

a. Go to Start | All Programs | Microsoft Office
b. Hold down the 'Shift' key and right-click any Office 2010 Program (ex. Microsoft Word 2010) and select Run as administrator
c. Follow the prompts to internet activate

3. Change the UserOperations key under HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform to have a value of 1.  Can automate this by running the following from an elevated command prompt:

reg add HKEY_LOCAL_MACHINE\software\microsoft\officesoftwareprotectionplatform /v USEROPERATIONS /t REG_DWORD /d 1 /f

After running this command, open any Office 2010 program and follow the prompts to internet activate.

Note - Setting UserOperations to a value of 1 permits administrator-privileged license operations including Internet or telephone activation by standard users.

4. If using a volume license version of Office 2010, use KMS activation instead of MAK activation.  For further information on KMS activation in Office 2010, please refer to the following Microsoft articles:

Plan KMS activation of Office 2010
http://technet.microsoft.com/en-us/library/ff603508(v=office.14).aspx

Deploy volume activation of Office 2010
http://technet.microsoft.com/en-us/library/ee624357(v=office.14).aspx

Customers using Microsoft Office 2010 may experience delays when provisioning new user accounts.  These users may receive the following error when attempting to sign-in and activate Microsoft Office 2010:
 
"No Subscription Found
 
No subscription for Microsoft Office can be found for the Microsoft Online Services ID that you provided.
 
If you want to try again and provide an alternate Microsoft Online Services ID, click Retry. Otherwise, click Cancel.
 
For more information on error message 0000000C, contact your support team."
 
Microsoft engineers are aware of the issue and are actively working on a fix. If this error message is still appearing after three business days please create a service request.
 
Note: Microsoft Office 2010 will not enter Reduced Functionality Mode for at least 30 days. For more information see Office Professional Plus for Office 365 activation overview http://technet.microsoft.com/en-us/library/gg982959(v=office.14).aspx

Update (September 5, 2013):

The issue with “No Subscription Found” has been resolved on the backend servers and the backlog created by the issue is slowly clearing. For now, please allow one day between the creation of a new account and the
successful provisioning of a subscription to the account.

BACKGROUND:

As part of Office 2010 and Office 2013 KMS activation, one important step is to ensure that each client computer has a unique CMID. When systems are created from an image on which the OSPPREARM.EXE was not run, each target system ends up with the same CMID and therefore the KMS Host count does not increase beyond the count of 5. This issue and its workaround are discussed at http://blogs.technet.com/b/odsupport/archive/2010/06/14/troubleshooting.aspx.

ISSUE:

When on a Windows 8 system running Office 2013, the command-line:

cscript ospp.vbs /dcmid

is run from an administrative command-prompt to check the CMID value, the CMID returned is that of Windows and not of Office

This occurs because with Office 2013 running on Windows 8, we rely on the Windows Software Protection Platform (SPP) service to provide activation for Windows as well as Office.

RESOLUTION:

In order to determine the CMID for Office 2013, look for event 12288 in the Application Event log of the system.  There you will find a number of event logs.  In order to determine the appropriate entry for Office, look for the event 12288 that ends with a ",5", as shown below:

The event 12288 associated with Windows will end with a ",25" as shown below:

As we can see from the above example the CMID for Office 2013 is 13befe68-308f-b99d-cc013122faff and the one for Windows 8 is da02ec22-a700-43ab-bfb7-6969691e58a2.

Overview:

The KMS Host installation and activation process for Microsoft Office 2013 is similar to the one for Microsoft Office 2010.

Prerequisites:

Installation of the update that adds support for Windows 8 and Windows Server 2012 to Windows 7 and Windows Server 2008 R2 KMS hosts is required for a successful installation of the KMS Host.  The update can be downloaded from the link http://support.microsoft.com/kb/2757817.

Installation:

STEP 1: If you have not downloaded and installed the update to add support for Windows 8 and Windows Server 2012 to Windows 2008 R2 KMS host, please do so by accessing the link http://support.microsoft.com/kb/2757817 and downloading and installing the appropriate update.

STEP 2: Download the Microsoft Office 2013 Volume License Pack from the Microsoft Download Center (MSDL) site

STEP 3: Double-click the downloaded EXE to run it:

STEP 4: Click Yes on the "Would you like to enter a Microsoft Office 2013 KMS host product key ..." prompt and enter the KMS Host Key:

STEP 5: Key installed and activated:

BACKGROUND

For Microsoft Office 2010, the MSDN/TechNet site provided a special key called the "Terminal Service enablement for Office 2010", to install Microsoft Office 2010 on a Windows Server running Terminal Service:

Micorosoft Office 2013 does not require a special key for this enablement, but rather uses the same key as the one used for a standalone installation.

MORE INFORMATION

To install the MSDN/TechNet copy of Microsoft Office 2013 on a Windows Server running Remote Desktop, please follow these steps:

STEP ONE: From Control Panel | Programs, click on Install Application on Remote Desktop:

STEP TWO: Click Next on the Install Program From Floppy or CD-ROM:

STEP THREE: Browse to the location of the Microsoft Office 2013 setup.exe and click Next:

STEP FOUR: Once the Office setup starts, you will immediately see the following message.  Click OK to the message:

STEP FIVE: You will be presented the Enter your Product Key dialog.  Enter the Microsoft Office 2013 Professional Plus key from the MSDN/TechNet site and click Continue:

STEP SIX: Read and accept the Microsoft Software License Terms:

STEP SEVEN: Choose the installation type and complete the installation:

STEP EIGHT: Click Finish on the Finish Admin Install dialog (this would be in the background during the installation of Office):

STEP NINE: Launch an Office application and choose File | Account to confirm that the product is activated:

The installation of the Office 2013 Click-to-Run version may appear to hang at "10% - Configuring..." when installing from a network share.

The Click-to-Run installation uses a service to manage the virtual file system during the intial portion of the setup process (up to 10% in the installation user interface progress screen), and the remainder of the process involves tasks required to integrate with Windows and cache the files onto the local hard drive. At 10%, because Windows Installer hands off additional task to the service, the System account (interactive Session 0) manages the remaining processes to install Office. This means that the System account needs access to the share or location where Office installation files are contained.

You will need to add the "Domain Computers" group to the network share to successfully install. To do so:

1. Right click on the folder where the Office installation files reside and choose Properties.
2. Click on the Security tab and then edit the Group or user names field by clicking on the Edit tab.
3. Click the Add tab and type in Domain Computers under the “Enter the object names to select” box and click Check Names.

An example of the added group is Domain Computers (CORP\Domain Computers); where "CORP" should reflect the name of your domain. If you have multiple domains in your environment, you will need to add each one.

By default, the group has the following permissions: Read & execute, List folder contents and Read.

We recommend running the Office 2013 troubleshooter to clean up the failed installation, prior to attempting the network installation again.

Overview

Unlike earlier versions of Microsoft Office, the Microsoft Office 2013 applications, when started, show a Start screen similar to the following, rather than opening the default blank template:

More Information

You can use the Office Customization Tool (OCT) or the Group Policy Management Editor to manage this Start screen.

Office Customization Tool (OCT):

Note: The OCT can only be used with Windows Installer based source files for Microsoft Office 2013.

STEP ONE: Using the OCT (setup.exe /admin), locate the "Disable the Office Start screen for all Office applications" under Features | Modify user settings | Microsoft Office 2013 | Miscellaneous:

STEP TWO: Enable the "Disable the Office Start screen for all Office applications" setting:

STEP THREE: Save the MSP file and place it in the Updates folder of your source files prior to deploying Microsoft Office 2013

Group Policy:

STEP ONE: If you have not already, download the Office 2013 Administrative Template files. These can be downloaded from http://www.microsoft.com/en-us/download/details.aspx?id=35554

STEP TWO: Copy the ADMX files to %systemroot%\PolicyDefinitions and the ADML files to the language specific folder (such as en-us) under %systemroot%\PolicyDefinitions.

STEP THREE: Using the Group Policy Management Editor, locate the "Disable the Office Start screen for all Office applications" under User Configuration | Policies | Administrative Templates: Policy definitions | Microsoft Office 2013 | Miscellaneous:

STEP FOUR: Enable the "Disable the Office Start screen for all Office applications" setting:

If you are attempting to set up an Office 2010 or Office 2013 KMS host by using the slmgr.vbs script, the "/ipk" switch, and a valid Office KMS host product key, the following error will occur:

Error: 0xC004F050 The software licensing service reported that the product key is invalid

Unlike Windows KMS host setup, Office KMS host setup involves installing a separate “KMS host license pack”, entering a related product key, and activating online or via phone.
 
See the following articles for additional information, to download the KMS host license packs, and step-by-step instructions for setting up Office KMS hosts:

Deploy volume activation of Office 2010 / Prepare and configure the KMS host
http://technet.microsoft.com/library/ee624357(office.14).aspx#section2

Download: Microsoft Office 2010 KMS Host License Pack
http://www.microsoft.com/en-us/download/details.aspx?id=25095

Deploy volume activation of Office 2013 / Prepare and configure the Office KMS host
http://technet.microsoft.com/en-us/library/ee624357(v=office.15).aspx#section2

Download: Microsoft Office 2013 Volume License Pack
http://www.microsoft.com/en-us/download/details.aspx?id=35584

Overview

Microsoft Office 2013 shows the following screens when an application is launched for the first time:

More Information

Both the Office Customization Tool (OCT) and Group Policy Management Editor provide a way to disable these First Run screens

Office Customization Tool (OCT)

Note: The OCT can only be used with Windows Installer based source files for Microsoft Office 2013.

STEP ONE: Using the OCT (setup.exe /admin), go to the Features section and select Modify user settings | Microsoft Office 2013 | First Run | Disable First Run Movie

STEP TWO: Set the Disable First Run Movie to Enabled

STEP THREE:Select the Disable First Run on application boot and set it to Enabled as well

STEP FOUR: Save the resulting MSP file and use it as part of the Microsoft Office 2013 deployment

Group Policy Management Editor

STEP ONE: If you have not already, download the Office 2013 Administrative Template files. These can be downloaded from http://www.microsoft.com/en-us/download/details.aspx?id=35554

STEP TWO: Copy the ADMX files to %systemroot%\PolicyDefinitions and the ADML files to the language specific folder (such as en-us) under %systemroot%\PolicyDefinitions.

STEP THREE: Using the Group Policy Management Editor go to User Configuration | Policies | Administrative Templates: Policy definitions | Microsoft Office 2013 | First Run

STEP FOUR: Set the Disable First Run Movie to Enabled and the Disable Office First Run on application boot to Enabled

Note: If you would like to manage the Opt-in or First things first prompt, please see my other blog post.

Overview

Like the Office 2010 Welcome screen, Office 2013 shows the following First things first prompt, when a user launches an application for the first time:

More Information

Administrators can manage this prompt either via the Office Customization Tool or via Group Policy as follows:

Office Customization Tool (OCT):

Note: The OCT can only be used with Windows Installer based source files for Microsoft Office 2013.

STEP ONE: Using the OCT (setup.exe /admin), go to the Features section and select Modify user settings | Microsoft Office 2013 | Privacy | Trust Center

STEP TWO: Configure each setting under Trust Center that best suits your needs.  If you wish to disable all of these settings, set the first one to Enabled and all the rest to Disabled as shown below

STEP THREE: Save the MSP file and place it in the Updates folder of your source files prior to deploying Microsoft Office 2013

Group Policy:

STEP ONE: If you have not already, download the Office 2013 Administrative Template files. These can be downloaded from http://www.microsoft.com/en-us/download/details.aspx?id=35554

STEP TWO: Copy the ADMX files to %systemroot%\PolicyDefinitions and the ADML files to the language specific folder (such as en-us) under %systemroot%\PolicyDefinitions. 

STEP THREE: Using the Group Policy Management Editor go to User Configuration | Policies | Administrative Templates: Policy definitions | Microsoft Office 2013 | Privacy | Trust Center

STEP FOUR: Configure each setting under Trust Center that best suits your needs.  If you wish to disable all of these settings, set the first one to Enabled and all the rest to Disabled as shown below

 Note: If you would like to manage the First Run screens, please see my other blog post on this topic.

Overview:

The KMS activation process for Microsoft Office 2013 is the same as what it was for Microsoft Office 2010. However, the interface to setup the KMS host for Microsoft Office 2013 on a Windows Server 2012 has been updated to use the Volume Activation Tools.

Prerequisites:

Microsoft Office 2013 running on both Windows 7 and Windows 8 client computers can be activated by installing the Microsoft Office 2013 Volume License Pack on a Windows Server 2012, or on one of the other supported host systems including Windows 7 VL edition, Windows 8 VL edition and Windows Server 2008 R2.

Installation:

STEP 1: Download the Microsoft Office 2013 Volume License Pack from the Microsoft Download Center (MSDL) site:

STEP 2: Double-click the downloaded EXE to run it:

STEP 3: Once the EXE finishes running, the Volume Activation Tools wizard will appear:

STEP 4: On the next screen, choose Key Management Service (KMS) and browse to, or specify the name of, the system running Key Management Service. Typically, this would be the system you are running the Volume Activation Tools on:

STEP 5: Next, enter the KMS host (CSVLK) key:

STEP 6: Choose activation method, online or phone:

STEP 7: Activation Succeeded: