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. I have an existing process to using, 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. 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. Since my work has a volume license, this isn’t a screen I should be seeing. This is a problem that I’ve seen before with and usually involves the license file not being applied when it should be. This behavior is seen on Macs in the following cases: • Office 2016 is installed and then updated to 15.12.3 while nobody is logged in • Office 2016 is installed and then updated to 15.12.3 without any Office applications being launched between the initial installation and the update. 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.

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. The needed file is /Library/Preferences/com.microsoft.office.licensingV2.plist. What is ng player for mac. If you have a volume-licensed version of Office 2016 installed on your Mac, you should have this file.

For Mac-only environments, Casper is the go-to item. But it is not cross-platform. David_CSG I need to be able to apply password and encryption policies to the Macs. For Mac-only environments, Casper is the go-to item. But it is not cross-platform. David_CSG I need to be able to apply password and encryption policies to the Macs.

To address this issue, you can use ‘ ability to add resources to a Packages-built package. See below the jump for an example using an Office 2016 volume licensed installer package, the, as well the com.microsoft.office.licensingV2.plist license file to build a unified Office 2016 15.12.3 installer package that does not prompt for a product key. Set up a new Packages project and select Raw Package. In this case, I’m naming the project Microsoft Office 2016 15.12.3 3.

Once the Packages project opens, click on the Project tab. You’ll want to make sure that the your information is correctly set here (if you don’t know what to put in, check the Help menu for the Packages User Guide.

The information you need is in Chapter 4 – Configuring a project.) In this example, I’m not changing any of the options from what is set by default. Next, click on the Settings tab. In the case of my project, I want to install with root privileges and not require a logout, restart or shutdown. To accomplish this, I’m choosing the following options in the Settings section: • In the Post-Installation Behavior section, set On Success: to Do Nothing • In the Options section, check the box for Require admin password for installation 5. Click on the Scripts tab in your Packages project. Select your installers and drag them into the Additional Resources section of your Packages project.

In the case of my example, I’m selecting the following installers: • Microsoft_Office_2016_15_11_2_Volume_Installer.pkg • Microsoft_Excel_15.12.3_Updater.pkg • Microsoft_OneNote_15.12.3_Updater.pkg • Microsoft_Outlook_15.12.3_Updater.pkg • Microsoft_PowerPoint_15.12.3_Updater.pkg • Microsoft_Word_15.12.3_Updater.pkg 7. Select the com.microsoft.office.licensingV2.plist file and drag it into the Additional Resources section of your Packages project. The last piece is telling the installers to run and for the com.microsoft.office.licensingV2.plist file to be fixed as needed. For this, you’ll need a postinstall script.