Ok all looks like I got this all working again, but slightly different.  2 things....just remember to enter your own SN and product ID for the x's and also make a pkg with composer that puts the 2023 installer in /Users/Shared but this is working great now.

@GabePPS your script works,

I made a slight modification for distributed network as shown below

/Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --pk "777O1" --pv "2023.0.0.F" --lm NETWORK --lt DISTRIBUTED --ls "2080@my_Lic_server1,2080@my_Lic_Server2" --sn "xxx-xxxxxxxx" --cf /Library/Application\\ Support/Autodesk/Adlm/.config/ProductInformation.Pit -el US

However the only problem like 2022 version, it cannot be installed when the computer restarts, the only option is either self service or on login.

@GabePPS 
Thanks Gabe.
I tried just tried updating last years script - I think lib.pkg gets stuck at gatekeeper (according to install.log).
A "sudo xattr -dr com.apple.quarantine /" of it didn't make a difference and as you highlighted, triggering setup with the --silent option works perfectly.

So, just wrestled with this a while, and think I finally got it. Turns out, if you uninstall the product, it leaves the licensing service running (I guess in case you have other AutoDesk products using it). So when you go to re-test after uninstalling, things don't work because it's waiting for the licensing service to spin up. 

Here's what I got working for a postinstall script. Note, with the "killall's" at the top, if any autodesk software is running on the machine, it MAY die on you if the license service is killed in the background. You may want/need to comment out those lines... 

Does this installation work without a user logged in? I have found that the latest versions of AutoCAD, last tried on 2022, does not install unless a user is logged in so when set to On Startup trigger it does not work, does your script above permit installation on startup?

I have the students running this from self service, so yes it does require a user to be logged in. 

Hmm... while this worked installing via package directly, it doesn't seem to work via Jamf... need to figure out why. =(

I haven’t tried a silent install unattended, but it should be fine.

Why is everyone insisting on using the DMG though?

I packed up the PKG from inside the DMG using composer. Haven’t seen any issues ‍♂

honestly, it's just tried and true on my side. I tried with the .app and got same thing. If you just install the pkg's though, I see it just crash on start.... 

Yup the old script just relied on running through the installer pkg files and the program for whatever reason didn't like that anymore.  Used to work just fine.  But as @rstasel said, we saw issues with it looking correct during the install but when the final user tried to open it, it would crash or give an error.

what just a garbage installer. I keep having it rollback because it can't start the licensing processes... which is why I had the killall's at the start, but now it's not working even with those. =/ 

what was working just running manually isn't even working at all now... so I'm completely lost. 

I used:

sudo /Library/Application\\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper register --pk Etc

right. I'm saying even before it gets to that stage, I'm seeing: 

2022-07-11 11:53:34-07 comp package_script_service[4344]: ./postinstall: 2022-07-11 11:53:34.972 postinstall[32309:30418943] AdskLicensingService is not running...

2022-07-11 11:53:34-07 comp package_script_service[4344]: ./postinstall: 2022-07-11 11:53:34.972 postinstall[32309:30418943] The AdskLicensingService is not ready.Try again...

Tries that 3 times, then gives up and rolls back the install. =/ 

hmm, so manually starting the license service first worked. ugh... what a nightmare. 

Package installs when run manually from a machine... fails to install when installed via jamf. 

Have you all gotten this to work via Policy called from terminal? I can't tell why it's failing because it's entirely hidden... just starts installing then nearly immediately fails and rolls back. If I run the postinstall script myself, it works. if I run the package that I built myself, it works. it just fails when being called from Jamf. =/ 

As I was planning to push it out to labs ad-hoc I thought I’d go through the process of trying an installation by check-in myself.

AutoCAD doesn’t even finish, but Maya at least exits 0 without deploying the app.

I humoured trying a:

sudo -H -u localadmin bash -c ‘install —silent etc’

Just to see if it needed a local account to dump stuff into. JAMF fed back…

Script result: HTTP/1.1 200
Date: Tue, 12 Jul 2022 15:35:32 GMT Content-Type: application/octet-stream Content-Length: 1091 Connection: keep-alive

Set-Cookie: JSESSIONID=E18CB6D25625DB5C71B6C04FD2559C; Path=/;

HttpOnly content-disposition: attachment; filename ={30BA09BB-CC25-3E2B-A403-C4AFB70A4D7F}.zip

checksum: a8c3818f45fa6ec23320558cdeffab05b2ffad8854dbffd013c88e5c1555 Set-Cookie: fileDownload=true; Path=/; domain=.autodesk.com;

HTTP/1.1 200 OK Accept-Ranges: bytes Content-Length: 16367718 Content-Type: application/octet-stream ETag: "5817f733cff6d92d1c1b247b709652a1655690408.4593"

Last-Modified: Mon, 20 Jun 2022 01:59:57

GMT Server: AkamaiNetStorage Date: Tue, 12 Jul 2022 15:35:35 GMT Connection: keep-alive

boost::filesystem::permissions: Operation not permitted: "/tmp"

Checksumming Protective Master Boot Record (MBR : 0)… Protective Master Boot Record (MBR :: verified CRC32 $BC5FCD8 Checksumming GPT Header (Primary GPT Header : 1)… GPT Header (Primary GPT Header : 1): verified CRC32 $A5DE0B7 Checksumming GPT Partition Data (Primary GPT Table : 2)… GPT Partition Data (Primary GPT Tabl: verified CRC32 $67A79011 Checksumming (Apple_Free : 3)… (Apple_Free : 3): verified CRC32 $00000000 Checksumming disk image (Apple_HFS : 4)… disk image (Apple_HFS : 4): verified CRC32 $FAB59D5D Checksumming (Apple_Free : 5)… (Apple_Free : 5): verified CRC32 $00000000 Checksumming GPT Partition Data (Backup GPT Table : 6)… GPT Partition Data (Backup GPT Table: verified CRC32 $67A79011 Checksumming GPT Header (Backup GPT Header : 7)… GPT Header (Backup GPT Header : 7): verified CRC32 $E2FDD81A verified CRC32 $178EC9FD /dev/disk2 GUID_partition_scheme /dev/disk2s1 Apple_HFS

/private/tmp/odis_download_dest/10239101429748123765/Darwin "disk2" ejected.

Preparing...

sudo: /Library/Application Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper: command not found

This tracks with what I was seeing. it fails out because it can't install some piece. I've got a ticket in with Autodesk, but I'm assuming they're not going to be of much help. Let us know if you find any additional info... even on machines with Adsk already installed it will still fail when deployed via Jamf (seemingly)

well, digging into ODIS logs ~/Library/Logs/Autodesk/ODIS/Setup.log, I'm seeing:

2022-07-13T08:56:52.172 [Bootstrap: 63187, 0x1191bf600] [Bootstrap INFO] [ ExecuteCommand ] Launching process: /Volumes/Installer/Install Autodesk AutoCAD 2023 for Mac.app/Contents/Helper/Setup.app/Contents/MacOS/../../../ODIS/AdODIS-installer.app --silent --install_mode install --manifest /Volumes/Installer/Install Autodesk AutoCAD 2023 for Mac.app/Contents/Helper/Setup.app/Contents/MacOS/../../../setup.xml --manifest_xsd /Volumes/Installer/Install Autodesk AutoCAD 2023 for Mac.app/Contents/Helper/Setup.app/Contents/MacOS/../../../ODIS//SetupRes/manifest.xsd --url_root https://dds.autodesk.com --installation_id f3058166-fbfa-4fc9-8966-82cc86d98a2a --install_source "/Volumes/Installer/Install Autodesk AutoCAD 2023 for Mac.app/Contents/Helper" --offline_mode --trigger_point local --installer_version 1.31.0.527
2022-07-13T08:56:52.174 [Bootstrap: 63187, 0x1191bf600] [Bootstrap ERROR] [ ExecuteCommand ] => Process failed to launch. System exit code 13
2022-07-13T08:56:52.174 [Bootstrap: 63187, 0x1191bf600] [Bootstrap INFO] [ ExecuteCommand ] Restore working directory: /Volumes/Installer/Install Autodesk AutoCAD 2023 for Mac.app/Contents/Helper/Setup.app/Contents/MacOS
2022-07-13T08:56:52.174 [Bootstrap: 63187, 0x1191bf600] [Bootstrap ERROR] [ ExecuteCommand ] => Unmapped error
2022-07-13T08:56:52.174 [Bootstrap: 63187, 0x1191bf600] [Bootstrap FATAL] [ execPostUIOperations ] ERROR! Failed to run DDA. Returned value=[ 0 ].
2022-07-13T08:56:52.174 [Bootstrap: 63187, 0x1191bf600] [Bootstrap DEBUG] [ Exit ] Exit
2022-07-13T08:56:52.174 [Bootstrap: 63187, 0x1191bf600] [Bootstrap INFO] [ TrackAdpEvent ] TrackEvent data: {"operationId":"24A48E96-A64B-4D95-8F9C-41DCCCA35BA7","operationStage":"BOOTSTRAP","operationStatus":"OP_ENDED","operationType":"install","operation_errors":{"BS_ERROR_311","BS_ERROR_706","BS_ERROR_706","BS_ERROR_706","BS_ERROR_701"},"operation_meta":{"bootstrap_error_code":"BS_ERROR_311, BS_ERROR_706, BS_ERROR_706, BS_ERROR_706, BS_ERROR_701","bootstrap_error_context":"odisver xml path does not exist###process completed with non-zero exit code: 1###process failed to launch: 13###unmapped error###failed to run DDA with exit code 0","bootstrap_execution":"fail","bootstrap_execution_time":"2.768058"},"product_meta":{"odis_session_id":"24A48E96-A64B-4D95-8F9C-41DCCCA35BA7","odis_events_category":"Bootstrap","installation_id":"f3058166-fbfa-4fc9-8966-82cc86d98a2a","target_product_name":"AutoCAD 2023 for Mac","target_product_line_name":"ACDMAC","target_product_id":"{EA0E78B5-DE74-3C81-8130-D458BFCD0C4B}","target_product_release_id":"2023"}}
2022-07-13T08:56:52.299 [Bootstrap: 63187, 0x1191bf600] [Bootstrap INFO] [ main ] Bootstrap exit code: 0

Only thing I can find about Error 13 is: https://knowledge.autodesk.com/support/autocad/learn-explore/caas/sfdcarticles/sfdcarticles/Common-FlexNet-error-codes.html

About calculated path too long. The log is a bit of a mess though... and so far, Autodesk support hasn't been terribly useful. 

I would run the uninstaller command for the year version you are using, then do a restart and try the installer script again.  My guess is something is still running that is keeping it from finishing the install.

Yeah, could be. I've been running uninstaller all along, but that doesn't remove their licensing piece, which is why I have code to unload that just in case. I'd be curious if others are able to get this working under Jamf... because like I say, works great if I install package I built as my user, or any user... but the moment it deploys with Jamf, it fails. So there's some permission/environmental variable that it wants that isn't set for user jamf agent runs under (root?)

Again I am running this specific script in self service without issue.  One the few times we have seen the installer do what you are describing, a restart seemed to fix it.  The first step is packaging up the "Install Autodesk AutoCAD 2023 for Mac" installer file with composer to just throw it in the /Users/Shared folder then running this script from self service but with your serial number:

 If this fails, during the install, then a reboot is required and fixes the issue for us.  However this maybe happened only in 1 out of 25 of the installs.

If you run it just via policy in terminal (sudo jamf policy -trigger <triggerhere>) does it also work for you? 

Yes except on ones that previously had a certain version installed (hence the one in 25 number) which then have to be restarted after first running this script.

same failures. fails one of the steps then just backs out. reboots do nothing. there's no uninstall to run because it never gets to the step of actually installing the AutoCAD folder. =/ 

Are you installing in 12.4? Have you set any pppc policies for the installer? 

So, I kept reading this over and over and something you said finally stuck:

"The first step is packaging up the "Install Autodesk AutoCAD 2023 for Mac" installer file with composer to just throw it in the /Users/Shared folder then running this script from self service"

So used pkgbuild to make a package of the .app, and have it thrown into /Users/Shared. Then made a Jamf script of what you have. Policy installs the pkg, then runs the script after (rather than a post-install script on the package). 

Then realized I already had a script for doing this back in the 2021 days. lol. 

Thank you sir!