Anyone ever tried packaging Maya as part of Autodesk's Entertainment Creation Suite? Judging by the lack of posts, i'm guessing people may have given up in disgust.
Thanks to some pretty intense googling today, i've come up with this. Full credits given in the readme.
https://github.com/franton/Maya-Postflight-Installer
This saved my bacon today. Hopefully it'll help save someone else's!
Alas I am calling it quits on trying to get this to work. Been at this days now with no luck. 50 plus manual installs here i come :(
This was as far as i got before the dummy hit the floor 20 yards away
If anyone has any ideas as to the issue thenwould love to hear them.
#!/bin/bash
# Script to install Maya 2016 ext 2 and Mudbox 2016 and Mental Ray
# Install Mudbox 2016
/Install Mudbox 2016.app/Contents/MacOS/setup --noui --log=/var/log/mudbox2016install.log --force --serial_number=XXX-XXXXXXX --product_key=498H1 --license_type=kStandalone
#Install Maya 2016
/Install Maya 2016 Extension 2.app/Contents/MacOS/setup --noui --log=/tmp/Maya_2016.log --force --serial_number=XXX-XXXXXXX --product_key=793H1 --license_type=kStandalone
#Install Mental Ray 2016
/Install mental ray For Maya 2016 Extension 2.app/Contents/MacOS/setup --noui --log=/tmp/MentalRay.log
#Register the Products
/Install Mudbox 2016.app/Contents/Resources/adlmreg -i S 498H1 793H1 2016.0.0.F XXX-XXXXXXXX /Library/Application Support/Autodesk/Adlm/PIT/2016/MudboxConfig.pit
/Install Maya 2016 Extension 2.app/Contents/Resources/adlmreg -i S 657H1 793H1 2016.0.0.F XXX-XXXXXXXX /Library/Application Support/Autodesk/Adlm/PIT/2016.5/MayaConfig.pit
# Disable intro screens
/usr/bin/defaults write /Library/Preferences/com.autodesk.MC3Framework MC3Enabled -int 0
#Remove installers from /
rm -rf /Install Maya 2016 Extension 2.app
rm -rf /Install Mudbox 2016.app
rm -rf /Install mental ray For Maya 2016 Extension 2.app
exit 0@garypuk I had similar issues.
I'm testing 10.11.5 on our machines, and the script you've outlined above works for the Maya 2016 installer, but not the Maya 2016 Ext 2 installer.
When I launch Maya Ext 2 for the first time after the postinstall runs, it still prompts for serial number and product key whereas the regular Maya 2016 app has this information applied and activates fine after the postinstall.
I reckon its the '2016.0.0.F' part as it must relate to the version number or something but I have no idea were i would get this. Are you installing a stand alone multi seat version also?
@garypuk standalone
Have had to roll out Maya 2016 Sp 6 as just cant get ext 2 working. Mudbox works as long as you run it as an admin first as it must want to write something to a location a standard user doesnt have access to.
Hi All,
I am new to the Casper Suite, so feel free to point out what I'm missing. We use multi seat licensing for the Autodesk Entertainment Creative Suite Ultimate to install Maya and Casper 2016. I see that there have been alot of issues imaging these 2 packages but I packaged both with Composer (Installed, serialized and customized) and they seem to work fine...What am I missing?
Also 2017 came out today, but I haven't tested it yet.
Hi Maristchris
I tried using Composer to start with but what I was finding was that when another user logged inand tried to use it, Mudbox hung and Maya wanted to be registered again. This is despite filling a user template. I tried a few times but never got it to work correctly. Glad you managed to do so.
Ok, thanks for the clarification.
We use a single user with the same username, secured with DeepFreeze in our labs. I'll have to do some more testing, but the simplified user structure might be the reason it still works on our machines. Thanks again.
-Chris
OK,
I've spent the day working with the 2017 version and I'm now having issues too. The current problem I have is with Mudbox. When I use composer to capture the software, Mudbox closes immediately after launch, so I am stepping away and looking at scripted methods.
I am now walking through the different scripts (thanks all) in Terminal. So far I've gotten Mudbox to install with:
sudo /Users/administrator/Desktop/Install Maya 2017.app/Contents/MacOS/setup --noui --log=/Users/administrator/Desktop/Install Maya 2017.log --force --serial_number=123-12345678 --product_key=793i1 --license_type=kStandalone
Mudbox 2017 seems to install and work fine with this command, but throws an error about closing unexpectedly when the program is closed properly. The same behavior occurs when I use the GUI to install the software, so I think thats just a Mudbox issue.
Do I still have to use the adlmreg command? It seems to be activated already.
If the adlmreg command is used what should be put in to replace "2016.0.0.F"? I assume that is a version code of some sort. I tried "2017.0.0.A" (a wild guess) with this command:
sudo /Users/administrator/Desktop/Install Mudbox 2017.app/Contents/Resources/adlmreg -i S 793i1 2017.0.0.A 123-12345678 /Library/Application Support/Autodesk/Adlm/PIT/2017/MudboxConfig.pit
and got error "Invalid number of arguments."
What am I missing? Thanks in advance. -Chris
Don't feel too bad, I'm having similar fits trying to get the 2017 versions working as well. Also seeing your "Program Closed Unexpectedly" error on scripted and GUI installs, so thats a product bug for sure, at least on 10.11.x systems.
It appears that they've made some changes to the licensing portion of these products. For instance, I've found that license files are no longer being written to
/private/var/flexlm/Instead, at first-time launch, they are creating multiple files (2-3) per product under
/Library/Application Support/Autodesk/CLM/LGS/<productKey>_2017.0.0.F/where <productKey> is your key for Maya or Mudbox. Inside of each folder are separate files that include the "SERVER" and "USE_SERVER" lines we've previously seen in the .lic files.
I've bashed my head against this all afternoon and I'm giving up for the day. I'll post any results if I make headway with it.
Ok, thanks.
Just FYI, that folder you mention has 2 files in it for me, both with a single line. Here are the file names and txt in them, in case it helps:
EXP_INFO.data
2018-08-17
LGS.data
_STANDALONE
We use standalone multi seat licensing. -Chris
I too am looking at Maya 2017. Right now, I'm testing Autodesk's approved silent install method. The software installs without issue, but it doesn't seem to be correctly setting the license type to network, nor is it setting the server name.
Based on the advice provided above, there are two files that aren't being created by the installer that should be, if you want to use network licensing:
/Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LICPATH.lic
/Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LGS.data
For LICPATH.lic, the content for me is:
SERVER server.host.edu 000000000000
USE_SERVER
and for LGS.data, the content is:
_NETWORK
So, what I'm doing to work around Autodesk's buggy installer is to just manually create those two files.
In my instance, I'm using "variant 2" that I documented above. In the post-install script, after I call the Autodesk installer, I'm creating the directory and echoing out to the files in question.
Seems to work so far. Our faculty doesn't use Mudbox, so that isn't an issue here.
For what it's worth, a case was opened with Autodesk, and they've responded: the "setup" installer cannot configure the licensing information for Maya. They don't consider it a bug - they consider it "a feature that hasn't been implemented yet." They don't expect it to return until Maya 2018 at the earliest.
Their recommendation matches my post immediately before this one: manually create those two files.
FYI, I had trouble with the script route as well and ended up packaging the three files that go into /Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F as the script option doesn't seem to work, resulting in a 'network license server not responding' error:
#!/bin/bash
if [ -f /Library/Installers/Install Maya 2017.app/Contents/MacOS/setup ] ;
then
say "Installing Maya"
# Install Maya 2017 with our serial number and server information
/Library/Installers/Install Maya 2017.app/Contents/MacOS/setup --noui --log=/Library/AdminToolBox/Maya_2016.log --force --serial_number=123-12345678 --product_key=657I1
# These parameters (above) are being ignored: --license_type=kNetwork --server_name=animation.lan
# Disabled these lines as there is something wrong which is unclear. Using pkg instead
# Need to create this directory as it doesn't exist and that would cause echo commands to fail
#mkdir /Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F
#echo -n "SERVER animation.lan 000000000000" >> /Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LICPATH.lic
#echo -n "_NETWORK" >> /Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LGS.data
#echo -n "done" >> /Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/nw.cfg
# Disable intro screens
/usr/bin/defaults write /Library/Preferences/com.autodesk.MC3Framework MC3Enabled -int 0
fiSo, the above installs Maya 2017 and together with the three files I packaged, everything seems to work.
Same shit, different Autodesk product.
Will they ever get their house in order?
We deploy the app installer to /tmp and then run this post install script.
This is for 2016 Ext 2 but adjust the paths and it works 2017 too.
#!/bin/sh
if [[ -e /tmp/Install Maya 2016 Extension 2.app/Contents/MacOS/setup ]]; then
/tmp/Install Maya 2016 Extension 2.app/Contents/MacOS/setup --noui
if [[ ! -e /Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F ]]; then
mkdir -p /Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F
fi
cat<<EOF>/Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F/LGS.data
_NETWORK
EOF
cat<<EOF>/Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F/LICPATH.lic
SERVER adsk-license 000000000000
USE_SERVER
EOF
cat<<EOF>/Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F/nw.cfg
done
EOF
else
echo "ERROR: Maya installer not found."
exit 1
fi
rm -rf /tmp/Install Maya 2016 Extension 2.app
exit 0Perhaps the issue you are having with the previously mentioned script is that you are appending to the files in /Library/Application Support/Autodesk/CLM/LGS/657I1_2017.0.0.F so if there is already data there or even whitespace you will possibly end up with an invalid file. Try replacing >> with just > or use cat<<EOF>...EOF instead.
cheers
Matt
Hi everyone, I've just started needing to deploy Maya 2016 on our campus network and come accross this thread. I just thought I'd throw my solution into the mix:
Basically Matts script worked fine for installing the package, but the licensing still didn't work on our machines for some reason and it would throw an error saying it couldn't determine the license method. So, I've ended up taking the script and adding the setup parameters into it from some other users posts and it looks to be working very well for us on macOS 10.11. Here's what my postInstall script now looks like:
#!/bin/sh
if [[ -e /tmp/Install Maya 2016.app/Contents/MacOS/setup ]]; then
/tmp/Install Maya 2016.app/Contents/MacOS/setup --noui --serial_number=560-xxxxxxxx --product_key=793H1 --license_type=kNetwork --server_name=your-server.net
if [[ ! -e /Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F ]]; then
mkdir -p /Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F
fi
cat<<EOF>/Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F/LGS.data
_NETWORK
EOF
cat<<EOF>/Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F/LICPATH.lic
SERVER your-server.net 000000000000
USE_SERVER
EOF
cat<<EOF>/Library/Application Support/Autodesk/CLM/LGS/657H1_2016.0.0.F/nw.cfg
done
EOF
else
echo "ERROR: Maya installer not found."
exit 1
fi
rm -rf /tmp/Install Maya 2016.app
exit 0Thanks for everyones help on here by the way!
Gary
@georgecm12 Thank you for the post. I'm trying to install Maya 2017 and I used your Variant 2. It seemed to have installed fine but when you run it, it comes up with the, Let's Get Started dialog box to enter Serial or Use Network license. Even after entering the info manually it just sits open on the dock. It never goes anywhere after that.
I entered all of my information in the script you provided for our version of the software but wondered if something may have changed in the Maya 2017's installer.
Has anyone had success installing Maya 2017 this way?
Thank you again for posting. If you or anyone hears of a fix, please let me know.
@georgecm12 I just saw the response by @gazlee and will try that. My apologies, I'll see if it works for Maya 2017.
I may have blown it and did a Postflght instead of postinstall. I'm trying again.
Thank you everyone.
In case anyone else is still having trouble (Standalone license, Maya 2017 Only)
Install Maya 2017 on a test machine, and license it manually.
On your composer box:
#!/bin/sh
#Install
/Library/Caches/MayaInstall/Install Maya 2017.app/Contents/MacOS/setup --noui --force --serial_number=xxx-xxxxxxx --product_key=657I1 --license_type=kStandalone
#License
/Library/Caches/MayaInstall/Install Maya 2017.app/Contents/Resources/adlmreg -i S 657I1 657I1 2017.0.0.F xxx-xxxxxxx /Library/Application Support/Autodesk/Adlm/PIT/2017/MayaConfig.pit
rm -rf /Library/Caches/MayaInstall/5. License command is essentially
adlmreg -i (Install) S (S for Standalone, N for Network) 657I1 (Product Code) 657I1 (Suite Code) 2017.0.0.F (Version. You can find this after manually licensing an install at /Library/Application Support/Autodesk/CLM/LGS/. There will be a folder here with the product code_Verison.) xxx-xxxxxxx (Serial Number) /Library/Application Support/Autodesk/Adlm/PIT/2017/MayaConfig.pit (This is the actual license file, adjust for year)
Product codes can be found here: https://knowledge.autodesk.com/customer-service/download-install/activate/find-serial-number-product-key/product-key-look
Couldn't have done it without NERDLogger post, http://nerdlogger.com/2013/08/15/installing-autodesk-entertainment-creation-suite-ultimate-maya-2014-for-osx-from-command-line/
Here's my postinstall script for installing Maya 2017. I am using a Network license, so I haven't been able to test the Standalone portion.
To use: Open Composer or another packaging tool and place the Install Maya 2017.app file into some directory such as /tmp. Then add this postinstall script to the package, making sure to change lines 50-56 to match your environment. The MAYA_SETUP_LOC variable should be the path to the Installer. If you put it in /tmp make sure to update /path/to to /tmp.
#!/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="657I1"
SUITE_KEY="657I1"
SERIAL="123-12345678"
LICENSE_TYPE="kNetwork" # Options: kNetwork or kStandalone
LICENSE_SERVER="license.server.domain.com"
MAYA_SETUP_LOC="/path/to/Install Maya 2017.app/Contents/MacOS/"
MAYA_SUPPORT_PATH="$3/Library/Application Support/Autodesk/CLM/LGS/${PRODUCT_KEY}_2017.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} 2017.0.0.F ${SERIAL} /Library/Application Support/Autodesk/Adlm/PIT/2017/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} 2017.0.0.F ${SERIAL} /Library/Application Support/Autodesk/Adlm/PIT/2017/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@mscottblake Awesome, Good Morning!
I ended up packaging it quite easily from a fresh install and using the drag and drop method even down to the Server info.
I posted my packaging info here: https://www.jamf.com/jamf-nation/discussions/22850/cinema-4d-r17-installation-solved
But I like your method of installing Maya better and will test it out so that way I can have a more fluid install including changing networking settings servers and licensing info.
Thank you so @mscottblake
@mscottblake thanks for this. I modified it to get Mudbox 2017 installed similarly. I didn't test Maya, but Mudbox installer leaves permissions on Mudbox 777, so I added some cleanup at the end.
################################################################################
# Variables
#
PRODUCT_KEY="498I1"
#SUITE_KEY="657I1"
SERIAL="123-12345678"
LICENSE_TYPE="kNetwork" # Options: kNetwork or kStandalone
LICENSE_SERVER="servername"
MUDBOX_SETUP_LOC="/var/tmp/Install Mudbox 2017.app/Contents/MacOS/"
MUDBOX_SUPPORT_PATH="/Library/Application Support/Autodesk/CLM/LGS/${PRODUCT_KEY}_2017.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}
# License separately since the setup binary is broken
# ../Resources/adlmreg -i S ${PRODUCT_KEY} ${SUITE_KEY} 2017.0.0.F ${SERIAL} /Library/Application Support/Autodesk/Adlm/PIT/2017/MUDBOXConfig.pit
# 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}
# License separately since the setup binary is broken
# ../Resources/adlmreg -i N ${PRODUCT_KEY} ${SUITE_KEY} 2017.0.0.F ${SERIAL} /Library/Application Support/Autodesk/Adlm/PIT/2017/MUDBOXConfig.pit
# 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 2017.app"
exit 0Having trouble with activating Maya 2018 using the previously provided scripts. We are using the kStandalone not network.
I updated the serial number and product keys in the postinstall script. Also added a YEAR variable to more easily specify 2018 in the places it needs to go.
I tried running the script as is as well as uncommenting the "License separately since the setup binary is broken" command.
Anyone get this script to work with Maya 2018, or know the secret sauce?
Running the script by @mscottblake after moving the Install Maya 2017.app into /tmp/. When I launch Maya for the first time after the script completes successfully, I'm being prompted to activate and enter my license key. Is there something I'm missing? If I enter the key manually (which I can't do when Maya is finally deployed) it asks for log in information for AutoDesk. Also expected behavior?
EDIT: Further information: I'm using the "Free Education" version of Maya 2017 and accompanying license. Can I some how use a network license server with the "Free Education" version?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.