Maya 2016

[Ray Kerce]

Hello Everyone!

Just wanted to let everyone know that Maya 2016 can be packaged in a very similar manner as described here:  https://groups.google.com/forum/#!topic/munki-dev/Mu9UvrjbHuQ

I just pointed the installer at the same disk image as Greg was saying to in the referenced thread.

I just wanted to update everyone on the packages that I used:

--pkgname="Install Maya 2016.app/Contents/Packages/Maya/Maya_core2016.pkg"

--pkgname="Install Maya 2016.app/Contents/Packages/Maya/Fcheck_app2016.pkg"

--pkgname="Install Maya 2016.app/Contents/Packages/ADLM/adlmframework11.pkg"

--pkgname="Install Maya 2016.app/Contents/Packages/ADLM/adlmapps11.pkg"

--pkgname="Install Maya 2016.app/Contents/Packages/ADLM/adlmflexnetclient.pkg"

--pkgname="Install Maya 2016.app/Contents/Packages/Maya/Maya_AdLMconf2016.pkg"

I grabbed adlmreg out of the Install Maya 2016.app/Contents/Resources and put it in a simple installer to install to /usr/bin

I made each one require the previous in the order I imported them and make the Maya_core2016.pkg require the adlmreg executable installer that I made.

On the last install, Maya_AdLMconf2016.pkg, I copied and modified slightly the referenced thread's post install script.  I will copy that below:

The product and quite codes can be looked up here: http://knowledge.autodesk.com/customer-service/installation-activation-licensing/get-ready/find-serial-number-product-key/product-key-look/2016-product-keys

PRODUCT=Maya

YEAR=2016

LIC=/private/var/flexlm/${PRODUCT}${YEAR}.lic

#Product Code

PRODCODE1=657H1

#Suite Code

PRODCODE2=793H1

SERIAL=XXX-XXXXXXXXX

SERVER=xxx.xxx.xxx

LICENSEENV=/Applications/Autodesk/maya${YEAR}/License.env

# Network license file

echo "SERVER ${SERVER} 0 27000" > ${LIC}

echo USE_SERVER >> ${LIC}

echo VENDOR adskflex port=2080 >> ${LIC}

chmod 644 ${LIC}

chown root:wheel ${LIC}

# License.env file

echo "MAYA_LICENSE=unlimited" > ${LICENSEENV}

echo "MAYA_LICENSE_METHOD=network" >> ${LICENSEENV}

chmod 755 ${LICENSEENV}

chown root:admin ${LICENSEENV}

# registration

/usr/bin/adlmreg -i N ${PRODCODE1} ${PRODCODE2} ${YEAR}.0.0.F ${SERIAL} /Library/Application\ Support/Autodesk/Adlm/PIT/${YEAR}/${PRODUCT}Config.pit

# symlink in Applications

ln -s /Applications/Autodesk/maya${YEAR}/${PRODUCT}.app /Applications/${PRODUCT}\ ${YEAR}.app

# disable MC3

/usr/bin/defaults write /Library/Preferences/com.autodesk.MC3Framework MC3Enabled -int 0

I am now working on Mudbox but wanted to share with the group as you all have helped me so much in the past.

Thanks everyone!  Let me know if there's something I could do better!

[Franson, Chris]

The 2015 and 2016 Autodesk products have a means of deployment without having to break out all the packages.

There’s several links here:

http://upandready.typepad.com/up_and_ready/2015/06/command-line-installation-on-mac-for-2016-products.html

The summary of the process with Munki is to copy the full .app installer to a temporary location then run a postinstall to use Autodesk’s setup. Works fine, without the guesswork of having to figure out if you have all the packages.

-Chris

[Gregory Neagle]

It’s nice to have options.

A third option: Build a “payload-free” pkg that has the install.app in the pkg resources or scripts directory, then a postinstall script that does Autodesk’s setup.

But why are we having to do any of this?

Keep complaining to the vendors, folks.

-Greg

--
Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
To post to this group, send email to munk...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ray Kerce]

Actually need to install the adlmreg file last and have the post install script run after that.  

Chris: Thanks for the link. I appreciate it!

Greg: Thanks!

[Matt Hansen]

On a related topic, I found Autodesk’s blog page on using “the Composer” to deploy AutoCAD for “MAC” amusing

http://upandready.typepad.com/up_and_ready/2015/07/how-to-create-an-autocad-for-mac-deployment-image.html

[Ray Kerce]

I found a solution in their forums but I cannot get autocad to update.  I just create a file /tmp with the license info and just run the default installer through Munki. Once I figure out how to get it to install the update I'll post again. 

Ray

[as...@siprep.org]

Does anyone have experience doing silent installs with a multi-seat standalone license for Maya? I don't think we really need (or want) to use our own license server, but the only way it seems to be able to do a silent install is to specify one.

[jerem...@gmail.com]

How well does this handle being run at loginwindow with no user session running, e.g. as a Munki bootstrap install?

[Gregory Neagle]

Any reason you don't just test this for yourself?

Sent from my iPhone

[jerem...@gmail.com]

1. Why reinvent the wheel if someone else is willing to share their testing and work… isn't this the whole point of open source?

2. I'm asking for a client where I'm not currently on-site and I would like to plan ahead.

[Gregory Neagle]

On Sep 13, 2015, at 3:14 PM, jerem...@gmail.com wrote:

1. Why reinvent the wheel if someone else is willing to share their testing and work… isn't this the whole point of open source?

Sure. But I assumed you had access to the installer (otherwise you wouldn’t be installing it). Testing your scenario would take all of a few minutes, and you’d have a solid answer.  Any answer you get from others risks that they aren’t doing exactly the same thing you are doing or they have something different about their infrastructure that makes their results differ from the results you might see.

I encourage people not only to ask questions, but do their own testing and share their results.

[steeve...@gmail.com]

Hi, if it's any help, Autodesk describe how to install Maya (2016) thru the command line here:

http://knowledge.autodesk.com/support/maya/troubleshooting/caas/CloudHelp/cloudhelp/2016/ENU/Installation-Maya/files/GUID-10885D2B-D900-4DD6-BB14-B82920C2D294-htm.html

it uses Setup which can be found in 'Install Maya 2016.app'.  

Re. general installation thru Munki, the DMG downloaded can be imported into Munki.  It will install 'Install Maya 2016.app' to /Applications upon clients.

I had some success with a (MunkiAdmin) Post Install Script which went onto use Autodesk's Command Line installation - plucking out Setup from 'Install Maya 2016.app'

Regards

[Gregory Neagle]

So did anyone test and determine if installing Maya 2016 via Autodesk’s setup binary works at the loginwindow? (My gut feeling is it won’t, that even though you can suppress the GUI it will still try to connect to the WindowServer and be rebuffed)

-Greg

[Gregory Neagle]

Answering my own question — despite throwing some errors at the beginning, the install proceeds and seems to be successful — I can at least log in and launch Maya 2016.

Here are the errors:

Oct 20 13:48:54 DTS3668 setup[54578] <Warning>: Untrusted apps are not allowed to connect to Window Server before login.

Oct 20 13:48:54 DTS3668 setup[54578] <Error>: Set a breakpoint at CGSLogError to catch errors as they are logged.

Oct 20 13:48:54 DTS3668 setup[54578] <Error>: This user is not allowed access to the window system right now.

_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.

Oct 20 13:48:54 DTS3668 setup[54578] <Error>: CGSCopyDisplayUUID: Invalid display 0x00000000

Oct 20 13:48:54 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:54 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:54 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:54 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:54 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:54 DTS3668 setup[54578] <Warning>: Invalid Connection ID 0

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: Invalid Connection ID 0

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: CGSConnectionByID: 0 is not a valid connection ID.

Oct 20 13:48:55 DTS3668 setup[54578] <Warning>: Invalid Connection ID 0

[Franson, Chris]

> On Oct 20, 2015, at 16:42, Gregory Neagle <gregn...@mac.com> wrote:
>
> So did anyone test and determine if installing Maya 2016 via Autodesk’s setup binary works at the loginwindow? (My gut feeling is it won’t, that even though you can suppress the GUI it will still try to connect to the WindowServer and be rebuffed)
>
> -Greg

I’ve been deploying it this way for several months, and surprisingly, it works. I do see Autodesk installer put up an otherwise blank menu bar but installation proceeds as it should.
-Chris

[Gregory Neagle]

Ugh.

> but installation proceeds as it should.
> -Chris
>

[Gregory Neagle]

How are you handling uninstall?

Autodesk’s guidance there is:

"To ensure a complete uninstallation, drag the Maya application to the trash, and remove the software product key from your system.”

More detail at another link:

To uninstall Maya from a Mac OS X.
1. Navigate to the Maya 2016 directory. Maya 2016 is installed by default to the /Applications/Autodesk/Maya2016/ directory.
2. Drag the Maya2016 directory to the trash.
3. Open a Terminal window and execute both of the following commands:
adlmreg –u S <productKey> 2016.0.0.F
adlmreg –u N <productKey> 2016.0.0.F
The product information is removed from the ProductInformation.pit file.

Problem there is `adlmreg` is not in any command path — `which adlmreg` returns nothing.

And removing it this way leaves other things behind:

1) Receipts for:
com.autodesk.pkg.AutodeskDirectConnect10.0
com.autodesk.pkg.Fcheck_app2016.0
com.autodesk.pkg.Maya_AdLMconf2016.0
com.autodesk.pkg.Maya_core2016

2) Files in /Library/Application Support that were installed by the com.autodesk.pkg.AutodeskDirectConnect10.0 pkg and the com.autodesk.pkg.Maya_AdLMconf2016.0 pkg
3) Licensing info stored in /var/flexlm (if you are using network licenses)
4) Files in /Users/Shared/Autodesk

The previous (unsupported) method cleaned up more of this stuff.

-Greg

> On Oct 20, 2015, at 1:59 PM, Franson, Chris <c.fr...@neu.edu> wrote:
>
>

[Franson, Chris]

> On Oct 20, 2015, at 17:13, Gregory Neagle <gregn...@mac.com> wrote:
> Problem there is `adlmreg` is not in any command path — `which adlmreg` returns nothing.

This looks like it may be a recent change with the Maya installer. Until right now I haven’t done a clean install of 2016 with SP3, so adlmreg had been in /usr/bin. Perhaps an undocumented change to improve SIP compatibility? I’ll need to do some further digging on this one.
I see that adlmreg is in Contents/Resources in the Maya installer bundle, so I assume the setup binary just runs it from there rather than putting it in /usr/bin as before. Maybe it’s worth copying adlmreg into /usr/local or similar as part of the Munki postinstall_script.
I haven’t dealt with Maya uninstalls as the vast majority of my installs go into lab machines, so when those need old copies removed, I just use that as an opportunity to refresh the whole system.

-Chris

[Gregory Neagle]

OK, but if I need to jump through hoops to install it (copy Install.app to /tmp; write and debug script to install using Contents/MacOS/setup; copy adlmreg somewhere, then write a custom uninstall script as well, I’m not convinced I’ve gained much here from the previous unsupported methods. IOW, it seems as much if not more work to do it Autodesk’s “supported” way.

-Greg

[Franson, Chris]

> On Oct 20, 2015, at 18:00, Gregory Neagle <gregn...@mac.com> wrote:
>
> OK, but if I need to jump through hoops to install it (copy Install.app to /tmp; write and debug script to install using Contents/MacOS/setup; copy adlmreg somewhere, then write a custom uninstall script as well, I’m not convinced I’ve gained much here from the previous unsupported methods. IOW, it seems as much if not more work to do it Autodesk’s “supported” way.

It’s tough to disagree with that thinking. Even if adlmreg was where it’s expected, Autodesk’s instructions don’t deal with the files in /Library/Application Support and who knows what else.
As a side note: in case your users use Mental Ray, it’s a separate install for Maya 2016, which may require using the same setup binary as Maya if installing the .pkg embedded in the Mental Ray installer bundle doesn’t work as expected.
-Chris

[Gregory Neagle]

Turns out there are three more pkgs:

com.Autodesk.adlmapps11 — installs stuff into /Applications/Autodesk/Adlm/R11
com.Autodesk.adlmflexnetclient — installs stuff into /Library/Application Support/Autodesk/Adlm/FLEXnet
com.Autodesk.adlmframework11 — installs stuff into /Library/Frameworks/Adlm.framework

If you have other Autodesk software installed you might not want to remove these, but if you don’t, and you are removing Maya, this is a lot of stuff to leave behind.

-Greg

[Gregory Neagle]

FWIW, here’s what I decided to do with Maya 2016.

I copy the app to /tmp and use a postinstall_script to run the setup binary with additional options to install, followed by removing the app from /tmp.

I also added a receipts array and a postuninstall_script. The receipts array allows Munki to determine that Maya has been installed, but is also used when removing Maya. The postuninstall_script does some additional cleanup.

Hope this is useful to some.

-Greg

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>autoremove</key>

<false/>

<key>catalogs</key>

<array>

<string>production</string>

</array>

<key>category</key>

<string>Production</string>

<key>description</key>

<string>3D animation, modeling, simulation, and rendering software</string>

<key>developer</key>

<string>Autodesk</string>

<key>display_name</key>

<string>Autodesk Maya 2016</string>

<key>icon_hash</key>

<string>f056bab114140173974eb38661b0a5bca0133e71990b222bf3323c77fe7ba108</string>

<key>installer_item_hash</key>

<string>6db78f7e294c26c67b4488bfca729afa9e9f48dfec651cb8ef3d5b156cefd55a</string>

<key>installer_item_location</key>

<string>apps/Autodesk_Maya_2016_EN_JP_ZH_MAC_OSX-2016.dmg</string>

<key>installer_item_size</key>

<integer>758950</integer>

<key>installer_type</key>

<string>copy_from_dmg</string>

<key>items_to_copy</key>

<array>

<dict>

<key>destination_path</key>

<string>/tmp</string>

<key>source_item</key>

<string>Install Maya 2016.app</string>

</dict>

</array>

<key>minimum_os_version</key>

<string>10.9.5</string>

<key>name</key>

<string>Maya2016</string>

        <key>postinstall_script</key>

        <string>#!/bin/sh

# See http://knowledge.autodesk.com/support/maya/troubleshooting/caas/CloudHelp/cloudhelp/2016/ENU/Installation-Maya/files/GUID-10885D2B-D900-4DD6-BB14-B82920C2D294-htm.html

/tmp/Install\ Maya\ 2016.app/Contents/MacOS/setup --noui —serial_number=XXX-XXXXXXXX —product_key=XXXXX --license_type=kNetwork --server_name=autodesklicense

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

        </string>

        <key>postuninstall_script</key>

<string>#!/bin/sh

/bin/rm -rf /Applications/Autodesk/maya2016

/bin/rm /var/flexlm/Maya2016.lic

        </string>

<key>receipts</key>

        <array>

            <dict>

                <key>packageid</key>

                <string>com.Autodesk.adlmapps11</string>

                <key>version</key>

                <string>0</string>

            </dict>

            <dict>

                <key>packageid</key>

                <string>com.Autodesk.adlmflexnetclient</string>

                <key>version</key>

                <string>11.0.18.0</string>

            </dict>

            <dict>

                <key>packageid</key>

                <string>com.Autodesk.adlmframework11</string>

                <key>version</key>

                <string>0</string>

            </dict>

    <dict>

                <key>packageid</key>

                <string>com.autodesk.pkg.AutodeskDirectConnect10.0</string>

                <key>version</key>

                <string>10.0</string>

            </dict>

            <dict>

                <key>packageid</key>

                <string>com.autodesk.pkg.Fcheck_app2016.0</string>

                <key>version</key>

                <string>2016.0</string>

            </dict>

            <dict>

                <key>packageid</key>

                <string>com.autodesk.pkg.Maya_AdLMconf2016.0</string>

                <key>version</key>

                <string>2016.0</string>

            </dict>

            <dict>

                <key>packageid</key>

                <string>com.autodesk.pkg.Maya_core2016</string>

                <key>version</key>

                <string>2016.0</string>

            </dict>

        </array>

<key>uninstall_method</key>

<string>removepackages</string>

<key>uninstallable</key>

<true/>

<key>version</key>

<string>2016.0</string>

</dict>

</plist>

[Ray Kerce]

Sorry for the late reply. I have not been able to check this regularly. It does install at the login window for me.  

As for uninstalling: We actually don't have this as its used in labs that are imaged every semester with a license server environment. Greg's way looks great though.

[Tim Sutton]

Thank you Greg. We've somehow escaped needing to do 2016 so far this year but may still get to it before 2017 is out. I like the idea of leaving in the receipts for Munki to be able to remove it, while still "simplifying" (sort of) the installation process.

Tim

[Gregory Neagle]

I do grow tired of having to revisit/re-reverse-engineer the install and removal process for EVERY SINGLE RELEASE of Autodesk products.

-Greg

[Franson, Chris]

> On Oct 26, 2015, at 12:43, Gregory Neagle <gregn...@mac.com> wrote:
>
> I do grow tired of having to revisit/re-reverse-engineer the install and removal process for EVERY SINGLE RELEASE of Autodesk products.
>
> -Greg

FWIW, the “setup” binary works with Maya 2015, too. I didn’t do anything with my postinstall script for 2016 aside from update the serial number, product code, and the name of the base application for the install. Maybe we’ve entered an era where there will be some continuity. I’m not holding my breath on that, though.
-Chris

[Daniel Warren]

New to munki here.  I have an issue where I can install Maya 2016 just fine copying the installer to the tmp directory and using the command line arguments to configure it in a post install script.  However I am having trouble with the uninstall process.  Using a script with Autodesk's commands and then cleaning up the previously installed files works to remove it, but then I cannot reinstall without re-imaging the client machine.  This is what I'm using for a post uninstall script in conjunction with the removepackages Uninstall method:

#!/bin/bash

/bin/rm -rf /Applications/Autodesk/maya2016
/bin/rm /var/flexlm/Maya2016.lic

adlmreg -u S 793H1 2016.0.0.F
adlmreg -u N 793H1 2016.0.0.F
rm -rf /Applications/Autodesk/
rm -rf /Library/Application\ Support/Autodesk/
rm -rf /Library/Frameworks/Adlm.framework/
rm -rf /Library/Preferences/*.autodesk.*/
rm -rf /tmp/*Maya*/
rm -rf /tmp/FLEXnet/
rm -f /tmp/Fcheck_app2016_postinstall.out/

Thanks in advance for any insight you can provide.

On Friday, August 21, 2015 at 12:16:10 PM UTC-4, Ray Kerce wrote:

Hello Everyone!

Just wanted to let everyone know that Maya 2016 can be packaged in a very similar manner as described here:  https://groups.google.com/forum/#!topic/munki-dev/Mu9UvrjbHuQ

I just pointed the installer at the same disk image as Greg was saying to in the referenced thread.

[Gregory Neagle]

I just use:

<key>uninstall_method</key>

<string>removepackages</string>

<key>uninstallable</key>

<true/>

together with:

<key>postuninstall_script</key>

<string>#!/bin/sh

/bin/rm -rf /Applications/Autodesk/maya2016

/bin/rm /var/flexlm/Maya2016.lic

        </string>

(we use network licensing and the license config is in /var/flexlm/Maya2016.lic)

When you say you "cannot reinstall without re-imaging the client machine" can you provide any details on what that exactly looks like?

-Greg

[Daniel Warren]

Through Managed Software Center if I click on install it runs through the install process (well pretends to anyway) and then gives the option to remove, but it never actually installs Maya.  I did not have a receipts array in place, other than the default so I think that might be part of the issue since the actual install is done with a script after the installer is copied to the /tmp directory.

After adding those receipts arrays and not removing the /tmp/Install Maya 2016 directory on install (I originally removed that folder in the post install script) it is working correctly.  Is there a way to remove the install Maya folder for cleanup purposes?

[pne...@gmail.com]

Have any of you checked the owner/permission settings on /Applications/Autodesk and /Library/Application Support/Autodesk? I have a postinstall action to correct them.