Deploying Custom Install 2022 to SCCM... Some more Information is needed

[BroomeIT]

Been really stoked about the new ability to bundle most of the 2022 AutoDesk products back into a single package. Though it seems to still be severely lacking or rage inducing to try and find more information about it.

Trying to get it into SCCM as an application has proved... difficult.

First the only information I could find was two pages one that just says to install silently comment out and uncomment these lines in the .bat file generated when you run the Custom Install bundle you create from your management site.

Good start

What about a detection method? Applications in SCCM need to have a detection method to tell when they are installed. I'd be fine if it was just layering in ALL the MSI GUID's for the major software installs. The problem is the bundle kind of obfuscates that all you get is a reference to the same installer.exe with uninstall and a xml manifest file for each piece you bundled. A simple list even a rem block under each item with its MSI GUID would go a LONG way to making this easier to package.

The second bigger issues is in order for An Application in SCCM to properly work it needs to WAIT to return until it's ALL done installing. Running either the Bat file OR the Installer.exe command line from the batch file promptly spawn entirely new installation processes and then promptly DIES! Which causes the SCCM client to go "guess we're done here... and failed." meanwhile the install is still rolling along.

I don't like to rant but it seriously like the people designing these bundling logic have NEVER touched a modern version of SCCM. News flash Packages are an ARCHAIC deployment option in SCCM (for probably a decade at this point and technically it's not SCCM its MEMCM for those of us who actually keep our environment up to date) This should be an Application period.

All that frustrated vitriol might be lessened if I could find an actual documented list of Installer.exe's  valid command switches, maybe there's a --wait or a --sccm I'd even take an antiquated --sms! Something ANYTHING to make this not like shooting off a shotgun in a dark room and hoping it doesn't kill someone.

So TL/DR

• Installer.exe where can I can find ALL possible command line switches
• Packaging for MEMCM - More info please, e.g. Detection Methods

Thank you

[kenetter]

I use ZCM instead of SCCM for my software deployments, but I did just figure out how to get Revit 2022 to install, so thought I would share my experiences in case it helps.  My solution may not exactly correlate with how SCCM works, but may provide some suggestions.

ZCM is able to take the install command line that Autodesk provides in the batch file and run it elevated.  Because I am running this from a network share, I added "SEE_MASK_NOZONECHECKS = 1" to the run task.  I have found that the ODIS logs provide good troubleshooting info (C:\Users\<username>\AppData\Local\Autodesk\ODIS).  Digging through those I discovered that one of the content installers wanted access to the network folder where we store our templates, families, etc.  I gave the system account I use for installations full access to that folder and the installation completed successfully.

Hope this helps,

Ken

[mockcm]

I know this is an old post, but I'm having this same issue with Autocad 2023, Care to share your Autoit script? I have tried this myself with an autoit script creating a local admin user installing then deleting the user, still no luck installing from SCCM.

[brantzdr]

Any Chance in getting a copy of that Autoit script to install AutoCad - I'm trying to install AutoCad2023 and running into the same issues.  Thanks!

[PeabApplicationdeployment]

Same issue for AutoCad2023.

[i.northwood]

For anyone coming here looking for a solution to the same issue for Revit 2023...

The return value is correct but, if you look further, it *might* be because Revit 2023 is already installed. The same applies to other ODIS-driven installs.

We deploy our apps using CMDs so it was a simple job to add a line to echo the %errorlevel% returned by the installer. 

[foxrj]

It's 2025 and the documentation for deploying via sccm is still horse feces. 

[Simon_Weel]

There are a couple of posts about this:

Youtube Videos for Intune Deployments - Autodesk Community

Using Intune for Installations - Autodesk Community