- Microsoft Office Updates Code 646
- Microsoft Office Updates Mac Package Download
- Microsoft Office Updates Docx
Note
Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information about this change, read this blog post.
Open one of the Office for Mac applications, such as Word. On the Word menu, click About Word. Note the version of the software. The version number will be displayed underneath the application title. To close the window, click OK. On the Help menu, click Check for Updates, and then click Check for Updates. Mar 12, 2020 Microsoft Office 2016 - Unmistakably Office, designed for Mac. The new versions of Word, Excel, PowerPoint, Outlook, and OneNote provide the best of both worlds for Mac users - the familiar Office experience paired with the best of Mac. If you already use Office on a PC or iPad, you will find yourself right at home in Office 2016 for Mac.
Summary
Existing Office 2016 for Mac customers will be seamlessly upgraded to 64-bit versions of Word, Excel, PowerPoint, Outlook, and OneNote as part of the August product release (version 15.25). This affects customers of all license types: Retail, Office 365 Consumer, Office 365 Commercial, and Volume License installations.
Deployment options for the 64-bit update
AutoUpdate (MAU)
Customers who use Microsoft AutoUpdate (MAU) to keep their Office applications up-to-date will see a 'regular' monthly update notification when their selected channel is upgraded to 64-bit builds. Depending on which version is installed on the local computer, MAU will offer either a delta or full update. The update package size does not change between 32-bit and 64-bit versions. Also, MAU can deliver a delta update when applicable to update a user from 32-bit to 64-bit applications. Therefore, customers won't experience a sharp increase in download activity. For the release to the Production channel, customers will see '(64-bit)' in the update title to make them aware that this is a 64-bit update.
For information about how to use the MAU, see Check for Office for Mac updates automatically.
Manual updates
The August release of Office for Mac is available for manual download. The following file provides a 64-bit package to replace existing 32-bit applications with 64-bit variants during installation:
Download the Microsoft Office 2016 for Mac August update package now.
Virus-scan claim
Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.
Volume License Service Center
Volume License customers typically get their Office 2016 software from the Volume License Service Center (VLSC). These builds are refreshed infrequently and are typically aligned with new language editions. The VLSC will continue to offer 32-bit installers (15.23) until November 2016. However, all updater packages that are released after August will be based on 64-bit builds. Therefore, a VLSC customer who updates either manually or through AutoUpdate will be transitioned to 64-bit builds.
More Information
64-bit only
The Mac operating system has been 64-bit for several years. Unlike for Windows, there's no choice between running a 32-bit or 64-bit version of the Mac operating system. Similarly, we won't offer a choice between 32-bit and 64-bit versions of Office 2016 for Mac. After each 'channel' is transitioned per the rollout schedule, only 64-bit builds will be available.
Effect on third-party applications and add-ins
The transition to 64-bit Office for Mac was announced on the Office developer blog in April 2016. This website is the primary reference for third-party vendors to understand the change and the effect on their products. IT Pros will want to understand which compiled add-ins are deployed to the users whom they manage so that they can assess the effect of the upgrade. The following Microsoft Office website summarizes the issues that affect the more common add-ins that are used together with Office 2016 for Mac:
Tools for inspecting product architecture
To verify the architecture of an Office application (that is, to understand whether you have a 32-bit or 64-bit build), start the application, open the Activity Monitor, and then enable the Kind column.
You can also use the file command in a terminal session to inspect the binary. For this use, type file -N <path of binary>.This method can be used with for any binary file, including third-party add-ins.
The file command returns one of three values.
| Return value | Meaning |
|---|---|
| Mach-O 64-bit executable x86_64 | 64-bit binary |
| Mach-O executable i386 | 32-bit binary |
| Mach-O 64-bit executable x86_64 | FAT binary (compatible with both 32-bit and 64-bit processes) |
| Mach-O executable i386 | FAT binary (compatible with both 32-bit and 64-bit processes) |
Options for reverting to 32-bit installations
There may be situations in which the customer has to change code that's not 64-bit ready. If customers can't immediately move forward to 64-bit builds, we will make available a one-time 32-bit update for the 15.25 release in addition to the default 64-bit updates. The 32-bit updates will be available only for manual download from the Office CDN.
The latest 32-bit release of Office 2016 for Mac (15.25.160818) can be downloaded from https://go.microsoft.com/fwlink/?LinkId=823192.
Customers who manually install the 32-bit release won't be offered the 64-bit version of 15.25 through MAU. However, MAU will offer the 64-bit version of 15.26 in September 2016. Therefore, customers have a limited time to remain on 32-bit builds.
If a customer has already upgraded to the 64-bit update of Office for Mac 15.25 and wants to revert to the 32-bit version, follow these steps:
- Exit all open Office 2016 applications.
- Start Safari, and then browse to https://go.microsoft.com/fwlink/?LinkId=823192 to start the download of the 32-bit installer.
- Double-click the downloaded package, and then follow the instructions.
The 64-bit installation has a build date of 160817. The 32-bit version has a build date of 160818.
-->Important
Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. To learn more about this name change, read this blog post.
For details of when this change takes effect, and what actions admins might need to take, read this article.
Microsoft Endpoint Configuration Manager has the ability to manage Office 365 client updates by using the Software Update management workflow. You can use Configuration Manager to update Office 365 ProPlus, Visio Online Plan 2 (previously named Visio Pro for Office 365), Project Online Desktop Client, and Office 365 Business.
When Microsoft publishes a new Office 365 client update to the Office Content Delivery Network (CDN), Microsoft simultaneously publishes an update package to Windows Server Update Services (WSUS). Then, Configuration Manager synchronizes the Office 365 client update from the WSUS catalog to the site server. Configuration Manager can then download the update and distribute it to distribution points selected by the administrator. The Configuration Manager desktop client then tells the Office client where to get the update and when to start the update installation process.
Here's an overview of the steps to enable Configuration Manager to manage Office 365 client updates:
After you perform these steps, you can use the software update management capabilities of Configuration Manager to deploy the updates. For more information, see Manage software updates in Microsoft Endpoint Configuration Manager.
Requirements for using Configuration Manager to manage Office 365 client updates
To enable Configuration Manager to manage Office 365 client updates, you need the following:
Microsoft word convert footnotes to endnotes mac 1. Microsoft Endpoint Configuration Manager (current branch)
An Office 365 client - Office 365 ProPlus, Visio Online Plan 2 (previously named Visio Pro for Office 365), Project Online Desktop Client, or Office 365 Business
Supported channel version for Office 365 client. For more details, see Release information for updates to Office 365 ProPlus
Windows Server Update Services (WSUS) 4.0
You can't use WSUS by itself to deploy these updates. You need to use WSUS in conjunction with Configuration Manager
The hierarchy's top level WSUS server and the top level Configuration Manager site server must have access to the following URLs: *.microsoft.com, *.msocdn.com, *.office.com, *.office.net, *.onmicrosoft.com, officecdn.microsoft.com, officecdn.microsoft.com.edgesuite.net. For more details, see Office 365 URLs and IP address ranges.
On the computers that have the Office 365 client installed, the Office COM object is enabled.
Enable Configuration Manager to receive Office 365 client package notifications
To start, you need to configure Configuration Manager to receive notifications when Office 365 client update packages are available. To do that, use the following steps:
In the Configuration Manager console, choose Site Configuration > Sites, and then select your site server.
On the Home tab, in the Settings group, choose Configure Site Components, and then choose Software Update Point.
In the Software Update Point Component Properties dialog box, do the following:
On the Products tab, under Office, select Office 365 Client.
On the Classifications tab, select Updates.
You can have other check boxes selected in the Products and Classifications tabs. But, Office 365 Client and Updates need to be selected for Configuration Manager to receive notifications when Office 365 client update packages are available.
Next, synchronize software updates. If you don't do that, you won't see the updates in the console and the updates won't be available to deploy. For more information about how to synchronize software updates, see Introduction to software updates in Microsoft Endpoint Configuration Manager.
Enable Office 365 clients to receive updates from Configuration Manager
For Configuration Manager to be able to manage Office 365 client updates, an Office COM object needs to be enabled on the computer where Office is installed. The Office COM object takes commands from Configuration Manager to download and install client updates.
You can enable the Office COM object by using client policy in Configuration Manager, Group Policy, or the Office Deployment Tool. If you use more than one method, the Group Policy setting determines the final configuration.
Method 1: Use client policy in Configuration Manager to enable updates from Configuration Manager
To enable Configuration Manager to manage Office 365 client updates on specific computers by using client policy, do the following:
- In the Configuration Manager console, click Administration > Overview > Client Settings.
- Open the client settings, click Software Updates and select Yes for the Enable management of the Office 365 Client Agent setting.
For more information, see client policy.
Method 2: Use Group Policy to enable updates from Configuration Manager
You can enable Configuration Manager to manage Office 365 client updates on specific computers by using Group Policy. You can apply this setting to multiple computers, an organizational unit (OU), or a domain.
To use Group Policy, do the following:
Download and install the Administrative Template files (ADMX/ADML) for Office from the Microsoft Download Center.
Enable the Office 365 Client Management policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.
Method 3: Use the Office Deployment Tool to enable updates from Configuration Manager
You can use the latest version of the Office Deployment Tool to configure Office 365 clients to receive updates from Configuration Manager.
To configure this capability, use a text editor, such as Notepad, to modify the configuration file for the Office Deployment Tool. In the Add element, include the OfficeMgmtCOM attribute and set its value to True, as seen in the following example.
We recommend that you also set the value of the Enabled attribute to True in the Updates element (note that this is the default setting). When OfficeMgmtCOM and Updates element are both set to true, updates are still delivered only by Configuration Manager. Note that the scheduled task Office Automatic Updates 2.0, which is registered during Office 365 ProPlus installation, must remain enabled. That task initiates product configuration tasks such as channel management.
Enable Office 365 clients to receive updates from the Office CDN instead of Configuration Manager
If it meets your business and technical requirements, we recommend updating your client devices automatically from the Office CDN. To enable a device to receive updates from the Office CDN instead of from Configuration Manager, use one of the following methods:
Method 1: Use client policy in Configuration Manager to enable updates from the CDN
- In the Configuration Manager console, click Administration > Overview > Client Settings.
- Open the appropriate device settings to enable the client agent. For more information about default and custom client settings, see How to configure client settings in Microsoft Endpoint Configuration Manager.
- Click Software Updates and select No for the Enable management of the Office 365 Client Agent setting.
For more information, see client policy.
Method 2: Use Group Policy to enable updates from the CDN
Download and install the Administrative Template files (ADMX/ADML) for Office from the Microsoft Download Center.
Disable the Office 365 Client Management policy setting. You can find this policy setting under Computer ConfigurationPoliciesAdministrative TemplatesMicrosoft Office 2016 (Machine)Updates.
Important
Microsoft Office Updates Code 646
The Microsoft Office Click-to-Run Service is responsible for registering and unregistering Office COM application during service startup. Change domain policy or Configuration Manager client settings require explicit Disable selection for Office COM to be successfully deregistered and restore default configuration. Toggling Office 365 Client Management via Group Policy or Client Settings for Configuration Manager from Enabled to Not Configured is not sufficient.
Microsoft Office Updates Mac Package Download
Contents of the Office 365 client update package for WSUS
The update package that Microsoft publishes to WSUS only appears in the WSUS catalog. It doesn't contain a copy of the updated version of Office that's on the Office CDN. Instead, it contains information that Configuration Manager needs to be able to download and distribute the updated version of Office.
The package contains a file named noop.exe. But, that file doesn't contain any code and shouldn't be downloaded or run.
For each update release there are different packages for each architecture and for each update channel. For example, for the May update release, there is a package for the 32-bit edition of the Monthly Channel and a package for the 64-bit edition of the Monthly Channel. In June, there will be two new packages for Monthly Channel, one for each architecture. The packages contain information so that Configuration Manager knows which packages are more recent than other packages. For example, that the June package supersedes the May package.
Microsoft Office Updates Docx
There aren't separate packages for the different Office 365 clients. For example, an update package for the 32-bit edition of the Monthly Channel has information about the Office 365 ProPlus, Visio Online Plan 2 (previously named Visio Pro for Office 365), Project Online Desktop Client, and Office 365 Business clients.