Here is what I had to do to get the whole suite working with SCCM.
1. Pull out the SCCM script from the install .bat file that is included and replace the network location with the local location and put this in its own batch script. ie.
"\\%network%\AutoCad2022\image\Installer.exe" -i deploy --offline_mode -q -o "\\%network%\AutoCad2022\image\Collection.xml" --installer_version "1.19.0.20"
to
.\image\Installer.exe -i deploy --offline_mode -q -o .\image\SCCMCollection.xml --installer_version "1.19.0.20"
All of the Autodesk suite apps will accept the .\image\Installer.exe location in this batch script except for Inventor. You'll have to specify the paths so it looks like this:
%~dp0image\Installer.exe -i deploy --offline_mode -q -o %~dp0image\SCCMCollection.xml --installer_version "1.20.0.44"
You'll also want to do the same for the uninstall path, it will look like this(Create a different batch for uninstall):
"%network%\Mudbox2022\image\Installer.exe" -i uninstall -q --manifest "%network%\Mudbox2022\image\MBXPRO_2022_en-US\setup.xml"
to this:
.\image\Installer.exe -i uninstall -q --manifest .\image\MBXPRO_2022_en-US\setup.xml
2. In the image folders of each deployment, copy the Collection.xml and rename it to something else, I've renamed them to "SCCMCollection.xml". Now edit this to take out the network portions and replace it with the local paths you've set earlier above. You'll want to change both the <DeploymentImagePath> variable and the <LoggingSettings><Path> variable. Here's an example what they will look like:
<DeploymentImagePath>.\image</DeploymentImagePath>
<LoggingSettings>
<Logging>true</Logging>
<Path>.\log\InventorPro2022.log</Path>
</LoggingSettings>
3. Repackage the dependencies that have been causing the stalling deployments. Take the Adodis-Installer.exe, ADSKLicensing, and ADSKApp(Autodesk Desktop App) from the included installers you've packaged. Keep in mind, if you've packaged the software on different days or after an update has gone out, the older software I mentioned above won't work with the newer Autodesk apps, you'll just get the same issues when the newer versions try to run.
You'll find these in the following locations(Or at least I did):
ADODIS-Installer.exe:
In your AutoCAD 2022 Folder
.\image\ODIS
ADSKLicensing-installer.exe:
In your AutoCAD 2022 Folder
.\image\ACD_2022_en-US\x86\Licensing
AdApplicationManager-installer.exe:
In your 3DS Max 2022 Folder
.\image\3DSMAX_2022_en-US\x86\ADSKAPP
You'll want to repackage ADODIS-Installer and AdApplicationManager-Installer with something like AdminStudio, as these both cannot run with the System context that SCCM uses to deploy applications.(This is where Autodesk has not done any testing, and it shows).
For the ADSKLicensing-Installer.exe, you can create an application in SCCM with the following switches:
"AdskLicensing-installer.exe" --mode unattended --unattendedmodeui none
For detection I've detected the version of the application .EXE located here(Not the best way for detection, but its all we have):
C:\Program Files (x86)\Common Files\Autodesk Shared\AdskLicensing\11.0.0.4854\AdskLicensingService\AdskLicensingService.exe
Add these into SCCM.
4. Because Autodesk refuses to spell out plainly what the MSI codes are for their deployments, we'll have to install the programs we want to use so we can grab the GUID of the applications.
Go ahead and install the 50+ GB of Autodesk Suite apps on a test machine(Takes like 3 hours) and run the following command using Powershell to grab all the MSI codes on your machine:
get-wmiobject Win32_Product | Sort-Object -Property Name |Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize
You can then use these codes for detection for their corresponding deployments.
5. Go ahead and add your deployments into SCCM now and use the information you've gathered earlier. For the install and uninstall paths, add in your newly created batch scripts. For detection, add in your captured MSI codes from earlier.
It will look something like this:
6. You'll want to deploy the ADODIS-Installer, ADSKAPP and ADSKLicensing first before deploying your Autodesk deployments to your machines. You can either do this using dependencies in SCCM or using the application groups or both.
I've used application groups and added the dependencies in the first part of the group so they will install before the rest of the deployments that require them to run.
Make sure to test out this using REQUIRED deployments to your test collections as this will force the deployments to be installed via SYSTEM context which is where this all started..
I hope this helps some of you, because I've spent the last few weeks battling with this. We shouldn't need third party packaging software to deploy these applications. Autodesk has documentation on how to install the Autodesk suite through, but I don't think they even tested it fully.
