Installation & Licensing
Welcome to Autodesk’s Installation and Licensing Forums. Share your knowledge, ask questions, and explore popular Download, Installation, and Licensing topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Deploying Maya with munki

8 REPLIES 8
SOLVED
Reply
Message 1 of 9
Anonymous
2135 Views, 8 Replies

Deploying Maya with munki

We are currently using Casper to deploy Maya in our environment and it works well.  However we are currently evaluating an alternative deployment solution called munki and need to address deploying Maya with this new tool.  I am posting here because so far the solutions I have found envolve extracting packages and installing them in a certain order.  Quite frankly it's a bit messy.  Does Autodesk offer any recommendations/support for deployment through munki?

8 REPLIES 8
Message 2 of 9
BJ.C
in reply to: Anonymous

Hello @Anonymous

Does Autodesk offer any recommendations/support for deployment through munki ? Official support - NO  I can find only a couple of old cases of anyone deploying Autodesk products using Munki so we would have very little to recommend. That does not mean that it would not work or if you had an existing case with Autodesk that they would not attempt to help you.

 

If you are successful I would suggest posting your results and methodology in this post. Your experience could become valuable to other using Munki with Autodesk products!

Thank you for taking part in our community forum!

Kind Regards,



BJ.C

Technical Support Specialist
Message 3 of 9
Anonymous
in reply to: BJ.C

I was actually successful at installing Maya 2016 using munki as a
deployment method. The process that I used was a follows:

1. Take the "Install Maya 2016.app" package and nest inside a package that
copies it to the /tmp folder. Import the resulting package into munki.

2. Add an install script to the package in Maya using Autodesk's command
line arguments. The one I used was this:
#!/bin/bash

cd /tmp/Install\ Maya\ 2016.app/Contents/MacOS

sudo ./setup --noui --force --serial_number=XXX-XXXXXXXX
--product_key=793H1 --license_type=kStandalone

sudo rm -rf /tmp/Install\ Maya\ 2016.app/

Adjust the serial number, product key and other arguments accordingly more
info on what the arguments do can be found here:

https://knowledge.autodesk.com/support/maya/troubleshooting/caas/CloudHelp/cloudhelp/2016/ENU/Instal...

I also added a line at the end to remove the temporary directory.

That's it! Works great. Some of this information can be found on munki
forums, but most scripts that I found were way too cluttered also this
solution was in most cases buried in blog posts way below more complicated
methods for installing Maya.

Cheers!
Message 4 of 9
avto
in reply to: Anonymous

Hi Dwarren,

 

Thank you for updating this thread and providing your workflow to the community. Thank you.

 

Regards,

 



Avto Chachava
Autodesk Product Support
Autodesk, Inc.
Message 5 of 9
Anonymous
in reply to: avto

Thanks, glad I could help.

 

One correction:  Step number 2 shoudl say "Add an install script to the package in MUNKI.." not Maya

Message 6 of 9
Anonymous
in reply to: Anonymous

Just an update.  I was new to munki at the time.  I did not realize that you can change the install location so nesting the installer within an installer is not necessary, you just need to install to the /tmp folder and proceed with the same script.

 

Cheers!

Message 7 of 9
natasha.l
in reply to: Anonymous

Hello @Anonymous,

 

Thank you for the updates and contributing to the community. Smiley Happy

Message 8 of 9
Anonymous
in reply to: natasha.l

Update for 2017 Standalone install.  A few lines need to be added to the end of the script.

 

#!/bin/sh
#Note: the installer has been copied to the /tmp/ folder

cd /tmp/Install\ Maya\ 2017.app/Contents/MacOS
sudo ./setup --noui --log=/var/log/autodesk/2017/INSTALL.log --force --serial_number=XXX-XXXXXXXX --product_key=657I1 --license_type=kStandalone

 

# Using adlmreg to activate the license

 

cd /tmp/Install\ Maya\ 2017.app/Contents/Resources

 

#Note:  for this is for standalone, for Network install you will need to change the product key and use an "N" instead of an "S".


sudo ./adlmreg -i S 657I1 657I1 2017.0.0.F XXX-XXXXXXXX /Library/Application\ Support/Autodesk/Adlm/PIT/2017/MayaConfig.pit
sudo mkdir /Library/Application\ Support/Autodesk/CLM/LGS/657I1_2017.0.0.F
sudo touch /Library/Application\ Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LGS.data
sudo chmod 777 /Library/Application\ Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LGS.data

 

#Note:  For a network install change this to echo "_NETWORK"


echo "_STANDALONE" >> /Library/Application\ Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LGS.data

 

#For Network install remove the comment (#) markers from the following commands:

 

#echo "_NETWORK" >> /Library/Application\ Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LGS.data
#echo "SERVER servername 000000000000" >> /Library/Application\ Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LICPATH.lic
#echo "USE_SERVER" >> /Library/Application\ Support/Autodesk/CLM/LGS/657I1_2017.0.0.F/LICPATH.lic

 

Cheers!

Message 9 of 9
natasha.l
in reply to: Anonymous

Hello @Anonymous,

 

Thank you for being a part of the community and providing this helpful information. Visitors of the board will greatly appreciate! Smiley Happy

 

 

 

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Administrator Productivity


Autodesk Design & Make Report