Microsoft releases security and quality updates for the Click-To-Run (C2R) version of Office 2016 and for Office 2019, which is exclusively C2R. These updates are released approximately once a month, usually on the second Tuesday of the month.
!!EXCLUSIVE!! 2016 Microsoft Office 2016 Pro Plus VL 16.0 November 2019
The following tables provide the update history for the volume licensed version of Office 2019, as well as the retail versions of Office 2016 C2R and Office 2019, with the most recent release date listed first.
This security update resolves an information disclosure vulnerability that exists in Microsoft Access software if the software does not handle objects in memory correctly. To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2019-1402.Note To apply this security update, you must have the release version of Office 2016 installed on the computer.
After you install this update, you may see a "File failed to upload" error message when you save files to a network location. To fix this issue, install the November 12, 2019, update for Office 2016 (KB3085368).
Microsoft Office 2019 (Second perpetual release of Office 16) is a version of Microsoft Office for both Windows and Mac. It replaces Office 2016 and was replaced by Office 2021 on October 5, 2021.[6] It was unveiled on April 27, 2018 for Windows 10 and June 12, 2018 for macOS, and launched on September 24, 2018.[1] Some features that had previously been restricted to Office 365 subscribers are available in this release.[7] Office 2019 remain same major version 16 as predecessor Office 2016, therefore it is second perpetual release of Office 16. Microsoft plans to end mainstream support for Office 2019 on October 10, 2023. Unlike other versions of Microsoft Office, Office 2019 will only get two years of extended support, which means that support for Office 2019 will end on the same day as support for Office 2016, and Windows 10 will on October 14, 2025.[8]
Same as its predecessor Microsoft Office 2016, Microsoft Office 2019 has the same perpetual SKU editions aimed towards different markets. Like its predecessor, Microsoft Office 2019 contains Word, Excel, PowerPoint and OneNote and is licensed for use on one computer.[18][19]
For Office 2013 and 2016, various editions containing the client apps were available in both Click-To-Run (inspired by Microsoft App-V) and traditional Windows Installer setup formats. However, Office 2019 client apps only have a Click-to-Run installer and only the server apps have the traditional MSI installer. The Click-To-Run version has a smaller footprint; in case of Microsoft Office 2019 Pro Plus, the product requires 10 GB less than the MSI version of Office 2016 Pro Plus.[22]
Corporate customers can activate Office products within the corporate network by using the local KMS server without connecting to Microsoft activation servers on the Internet. Earlier we have already considered the peculiarities of KMS activation of MS Office 2013, and the main principles and approaches to the MS Office 2021, 2019, and 2016 activation on a KMS server remained unchanged.
Office 2021/2019/2016 Active Directory-Based Activation (ADBA)If you are going to use ADBA for the automatic activation of Office 2021/2019/2016 on AD-joined computers, select Active Directory-Based Activation as a volume activation method in Volume Activation Tools. This activation method works for Windows Server 2022/2019/2016/2012R2 and Windows 11/10/8.1.
GVLK Keys for Microsoft Office 2021/2019/2016All corporate Office 2021/2019/2016 versions are installed with Generic Volume License Keys (GVLK). These keys are public and accessible to everyone on Microsoft TechNet. Due to them, all Office product versions are automatically activated if there is a KMS server on the network. So, in most cases, it is not required to specify the GVLK key for Office.
If you are trying to install a KMS server for Office 2021/2019/2016 on Windows Server 2019/2016, keep in mind that it has a number of problems with the launch of the Volume Activated Services Tool. When you try to activate an Office KMS server through the Volume Activated Services GUI, you can receive an error:
If i have an environment of 100 workstation that I reimage every 6 months and i only have 120 VL of office 2016.When I activate the 100 workstation, I will use up the 100 licenses but what if i reimage the computers on the 6 months. What will happen? will only 20 computers be activated or all 100 computers of office 2016 be activated?Thanks
End of 2020, just wanted to check in and let everybody know this works beautifully on a 2016 or 2019 server and I verified it works for activating clients with Office 2016 or Office 2019. Thank you so much for this awesome tutorial.
Hi !Thanks for this great article.However, when you have several GVLK keys for the same Office 2016/2019 product and that you encounter the issue to add new keys from the GUI, how can I specify multiple GVLK keys for my KMS server using the slmgr utility from command prompt ?Thanks in advance.
I have worked on couple of office 365 proplus rollout projects. In all projects ,one of the critical task is to manage MSI based deployments for visio/project 2016 on computer that runs office 365 proplus (Click-to-Run).
Click-to-Run is the technology used to install Office 365 proplus subscription based .Windows Installer technology (MSI) was used to install the volume license editions of older versions of Office 2016 and older, such as Microsoft Office Professional Plus ,Microsoft Office Standard,visio and project.
Until now ( if you are not on office 365) ,we usually deploy volume licensed versions of Project 2016 and Visio 2016 by using the Windows Installer (MSI) installation technology. But that won't work if you're trying to install volume licensed versions of Project 2016 and Visio 2016 on the same computer that has Office 365 ProPlus. That's because Office 365 ProPlus uses Click-to-Run as its installation technology, and in this case, having MSI and Click-to-Run installations on the same computer isn't supported.
Example: If a computer has office 365 proplus ,then you cannot install any MSI version of 2016 on the same computer but you can install MSI version of 2013 and lower versions of visio/project,office et because they share different versions.
With the introduction of C2R ,MSI and its versions ,how do you deploy visio/project 2016 on computer that has office 365 proplus (C2R) installed and also get it activated using KMS/MAK volume license?
Download the office deployment tool from here. Right click the executable and run as administrator. You will now see Microsoft Office 2016 click-to-run administrator tool. Accept the license terms and click Continue.
Dear Prajwal Desai,Thanks very much for your posts. Your blog is a favorite for me and my co-workers for answering SCCM questions. We are working on updating our Citrix farm from Office 2016 to Office 2019. While we have our xml files and deployment applications working fine, we are having issues pushing Office 2019 updates using CDN through SCCM. We have our Proxy open and accepting the Microsoft websites, and have created the deployment package, added O365 and Office 2019 in SUP, but when we go to download the .CAB file, it errors out. Any thoughts?
Had to use POL wine 3.14 (latest 3.19 or 3.0 /3.4 did not work for me) on Ubuntu 18.04 and steps 1-5 post Kevin to get MS Office 2016 (Word/Excel/Powerpoint) started. If you download the complete office 2016 IMG file, the installation includes your personal license and is already activated on start.
During the BYOL image ingestion process, if you are using Windows 10, you have the option to subscribe to Microsoft Office Professional 2016 (32-bit) or 2019 (64-bit) through AWS. If you choose this option, Office is pre-installed in your BYOL image and included on any WorkSpaces that you launch from this image.
For more information about using GPO to set the language for Office, see Customize language setup and settings for Office in the Microsoft documentation. Office 2016 and Office 2019 use the same GPO settings (labeled with Office 2016).
Before you can configure Office 2016 or Office 2019 policy settings, you must download the administrative template files (.admx/.adml) for Office from the Microsoft Download Center. After you download the administrative template files, you must add the office16.admx and office16.adml files to the Central Store of the domain controller for your WorkSpaces directory. (The office16.admx and office16.adml files apply to both Office 2016 and Office 2019.) For more information about working with .admx and .adml files, see How to create and manage the Central Store for Group Policy Administrative Templates in Windows in the Microsoft documentation.
Office 2016 and Office 2019 use the same GPO settings (labeled with Office 2016). If you don't see Administrative Template Policy definitions (ADMX files) retrieved from the local computer under User Configuration, Policies, the office16.admx and office16.adml files aren't correctly installed on your domain controller.
To migrate from Office 2016 to Office 2019 or from Office 2019 to Office 2016, you must create a BYOL bundle that is subscribed to the version of Office that you want to migrate to. Then, you use the WorkSpaces migration feature to migrate your existing BYOL WorkSpaces that are subscribed to Office to the BYOL bundle that is subscribed to the version of Office that you want to migrate to.
For example, to migrate from Office 2016 to Office 2019, create a BYOL bundle that is subscribed to Office 2019. Then use the WorkSpaces migration feature to migrate your existing BYOL WorkSpaces that are subscribed to Office 2016 to the BYOL bundle that is subscribed to Office 2019.
Last Modified: Jul 21, 2022 @ 8:38 am73 CommentsNavigationChange Log
Create Group Policy Objects (separate article)
VDA Group Policy Computer Settings (separate article)
User LockdownStart Menu
File Explorer
Google Chrome
Internet Explorer/EdgeInternet Explorer Security Zones
Internet Explorer Performance
Folder Redirection
Microsoft 365 Apps / Office 365 / 2021 / 2019 / 2016
Adobe Reader / Acrobat Reader DC
Citrix Files on Citrix Virtual Apps and Desktops (CVAD)
File Type Association
? = Recently Updated 2ff7e9595c
Comments