I've created a post-install task to install Office 2016 for Mac, but the volume licensing is getting skipped. For my task, I mounted the .iso and copied the pkg. out to my desktop to zip it and upload it to my task - is this step necessary? Or can I upload the .iso directly to the task?

When users log into the imaged iMac, they are prompted to enter their Office 365 credentials in order to activate the software (which then ties the installation to their O365 account). I've got more testing to do to verify this, but it seems that when I mount the extracted pkg and install, the suite does not license, but when I mount the .iso locally, the suite licenses normally.

Could this be something getting lost in the unpacking of the .iso? Or am I maybe missing something else?
2 Comments   [ + ] Show Comments

Comments

This question is locked
  • There is a volume serializer package that you can run to license Office 2016, assuming you have a volume license. Did you download the ISO from the MS volume licensing website? You might want to check my blog post on building a package for deployment: http://www.itninja.com/blog/view/creating-an-office-2016-package-for-mac-deployment
  • Confirms my suspicion that either the search function on this site is sketchy or I'm just not as good at searching as I'd like to believe, because I searched the site yesterday and did not find your blog, which looks like it is exactly what I need.

    Yes. We downloaded the iso from the the MS volume licensing website.

    Forgive my probably remedial question, but why does the root package behave differently when launched from the mounted iso than it does when launched from the extracted from the iso? Or will that question be answered when I work through the steps in your blog?

Answers

0
chucksteel's blog helped my figure out, ultimately, that I didn't not have the most recent volume license .iso from Microsoft, and was missing the volume license .pkg - so I'm still not sure about the difference between launching directly from the iso and extrating the package to launch it independently, but with the new download (jan 2016 release, versus the sept 2015 release I'd been working with), I was able to run the VL package and license the suite during my post-install tasks.
Answered 04/28/2016 by: sarahmurray
Senior Yellow Belt

  • http://www.itninja.com/blog/view/creating-an-office-2016-package-for-mac-deployment
  • I'm glad I was able to help. We don't use the K2000 to image Macs but it is nice to know that the method is applicable.
Please log in to comment
This question is locked