/build/static/layout/Breadcrumb_cap_w.png

Creating an Office 2016 package for Mac Deployment

I combined several resources to create our Office 2016 for Mac installer. The steps below outline the process that I followed. The resources I used include the following:

https://github.com/maxschlapfer/MacAdminHelpers/tree/master/Office2016PackageBuilder 

https://github.com/kcrawford/dockutil

https://github.com/talkingmoose/Outlook-Exchange-Setup-5

Things you will need:

* The scripts from the above sites

* A copy of the volume serializer package from the Microsoft Volume Licensing website (Microsoft_Office_2016_VL_Serializer.pkg). This is found inside of the Office 2016 for Mac download.

* The Packages app for creating a combing package. http://s.sudre.free.fr/Software/Packages/about.html

* The post_install script for the package (https://github.com/csteelatgburg/scripts/blob/master/MacOS/Office%202016%20post_install)

* A customized package from the Outlook Exchange setup site above (not covered in this document)

The basic process is as follows:

1. Create a package that installs Office 2016

2. Combine the Office 2016 package with the Outlook Configuration package and the script to update dock items.

3. Place the combined package in a disk image

4. Create the software title on the K1000

5. Create the managed install on the K1000


Creating the Office 2016 Package

1. Create a folder on your computer to create the package. I recommend something like /temp/Office2016

2. In the folder create a folder titled volume_license

3. Place the Microsoft_Office_2016_VL_Serializer.pkg file in the volume_license folder.

4. Open Terminal and change to the folder you created in step 1.

5. Run the Office2016PkgBuilder.sh script. The script will download the required files and create a folder called result.

6. Open the result folder and mount the disk image found there.

7. Copy the Office installer package to the folder you created in Step 1.


Combining the Office Package with the other components

1. Open the Packages app.

2. Create a new package. I recommend saving it in the same folder that you created above in step 1. I named my package Office2016Deployment.

3. On the Settings tab change the identifier to match your organization.

4. Set the version to the Office version that was created by the script above.

5. On the Scripts tab add the following files to the Additional Resources pane

a. Dockutil

b. The Office 2016 package you built above

c. The Outlook Auto configuration package. If you built a new Outlook Auto Configuration package change the name to OutlookAutoConfig.pkg before adding it to the resources.

6. Set the Post-installation script to the post_install script supplied. The post install script performs the following actions:

a. Installs Office 2012

b. Installs the Outlook configuration package

c. Updates the dock for all users

d. Removes Office 2011

7. Save the package

8. Build the package (click Build, Build).


Place the package in a disk image

1. In Terminal change to the directory you created above

2. Packages should have placed the output of the combined installer in a folder named build. Verify that it is there.

3. Use the following command to create a disk image with the package: hdiutil create –format UDZO –srcfolder build/Office2016Deployment.pkg Office2016.<version>.dmg Where <version> is the version number of Office, e.g. Office2016.15.21.1.dmg If you named your package something other than Office2016Deployment then change the srcfolder option accordingly.


Create the Software Title on the K1000

Unfortunately the K1000 doesn't detect the Microsoft Office Suite for Mac as an installed application because there isn't one .app that is Office. We will create a custom software title that detects the version of Word instead:

1. In the K1000 interface click Software

2. Click Choose Action, New

3. Enter Microsoft Office 2016 for Mac Standard for the name

4. Enter the version number

5. Select the supported operating systems

6. Enter the following for the custom inventory rule: PlistValueEquals(/Applications/Microsoft Word.app/Contents/Info.plist, CFBundleVersion, NUMBER, 15.19.1) Use the correct version number for the package you created.

7. Associate the disk image you created earlier.

8. Save the software title.


Create the Managed Install on the K1000

When KACE sees a disk image as part of a managed install it will mount the image and install and packages contained on the drive. Because we uploaded a disk image to the software title that means we can leave the defaults for the managed install in place.

1. In the K1000 interface click Distribution

2. Click Choose Action, New

3. Select the Office title that you just created from the Software dropdown menu.

4. Enter Office 2016 for Mac – Removes 2011 or something similar for the name.

5. Set the Execution menu to "With user logged off"

6. Select a test device in the Devices section

7. Click Save


Edit: 2017/11/03 - removed space from -srcfolder argument in hdiutil command.


Comments

  • (the second github link above is broken, but the shown address is right) - sarahmurray 5 years ago
    • Thanks, there was a space at the end of the target. Fixed. - chucksteel 5 years ago
  • Also, does this all work in OS X 10.11 - even the dock utility (listed on the site to work with 10.9 and 10.10 - have you tested it in 10.11)? - sarahmurray 5 years ago
    • Yes, I have done all of my testing on 10.11 so it's more likely that it might not work on 10.10. - chucksteel 5 years ago
  • manners: this looks awesome, btw - once I've run through it all, I'll definitely rate and elsewise promote this blog post, chucksteel... thanks for the time you took putting it together. - sarahmurray 5 years ago
  • See also https://derflounder.wordpress.com/2016/01/14/creating-an-office-2016-15-18-0-installer/ - MacDude 5 years ago
  • is volume license the same thing as assigning license via 365 portal? We assign our licenses via the 365 portal and we don't have activate with a key. Will this still work for us? - sam240 4 years ago
    • If your users sign into the Office applications using their 365 credentials then you don't need to use the volume license package. - chucksteel 4 years ago
      • Thank you Chuck but I'm confused. Yes our users login with 365 credentials. So do I skip the Creating the Office 2016 Package step? where should i start from? - sam240 4 years ago
      • Yes, these instructions are for building a package that uses the volume license package. You can still use the package from Microsoft to install Office and create the software title and managed install as described above, however. - chucksteel 4 years ago
  • The command for creating a disk image will not work in my case. hdiutil create –format UDZO –src folder build/Office2016Deployment.pkg Office2016.<version>.dmg
    I get a message " hdiutilil: create: Only on image can be create at a time. Usage: hdiutil create <sizespec> [options] <imagepath> " - Barracuda_de 3 years ago
    • srcfolder is one word, it looks like you have a space in there, which apparently I have in the instructions. I'll fix that. - chucksteel 3 years ago
  • When I run the ms_office_2016_pkgbuilder.sh file on my machine, the no license pkg found error message comes up. The file is in the same directory as the pkgbuilder file. What do I have to do? - fleminsa 3 years ago
    • Read steps 2 and three under the "Creating the Office 2016 Package" section. - chucksteel 3 years ago
  • Once this is installed with volume licensing, is there a way to set up the machine to automatically sign the user out of Office365 from the Office2016 desktop app when the machine shuts down without removing the volume license? I'm looking to use the script (if there is one) for loaner laptops that we periodically make available for employees. - anonymous_142769 3 years ago
    • Not that I'm aware of. We re-image our loaner laptops when they are returned, so this hasn't been an issue for us. - chucksteel 3 years ago
This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ