This may be so because a machine has just had its OS installed or re-imaged, and the deployment tools are now automatically installing all the other software destined for this machine. The installation may take place while no user is logged in, and the machine is waiting at the login window.Installer scripts may make use of this to adjust their behavior accordingly. This happens to set an environment variable, COMMAND_LINE_INSTALL, which is not present if an installer package is double-clicked and run using the standard Installer UI. mpkg), the installation will take place by some invocation of the installer command-line tool. If installing a standard OS X installer package (.pkg.There are several ways in which the context of such deployment tools install software is different than that of a user manually installing software onto his or her own personal machine (where the user also has admin privileges), but two important ones are:

do users install on their own via a self-service system, is it installed automatically at the time the machine is deployed to a user, or later on a schedule, etc.). These tools make it possible for IT to deploy the software without numerous manual steps on each client, and control when the software is made available and in what context (i.e. Volume licensed copies of software are often installed within organizations using automated deployment tools like Munki or Casper. The volume license is activated during the install process, very similar to Office 2011.

Microsoft provides Office 2016 for Mac in two flavors: one for Office365 subscribers which users can “activate” by signing into their O365 accounts, and one for organizations entitled to a volume license through some agreement. In this post, as usual I’ll go into some detail about this installer’s problems, review some known workarounds and propose some solutions. Office is probably the most common software suite deployed in organizations, and so it’s a very bad sign that 2016 for Mac has begun its life as an installer that cannot be deployed without workarounds and/or repackaging. The best way to “fix” the installer is to have Microsoft fix it so that it can be deployed the same way we deploy any other software. At least a couple posts exist already for how to “fix” the installer and deploy the software, but I haven’t seen anyone actually detail some of these issues publicly. Office 2016 for Mac comes in an installer package that has been causing several issues for Mac sysadmins deploying it in their organizations.

Microsoft office pkg file