/build/static/layout/Breadcrumb_cap_w.png

Deploying Office 2019 for Mac Kace

Has anybody used Kace to deploy Office 2019 packages that also use the volume license serializer?  If so how did it go.  I was thinking of just creating a dmg of the Office 2019 pkg file and the serializer and deploy that way.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: chucksteel 1 year ago
Red Belt
0

Yes, we have deployed 2019 using a script. I generally prefer managed installs, but the software catalog doesn't detect Office 2019 for macOS as an application suite, so a script is easier. I use a customized version of this tool to build the package:

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

The script will build a DMG file containing the latest Office 2019 installer and the serialization package all in one. I modified my version to download and install the latest Office package so whenever we push the script the machine gets the latest version. We also use the same script for new machines.




Comments:
  • Sorry. I know this post is old, but I'm new to much of this and I'm trying to deploy Office 2019 on a number of Macs in our company. I tried to use the script that you referenced, but I get an error when I try to run it. I am running the script on a Mac Mini. Would you be able to offer any addition info about how to do this or point me to a guide of some sort.

    I'm not having much luck finding helpful AND current documentation for managing Macs via KACE SMA. - jjacob 3 months ago
    • I'm still using the same basic technique successfully. If you are getting an error when running the script, it would be helpful if you shared the error. - chucksteel 3 months ago
      • This is what I get:
        $ sudo ./MS_Office_2019_PKGBuilder.sh --exclude "OneDrive onenote.mac outlook"
        : invalid option
        Usage: /bin/sh [GNU long option] [option] ...
        /bin/sh [GNU long option] [option] script-file ...
        GNU long options:
        --debug
        --debugger
        --dump-po-strings
        --dump-strings
        --help
        --init-file
        --login
        --noediting
        --noprofile
        --norc
        --posix
        --protected
        --rcfile
        --restricted
        --verbose
        --version
        --wordexp
        Shell options:
        -irsD or -c command or -O shopt_option (invocation only)
        -abefhkmnptuvxBCHP or -o option

        I have also tried it without the exclude option, but it produces the same error. I just noticed that it appears to be telling me to use sh to run the script... Sorry, I told you I was new to this. When I run with sh I get a different error:

        $ sh ./MS_Office_2019_PKGBuilder.sh --exclude "OneDrive onenote.mac outlook"
        : command not foundGBuilder.sh: line 29:
        : command not foundGBuilder.sh: line 30:
        : command not foundGBuilder.sh: line 35:
        : command not foundGBuilder.sh: line 39:
        : command not foundGBuilder.sh: line 42:
        -:1: parser error : Document is empty

        ^
        : command not foundGBuilder.sh: line 45:
        : command not foundGBuilder.sh: line 48:
        '/MS_Office_2019_PKGBuilder.sh: line 58: syntax error near unexpected token `do
        '/MS_Office_2019_PKGBuilder.sh: line 58: `do - jjacob 3 months ago
      • Is your script executable? How did you get a copy of it from the GitHub page to your computer? - chucksteel 3 months ago
      • I copied the script from the page with cmd+c and then pasted in text edit and saved as .sh. I modified a few things in the script as directed in the instructions on the GitHub page. Based on those same instructions I made the script executable with chmod 755. - jjacob 3 months ago
 
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