![]() The easiest fix I’ve found in my testing is to get the necessary volume license file from a machine that has Office 2016 installed on it and put it back on an as-needed basis. These two scenarios will likely apply if you’re building a new machine using an automated deployment tool, but likely will not if you’re a home user. Office 2016 is installed and then updated to 15.12.3 without any Office applications being launched between the initial installation and the update.Office 2016 is installed and then updated to 15.12.3 while nobody is logged in.This behavior is seen on Macs in the following cases: This is a problem that I’ve seen before with previous Microsoft Office 2011 installers and usually involves the license file not being applied when it should be. Since my work has a volume license, this isn’t a screen I should be seeing. However, when I installed the combined Office 2016 installer with DeployStudio, then logged in, I was asked to sign into an account and activate Office. I have an existing process to build a combined Office 2011 installer using Packages, which I’ve used successfully for a while, so I decided to see if I could apply the same process to building an Office 2016 installer. ![]() ![]() One of the issues I worked on this week was building a new Office 2016 installer after Microsoft began making Office 2016 available to its volume license customers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |