You can get the suite and individual app pkgs from https://macadmins.software
I run 2 policies: One to cache the packages because of the size & the second to install the specific cached packages. I have the volume licence key packaged separately so I can uninstall it easily without removing all the apps.
You could put together an installer package using Composer that would copy both the MS Office installer and Serializer to a temporary location and include a postinstall script to run the two in sequence using the installer command then remove the two once that is completed. That would work.
Just to chime in, I also use a single policy with two packages, exactly like @mlizbeth. I don't know if packaging both in Composer will work but I would advise against it unless there's a specific need in your environment for it. Having the packages separate in one policy works perfectly and allows you to update the policy easily by just uploading the updated installer and changing the installer package in the policy instead of having to rebuild a composer package every time you need to update.
I would keep it one policy, two separate packages. Since new versions of Office 2019 come out every month, it would save a whole of time. Also, I've noticed from time to time Office 2019 becomes unlicensed after applying updates. I have a policy available in Self Service that re-installs the serializer so that the users can re-serialize office if it becomes unlicensed.
When I first started as an administrator, I wanted to put everything in one package, from Adobe to Office. In my experience, and I am sure others too, keeping it modular is better because it can be reused in multiple different ways. That's not to say that installing Office and the Serializer and capturing with composer won't work, just that if someone needs to be reactivated and that is your only package, it turns out to be a ~2GB download.
In one case when I was deploying Office 2019 for the first time, it upgraded the Office 2016 users to 2019 but did not serialize properly and I had to run the seralizer separately instead of the giant activated package. Just my 2 cents though, there is no wrong way to approach this.
One year I put all my configuration type packages into one super-giant package for deployment to a bunch of student labs. I wrote a script that installed all the packages in alphabetical order and I was really impressed with my ingenuity. At the time (for some reason) I thought it would be really cool and I figured I wouldn't need to change any of the individual component packages over the course of the year. Except I did have to make changes and it was a massive pain having to replace individual components by rebuilding the super-giant package each time. So yeah probably don't do that. Keep it all separate if you can.
I'm on the super granular, Individual policies for everything and anything that needs deployment train. As stated by others above...
1 Policy, 2 Packages.
MS Installer - Deployed 1st
MS Serializer - Deployed 2nd
Done Deal. Easy to swap out the package on the fly to the latest version of ms office.
The workflow is likely the same, if not similar to the image I posted above.
Make a policy -> add the Office Installer -> add the Office Serializer -> Scope it
and it will install Office first, then serialize the installation.
If you want to deploy a new version of Office 2019, just upload it to the JSS, go to your policy and select the new Office pkg.
I like to delete both packages from the payload and reselect Office 2019 and then the Serializer just so I know it executes in the proper order: Office -> Serial license
However in my environment, Office 2019 updates are managed with Configuration Profiles, so I only update the Office package as needed for our DEPNotify installation.
Thank you @mlizbeth thats exactly it (Except I always disable that annoying Restart Option payload!)
You can use this to create individual Office PKGs for use in patch management, but the entire office installer should work too. It will embed the serializer in the resulting PKG.
What we do is download the individual packages from macadmins.software, relabel them Word_July2019.pkg, Excel_July2019.pkg, etc. Our policy just does the usual download & install process, then we run the volume serializer. Be sure in your JAMF Admin to set the priority to 11, that will force it to run after the Office packages (default priority is 10).
Hey all. Rather than wasting precious time and space re-packaging apps into your distribution points every month, you should check out @talkingmoose's scripts for MS Office 2019 deployment. It works every time for my JAMF environment even with the serializer .pkg. No need to build anything out in Composer. Here is a link to his scripts and an example photo of how I do it at HBO for shared Macs that need a serialized version of Office 2019.
You utilize the URLs from https://macadmins.software/ to hardcode what package you want to trigger from the script. I created 3 scripts. One for the base O365 VL package, one for Skype for Business and one for Teams (the 3 scripts in the image)
Yes it does... If you look on the site, they still list the standalone packages for 2019. Here is an example of the script if you wanted to make it for Word 2019 Standalone Installer based off of the macadmins site (https://macadmins.software/) showing the link to be https://go.microsoft.com/fwlink/?linkid=525134
You could make packages with Composer that run the script if you wanted to use this script in Patch Management too.
Written by:William Smith Professional Services Engineer Jamf firstname.lastname@example.org https://gist.github.com/talkingmoose/a16ca849416ce5ce89316bacd75fc91a
Originally posted: November 19, 2017 Updated: March 27, 2018
Instructions: Update the linkID value to one of the corresponding Microsoft products in the list and run the script with elevated privileges. If using Jamf Pro, consider replacing the linkID value with "$4" and entering the ID as a script parameter in a policy. Except where otherwise noted, this work is licensed under http://creativecommons.org/licenses/by/4.0/ "You say goodbye and I say exit 0."
linkID="525134" # AutoUpdate SKUless download
/usr/bin/curl -JL "$url" -o "$linkID.pkg"
/usr/sbin/installer -pkg "$linkID.pkg" -target /
/bin/rm -f "$linkID.pkg"
Photo attached of the MAU Config Profile we use
I am unable to upload any packages to Jamf Cloud. Is anyone else having this issue? It gets to 100% then gets a loading screen and then all the fields are empty except the last two which then say "null"
If you look within the Serializer iso, there's a readme.txt that gives some clues on how to set this up. With some help from D8, we use a policy that downloads the software from Microsoft links (as in txt file) then apply the Serializer package.