Background

When you attempt to download the Office 365 ProPlus from the Microsoft content delivery network (CDN) using the Office Deployment Tool (ODT) you get the following message:

Image may be NSFW.
Clik here to view.

More Information

This occurs when you leave the SourcePath blank in the configuration.xml.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath=" " OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Workaround

To workaround this issue, you will need to specify a path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  This requirement is for /download only and not for /configure.

Image may be NSFW.
Clik here to view.

Background

When you attempt to install Office 365 ProPlus from a local folder using the Office Deployment Tool (ODT) you get the following message:

Image may be NSFW.
Clik here to view.

More Information

This occurs when you have a relative path specified in the SourcePath the configuration.xml.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath=".\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Workaround

To workaround this issue, you will need to specify an absolute path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath="c:\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Image may be NSFW.
Clik here to view.

For Enterprise Customers using Office 365 ProPlus, users will be migrated to the latest version in February of 2016. If you want your users to stay on Office 2013 and continue to receive 2013 security updates, you can delay their migration to Office 2016 ProPlus. Your users will continue to receive security updates for Office 2013 ProPlus until September of 2016 through the same update method you are currently using. However after that time, no additional security updates will be made for Office 2013 ProPlus, so we strongly recommend that you migrate to the latest version before September of 2016.

There are three ways we can delay the migration to Office 2016 ProPlus, The first is to use a GPO setting that blocks the update or you can push out a registry key manually that will do the same. Those options are outlined in our KB here:

https://support.microsoft.com/en-us/kb/3097292

Thirdly, we can use the Office Deployment Tool (ODT) and the configuration.xml file to prevent the migration as well.

In the configuration.xml file we will add the AutoUpgrade attribute and set it to "FALSE" like in this example configuration.xml file here:

<Configuration> 
<Updates Enabled="TRUE" AutoUpgrade="FALSE" />
</Configuration>

The Office Deployment tool was updated in August of 2015 to accommodate this new switch. If you are using the old version of the tool you can download the newest one here.

Additional Links:

Prepare to update Office 365 ProPlus to the Office 2016 version

https://technet.microsoft.com/en-us/library/mt422981.aspx

Image may be NSFW.
Clik here to view.

We always recommend only having one version of Office on a machine and we recommend you use our most current versions. Having said that, there are times that due to adoption, testing, budget or migration strategies, it becomes necessary to have multiple versions of Office on a machine. There are certain combinations that are supported and others that are not.

First, there are now two architectures of Office builds. Volume Licensing (MSI) and Office click-to-run (Office 365) There are also three main Office products that we will look at here. Office Professional Plus, Visio and Project. Also, for the purpose of this article, installing one application like Skype for Business for example is the same as installing the entire Office suite. I will walk through some supported and unsupported scenarios here:

Unsupported:

Any MSI product(s) alongside the same year’s Click-to-run product(s) Example – Office ProPlus 2013 click-to-run and Visio 2013 MSI

Any Office 2013 Click-to-run product(s) alongside any 2016 click-to-run product(s).

Any Office 2016 click-to-run product alongside 2016 MSI language packs. (*note- you can have Office 2013 click-to-run and 2013 MSI language packs but they are not recommended. There are some known issues with this configuration)

Supported: (but not recommended)

Office ProPlus 2016 click-to-run and any 2013, 2010, or 2007 MSI product (ProPlus, Visio, Project)

Office ProPlus 2013 click-to-run and any 2016, 2010 or 2007 MSI product (ProPlus, Visio, Project)

Any combination of Office 2007, 2010, 2013 and 2016 MSI products (*note – you can only have one version of Outlook running at one time)

Keep in mind that there is a reason that we will say “supported but not recommended.” Issues with SharePoint Integration, Interop keys and other issues have been reported, as well as potentially new issues can occur when you use multiple versions of Office. So again, we recommend always being on the latest and greatest builds.

Additional resources:

Office installed using Click-to-Run and Window Installer on same computer isn't supported:
https://support.office.com/en-us/article/Office-installed-using-Click-to-Run-and-Window-Installer-on-same-computer-isn-t-supported-30775ef4-fa77-4f47-98fb-c5826a6926cd?ui=en-US&rs=en-US&ad=US

Install and use different versions of Office on the same PC:
https://support.office.com/en-us/article/Install-and-use-different-versions-of-Office-on-the-same-PC-6EBB44CE-18A3-43F9-A187-B78C513788BF

Image may be NSFW.
Clik here to view.

The first step in configuring local Office 365 updating is to download the Office media using the Office Deployment Tool.  See the following article for more information on downloading and installing using the ODT.  Once it has been successfully downloaded, place the media in your desired network share location.  It is imperative that client machines have Read access to this folder.  One of the most common issues experienced with local updating is due to a lack of read permissions on the share.  The recommended method for directing client machines to a network location for updates is to set the UpdatePath at install.  To set the UpdatePath remove the XML comment tags <!–   –> from either side of the updates property in the configuration.xml file. Change the UpdatePath to the location where the updated versions will be stored.

<Updates Enabled="TRUE" UpdatePath=\\Server\Share\ />

This method is automatically creating the UpdateURL key in the registry (HKLM\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration) and assigning the value "\Server\Share\" to it.  Client machines will look to the location specified in the UpdateURL key at increments according to the scheduled task Office Automatic Updates.  Please note that if the UpdateURL key does not exist, client machines will download updates from the Microsoft Client Delivery Network (CDN).  If you choose to circumnavigate the scheduled task, client machines can be forced to check for updates immediately using the following command:

C:\Program Files\Microsoft Office 15\ClientX64\OfficeC2RClient.exe /Update User displaylevel=True

For more information on available Office 365 update commands see the following article.

Additional Information:

Office Deployment Tool for Click-to-Run
http://technet.microsoft.com/en-us/library/jj219422(v=office.15).aspx

Reference for Click-to-Run configuration.xml file
http://technet.microsoft.com/en-us/library/jj219426(v=office.15).aspx

Managing Updates for Office 365 ProPlus
http://blogs.technet.com/b/office_resource_kit/archive/2014/01/28/managing-updates-for-office-365-proplus-part-2.aspx

It’s very common for users to switch devices or for an enterprise company to add/move Office 365 tenants. Once an Office 365 user activates a client machine there are three locations that need to be cleared to reset the activation/install to a clean state.

** If utilizing Shared Computer Activation there are two additional locations that must be cleared.
*** The path will change if you’ve installed 2013 or 2016 Office Click To Run.
**** The location of the OSPP file will change depending on your client architecture of Office X86 vs x64. 

1. The Office 365 license:

1. 1. To remove the Office 365 license you must run two cscript command lines. The command lines are as follows.

C:\program files <x86>\Microsoft office\office15>cscript ospp.vbs /dstatus

The above command line will generate a report of the currently installed/activated license. (See Below)

Image may be NSFW.
Clik here to view.

The line you need to reference is “Last 5 characters of installed product key” Once you have the last 5 of the installed/activated product key tap the up arrow to bring back you most recently used command line. Then remove /dstatus and replace with /unpkey:(Last 5 of Product key)  NOTE: Make sure you Do Not have any spaces

(See below)

Image may be NSFW.
Clik here to view.

After running /unpkey: command line you will see a “Product Key successfully removed” message. You can now close the Command Prompt and move onto Step 2.

*NOTE: Make sure you remove all of the licenses that show up in the /dstatus report until it states “No Installed Product Keys”.

2. Remove Credentials in HKCU registry:

1. 1. Navigate to HKCU\Software\Microsoft\Office\15.0\Common\Identity\Identities and remove all of the identities under the key. Simply right click and choose delete. **

**NOTE: If using SCA on a Terminal Server/Citrix remove the above Identities from the users SID from HKEY Users as well.

3. Remove the stored Credentials in the Credential Manager:

a. Click on Start > Click in Search and type cred > Then click on Credential Manager in the list. or go to Control Panel > Credential Manager.  Remove all credentials titled with Office15. (See Below)

Image may be NSFW.
Clik here to view.

To remove the Credential Click on the Drop down arrow and choose Remove from Vault.

***NOTE: In Shared Computer Activation scenarios (RDS/Terminal Server/Citrix VDI) You will need to remove the Tokens Credentials listed below.

File Location

Appdata\local\Microsoft\Office\15.0\Licensing

Registry Location

HKCU\Software\Microsoft\Office\15.0\Common\Identity

HKU\(The Users SID)\Software\Microsoft\Office\15.0\Common\Identity

After the above process is completed your Office 365 install will be reset to the initial install state for Activation.

Office 365 ProPlus User Activations Management
(Authored by Shubham Gupta, Program Manager)

User Management Admin and Global Admin roles can now view and manage users’ O365 ProPlus Desktop Installations.

When a user is unable to install office, most likely because they have exhausted their allowed installs; the user would call the IT Admins to help troubleshoot the issue. IT Admins would then help the user to get to the portal page and deactivate office from a computer that is no longer in use.

With User Activations Management feature, IT Admins can now view and manage PCs/Macs the user has Office Apps installed on.

[View:https://youtu.be/uh_LB3kl-v8:0:0]

To manage a user’s O365 ProPlus desktop installs, go to:

1. On the O365 Admin Center and select Active Users.

Image may be NSFW.
Clik here to view.

2. Select the user for whom you want to manage desktop installs.

Image may be NSFW.
Clik here to view.

3. In the fly out page on the right you will see a new setting: Office Installations. Click on “Edit”.

Image may be NSFW.
Clik here to view.

4. The following page will list the devices the user has installed Office apps on.

Image may be NSFW.
Clik here to view.

5. Click on the “Deactivate” link to deactivate Office from the computer

Image may be NSFW.
Clik here to view.

6. Deactivating the install will free up the number of available installs allowing the user to activate office on a new PC/Mac.

Important Notes:

• The computer names are obfuscated to the IT Admins in order to comply with privacy requirements of certain countries.
• Once an Office install is deactivated, office apps may enter into reduced-functionality mode and function more like viewers.
• Deactivating a device doesn’t remove the app from the device. If the user wants to keep using the app on a device you have deactivated, they can reactivate it the next time they open the app.

Background

When you attempt to download the Office 365 ProPlus from the Microsoft content delivery network (CDN) using the Office Deployment Tool (ODT) you get the following message:

Image may be NSFW.
Clik here to view.

More Information

This occurs when you leave the SourcePath blank in the configuration.xml.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath=" " OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Workaround

To workaround this issue, you will need to specify a path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  This requirement is for /download only and not for /configure.

Background

When you attempt to install Office 365 ProPlus from a local folder using the Office Deployment Tool (ODT) you get the following message:

Image may be NSFW.
Clik here to view.

More Information

This occurs when you have a relative path specified in the SourcePath the configuration.xml.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath=".\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Workaround

To workaround this issue, you will need to specify an absolute path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath="c:\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

For Enterprise Customers using Office 365 ProPlus, users will be migrated to the latest version in February of 2016. If you want your users to stay on Office 2013 and continue to receive 2013 security updates, you can delay their migration to Office 2016 ProPlus. Your users will continue to receive security updates for Office 2013 ProPlus until February 2017 through the same update method you are currently using. However after that time, no additional security updates will be made for Office 2013 ProPlus, so we strongly recommend that you migrate to the latest version before February of 2017.

There are three ways we can delay the migration to Office 2016 ProPlus, The first is to use a GPO setting that blocks the update or you can push out a registry key manually that will do the same. Those options are outlined in our KB here:

https://support.microsoft.com/en-us/kb/3097292

Thirdly, we can use the Office Deployment Tool (ODT) and the configuration.xml file to prevent the migration as well.

In the configuration.xml file we will add the AutoUpgrade attribute and set it to "FALSE" like in this example configuration.xml file here:

<Configuration> 
<Updates Enabled="TRUE" AutoUpgrade="FALSE" />
</Configuration>

The Office Deployment tool was updated in December of 2015 to accommodate this new switch. If you are using the old version of the tool you can download the newest one here.

Additional Links:

Prepare to update Office 365 ProPlus to the Office 2016 version

https://technet.microsoft.com/en-us/library/mt422981.aspx

We always recommend only having one version of Office on a machine and we recommend you use our most current versions. Having said that, there are times that due to adoption, testing, budget or migration strategies, it becomes necessary to have multiple versions of Office on a machine. There are certain combinations that are supported and others that are not.

First, there are now two architectures of Office builds. Volume Licensing (MSI) and Office click-to-run (Office 365) There are also three main Office products that we will look at here. Office Professional Plus, Visio and Project. Also, for the purpose of this article, installing one application like Skype for Business for example is the same as installing the entire Office suite. I will walk through some supported and unsupported scenarios here:

Unsupported:

Any MSI product(s) alongside the same year’s Click-to-run product(s) Example – Office ProPlus 2013 click-to-run and Visio 2013 MSI

Any Office 2013 Click-to-run product(s) alongside any 2016 click-to-run product(s).

Any Office 2016 click-to-run product alongside 2016 MSI language packs. (*note- you can have Office 2013 click-to-run and 2013 MSI language packs but they are not recommended. There are some known issues with this configuration)

Supported: (but not recommended)

Office ProPlus 2016 click-to-run and any 2013, 2010, or 2007 MSI product (ProPlus, Visio, Project)

Office ProPlus 2013 click-to-run and any 2016, 2010 or 2007 MSI product (ProPlus, Visio, Project)

Any combination of Office 2007, 2010, 2013 and 2016 MSI products (*note – you can only have one version of Outlook running at one time)

Keep in mind that there is a reason that we will say “supported but not recommended.” Issues with SharePoint Integration, Interop keys and other issues have been reported, as well as potentially new issues can occur when you use multiple versions of Office. So again, we recommend always being on the latest and greatest builds.

Additional resources:

Office installed using Click-to-Run and Window Installer on same computer isn't supported:
https://support.office.com/en-us/article/Office-installed-using-Click-to-Run-and-Window-Installer-on-same-computer-isn-t-supported-30775ef4-fa77-4f47-98fb-c5826a6926cd?ui=en-US&rs=en-US&ad=US

Install and use different versions of Office on the same PC:
https://support.office.com/en-us/article/Install-and-use-different-versions-of-Office-on-the-same-PC-6EBB44CE-18A3-43F9-A187-B78C513788BF

Issue: When customers install Office Professional Plus 2013 MSI or Lync 2013 MSI standalone and use the Office Customization Tool (OCT) to change the default Start Menu Shortcut path, after installing the April 2015 update for Office which transforms Lync 2013 to Skype for Business 2013, the shortcut for Skype for Business will remain as “Lync 2013” which can be confusing for end users.

We can work around this by using a PowerShell script like the following sample to change the Lync shortcut icons to Skype for Business icons. *Note – this script is an example script and should be tested before being used in production.

============================================
$shortcutLocation = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Office 2013\"
$oldShortcut = "Lync 2013.lnk"
$newShortcut = "Skype for Business 2015.lnk"
$iconComment = "Connect with people everywhere through voice and video calls, Skype Meetings, and IM."

# Rename shortcut:
Rename-Item $shortcutLocation$oldShortcut $newShortcut

# Change the new shortcut settings
$shell = New-Object -COM WScript.Shell
$shortcut = $shell.CreateShortcut($shortcutLocation+$newShortcut)
$shortcut.Description = $iconcomment
$shortcut.Save()

#Get the Icon Name and Folder
$iconlocation = $shortcut.IconLocation
$tempInd = $iconlocation.indexof("Icon")

$iconName = $iconlocation.substring($tempInd,$iconlocation.indexof(".exe")-$tempInd )
$iconFolder = $iconlocation.substring(0,$tempInd)

#Change the icon:
Rename-Item $iconFolder$iconName".exe" $iconFolder$iconName"_old.exe"
Copy-Item $iconFolder"lyncicon.exe" $iconFolder$iconName".exe" -force

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

This blog was submitted by Jeremy Chapman, director on the Office team

Many organizations use the Microsoft Deployment Toolkit (MDT) to deploy Windows with Office to new computers or when re-imaging computers. You can use the tools to deploy just applications, or as part of an operating system + application deployment.

If you’ve been deploying Office or using MDT for a few years, you may know that the integration for Office deployment began in 2007 when MDT was called Business Desktop Deployment 2007 and Office 2007 suites introduced the Office Customization Tool. These capabilities have remained largely unchanged for the MSI package versions of Office over the years – currently Office Professional Plus 2016 and Office Standard 2016.

Fast forward to 2016 and while the tools have been consistent for around nine years, what if you were the IT administrator tasked with building out an imaging solution for Windows 10 and Office 2016 today using MDT? Where is the process documented for installing Office 2016? It turns out the process is documented on TechNet… but labeled as the approach for Office 2010. In reality, the same approach works in Office 2013 and Office 2016 MSI packages.

Once you’ve downloaded and installed MDT, installed the Windows 10 Automated Deployment Kit, and downloaded Office installation files from the Volume Licensing Service Center, here’s what you do to add Office 2016 into your MDT deployment share.

1.  Under MDT Deployment Share, click Applications and then click New Application in the Action pane. The New Application Wizard opens to the Application Type page.

Image may be NSFW.
Clik here to view.

2.  On the Application Type page, make sure that Application with source files is selected, and then click Next.

Image may be NSFW.
Clik here to view.

3.   On the Details page:

       a.     Under Publisher, type the name of the application publisher (optional).

       b.     Under Application Name, type a descriptive name for the application (required).

       c.     Under Version, type the application version (optional).

       d.     Under Language, type the application language (optional).

       e.     Click Next.

Image may be NSFW.
Clik here to view.

4.   On the Source page:

       a.     Click Browse. In the Browse for Folder dialog box, locate and select the folder that contains the setup files for the particular application, and then click OK.

       Note: If you want to move the setup files instead of copying them, select the check box that is next to Move the files to the deployment share instead of copying them.

       b.    Click Next.

Image may be NSFW.
Clik here to view.

5.    On the Destination page, accept or change the default destination folder (the deployment share folder that will contain the application source files) that was assigned by the wizard, and then click Next.

Image may be NSFW.
Clik here to view.

6.    On the Command Details page:

       a. Under Command line, type the command that you want to be run at the start of the application installation. This is typically “setup.exe”, you can access the Office Customization Tool via the Application Properties > Office Products tab later.

       b. Click Next

Image may be NSFW.
Clik here to view.

7.    On the Summary page, click Next.

Image may be NSFW.
Clik here to view.

8.    The Progress page indicates that the share is being created. On the Confirmation page, click Finish. The New Application Wizard finishes, and the application name that you typed in the Application Name page appears in the Deployment Workbench details pane.

Image may be NSFW.
Clik here to view.

Now you can access the properties of the Office 2016 install in the Applications menu of your deployment share.

Image may be NSFW.
Clik here to view.

Here in the Office Products tab, you can select the Office product to install and configure Display Level, automatically accept the EULA and suppress reboots.

Image may be NSFW.
Clik here to view.

The majority of your granular Office customization will be done via the Office Customization Tool (OCT), which outputs an update (.MSP) file that is automatically consumed as part of the Office installation. Plus you can use MDT to deploy additional Office applications – like the legacy versions of InfoPath or SharePoint Designer – or use it to install custom Office add-ins. Once you’ve finished the above steps and anything you want to do with the OCT, you can start building Windows or custom application-only deployment task sequences with MDT. 

Starting April, 2016, MSI-based non-security updates will be released on the first Tuesday of each month and MSI-based security updates will be released (as usual) on the second Tuesday of each month.

For more details, please see the following blog post:

https://blogs.technet.microsoft.com/office_sustained_engineering/2016/03/28/upcoming-change-to-the-release-schedule-for-non-security-updates/

After you install the April 5, 2016, update for Outlook 2013 (KB3114941), you may experience random crashes of Microsoft Lync 2013 (Skype for Business) or Microsoft Outlook 2013, or both. This issue is outlined in detail here.

The workaround is to roll your 2013 ProPlus users back to the March build – here are the steps to do so:

Referencing this article, we can use the C:\Program Files\Microsoft Office 15\Clientx64\OfficeC2RClient.exe command to roll a user back to the March build. If your organization is using the Microsoft CDN to get your Office click to run updates, simply run this command on your affected machine(s):

C:\Program Files\Microsoft Office 15\Clientx64\OfficeC2RClient.exe /update user updatetoversion=15.0.4805.1003   *note – in the article linked at the beginning of this paragraph, there are other switches we can also add such as display level and update prompts for the users that we can also use depending on the experience you want to deliver for this workaround.

If you are managing your own updates, you have to take one extra step by first downloading the 15.0.4805.1003 build first if you no longer have it. This is because if we do not use the Office CDN as our updates location, but rather an internal file share, when running the command to roll back to the March build, Office will look to that internal updates location for 15.0.4805.1003. If it is not present, we will see this error:

Image may be NSFW.
Clik here to view.

If you are not sure if your updates are coming from an internal share or the Microsoft CDN, look to this registry key to tell us:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\configuration

In this key, look for UpdateURL and the value will either be HTTP://officecdn.microsoft.com/…. indicating you are using Microsoft’s CDN or you will see \\servername\share\… Indicating you are managing your own updates. If you don’t have an UpdateURL value at all, you are also using the Microsoft CDN.

Once you verify that your organization is managing its own updates, we can use the Office Deployment Tool (ODT) to download 15.0.4805.1003 and then add it your internal update share.

Here is a blog outlining how to use the Office Deployment Tool (ODT)

One change we will have to make when using the Office deployment tool is we will have to specify the version we want to download because the default is to download the newest version and we want 15.0.4805.1003. Here is what your configuration.xml file will look like with the added Version value.

<Configuration>
<Add SourcePath=”\\server\share\…” Version=”15.0.4805.1003″ OfficeClientEdition=”32″ >
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
</Product>
</Add>
</Configuration>

Next, follow the steps outlined in the Using the Office Deployment tool for click to run blog to download (setup.exe /download configuration.xml) 15.0.4805.1003 and once the download is complete, add the source files to your internal updates location. Now we can run the command to roll back to that build:

C:\Program Files\Microsoft Office 15\Clientx64\OfficeC2RClient.exe /update user updatetoversion=15.0.4805.1003

Links:

April 5, 2016, update for Outlook 2013 (KB3114941) https://support.microsoft.com/en-us/kb/3114941

Lync 2013 (Skype for Business) or Outlook 2013 Crash https://support.microsoft.com/en-us/kb/3158521

The new Update Now feature for Office 2013 Click-to-Run for Office365 https://blogs.technet.microsoft.com/odsupport/2014/03/03/the-new-update-now-feature-for-office-2013-click-to-run-for-office365-and-its-associated-command-line-and-switches/

Using the Office Deployment Tool for Click-to-Run https://blogs.technet.microsoft.com/odsupport/2014/07/11/using-the-office-deployment-tool-for-click-to-run/

Issue:

If your organization has not taken steps to prevent the upgrade, users will start seeing the following business bar in their Office applications:

Image may be NSFW.
Clik here to view.

Resolution:

If you would like to stop receiving this business bar and block upgrades, please take the following steps:

1. Follow these steps to prevent the upgrade
2. On the systems that already seeing the above business bar, edit the following registry key:
   1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Updates
      UpgradePackageVersion REG_SZ   Value = 0.0.0.0

 

More Information:

When you are ready to enable upgrades simply undo the changes you made per the steps to prevent the upgrade.

 

Issue: After the recent release of the Office Deployment Tool version 16.0.7118.5775 users are seeing issues with installs/updates due to not having the V32.cab data file come down with the source files download.

Errors seen are 30029.1011 and a few other issues all stemming from the missing v32.cab file.

NOTE: Microsoft is aware of this issue and working on releasing an updated version of the Office Deployment Tool as soon as possible.

Workaround: The current workaround is to copy, duplicate, and rename the copied v32_16.0.xxxx.xxx.cab to v32.cab (See Below)

Step 1: Source file location after the initial download. As stated above you’re missing the v32.cab file.

Image may be NSFW.
Clik here to view.

Step 2: Copy, and then paste the copied version seen below.

Image may be NSFW.
Clik here to view.

Step 3: Then rename the resulting copied V32_versoned.cab to v32.cab to allow Install/Updates to continue as expected.

Image may be NSFW.
Clik here to view.

Office 365 updates are designed to be very network bandwidth friendly. There is Binary Delta Compression that occurs so long as the machines are staying current and Office has built in throttles to prevent every machine from trying to update at the same time. However, IT admins will sometimes still need to monitor the size of the monthly updates very closely. Here is how to determine how large the update for Office ProPlus will be:

Step 1.
Download Process Monitor from the Windows Sysinternals collection here:
https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Step 2.
When you launch Process Monitor the filter menu may auto load but if not, click on Filter > filter to open the filter menu. In here Exclude the following Event Classes:

• Registry
• File System
• Process

And only include the “OfficeClicktoRun.exe” Process Name. Your filter should look something like this:

Image may be NSFW.
Clik here to view.

Step 3.
Start Process Monitor and launch the manual update process by clicking “Update Now” in the File > Account menu of any Office Click-to-Run app. We will see the updates downloading and data filling in the Procmon log.

Image may be NSFW.
Clik here to view.

Step 4.
Once the update finishes, stop the Procmon trace and then check for the network traffic summary by going to Tools > Network Summary.

Image may be NSFW.
Clik here to view.

In my example I was on the July version of Deferred Channel – 16.0.6741.2056 and then updated to the August version – 16.0.6741.2063. As we can see, this update is 167,829,264 bytes, or roughly 167 MB of data.

We have an emerging issue where some clients that are using Shared Computer Activation (SCA) on our Office 2013 click-to-run clients cannot sign in. Users are seeing an error similar to this when trying to log in:

Image may be NSFW.
Clik here to view.

“There is a problem with your account. Please try again later.”

The reason is one of the required URLs for SCA is being blocked by some security programs:

http://clientconfig.microsoftonline-p.net/fplist.xml

We are investigating why this particular URL is being flagged to be blocked, but to fix this issue, please work with your networking and security team to ensure that this URL is whitelisted per our documentation of required URLs for Authentication and Identity here:

https://support.office.com/en-us/article/Network-requests-in-Office-365-ProPlus-eb73fcd1-ca88-4d02-a74b-2dd3a9f3364d?ui=en-US&rs=en-US&ad=US

Image may be NSFW.
Clik here to view.

Background

When you attempt to install Office 365 ProPlus from a local folder using the Office Deployment Tool (ODT) you get the following message:

Image may be NSFW.
Clik here to view.

More Information

This occurs when you have a relative path specified in the SourcePath the configuration.xml.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath=".\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Workaround

To workaround this issue, you will need to specify an absolute path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath="c:\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>