- #REINSTALLED OFFICE 2016 WILL NOT ACTIVATE INSTALL#
- #REINSTALLED OFFICE 2016 WILL NOT ACTIVATE WINDOWS#
The ELM console did throw warnings about things possibly not working with this layer assigned elastically, but I have been able to use the apps in this layer just fine most of the time. On-Campus by logging into the LSU network. In order to stay activated you will need to connect back to the LSU Activation Server Every 90-Days.
#REINSTALLED OFFICE 2016 WILL NOT ACTIVATE INSTALL#
This layer was the only App Layer where I had to actually join the domain to install the application, and then remove it from the domain before Finalizing the layer. The first method to stop Office to prompt you to activate an old Office 2016/2019 license, is to remove the license from your computer. You have now Activated your Microsoft Office 2016 License. Throughout my testing, I did not see this issue once until I started working on that final Micromedex/Toxicall elastically-assigned layer. That’s it Step 3: After completing the installation, launch any Office application, enter NKGG6-WBPCC-HXWMY-6DQGJ-CPQVG product key when asked to activate Office 2016 Preview. Office 2016 (standard apps minus OneDrive and OneNote KMS)Ĭore Apps (Adobe Reader, Cisco WebEx Meeting, and a few other apps)Īdmin Tools (RSAT, Notepad++, Firefox 57, and a few other apps) Once Office 2016 is installed, you’ll see Installation is finished message. VCache (D: volume with pagefile and Event Logs moved onto it) The layered image consists of the following:
#REINSTALLED OFFICE 2016 WILL NOT ACTIVATE WINDOWS#
Before I even get a chance to verify that both Office and Windows appear to be activated, the VDI begins shutting down, and I'm booted out. For the life of me I can't recall the exact message, so I'm going to try and grab the exact verbiage tomorrow, hopefully. Randomly - not all of the time, and I cannot reproduce it at-will - I will login to the VDI desktop, and a few seconds after the desktop loads will be presented with an Office 2016 message about needing to finish configuration/installation. I have Office 2016 installed in its own App Layer, following the recipe to the letter, using KMS activation. I've got a completely random issue that I'm hoping somebody else has come across before.
0 kommentar(er)
