top of page


Öffentlich·131 Mitglieder
Thomas Panfilov
Thomas Panfilov

EXCLUSIVE 2016 Microsoft Office 2016 Pro Plus VL 16.0 November 2019

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.

EXCLUSIVE 2016 Microsoft Office 2016 Pro Plus VL 16.0 November 2019

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.

In this article, we will discuss the basics of MS Office KMS activation (this guide applies to the volume editions of Office 2021, 2019, and 2016, including Project and Visio). This takes place after you have to install and activate the KMS (Key Management Service) host on Windows Server 2022/2019/2016/2012 R2.

Note. This guide applies only for Microsoft Office 2021/2019/2016 under volume license excluding Microsoft 365 Apps for enterprise (ex- Office 365 ProPlus). This MS Office version is subscription-based and can be activated online only.

You need to run the downloaded file (office2016volumelicensepack_4324-1002_en-us_x64.exe, office2019volumelicensepack_x64.exe, or Office2021VolumeLicensePack_x64.exe) as an administrator on your KMS server. The installer contains new KMS host license files. These license files allow your KMS host service to recognize KMS Host keys for Office, Project, and Visio. The activation files update script will be launched.

If you want to use Active Directory-Based Activation, you need to choose this option in your Volume Activation Tools wizard (you can use the ADBA activation for the clients running Windows 11/10/8.1 or Windows Server 2012/2012 R2/2016/2019/2022).

By default, volume licensed versions of Office 2021, 2019, and Office 2016 are preinstalled with the Generic Volume License Keys (GVLK). GVLKs allow the installed Office copy to automatically discover and activate Office on the KMS host by using a special VLSC record in DNS.

Meanwhile, after you installed the KMS host or created the ADBA object, the installed MS Office copy on the computer is activating automatically (as long as the computer has a GVLK installed, and the computer is joined to the Active Directory domain). Therefore, the GVLK key is not required usually (they are preinstalled in all Office 2021/2019/2016 volume license products).

You can get an up-to-date GVLK list for KMS activation of Office 2021, 2019, and 2016 (including Office Professional Plus/Standard, Project Professional/Standard, Visio Pro/Standard, Access, Excel, Outlook, Word, Skype for Business) using the link.

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.

When you are using an Microsoft 365 (formerly Office 365) installation or a Click-to-Run installation of Office 2013, Office 2016, Office 2019, and Office 2021, then the updates will not be offered via Windows Update but will be installed automatically. Depending on your installation source, you can manually check for updates from within any Office application or the Microsoft Store on Windows 10 and Windows 11.

  • 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

Microsoft 365 Apps, Office 365, Office 2019, and Office 2016 are all version 16.0, thus the same GPO settings work for all of these versions. In Group Policy Editor, the GPO settings are under the Office 2016 folders.

If you are wondering how to update Microsoft Office and download & install Office updates on your computer, this post offers a detailed guide for how to update Office 365/2021/2019/2016, etc. To recover deleted or lost Word, Excel, PPT, or any other kind of files for free, you can try MiniTool Power Data Recovery.

How to Activate Microsoft Office 365/2021/2019/2016/2013This post teaches you how to activate Microsoft Office 365/2021/2019/2016/2013 on Windows 11/10. Learn how to activate Microsoft Office with product key or KMS.

I would like to say that even though it may show office 2016 or 365, it doesn't matter. What matters, is the version that is version 2104(the latest version as if right now I am typing this text), etc.

For Win10 also look under Settings/Apps. Check to see if there are multiple entries for MSOffice under Apps and Features. You probably have listed multiple MSOffice listings, for the one you purchased 2016 and another entry for Office that is the Preloaded Software. I had several customers that "all the sudden" had 365 profile features after MSPatches and after uninstalling the preloaded office, everything was back to 2016 version

We had a similar issue with cloud exchange and Outlook 2016. Users would get the popup constantly and it was causing a lot frustration for both our users as well as our support team. The solution that ended up working for us was to enable modern authentication on both the client and server side and disable legacy authentication. -us/exchange/clients-and-mobile-in-exchange-online/enable-or-disable-mo... -Team-Blog/Disabling-Legacy-Authentication-in-Exchange-Server-2019/ba-p/712048 Opens a new window

As for the client, you just need to create the "EnableADAL" registry keys. The link below has a section that shows how to enter this for Outlook 2013, but just change the 15 to 16 for Outlook 2016.This link outlines enabling modern auth for all office products. -modern-authentication-office/

The bigger challenge before you go too far is that Microsoft doesn't support Office 365 Pro Plus on Server 2019 -little-unknown-secrets-of-using-office-365-proplus-and-office-2019-on-a-virtual-desktop-environment-survival-guide/

Do you want to change the product key of Office 2019 or Office 2016? Would you like to change Microsoft Office 2019 or Office 2016 product key without re-installing the Office suite? In this guide, we will show how you can change or update the product key.

I believe the registry only has the major build - if you want the full value, Version 2007 (Build 13020.20004 Click-to-Run), you need to get FileVersionInfo. from outlook. This has a C# example

Thanks. You answered a lingering question of mine I'd tried twice to get resolved from Microsoft tech support. I do indeed have the final RTM version of office 2016 installed and activated. I'd been afraid I'd activated a preview version when I saw vl rtm's circulating. The higher build number and all.


Willkommen in der Gruppe! Hier können Sie sich mit anderen M...


  • S
  • Gaurworld smartstreet
    Gaurworld smartstreet
  • R
  • Putrsa Chola
    Putrsa Chola
  • connections nyt
    connections nyt
bottom of page