Here is the code I modified for Mudbox 2023. It shouldn't be hard to adapt it for the other Autodesk products. Key things to change for other softwares are pkgPaths, pKey, and networkServer, unless they use a pkg like the Fusion lab installer, then it's plug and play.

@mgshepherd Does Autodesk's own silent installer still not work properly then? e.g. as documented here? https://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2023/ENU/Maya-Installlation/files/GUID-FBFA0C09-8E21-4EA1-95CD-E47A40D7C9F0-htm.html

EDIT: having now tried it myself I can confirm their new installation process works great, no problems. Does anyone know if there's a way to suppress the Data Privacy dialog that comes up at first launch? Other than that everything looks great.

EDIT 2: although now I've packaged it with Composer, I'm finding it doesn't work as a package with a postinstall script? what's that all about?

EDIT 3: so if I split up the files and the script into separate things (i.e. have a package that just puts the files on the machine, and then have the install command in a separate script) this works. what's different about the environment of a postinstall script in a package installer?

Aaand of course Mudbox 2023 uses a completely different installer :(

fwiw, running into odd issues myself. Maya has documentation for network deployment using the setup binary and feeding it an xml. AutoCAD doesn't seem to support this, and when I run setup --silent via a postinstall script, it hits some error then backs out the install. =(

I edited the original script because I needed it quick and I haven't had any issues. FWIW

I had a similar headache with Corel Painter. Three separate parts to get it installed. 

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!

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?

 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.

@kwoodard Thanks!  Yep the '000000000000' should be just like that.  Nothing to replace.  If you run the 'legit' license command it produces exactly this as well, no idea why, but it needs to be that way.  I want to say Arnold comes down with the Maya install, but I wasn't watching closely.  Here's what I see after install:

 That said, I did pull down a standalone 'Autodesk MtoA-5.1.3.2-darwin-2023.pkg' as well, but didn't install it.  The pkg contents appear to be the same as what comes with Maya.

Awesome! Thank you @jonw !

One last question, it seems that we have a server license for Maya and AutoCAD, but use a serial number for Mudbox. How would I modify the code to use the serial number over the server?

That's a great question! ... I have no idea 😉 
Though this should be a good place to start:
https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Use-Installer-Helper.html
I'm in higher education, so luckily we just use the free education network licenses.  If an instructor wants an 'offline'  version we have them create their own account to deal with annual license verifications themselves.  They almost always opt to just use the network license.

Actually now that I look closer you're probably better off using the 'legit' register command.  There's a flag for a serial number --sn and I'm guessing your --lm for MudBox would be USER or STANDALONE

Install one of the apps, then check this out for details:

Good luck!

OK, I am stuck... The above scripts work great for a network licensing server setup... For the life of me I cannot figure out how to do a serial number setup. On our campus, we have a serial number license for Mudbox. I have tried using the following, but I get an error: "flag provided but not defined: -sn"

 I commented out the server stuff since our Mudbox uses a serial...Lord knows why. 

I talked the guy that manages our server license for Autodesk to add Mudbox to the license server... Now everything works great. Thanks @jonw , your script is awesome!

Anyone know how to suppress the two dialog boxes that show up when the app starts (mainly Maya and CAD)? My stuff from 2018 doesn't seem to be the case anymore.

For those of you looking for a STANDALONE deployment check out @robertojok's  solution here. Amazing! Thank you @robertojok 

Here is the full script for 2023 Standalone Serial

Hi, our devices are running Monterey 12.5.1. Do you know if your script is compatible with this version? Tnx

Have you encountered any issues with macOS Monterey 12.5.1?

Our institution has three license servers. Ho do I populate 'networkServer=' correctly with the license server names/IPs?

Autodesk’s guide states to separate them by a “ ; ” but I was not able to get that to work. 

Thanks for responding. Yeah, same here, no joy!

I tried using @jonw 's script, but I seem to be running into an issue where Maya doesn't install and I believe it rolls everything back. Not sure where to check exactly as to what is happening. I made a new package with the --silent removed and the Install worked, but obviously had to click through all the menus. Does anyone have any idea as to what might be causing the install to fail? Should the postinstall script be in Composer or Jamf?

Thanks!

The summary log in the macos consolde shows this.

@Medo Funny timing, I'm actually working on Autodesk updates this week.

I can confirm my script worked without issue a few weeks ago on a dozen Intel iMacs with macOS 13.1 using the same 2023 pkg's I've used since July.  

BUT, just yesterday I had Maya fail on a fresh install as well!  Kicking the licensing service, fully removing & re-installing worked fine on the 2nd round.  Go figure.

I've noticed the install app does perform a curl to Autodesk during installation, I'm wonder if a failed network connection is the culprit?  Just a thought.

btw, here's my removal script, I take no responsibility for its use, it needs some cleanup, please use with care.  My policy always runs this prior to an install/re-install.

sorry, duplicate reply

Thanks for the update. I ended up removing the script from Composer and adding it to Jamf. Then I added the the script to the policy that had the Composer package. That seems to have fixed the issue for me. Deployed the policy successfully to 30 M1 iMacs. Maybe a permission issue with whatever the installer downloads when it runs?!

On a side note, do you have a solution to automate the privacy/data collection popup on first launch or do you just run it once on all computers?

Thanks for sharing your script.

No problem!  And yep, I would expect the script to fail as part of the Composer built pkg.

I get around the privacy/data collection popup by deploying this directory & json files (grabbed from an already agreed login) to all user accounts prior to first launch.  I don't recall if I made any edits to the files, you might want to take a look & test/edit for your environment.

.

This worked in the Mac Labs at our college. Really appreciate your work on this! Saved me a bunch of time. Deployed Maya 2023 successfully in our Mac Studio lab and pointed to our License server. You Rock!