Hi all, I'm wondering if anyone has had success in packaging Maya 2022 with a non-network server license key, which our institution is able to put on 1200 machines. I tried referencing this post, but havent been able to successfully deploy the program with my modifications. Any help would be appreciated. Thank you.
Page 3 / 3
I noticed significant changes to the .pkg files within /Helper/Packages compared to previous years so I replaced that section with a for loop that recursively installs all .pkgs rather than updating the hardcoded paths. also pushing script parameters for Year, Product Key and
Policy puts Install Maya $year.app in /tmp
add this script as a postinstall in the .pkg or run it in the same policy 'After'
#!/bin/sh
year="$4"
pkgpath="/tmp/Install Maya ${year}.app"
pKey="$5"
networkServer="$6"
licPath="/Library/Application Support/Autodesk/AdskLicensingService/${pKey}_${year}.0.0.F"
licFile="licpath.lic"
runInstaller ()
{
for PKG in $(find $pkgpath -name "*.pkg"); do
/usr/sbin/installer -dumplog -verbose -pkg "${PKG}" -target /
done
}
createLicenseFiles ()
{
if [[ ! -e "${licPath}" ]];
then
/bin/mkdir "${licPath}"
fi
/usr/bin/touch "${licPath}/${licFile}"
/bin/chmod 777 "${licPath}/${licFile}"
/bin/echo "SERVER ${networkServer} 000000000000 " > "${licPath}/${licFile}"
/bin/echo "USE_SERVER\\c" >> "${licPath}/${licFile}"
}
runInstaller
createLicenseFiles
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${pKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
/bin/rm -rf "${pkgPath}"
Hope this helps you until they change how this works, It should be the same for other apps, just change the pkgpath line (or use another variable).
Hoping this thread can reactivate for the 2024 installers. Using @robertojok's script, I was able to activate a standalone Maya without issue. But it looks like they've changed Mudbox 2024, and so it's failing to activate. Per Mudbox 2024's release notes, the installer is new. Has anybody dug into this yet?
Hoping this thread can reactivate for the 2024 installers. Using @robertojok's script, I was able to activate a standalone Maya without issue. But it looks like they've changed Mudbox 2024, and so it's failing to activate. Per Mudbox 2024's release notes, the installer is new. Has anybody dug into this yet?
@Bovio I'll be digging into this again in the next few weeks, and there are a number of script variations in this thread, so I can only speak for my own, but two places I would look first are the 1) the setup command for Mudbox has been using the flag --noui instead of --silent. Maybe that's changed in v2024? 2) It might be time to start using the --cf flag to denote the path to the app's .pit file. See the notes at the end of my script above dated 7/28/22 for details. I'm saying all this without having looked at a 2024 installer, so take it with a grain of salt.
Beautiful work! I love it! Thank you @jonw ! I have a question though... Are all those 000000000000 supposed to be like that, or do I have to substitute something in its place?
licenseFunction ()
{
### based off Onkstons's terrific work (I think they we're the first?) but simplified for 2023.
### see also, addl details at the end of script for alternative 'legit' licensing method.
licensePath="/Library/Application Support/Autodesk/AdskLicensingService/${productKey}_${year}.0.0.F"
/bin/mkdir -p "${licensePath}"
/usr/bin/touch "${licensePath}/licpath.lic"
/bin/echo "SERVER ${networkServer} 000000000000" > "${licensePath}/licpath.lic"
/bin/echo "USE_SERVER" >> "${licensePath}/licpath.lic"
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${productKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
}Also, does anyone know if the Arnold renderer is bundled in Maya or Mudbox? I remember years ago that it was a stand-alone installer.
Hi!
How can I modify this script, if I have no license key and license server? I have user license only, but when I install and open Maya 2023 the icon bounces a few seconds on the tray, then disappears. How can I force/trigger the login screen of the app?
Thank you.
Just thought I'd share my latest solution to silently install 2023 versions of AutoCAD, Maya & Mudbox with network licenses, while at the login window (aka a lab/classroom install). My goal was to make it as simple to use and to modify as possible. I've been using a variation of methods shared here for years (thanks by the way!) but decided it was time to really get to the bottom of things for myself.
It's a mashup of Autodesk's 'legit' install method with a simplified version of the custom network licensing steps we all know & love. However I do make note of the 'legit' network license registration steps for those who care, or are curious as I was (it does work, I just prefer the custom method). All details are in the script.
I've only deployed to macOS 12.4 Intel & Silicon, so ymmv, but I'm happy to report it's working perfectly for me on over 100 stations so far. Enjoy!
#!/bin/zsh
### Install AutoDesk Combo 2023 (AutoCAD, Maya & MudBox)
### silently @ login window with network licenses (aka multi-user lab/classroom deploy)
### 2022.07.27 by JonW
### Simply update variables/products below the function section as desired
### Read the additional details at the end of the script for more clarity on licensing.
### Ensure:
### 1) installer app(s) re-packed from .dmg by Composer & deployed to /private/tmp (root:wheel 755)
### 2) the network license server is functional
### 3) optionally, that previous Autodesk installations have been removed.
### and if so, you've also unloaded com.autodesk.AdskLicensingService.plist
#################################################
installFunction ()
{
### Before install, clear quarantine that may step on Setup.app when run at the login window.
### Also as of 2023, Mudbox still uses a different setup app path with --noui flag NOT --silent
### Finally, remove the installer app when complete
/usr/bin/xattr -rc /private/tmp/"${installerApp}"
if echo "$installerApp" | grep -iq "Mudbox"; then
/private/tmp/"${installerApp}"/Contents/MacOS/setup --noui
else
/private/tmp/"${installerApp}"/Contents/Helper/Setup.app/Contents/MacOS/Setup --silent
fi
/bin/rm -rf /private/tmp/"${installerApp}"
}
licenseFunction ()
{
### based off Onkstons's terrific work (I think they we're the first?) but simplified for 2023.
### see also, addl details at the end of script for alternative 'legit' licensing method.
licensePath="/Library/Application Support/Autodesk/AdskLicensingService/${productKey}_${year}.0.0.F"
/bin/mkdir -p "${licensePath}"
/usr/bin/touch "${licensePath}/licpath.lic"
/bin/echo "SERVER ${networkServer} 000000000000" > "${licensePath}/licpath.lic"
/bin/echo "USE_SERVER" >> "${licensePath}/licpath.lic"
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${productKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
}
#################################################
networkServer="your.network.license.server.here"
### AutoCAD
productKey="777O1"
year="2023"
installerApp="Install Autodesk AutoCAD 2023 for Mac.app"
installFunction
licenseFunction
### Maya
productKey="657O1"
year="2023"
installerApp="Install Maya 2023.app"
installFunction
licenseFunction
### Mudbox
productKey="498O1"
year="2023"
installerApp="Install Mudbox 2023.app"
installFunction
licenseFunction
#################################################
### Verify license details - not required, but kind of nice to see.
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper list
echo "Autodesk network licensing complete"
##################################################
### Additional network license details:
### For those who are curious, or if the above ever ceases to function:
### The 'legit' method for initial silent license registration (using autoCAD as an example) uses the 'register' command instead of 'change'.
### It also requires use of the --cf flag to denote a path to the app's config (.pit) file.
### e.g.
### configFile="/Library/Application Support/Autodesk/ADLM/.config/ProductInformation.pit"
### /Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --pk "${productKey}" --pv "${year}.0.0.F" --cf "${configFile}" --lm NETWORK --ls "${networkServer}"
### The end result is the same as the 'change' method used above (at least after the initial app launch).
### Essentially the 'change' method works backwards to manually create the licpath.lic directory & file,
### then uses the 'change' command to register it.
### Anecdotally, the 'change' method appears to produce a slightly faster initial app launch,
### but it's hard to say which is better.
### Either way, it's good to know both & having handle on the AdskLicensingInstHelper utility helps a lot!
### Check these out >>>
### /Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --help
### /Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --help
### Also, either method seems to deploy fine while at the login window, so no worries there.
### Some good tips & reference:
### https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Use-Installer-Helper.html
### https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/ENU/Autodesk-Installation-Basic-ODIS/files/ODIS-silent-install-htm.html
### Hope this helps some folks out!
Hi jonw, I used your 2023 script for AutoCAD & Maya last year (2022) & am proposing to use the same script with the 2024 versions of the applications. Are there any caveats you may have with this? Tnx Glenn.
Beautiful work! I love it! Thank you @jonw ! I have a question though... Are all those 000000000000 supposed to be like that, or do I have to substitute something in its place?
licenseFunction ()
{
### based off Onkstons's terrific work (I think they we're the first?) but simplified for 2023.
### see also, addl details at the end of script for alternative 'legit' licensing method.
licensePath="/Library/Application Support/Autodesk/AdskLicensingService/${productKey}_${year}.0.0.F"
/bin/mkdir -p "${licensePath}"
/usr/bin/touch "${licensePath}/licpath.lic"
/bin/echo "SERVER ${networkServer} 000000000000" > "${licensePath}/licpath.lic"
/bin/echo "USE_SERVER" >> "${licensePath}/licpath.lic"
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${productKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
}Also, does anyone know if the Arnold renderer is bundled in Maya or Mudbox? I remember years ago that it was a stand-alone installer.
Arnold is separate: https://arnoldrenderer.com/download/
Also simplified & parameterised the Maya install, it installs all .pkgs inside the .app installer so you don't need to hardcode them anymore. It should be straightforward to adapt for Mudbox and non-network server.
#!/bin/sh
year="$4"
pkgpath="/tmp/InstallMaya${year}.app"
pKey="$5"
networkServer="$6"
licPath="/Library/Application Support/Autodesk/AdskLicensingService/${pKey}_${year}.0.0.F"
licFile="licpath.lic"
runInstaller ()
{
for PKG in $(find "$pkgpath" -name "*.pkg"); do
echo "Installing $PKG"
installer -pkg ${PKG} -target /
done
}
createLicenseFiles ()
{
{
if [[ ! -e "${licPath}" ]];
then
/bin/mkdir "${licPath}"
fi
/usr/bin/touch "${licPath}/${licFile}"
/bin/chmod 777 "${licPath}/${licFile}"
/bin/echo "SERVER ${networkServer} 000000000000 " > "${licPath}/${licFile}"
/bin/echo "USE_SERVER\\c" >> "${licPath}/${licFile}"
}
}
runInstaller
createLicenseFiles
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${pKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
/bin/rm -rf "${pkgPath}"
Hi!
How can I modify this script, if I have no license key and license server? I have user license only, but when I install and open Maya 2023 the icon bounces a few seconds on the tray, then disappears. How can I force/trigger the login screen of the app?
Thank you.
Add your serial as a variable and change the last line from Network to Standalone:
serial="XXX-XXXXXXXX"
/Library/Application\\Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --pk ${pKey} --pv ${year}.0.0.F --lm STANDALONE --sn ${serial} --cf /Applications/Autodesk/maya2023/adlmreg/MayaConfig.pit --nu
Arnold is separate: https://arnoldrenderer.com/download/
Also simplified & parameterised the Maya install, it installs all .pkgs inside the .app installer so you don't need to hardcode them anymore. It should be straightforward to adapt for Mudbox and non-network server.
#!/bin/sh
year="$4"
pkgpath="/tmp/InstallMaya${year}.app"
pKey="$5"
networkServer="$6"
licPath="/Library/Application Support/Autodesk/AdskLicensingService/${pKey}_${year}.0.0.F"
licFile="licpath.lic"
runInstaller ()
{
for PKG in $(find "$pkgpath" -name "*.pkg"); do
echo "Installing $PKG"
installer -pkg ${PKG} -target /
done
}
createLicenseFiles ()
{
{
if [[ ! -e "${licPath}" ]];
then
/bin/mkdir "${licPath}"
fi
/usr/bin/touch "${licPath}/${licFile}"
/bin/chmod 777 "${licPath}/${licFile}"
/bin/echo "SERVER ${networkServer} 000000000000 " > "${licPath}/${licFile}"
/bin/echo "USE_SERVER\\c" >> "${licPath}/${licFile}"
}
}
runInstaller
createLicenseFiles
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${pKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
/bin/rm -rf "${pkgPath}"
Hi Future,
I made a composer package that puts the Install Maya 2024.app in /private/tmp/Install\\ Maya\\ 2024.app. I put in the parameters 4,5,and 6 for the year, product key, and networkServer in the script. I set it to run after the package runs. I get the following script result when I look at the log details. Do you know what I'm doing wrong?
| Executing Policy Install Maya 2024 |
| Downloading Install Maya 2024.pkg... |
| Downloading https://use1-jcds.services.jamfcloud.com//download/a06625f1d2984ea0a97953ae5acd96b8/Install%20Maya%202024.pkg... |
| Verifying package integrity... |
| Installing Install Maya 2024.pkg... |
| Successfully installed Install Maya 2024.pkg. |
| Running script Maya 2024... |
| Script exit code: 0 |
| Script result: find: /tmp/InstallMaya.app: No such file or directory mkdir: /Library/Application Support/Autodesk/AdskLicensingService: No such file or directory touch: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory chmod: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2024: line 28: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2024: line 29: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2024: line 35: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory |
| Running Recon... |
| Retrieving inventory preferences from https://xxxx.jamfcloud.com/... |
| Locating accounts... |
| Locating package receipts... |
| Searching path: /System/Applications |
| Locating printers... |
| Gathering application usage information from the JamfDaemon... |
| Searching path: /Applications |
| Locating hardware information (macOS 12.6.7)... |
@Bovio I'll be digging into this again in the next few weeks, and there are a number of script variations in this thread, so I can only speak for my own, but two places I would look first are the 1) the setup command for Mudbox has been using the flag --noui instead of --silent. Maybe that's changed in v2024? 2) It might be time to start using the --cf flag to denote the path to the app's .pit file. See the notes at the end of my script above dated 7/28/22 for details. I'm saying all this without having looked at a 2024 installer, so take it with a grain of salt.
I just took another look at this and the install goes smoothly until license time, when I get the error
reading configuration file /Library/Application Support/Autodesk/AdskLicensingService/AdskLicensingService.data failed: open /Library/Application Support/Autodesk/AdskLicensingService/AdskLicensingService.data: no such file or directory
Any clue what that could be about?
Hi Bovio, are you using a license server? If so you need to be able to contact it prior to installation.
Sorry I hope you don't mind, I'm not 'trying to teach my grandmother to suck eggs'.
Chers,
Glenn.
Hi Bovio, are you using a license server? If so you need to be able to contact it prior to installation.
Sorry I hope you don't mind, I'm not 'trying to teach my grandmother to suck eggs'.
Chers,
Glenn.
No license server, this is standalone.
Hi Future,
I made a composer package that puts the Install Maya 2024.app in /private/tmp/Install\\ Maya\\ 2024.app. I put in the parameters 4,5,and 6 for the year, product key, and networkServer in the script. I set it to run after the package runs. I get the following script result when I look at the log details. Do you know what I'm doing wrong?
| Executing Policy Install Maya 2024 |
| Downloading Install Maya 2024.pkg... |
| Downloading https://use1-jcds.services.jamfcloud.com//download/a06625f1d2984ea0a97953ae5acd96b8/Install%20Maya%202024.pkg... |
| Verifying package integrity... |
| Installing Install Maya 2024.pkg... |
| Successfully installed Install Maya 2024.pkg. |
| Running script Maya 2024... |
| Script exit code: 0 |
| Script result: find: /tmp/InstallMaya.app: No such file or directory mkdir: /Library/Application Support/Autodesk/AdskLicensingService: No such file or directory touch: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory chmod: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2024: line 28: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2024: line 29: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2024: line 35: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory |
| Running Recon... |
| Retrieving inventory preferences from https://xxxx.jamfcloud.com/... |
| Locating accounts... |
| Locating package receipts... |
| Searching path: /System/Applications |
| Locating printers... |
| Gathering application usage information from the JamfDaemon... |
| Searching path: /Applications |
| Locating hardware information (macOS 12.6.7)... |
Hi Mochi,
I had to drop the spaces from the .app before packaging to get it to work.
Hi Mochi,
I had to drop the spaces from the .app before packaging to get it to work.
Thanks. Dropping the spaces worked for me too. I appreciate the help. Now I don't have to setup Maya 2024 by hand on 120 mac lab computers.
Add your serial as a variable and change the last line from Network to Standalone:
serial="XXX-XXXXXXXX"
/Library/Application\\Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --pk ${pKey} --pv ${year}.0.0.F --lm STANDALONE --sn ${serial} --cf /Applications/Autodesk/maya2023/adlmreg/MayaConfig.pit --nu
Good morning Luke,
I really do appreciate your post. They have helped me get further down this autodesk Maya Journey. I am stuck now though and am looking for guidance. The app downloads, but it does not license it. I see that it includes spaces in the second to last line. This is where I am at with my script logs.
| [STEP 1 of 4] |
| Executing Policy Autodesk Maya 2024 |
| [STEP 2 of 4] |
| Running script Autodesk Maya 2024... |
| Script exit code: 127 |
| Script result: Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/Maya_AdLMconf2024.pkg installer: Package name is Maya_AdLMconf2024 installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/MayaUSD.pkg installer: Package name is MayaUSD installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/AdobeSubstance3DforMaya-2.4.0-2024-mac-universal.pkg installer: Package name is Adobe Substance 3D for Maya installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/LookdevX.pkg installer: Package name is LookdevX installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/Maya_core2024.pkg installer: Package name is Maya_core2024 installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/MtoA.pkg installer: Package name is MtoA 5.3.4.1 Maya 2024 installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/bifrost.pkg installer: Package name is bifrost installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Licensing/AdskLicensing-13.3.1.9694-mac-installer.pkg installer: Package name is AdskLicensing-13.3.1.9694-mac-installer installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Licensing/adskflexnetserverIPV6.pkg installer: Package name is AdskFlexnetServerIPV6 installer: Upgrading at base path / installer: The upgrade was successful. /Library/Application Support/JAMF/tmp/Autodesk Maya 2024: line 36: /Library/ApplicationSupport/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory |
| Error running script: return code was 127. |
| [STEP 3 of 4] |
| [STEP 4 of 4] |
Good morning Luke,
I really do appreciate your post. They have helped me get further down this autodesk Maya Journey. I am stuck now though and am looking for guidance. The app downloads, but it does not license it. I see that it includes spaces in the second to last line. This is where I am at with my script logs.
| [STEP 1 of 4] |
| Executing Policy Autodesk Maya 2024 |
| [STEP 2 of 4] |
| Running script Autodesk Maya 2024... |
| Script exit code: 127 |
| Script result: Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/Maya_AdLMconf2024.pkg installer: Package name is Maya_AdLMconf2024 installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/MayaUSD.pkg installer: Package name is MayaUSD installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/AdobeSubstance3DforMaya-2.4.0-2024-mac-universal.pkg installer: Package name is Adobe Substance 3D for Maya installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/LookdevX.pkg installer: Package name is LookdevX installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/Maya_core2024.pkg installer: Package name is Maya_core2024 installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/MtoA.pkg installer: Package name is MtoA 5.3.4.1 Maya 2024 installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Maya/bifrost.pkg installer: Package name is bifrost installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Licensing/AdskLicensing-13.3.1.9694-mac-installer.pkg installer: Package name is AdskLicensing-13.3.1.9694-mac-installer installer: Upgrading at base path / installer: The upgrade was successful. Installing /tmp/InstallMaya2024.app/Contents/Helper/Packages/Licensing/adskflexnetserverIPV6.pkg installer: Package name is AdskFlexnetServerIPV6 installer: Upgrading at base path / installer: The upgrade was successful. /Library/Application Support/JAMF/tmp/Autodesk Maya 2024: line 36: /Library/ApplicationSupport/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory |
| Error running script: return code was 127. |
| [STEP 3 of 4] |
| [STEP 4 of 4] |
OH! I believe it may have worked.
This post was missing a space between Application\\ Support. I kept comparing your posts to narrow it down. If for some reason I run into an issue I'll be back!
I noticed significant changes to the .pkg files within /Helper/Packages compared to previous years so I replaced that section with a for loop that recursively installs all .pkgs rather than updating the hardcoded paths. also pushing script parameters for Year, Product Key and
Policy puts Install Maya $year.app in /tmp
add this script as a postinstall in the .pkg or run it in the same policy 'After'
#!/bin/sh
year="$4"
pkgpath="/tmp/Install Maya ${year}.app"
pKey="$5"
networkServer="$6"
licPath="/Library/Application Support/Autodesk/AdskLicensingService/${pKey}_${year}.0.0.F"
licFile="licpath.lic"
runInstaller ()
{
for PKG in $(find $pkgpath -name "*.pkg"); do
/usr/sbin/installer -dumplog -verbose -pkg "${PKG}" -target /
done
}
createLicenseFiles ()
{
if [[ ! -e "${licPath}" ]];
then
/bin/mkdir "${licPath}"
fi
/usr/bin/touch "${licPath}/${licFile}"
/bin/chmod 777 "${licPath}/${licFile}"
/bin/echo "SERVER ${networkServer} 000000000000 " > "${licPath}/${licFile}"
/bin/echo "USE_SERVER\\c" >> "${licPath}/${licFile}"
}
runInstaller
createLicenseFiles
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${pKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
/bin/rm -rf "${pkgPath}"
Hope this helps you until they change how this works, It should be the same for other apps, just change the pkgpath line (or use another variable).
Hello,
I recently used your script for the 2025 installation on an Intel Mac but are running into some issues.
I've been able to get the app itself to install but it won't launch, the app icon just bounces a few times on the taskbar and doesn't do anything else.
This is what the Jamf log displays after a "successful" installation:
Script result: find: /tmp/InstallMaya.app: No such file or directory
mkdir: /Library/Application Support/Autodesk/AdskLicensingService: No such file or directory touch: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory chmod: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 26: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 27: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 32: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory
Not sure if anything could be causing this issues.
Thanks.
Hello,
I recently used your script for the 2025 installation on an Intel Mac but are running into some issues.
I've been able to get the app itself to install but it won't launch, the app icon just bounces a few times on the taskbar and doesn't do anything else.
This is what the Jamf log displays after a "successful" installation:
Script result: find: /tmp/InstallMaya.app: No such file or directory
mkdir: /Library/Application Support/Autodesk/AdskLicensingService: No such file or directory touch: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory chmod: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 26: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 27: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 32: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory
Not sure if anything could be causing this issues.
Thanks.
Sounds like a license issue
Hello,
I recently used your script for the 2025 installation on an Intel Mac but are running into some issues.
I've been able to get the app itself to install but it won't launch, the app icon just bounces a few times on the taskbar and doesn't do anything else.
This is what the Jamf log displays after a "successful" installation:
Script result: find: /tmp/InstallMaya.app: No such file or directory
mkdir: /Library/Application Support/Autodesk/AdskLicensingService: No such file or directory touch: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory chmod: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 26: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 27: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 32: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory
Not sure if anything could be causing this issues.
Thanks.
Could you share your script? There are many incarnations floating in the thread.
Hello,
I recently used your script for the 2025 installation on an Intel Mac but are running into some issues.
I've been able to get the app itself to install but it won't launch, the app icon just bounces a few times on the taskbar and doesn't do anything else.
This is what the Jamf log displays after a "successful" installation:
Script result: find: /tmp/InstallMaya.app: No such file or directory
mkdir: /Library/Application Support/Autodesk/AdskLicensingService: No such file or directory touch: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory chmod: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 26: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 27: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 32: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory
Not sure if anything could be causing this issues.
Thanks.
this is my solution for Maya 2025.It also works for Mudbox too.
https://community.jamf.com/t5/jamf-pro/packaging-maya-2025/m-p/319704/highlight/true#M276963
Just thought I'd share my latest solution to silently install 2023 versions of AutoCAD, Maya & Mudbox with network licenses, while at the login window (aka a lab/classroom install). My goal was to make it as simple to use and to modify as possible. I've been using a variation of methods shared here for years (thanks by the way!) but decided it was time to really get to the bottom of things for myself.
It's a mashup of Autodesk's 'legit' install method with a simplified version of the custom network licensing steps we all know & love. However I do make note of the 'legit' network license registration steps for those who care, or are curious as I was (it does work, I just prefer the custom method). All details are in the script.
I've only deployed to macOS 12.4 Intel & Silicon, so ymmv, but I'm happy to report it's working perfectly for me on over 100 stations so far. Enjoy!
#!/bin/zsh
### Install AutoDesk Combo 2023 (AutoCAD, Maya & MudBox)
### silently @ login window with network licenses (aka multi-user lab/classroom deploy)
### 2022.07.27 by JonW
### Simply update variables/products below the function section as desired
### Read the additional details at the end of the script for more clarity on licensing.
### Ensure:
### 1) installer app(s) re-packed from .dmg by Composer & deployed to /private/tmp (root:wheel 755)
### 2) the network license server is functional
### 3) optionally, that previous Autodesk installations have been removed.
### and if so, you've also unloaded com.autodesk.AdskLicensingService.plist
#################################################
installFunction ()
{
### Before install, clear quarantine that may step on Setup.app when run at the login window.
### Also as of 2023, Mudbox still uses a different setup app path with --noui flag NOT --silent
### Finally, remove the installer app when complete
/usr/bin/xattr -rc /private/tmp/"${installerApp}"
if echo "$installerApp" | grep -iq "Mudbox"; then
/private/tmp/"${installerApp}"/Contents/MacOS/setup --noui
else
/private/tmp/"${installerApp}"/Contents/Helper/Setup.app/Contents/MacOS/Setup --silent
fi
/bin/rm -rf /private/tmp/"${installerApp}"
}
licenseFunction ()
{
### based off Onkstons's terrific work (I think they we're the first?) but simplified for 2023.
### see also, addl details at the end of script for alternative 'legit' licensing method.
licensePath="/Library/Application Support/Autodesk/AdskLicensingService/${productKey}_${year}.0.0.F"
/bin/mkdir -p "${licensePath}"
/usr/bin/touch "${licensePath}/licpath.lic"
/bin/echo "SERVER ${networkServer} 000000000000" > "${licensePath}/licpath.lic"
/bin/echo "USE_SERVER" >> "${licensePath}/licpath.lic"
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --pk "${productKey}" --pv "${year}.0.0.F" --lm NETWORK --ls "${networkServer}"
}
#################################################
networkServer="your.network.license.server.here"
### AutoCAD
productKey="777O1"
year="2023"
installerApp="Install Autodesk AutoCAD 2023 for Mac.app"
installFunction
licenseFunction
### Maya
productKey="657O1"
year="2023"
installerApp="Install Maya 2023.app"
installFunction
licenseFunction
### Mudbox
productKey="498O1"
year="2023"
installerApp="Install Mudbox 2023.app"
installFunction
licenseFunction
#################################################
### Verify license details - not required, but kind of nice to see.
/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper list
echo "Autodesk network licensing complete"
##################################################
### Additional network license details:
### For those who are curious, or if the above ever ceases to function:
### The 'legit' method for initial silent license registration (using autoCAD as an example) uses the 'register' command instead of 'change'.
### It also requires use of the --cf flag to denote a path to the app's config (.pit) file.
### e.g.
### configFile="/Library/Application Support/Autodesk/ADLM/.config/ProductInformation.pit"
### /Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --pk "${productKey}" --pv "${year}.0.0.F" --cf "${configFile}" --lm NETWORK --ls "${networkServer}"
### The end result is the same as the 'change' method used above (at least after the initial app launch).
### Essentially the 'change' method works backwards to manually create the licpath.lic directory & file,
### then uses the 'change' command to register it.
### Anecdotally, the 'change' method appears to produce a slightly faster initial app launch,
### but it's hard to say which is better.
### Either way, it's good to know both & having handle on the AdskLicensingInstHelper utility helps a lot!
### Check these out >>>
### /Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --help
### /Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --help
### Also, either method seems to deploy fine while at the login window, so no worries there.
### Some good tips & reference:
### https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Use-Installer-Helper.html
### https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/ENU/Autodesk-Installation-Basic-ODIS/files/ODIS-silent-install-htm.html
### Hope this helps some folks out!
For anyone looking at my script above - please seen new 2025 version here, dated July 22nd 2024:
https://community.jamf.com/t5/jamf-pro/packaging-maya-2025/m-p/319704/highlight/true#M276963
Hello,
I recently used your script for the 2025 installation on an Intel Mac but are running into some issues.
I've been able to get the app itself to install but it won't launch, the app icon just bounces a few times on the taskbar and doesn't do anything else.
This is what the Jamf log displays after a "successful" installation:
Script result: find: /tmp/InstallMaya.app: No such file or directory
mkdir: /Library/Application Support/Autodesk/AdskLicensingService: No such file or directory touch: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory chmod: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 26: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 27: /Library/Application Support/Autodesk/AdskLicensingService/_.0.0.F/licpath.lic: No such file or directory /Library/Application Support/JAMF/tmp/Maya 2025 Post Install: line 32: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: No such file or directory
Not sure if anything could be causing this issues.
Thanks.
@MCerano
I've just updated and tested my solution for 2025 apps on macOS13 (Intel) and macOS 13 & 14 (Silicon). Take a look here, it's quite different than previous versions. It's been solid in all my testing so far: https://community.jamf.com/t5/jamf-pro/packaging-maya-2025/m-p/319704/highlight/true#M276963
@MCerano
I've just updated and tested my solution for 2025 apps on macOS13 (Intel) and macOS 13 & 14 (Silicon). Take a look here, it's quite different than previous versions. It's been solid in all my testing so far: https://community.jamf.com/t5/jamf-pro/packaging-maya-2025/m-p/319704/highlight/true#M276963
Thanks @jonw, I'll check this out shortly. We are running OS 14 on Intel for now, hopefully this works well for us.
@MCerano
I've just updated and tested my solution for 2025 apps on macOS13 (Intel) and macOS 13 & 14 (Silicon). Take a look here, it's quite different than previous versions. It's been solid in all my testing so far: https://community.jamf.com/t5/jamf-pro/packaging-maya-2025/m-p/319704/highlight/true#M276963
Thanks so much, I was able to follow all of the steps you mentioned and got my deployment to work without any issues.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.