Packaging and deployment of AutoCAD 2023 Installation with Network server

[raghdasi]

Hello All,

Hope you all wonderful people having a nice and relaxing days.

I am trying to package and deploy AutoCAD 2023 with Network server license but It is not working for me. I am using script from following sites with customising to our licensing server and pKey but still no joy:

https://community.jamf.com/t5/jamf-pro/autocad-2021-deployment-with-network-server/m-p/229028

Also try to customise the scripts from following site but didn't work.

https://www.autodesk.com/support/download-install/admins/create-deployments/create-deployments-for-a...

The issues that it is coming up with are like:

Crashes while launching the app.

Sometime after installation it starts to roll back!! And uninstalls AutoCAD folder from  /Application Folder.

Doesn’t create data file then comes up with error can’t find the data file while doing activation.

Any idea please.

[nicholi]

I use this for 2022. You can modify it and see if it helps.  I do the installation via Self Service.

#!/bin/sh

## postinstall

## Mount dmg disk

hdiutil attach -nobrowse /private/tmp/AutoCAD2022_Installer/Autodesk_AutoCAD_2022.2_macOS.dmg

## Install AutoCAD 2022

sudo /Volumes/Installer/Install\ Autodesk\ AutoCAD\ 2022\ for\ Mac.app/Contents/Helper/Setup.app/Contents/MacOS/Setup --silent

## Activate AutoCAD 2022 with single type network license server

sudo /Library/Application\ Support/Autodesk/AdskLicensing/Current/helper/AdskLicensingInstHelper change --prod_key 777N1 --prod_ver 2022.0.0.F --lic_method NETWORK --lic_server_type SINGLE --lic_servers "Port@ServerIP"

sudo chown -R $USER /Users/$USER/Library/Application\ Support/Autodesk

exit 0 ## Success

exit 1 ## Failure

[emadams]

I am currently trying to deploy AutoCAD 2023 my self.  I have the package built and I can run it successfully.  It will install AutoCAD and I can launch it perfectly.  The big issue I am having is the fact that we don't use a single type network license server.  We use the redundant type network license server so I can't get the software to recognize the three servers we use so that it will just launch for the user and not prompt them to enter the license information. I know that the server connections do work because I am able to manually enter the server information and it connects and launches the software perfectly.  Any thoughts?

[JDK-JAMF]

I added dmg to a policy, cache the dmg and use this script to mount the dmg then install the application.

// Mount dmg disk
hdiutil attach -nobrowse ~/Library/Application Support/JAMF/Waiting Room/Autodesk_AutoCAD_2023_macOS.dmg

// Install AutoCAD 2023

sudo /Volumes/Installer/Install Autodesk AutoCAD 2023 for Mac.app/Contents/Helper/Setup.app/Contents/MacOS/Setup --silent

[JDK-JAMF]

changed the script, here is the update 

#!/bin/zsh

## Mount dmg disk
open /Library/Application\ Support/JAMF/Waiting\ Room/Autodesk_AutoCAD_2023.3_macOS.dmg

##Install AutoCAD 2023
sudo /Volumes/Installer/Install\ Autodesk\ AutoCAD\ 2023\ for\ Mac.app/Contents/Helper/Setup.app/Contents/MacOS/Setup --silent

[J_Morgan]

@JDK-JAMF 

When you say you "cache the dmg", what do you mean and how exactly would I do this?

Thanks,
Jim

[JDK-JAMF]

when creating the policy, you add the dmg as the payload but choose the dropdown from install to cache, this will store the DMG in the Jamf Waiting Room on the mac  /Library/Application\ Support/JAMF/Waiting

[J_Morgan]

Thanks, I think I've got it, but I'm getting this error message when the script runs during policy. I get the same error message if I run "open" command via Terminal.

Jim

[JDK-JAMF]

hi Jim, this maybe because the PKG is different, im using autocad 2023, you are using 2025, the setup path executable maybe different

[J_Morgan]

Yes, newer install so I had checked to make sure that setup was in same path before creating the script.

Thanks,
Jim

[nicholi]

Could it be because of the spaces you have in the command?

sudo /Volumes/Installer/Install\ Autodesk\ AutoCAD\ 2025\ for\ Mac.app/Contents/Helper/Setup.app/Contents/MacOS/Setup --silent

The above has backslash to account for spaces.

[J_Morgan]

It looks like the error message strips out backslashes. I think that I'd accounted properly for spaces in the path. Here's the actual script. I used zsh, since that is what was in JDK-JAMF's example. Mode would still use Shell/Bash, correct?

[J_Morgan]

I placed the .dmg in Downloads and ran "open" command, followed by "sudo" command, and application gets installed. It seems like there is something going on in when the .dmg is in the Waiting Room. I note that the perms for Waiting Room are for root only, but that shouldn't matter to Jamf Pro would it?

Jim

[J_Morgan]

Found this from a good while back, which sounds like what is happening to me.

https://community.jamf.com/t5/jamf-pro/waiting-room-folder-permissions/m-p/168315#M157230 

I set up this script to check if there is actually anything in Waiting Room and to report contents.

Looking at logs after running the script, we know that the ACAD 2025 .dmg is in there, just fails to run it. Curious that the .dmg does not have execution perms for anyone -- not even root?