@aporlebeke and @LU_justin , I got things working by removing the $3 variable from the MAYA_SUPPORT_PATH in @mscottblake 's script, so it just installs directly to the System Library folder.

I've just finished packaging both 2017 and 2018. We are running off a single license server. Originally, with 2017, I was stuck with an Autodesk system repair error when opening it. 2018 would still prompt me to enter my licensing information. Both of these applications opened correctly after reinstalling with the $3 variable removed from the install script.

I also found that the file created at the MAYA_SUPPORT_PATH location had been adding multiple entries of the data I had entered into a single file, because I was just deleting the /Applications/Autodesk folder and re-running the script when I was testing things. Autodesk did not like that! Make sure to delete that licensing file when you are testing. It could throw out an error that would be tough to track down if you don't think to look at that file location. This is what broke 2017 for me while getting things set up.

@mscottblake -- Thank you for posting your script, it was very helpful!

@ChickenDenders Thanks for the helpful push!

Initially even when I specified the root /Library/Application Support folder it still prompted for activation on first launch, however I think there may have been something with our Autodesk account. I had to completely disassociate our Autodesk account from Maya 2018 on our test computer and manually go through the process, including entering & updating some account info. I specified us as an institution rather than an individual.

After doing all that I ended up with a successful Maya 2018 activation.

Subsequent installs with the postinstall script that previously failed to auto activate Maya 2018 then succeeded in activating on first launch on several fresh test machines.

I edited @mscottblake original script to work with Maya/Mudbox 2018. It installed but didn't license correctly.

Can anyone see what i've done wrong?

[#!/bin/bash

####################################################################

Author: Scott Blake

Modified: 2017-02-10

Postinstall script to install and license Autodesk Maya 2017.

####################################################################

Command Line Parameters for Maya Setup

./setup [--option[=value]]

--help:

display the argument options of the installer and quit.

--noui:

disable the UI of the installer. If not specified, installer starts with UI.

--log=<filename>:

the log filename with path. If not specified, /var/log/autodesk/<app><version>INSTALL.log is used as log file.

--debug:

create the log file with detailed debug information.

--force:

force installation of the rpm (when this option is used, --nodeps --force will be used on all rpms to install.

--serial_number=XXX-XXXXXXXX:

specify the adlm serial number.

--product_key=<product code>:

specify the adlm product key.

--license_type=<kNetwork or kStandalone>:

specify the adlm license type.

--server_name=<name>:

specify the adlm license server name.

####################################################################

Changelog

Version 1.0 - Scott Blake

Initial script

####################################################################

Variables

PRODUCT_KEY="657J1"
SUITE_KEY="657J1"
SERIAL="398-93068255"
LICENSE_TYPE="kStandalone" # Options: kNetwork or kStandalone
LICENSE_SERVER="license.server.domain.com"

MAYA_SETUP_LOC="/private/var/tmp/Maya_2018/Install Maya 2018.app/Contents/MacOS/"
MAYA_SUPPORT_PATH="/Library/Application Support/Autodesk/CLM/LGS/${PRODUCT_KEY}_2018.0.0.F"

####################################################################

Code

Change directory to wherever the Maya setup is located

The setup file is dumb and seg faults when `pwd` is not the same.

cd "${MAYA_SETUP_LOC}"

if [ "${LICENSE_TYPE}" == "kStandalone" ]; then
# Trigger installation
./setup --noui --force --serial_number=${SERIAL} --product_key=${PRODUCT_KEY} --license_type=${LICENSE_TYPE}

# License separately since the setup binary is broken
# ../Resources/adlmreg -i S ${PRODUCT_KEY} ${SUITE_KEY} 2018.0.0.F ${SERIAL} /Library/Application Support/Autodesk/Adlm/PIT/2018/MayaConfig.pit

# Manually create random stuff since the setup binary is broken
mkdir "${MAYA_SUPPORT_PATH}/"
touch "${MAYA_SUPPORT_PATH}/LGS.data"
chmod 755 "${MAYA_SUPPORT_PATH}/LGS.data"
echo "_STANDALONE">>"${MAYA_SUPPORT_PATH}/LGS.data"
else
# Trigger installation
./setup --noui --force --serial_number=${SERIAL} --product_key=${PRODUCT_KEY} --license_type=${LICENSE_TYPE} --server_name=${LICENSE_SERVER}

# License separately since the setup binary is broken
# ../Resources/adlmreg -i N ${PRODUCT_KEY} ${SUITE_KEY} 2018.0.0.F ${SERIAL} /Library/Application Support/Autodesk/Adlm/PIT/2018/MayaConfig.pit

# Manually create random stuff since the setup binary is broken
mkdir "${MAYA_SUPPORT_PATH}"
touch "${MAYA_SUPPORT_PATH}/LGS.data"
chmod 755 "${MAYA_SUPPORT_PATH}/LGS.data"
echo "_NETWORK" >> "${MAYA_SUPPORT_PATH}/LGS.data"

echo "SERVER ${LICENSE_SERVER} 0" >> "${MAYA_SUPPORT_PATH}/LICPATH.lic"
echo "USE_SERVER" >> "${MAYA_SUPPORT_PATH}/LICPATH.lic"
fi](link URL)

@jthurwood It might help get better responses if you reformat your post to make the script render correctly.

I have seen Autodesk products in general act weird when using standalone licenses. For instance, the last time I deployed something like that, I had to manually activate it once, then the rest would activate properly. I should also note that I deployed with that script via network license, so there might be something else that needs to be manually entered into those license files.

My recommendation would be to install and license manually onto a machine and see what everything looks like.

Also, @ChickenDenders, I used that script within an installer package as a postinstall script, that's where the $3 variables come into play. They are referencing the target disk. I'm glad the script helped.

Hi all,

Just wondering if anyone has managed to suppress the startup dialog windows for Maya 2018?

The command-line used in some of the scripts in this thread,
/usr/bin/defaults write /Library/Preferences/com.autodesk.MC3Framework MC3Enabled -int 0

has no effect in Maya 2018.

Cheers,
Ron.

Here's my script for mudbox 2018 if anyone needs it.

#!/bin/bash



################################################################################

# Postinstall script to install and license Autodesk Mudbox 2018.

#

################################################################################

#

# ./setup [--option[=value]]

#

# --help:

#   display the argument options of the installer and quit.

#

# --noui:

#   disable the UI of the installer. If not specified, installer starts with UI.

#

# --log=<filename>:

#   the log filename with path. If not specified, /var/log/autodesk/<app><version>INSTALL.log is used as log file.

#

# --debug:

#   create the log file with detailed debug information.

#

# --force:

#   force installation of the rpm (when this option is used, --nodeps --force will be used on all rpms to install.

#

# --serial_number=XXX-XXXXXXXX:

#   specify the adlm serial number.

#

# --product_key=<product code>:

#   specify the adlm product key.

#

# --license_type=<kNetwork or kStandalone>:

#   specify the adlm license type.

#

# --server_name=<name>:

#   specify the adlm license server name.

#



#

################################################################################

# Variables

#



PRODUCT_KEY="498J1"

#SUITE_KEY="657I1"

SERIAL="123-1234567"

LICENSE_TYPE="kNetwork"  # Options: kNetwork or kStandalone

LICENSE_SERVER="servername"



MUDBOX_SETUP_LOC="/var/tmp/Install Mudbox 2018.app/Contents/MacOS/"

MUDBOX_SUPPORT_PATH="/Library/Application Support/Autodesk/CLM/LGS/${PRODUCT_KEY}_2018.0.0.F"



################################################################################

# Code

#



# Change directory to wherever the MUDBOX setup is located

# The setup file is dumb and seg faults when `pwd` is not the same.

cd "${MUDBOX_SETUP_LOC}"



if [ "${LICENSE_TYPE}" == "kStandalone" ]; then

  # Trigger installation

  ./setup --noui --force --serial_number=${SERIAL} --product_key=${PRODUCT_KEY} --license_type=${LICENSE_TYPE}





  # Manually create random stuff since the setup binary is broken

  mkdir "${MUDBOX_SUPPORT_PATH}/"

  touch "${MUDBOX_SUPPORT_PATH}/LGS.data"

  chmod 755 "${MUDBOX_SUPPORT_PATH}/LGS.data"

  echo "_STANDALONE">>"${MUDBOX_SUPPORT_PATH}/LGS.data"

else

  # Trigger installation

  ./setup --noui --force --serial_number=${SERIAL} --product_key=${PRODUCT_KEY} --license_type=${LICENSE_TYPE} --server_name=${LICENSE_SERVER}



  # Manually create random stuff since the setup binary is broken

  mkdir "${MUDBOX_SUPPORT_PATH}"

  touch "${MUDBOX_SUPPORT_PATH}/LGS.data"

  chmod 755 "${MUDBOX_SUPPORT_PATH}/LGS.data"

  echo "_NETWORK" >> "${MUDBOX_SUPPORT_PATH}/LGS.data"



  echo "SERVER ${LICENSE_SERVER} 0" >> "${MUDBOX_SUPPORT_PATH}/LICPATH.lic"

  echo "USE_SERVER" >> "${MUDBOX_SUPPORT_PATH}/LICPATH.lic"

fi



chmod -R o-w /Library/Application Support/Autodesk

chmod -R o-w /Applications/Autodesk

/bin/rm -rf "/var/tmp/Install Mudbox 2018.app"

exit 0

I have two packages that work independently, one for Maya 2018 and one for Mudbox 2018. When I run them on the same machine, I either get Maya that works and Mudbox doesn't or vise versa. The package that I install first works, then second one starts to launch but then goes away.
Thoughts?

I have two packages that work independently, one for Maya 2018 and one for Mudbox 2018. When I run them on the same machine, I either get Maya that works and Mudbox doesn't or vise versa. The package that I install first works, then second one starts to launch but then goes away.
Thoughts?

Is there an update for Maya 2018?

yes I believe there is a combo updater out there for Maya 2018..

@colleen_keenan I'm getting something similar... I have installed Maya 2018 and Mudbox 2018 via the instructions in this thread, and then ran the post install script on both applications. When I go to launch the applications, the icon bounces on the dock and then goes away. The application never opens. I have verified from the JSS log files that the install was successful without any errors.

@colleen_keenan I figured it out. Both with Maya and Mudbox. When I built the package in Composer I included the license within the Library/Application Support folder (screen shot attached)

Then, I was running the big postinstall script from @mscottblake. The log files said everything ran successfully, but then Maya and Mudbox would just bounce on the dock and close when I clicked on it. When I really thought about it, the license was already applied within the package I created, and then again when I ran the script. I omitted the script and created a new one to just install the application:

#!/bin/sh

/Library/temp/Install Mudbox 2018.app/Contents/MacOS/setup --noui

Then I created an "activation" policy scoped to a smart group with criteria of Mudbox 2018 Installed. I added a Files and Processes payload and filled in the Command Execute portion with the following info:

#!/bin/sh

/Library/temp/Install Mudbox 2018.app/Contents/Resources/adlmreg -i S #### #### 2018.0.0.F ###-######## /Library/Application Support/Autodesk/Adlm/PIT/2018/MudboxConfig.pit; /Library/temp/Install Mudbox 2018.app/Contents/Resources/adlmreg -i S #### #### 2018.0.0.F ###-######## /Library/Application Support/Autodesk/Adlm/PIT/2018/MudboxConfig.pit

Yes, you are seeing that correct. I ran the command twice. And here is why: When I ran the command on a machine locally, I received an message: "Serial Number doesn't exist. Call setSerialNumber". When I re-ran the command, it was successful.

This site was extremely helpful: https://www.moof-it.co.uk/technical/deploying-autodesk-maya-2018-with-jamf-pro/

Thank you @edullum ! My experience has been the same with having to rerun the serial activation twice. Your post put all the missing pieces together for us. Cheers

Thanks, @mscottblake Just changed your script to reflect the Install Maya 2019 installer, and it worked like a charm.

Sometime I'd love to talk with you about your printer scripting talk at MacAdmins 2018 last year I was there and blessed to be at MacAdmins this year too. I have a few quick questions. Not here though I understand.

Thanks again, @mscottblake, very cool!

@skinford You can almost always find me on Twitter or Slack. Same username.

Afternoon,

I am after some help if possible, please.

I am attempting to package and deploy Autodesk Maya and Mudbox 2019.

I have downloaded both of the .app files and have copied/edited a copy of the @mscottblake script for both (looks to have helped a few others, thanks for posting!).

I then copy the relevant app file to the /tmp directory and copy this into Composer - no issue. I then create a postinstall script, which is a copy of the edited script, and save that.

I then create a pkg from this. I them deploy the pkg through a policy with the Action set to Install.

When deploying the app file is downloaded into the /tmp directory, but then the install doesn't seem to start - I get the message:
Installation failed. The installer reported: installer: Package name is Autodesk Maya 2019 - Labs 2019
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

If I copy the .app file to /tmp manually and then run the command "/tmp/Install Maya 2019.app/Contents/MacOS/ setup --noui" from Terminal, it seems to work fine. Its just as if the postinstall script is maybe being ignored?

We're using JAMF 10.11.1 and deploying to Mojave 10.14.5. Also I am still quite new to JAMF/Mac App packaging.

Thanks in advance of any help/advice, James.

I just completed a successful deployment of both Maya and Mudbox with the server licensing model.
Check this link.

Instead of scripting the creation of the required files as are directed in steps 2-4, I used Composer to capture those files and create a second package, (six of one... do what make the most sense for you).

Install policy includes three payloads:
1) InstallMaya2019.pkg (created with Composer)
puts the installer into /private/tmp/

2) Maya2019License.pkg (created with Composer)
installs the following files:
- LGS.data
- LICPATH.lic
- nw.cfg
Into /Library/Application Support/Autodesk/CLM/LGS/XXXXX_2019.0.0.F

3) Files and Processes > Execute Command:
/private/tmp/Install Maya 2019.app/Contents/MacOS/setup --noui --serial_number=XXX-XXXXXX --product_key= XXXXX --license_type=kNetwork --server_name=your server url

Hi,

Thanks for your repsonse!

That all does make sense. Could I please ask jhow you're linking your various steps? I have created a package and linked it to a policy that caches the App file. I have then created an addtional script and linked that to another policy that I want to run after the App file copy policy has run.

Thanks,
James.

I created mine for a DEP/Pre-Stage enrollment process so just one policy is used to keep it simple.
Have you tested your process yet? Any errors?
Something that I also encountered during testing: After the apps are installed, if you launch Mudbox before Maya there are some license issues. I have that sorted out as well if you are interested.

Hi, thanks again.

We're not using DEP for our setup unfortunately, so we're deploying with Jamf Pro.

After playing this morning I have now...
Created a policy to copy the App file to /tmp directory
Have added a custom trigger to this package
Created a policy which installs and licenses Maya, once triggered as per above.

All now seems to be working. I am now looking into Mudbox being done the same way.

If you could advise about the Mudbox before Maya issue, that would be great, thanks. A colleague has informed me there was an issue last year around running them both post install.

Cheers.

I'm using Jamf Pro too. My DEP/Pre-Stage is an answer to "imaging in the modern world".
Using Composer to build the Mudbox package after Maya has been installed on the test machine. Placed the Install Mudbox.app in /private/tmp/. Saved that out as Mudbox2019.pkg.
Ran the manual install on the same test machine to gather required directories/files which are: /Library/Application Support/Autodesk/CLM/LGS/198K1_2019.0.0.F/
In that directory is the file: NGS.data
Go to: /Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F and copy the file nw.cfg to the 198K1_2019.0.0.F directory. Package that up as Mudbox2019Licensing.pkg

In Jamf Pro I created a policy includes three payloads:
1) Mudbox2019.pkg
2) Mudbox2019License.pkg
3) Files and Processes > Execute Command:
/private/tmp/Install Mudbox 2019.app/Contents/MacOS/setup --noui --serial_number=XXX-XXXXXX --product_key= XXX --license_type=kNetwork --server_name=server url

This process is similar to my Maya install policy, but it had to be created after installing Maya. Payload 3 eliminates the need for an additional script. Since Jamf runs the policies in alphanumeric order, Maya installs before Mudbox so everything works as planned. Hopefully my instructions above are not too confusing.

Righty oh, here is where I am...

So I have a single policy comprising:
- A pkg that copies the Maya App file to /tmp
- This script:

#!/bin/bash

################################################################################

#

# Script to install and license Autodesk Maya 2019.

#

################################################################################

# Code

#



# Installation

/private/tmp/Install Maya 2019.app/Contents/MacOS/setup --noui --serial_number=xxx-xxxxxxxx --product_key=657K1 --license_type=kNetwork --server_name=servername



# License separately

mkdir "/Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F"

touch "/Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F/LGS.data"

chmod 755 "/Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F/LGS.data"

echo "_NETWORK" >> "/Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F/LGS.data"



echo "SERVER servername 0" >> "/Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F/LICPATH.lic"

echo "USE_SERVER" >> "/Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F/LICPATH.lic"



echo "done" >> "/Library/Application Support/Autodesk/CLM/LGS/657K1_2019.0.0.F/nw.cfg"



exit 0

I have the same policy/script setup for Mudbox, with the Maya and 657K1 references replaced with Mudbox and 498K1.

I have tested installing Mudbox first and Maya after, they both seem to open and work independently of each other(?)

I want to do more with the scripts with regards what I have seen others do - delete the App file in the /tmp directory and supress the first run gumph, but I am more than happy with where I now am.

Thanks for the helpful info in this thread and @tomhastings

Looks good! No need to delete the app in the tmp file via script, it will self remove on reboot or log out.

Has anybody found a way to install this on Mojave?

I tried the following and all I get is a crash log.

/Users/shared/Install Maya 2019.app/Contents/MacOS/setup --noui --log=/tmp/Maya_2019.log --force --serial_number=566-XXXXXX --product_key= 657K1 --license_type=kStandalone

Here is a link to my crash log so I don't fill the page with nonsense.

Has anybody found a way to install this on Mojave?

I tried the following and all I get is a crash log.

/Users/shared/Install Maya 2019.app/Contents/MacOS/setup --noui --log=/tmp/Maya_2019.log --force --serial_number=566-XXXXXX --product_key= 657K1 --license_type=kStandalone

Here is a link to my crash log so I don't fill the page with nonsense.

The script that I have used above successfully installs Maya and Mudbox onto Mojave.

Could you copy the App file to /tmp/Install and then try using the line:

/private/tmp/Install Maya 2019.app/Contents/MacOS/setup --noui --serial_number=xxx-xxxxxxxx --product_key=657K1 --license_type=kNetwork --server_name=servername

Of course edited as you need it, just to see if that works? Not saying it will, as our setup is network license, tweaked to a standalone instance might be worth a look.