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

You may find that end users are receiving the following message when attempting to download/install Visio or Project from the O365 Portal.

Visio

Install Visio

Your admin has turned off Visio installs. Contact your admin for more information about how to get Visio in your organization.

If this is unexpected and users should have access to download Visio/Project, check the Software Download Settings from within the Admin Portal.

1. Open the Office 365 Admin Center Home page. (https://portal.office.com/adminportal/home#/homepage)

2. Under the 'Office Software' tile, select 'Software download settings'

3. You may find that Visio/Project are already set to be available for download, if so, toggle the setting to Off, then back On.

4. It may take some time for the change to be seen in the Portal download page.

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

You may find that end users are receiving the following message when attempting to download/install Visio or Project from the O365 Portal.

Visio

Install Visio

Your admin has turned off Visio installs. Contact your admin for more information about how to get Visio in your organization.

If this is unexpected and users should have access to download Visio/Project, check the Software Download Settings from within the Admin Portal.

1. Open the Office 365 Admin Center Home page. (https://portal.office.com/adminportal/home#/homepage)

2. Under the 'Office Software' tile, select 'Software download settings'

3. You may find that Visio/Project are already set to be available for download, if so, toggle the setting to Off, then back On.

4. It may take some time for the change to be seen in the Portal download page.

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

Starting on Version 1708 the ‘Update Now’ from the Office 365 Application backstage is no longer visible if the Office installation is also configured to receive updates through SCCM.

This change was implemented so that Users cannot bypass administrative configuration settings around updating Office.

Prior to Version 1708:

At Version 1708 and greater you will see a message that Updates are managed by your admin:

The ‘Update Now’ option is also hidden:

If a user requires individually updating the Office Client outside of SCCM, they can still do this through command line with elevated privileges.

To manually trigger an Office update, run “OfficeC2RClient.exe /update user” from the cmd prompt path ‘C:\Program Files\Common Files\Microsoft Shared\ClickToRun>”

To specify a specific version run “OfficeC2RClient.exe /update user updatetoversion=16.0.xxxx.xxxx”

For more information around configuring updates, please see Configure Update Settings for Office 365 ProPlus.

There are times during troubleshooting an Office issue when the traditional log settings are not gathering enough information. This could be for Sign-In issues, installation and patching issue, even App issues.

To gather more verbose logging details, set the following registry key.

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Logging]
"EnableLogging"=dword:00000001

Reproduce the issue and gather the logs for review. The logs will be stored under %temp%. Note the time stamp you did the repro so you gather the correct logs.

Turn off the Office ULS verbose logging setting after you gather the logs, otherwise this will continue to gather verbose data and take up more dive space.

Reg keys to automate logging enabled/disabled: Enable-Local-Logging2016 Disable-Local-Logging2016

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

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