Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
@RonBarker - This thread is about 2016 - 2013 does not have the issue. As for making the clients a 2016 DVD, that doesn't work because you still have to register an account to the installation of Office 2016 on that machine. The key literally doesn't matter after that either... upon installing again, it will require the user to log in to an account registered to the software and it has to be from that particular machine as well.
More recently my company has been receiving machines that already have the hardware registered with Microsoft as having Office 2016 purchased for it and when you log in to your MS account is validates that the machine should have the software and let's it run. Literally no key ever given... a completely new way of delivering software. It can also be a pain in the a** though - if you have a different version pre-installed (typically Office 365 is) it will say Office has been purchased for the machine but then will not activate when you try and use it... because although the applications themselves are identical (Word, Excel, etc.) they technically are not the same as what you purchased. Of course you can download the installer for your purchase from your MS account online that' snow registered to the purchase... but you better make sure you remove the pre-installed version (Office 365, etc.) because the system will still run the wrong version of the apps and fail to properly activate. (good grief Charlie Brown!)
At any rate there *is* a solution but it is only good for companies... those that contract their services and work with individuals are still out of luck (sorry). The option is to purchase volume licensing and then burn the ISO for whatever version of 2016 you need and install on each machine from that. No hassles in setting up a licensing server and you just pay for additional keys as needed and install the good old fashioned way.
We've also found this is better too because it uses the MS installer for the installation rather than Click-To-Run. In the past we've found that Click-To-Run installations cause problems with other Office products we purchase later on an as-needed basis, such as Visio, because those individual purchases are always "here's your key and here's a link to an ISO file" and the installer is consequently an msi. I had to jump through all kinds of hoops recently to get an msi version of Visio to install on the same machine we had already purchased Office which used the Click-To-Run installer! Here's a hint - the OfficeDeplymentTool can be modified to accomplish the task. ;-)