Office 2016 Deployment Tool For Mac

Download here

→

• Microsoft Office 2016 Deployment Tool
• Office 2016 Deployment Tool Download
• Office 2016 Deployment Tool For Click-to-run

Office 2016 for Mac is a version of Office that’s available as a one-time purchase from a retail store or through a volume licensing agreement. It will be supported with security updates and bug fixes, as needed, until October 13, 2020. The minimum supported macOS for Office 2016 for Mac is 10.10.

Office 2016 for Mac is a version of Office that’s available as a one-time purchase from a retail store or through a volume licensing agreement. It will be supported with security updates and bug fixes, as needed, until October 13, 2020. The minimum supported macOS for Office 2016 for Mac is 10.10 (Yosemite).

Note

• For security reason, Microsoft has deprecated the use of SHA-1. Learn more
• For release notes for Office 2016 for Mac releases prior to September 2018, see Release notes for Office for Mac.
• For release information for Office for Mac, which is the version that comes with Office 365 subscriptions, see the release notes and update history for Office for Mac.
• Office 2019 for Mac is the most current version that’s available as a one-time purchase. For release information for Office 2019 for Mac, see the release notes and update history for Office for Mac.

Updates for Office 2016 for Mac are available from Microsoft AutoUpdate (MAU). To use Microsoft AutoUpdate, start an Office application, such as Word, and then choose Help > Check for Updates. If you’re an admin and want to update the computers in your organization with your existing software deployment tools, you can download and deploy the update packages for each application.

Most current packages for Office 2016 for Mac

The following table lists the most current packages for Office 2016 for Mac and for the individual applications, such as Word and Excel. All packages are 64-bit only. The build date is listed in parentheses, in a YYMMDD format, after the version number. The install package is used if you don’t have the application already installed, while the update package is used to update an existing installation.

August 13, 2019

Version 16.16.13 (19081100)

ApplicationDownload linksSHA256 hashes for install packageOffice suite (all applications)
Install package
B7C0C0F07ED96CF0B05DAC594B08935BB53A19DF5C973BB341573EB19DD62DA4
Word
Install package
Update package
1E5C0F7D2665707FEB34D275E67A59E22B55DE5E9C433D095D95A55373C94061
Excel
Install package
Update package
91642A3049EE45B436C0E71C635D149B60C7D2BD8A887EDEE9E3EACFACEE9498
PowerPoint
Install package
Update package
DFC76E11AE3CDCB3BC4012609EE199DEFE69B322FA3AF6D9CE35A77ED4BB15E0
Outlook
Install package
Update package
FC546182395BC191979476373452EF48646043DC4098C03A4A7D538A744B9552
OneNote
Update package
Not applicable

August 2019 release

Release Date: August 13, 2019

Version 16.16.13 (Build 19081100)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
CVE-2019–1201
CVE-2019–1205Word update package
Excel
Excel update package
PowerPoint
PowerPoint update package
Outlook

Outlook update package
OneNote
OneNote update packageOffice suite

July 2019 release

Release Date: July 16, 2019

Version 16.16.12 (Build 19071500)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
Word update package
Excel
CVE-2019–1110
CVE-2019–1111Excel update package
PowerPoint
PowerPoint update package
Outlook
CVE-2019–1084
Outlook update package
OneNote
OneNote update packageOffice suite

June 2019 release

Release Date: June 11, 2019

Version 16.16.11 (Build 19060902)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
CVE-2019–1034
CVE-2019–1035Word update package
Excel

Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite

May 2019 release

Release Date: May 14, 2019

Version 16.16.10 (Build 19051200)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
CVE-2019–0953
Word update package
Excel

Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite

April 2019 release

Release Date: April 16, 2019

Version 16.16.9 (Build 19041201)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord

Word update package
Excel
CVE-2019–0828
Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite
CVE-2019–0822

March 2019 release

Release Date: March 12, 2019

Version 16.16.8 (Build 19031202)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord

Word update package
Excel

Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite

February 2019 release

Release Date: February 12, 2019

Version 16.16.7 (Build 19021001)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord

Word update package
Excel
CVE-2019–0669
Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite

January 2019 release

Release Date: January 16, 2019

Version 16.16.6 (Build 19011400)

Microsoft Office 2016 Deployment Tool

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
CVE-2019–0561: Microsoft Word Information Disclosure Vulnerability
CVE-2019–0585: Microsoft Word Remote Code Execution Vulnerability
Word update package
Excel
Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite

December 2018 release

Release Date: December 11, 2018

Version 16.16.5 (Build 18120801)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
Word update package
Excel
CVE-2018–8597: Microsoft Excel Remote Code Execution Vulnerability
CVE-2018–8627: Microsoft Excel Information Disclosure VulnerabilityExcel update package
PowerPoint
CVE-2018–8628: Microsoft PowerPoint Remote Code Execution Vulnerability
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite

November 2018 release

Release Date: November 13, 2018

Version 16.16.4 (Build 18111001)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
Word update package
Excel
CVE-2018–8574: Microsoft Excel Remote Code Execution Vulnerability
CVE-2018–8577: Microsoft Excel Remote Code Execution Vulnerability
Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite

October 2018 release

Release Date: October 16, 2018

Version 16.16.3 (Build 18101500)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
Word update package
Excel
Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite
CVE-2018–8432 Microsoft Graphics Components Remote Code Execution Vulnerability

September 2018 release

Office 2016 Deployment Tool Download

Release Date: September 11, 2018

Version 16.16.2 (Build 18091001)

This release provides the following updates.

ApplicationSecurity updatesDownload link for update packageWord
Word update package
Excel
CVE-2018–8429: Microsoft Excel Information Disclosure Vulnerability
CVE-2018–8331: Microsoft Excel Remote Code Execution Vulnerability
Excel update package
PowerPoint
PowerPoint update package
Outlook
Outlook update package
OneNote
OneNote update packageOffice suite
CVE-2018–8332: Microsoft Graphics Remote Code Execution Vulnerability

One of the issues I worked on this week was building a new Office 2016 installer after Microsoft began making Office 2016 available to its volume license customers. I have an existing process to build a combined Office 2011 installer using Packages, which I’ve used successfully for a while, so I decided to see if I could apply the same process to building an Office 2016 installer.

However, when I installed the combined Office 2016 installer with DeployStudio, then logged in, I was asked to sign into an account and activate Office. Since my work has a volume license, this isn’t a screen I should be seeing.

This is a problem that I’ve seen before with previous Microsoft Office 2011 installers and usually involves the license file not being applied when it should be. This behavior is seen on Macs in the following cases:

1. Office 2016 is installed and then updated to 15.12.3 while nobody is logged in
2. Office 2016 is installed and then updated to 15.12.3 without any Office applications being launched between the initial installation and the update.

Office 2016 Deployment Tool For Click-to-run

These two scenarios will likely apply if you’re building a new machine using an automated deployment tool, but likely will not if you’re a home user.

The easiest fix I’ve found in my testing is to get the necessary volume license file from a machine that has Office 2016 installed on it and put it back on an as-needed basis.

The needed file is /Library/Preferences/com.microsoft.office.licensingV2.plist. If you have a volume-licensed version of Office 2016 installed on your Mac, you should have this file.

To address this issue, you can use Packages‘ ability to add resources to a Packages-built package. See below the jump for an example using an Office 2016 volume licensed installer package, the Office 2016 15.12.3 updates for Excel, OneNote, Outlook, PowerPoint, and Word, as well the com.microsoft.office.licensingV2.plist license file to build a unified Office 2016 15.12.3 installer package that does not prompt for a product key.

1. Set up a new Packages project and select Raw Package.

2. In this case, I’m naming the project Microsoft Office 2016 15.12.3

3. Once the Packages project opens, click on the Project tab. You’ll want to make sure that the your information is correctly set here (if you don’t know what to put in, check the Help menu for the Packages User Guide. The information you need is in Chapter 4 — Configuring a project.)

In this example, I’m not changing any of the options from what is set by default.

4. Next, click on the Settings tab. In the case of my project, I want to install with root privileges and not require a logout, restart or shutdown.

To accomplish this, I’m choosing the following options in the Settings section:

• In the Post-Installation Behavior section, set On Success: to Do Nothing
• In the Options section, check the box for Require admin password for installation

5. Click on the Scripts tab in your Packages project.

6. Select your installers and drag them into the Additional Resources section of your Packages project.

In the case of my example, I’m selecting the following installers:

• Microsoft_Office_2016_15_11_2_Volume_Installer.pkg
• Microsoft_Excel_15.12.3_Updater.pkg
• Microsoft_OneNote_15.12.3_Updater.pkg
• Microsoft_Outlook_15.12.3_Updater.pkg
• Microsoft_PowerPoint_15.12.3_Updater.pkg
• Microsoft_Word_15.12.3_Updater.pkg

7. Select the com.microsoft.office.licensingV2.plist file and drag it into the Additional Resources section of your Packages project.

8. The last piece is telling the installers to run and for the com.microsoft.office.licensingV2.plist file to be fixed as needed. For this, you’ll need a postinstall script. Here’s the one I’m using:

Notice that $install_dir in the postinstall script refers to the path to the package’s working directory. That’s where Packages will be storing the installers along with the com.microsoft.office.licensingV2.plist file, inside the Package-built installer’s embedded directory where it stores the items defined in the Additional Resources section.

The -target value is defined as “$3” because some information is passed along by the Packages-built installer to its included scripts when those scripts are run by the installation process. (For more information, see the PackageMaker How-To available here and search on the page for $3)

In this case, -target being defined as “$3” means that the postinstall script will install the two Office 2016 packages onto the desired drive. The $3 variable will also allow the installer to correctly determine if the com.microsoft.office.licensingV2.plist license file is in the right place on the target drive and take appropriate action if it isn’t.

The script also governs what order the installers run in, so the main Office 2016 installer runs first and the updates run next after the first job finishes. The -dumplog and -verbose flags are to help you track the progress of installation if you’re looking at the installer log.

9. Once you’ve got the postinstall script built, run the following command to make the script executable:

10. Once completed, add the postinstall script to your Packages project.

11. Last step, go ahead and build the package. (If you don’t know to build, check the Help menu for the Packages User Guide. The information you need is in Chapter 3 — Creating a raw package project and Chapter 10 — Building a project.)

Testing

Once you have the package built, you should be able to test it by installing it on a machine while the machine is logged out. Once installed, Office 2016 15.12.3 should be properly licensed and not prompt you for a product key.

Download here