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

[JTBWorld]

Have you see this? AutoCAD 2022 Help | Using Microsoft Configuration Manager to deploy and manage Autodesk products | A...

[BroomeIT · Accepted solution]

Yeah I've seen that again it's basically a rip off of ANY how to create a MEMCM Application it gives ONE msi product code and its Civil-3D 2020. Because they hide the actual MSI's behind a got dang installer.exe and an xml file there is noway without a LOT of digging to find your way to the actual MSIs to open them to find their actual product codes to add into my application's detection method.

I should not have to setup a new VM JUST to install the bundle so I can go on a GD fetch quest for the detection methods for each piece. The Bundle logic knows ENOUGH to give me the installer.exe version of how to uninstall EACH separate piece in the batch file there is ZERO reason aside from either laziness or ignorance that each piece can't also have a few more rem lines 

so instead of JUST this

rem ========== Uninstall Autodesk Revit 2022
rem "C:\AutoDeskBundle\image\Installer.exe" -i uninstall -q --manifest "C:\AutoDeskBundle\image\RVT_2022_en-US\setup.xml"

It Should have something like this

rem ========== Uninstall Autodesk Revit 2022
rem "C:\AutoDeskBundle\image\Installer.exe" -i uninstall -q --manifest "C:\AutoDeskBundle\image\RVT_2022_en-US\setup.xml"
rem ===== For MEMCM
rem Detection Method: MSI
rem Product Code: {28B89EEF-1001-3102-CF3F3A09B77D}

The older 2015 installs at least when you got done running the bundle gave you SOME SCCM information to go on.

All that being said there's still the TINY issue of installer.exe spawning entirely separate processes and ending its own process BEFORE the other actual installer's finish installing!! when that happens the local configuration manager service will immediately flag the application as "done" run its detection methods and declare it a failure.

[ArjanBouwhuis3415]

Hi BroomIT,

Did you found a fix for the installation of Revit 2022? Because it keeps failing for me too. Strange thing is that the uninstaller works fine...

Regards,

Jan Peter

[ITSteve]

+1 for better options for deployments.  

Also, with the online deployment tool I don't see how to add additional files/folders to the deployment in AutoCAD.  Is that available?

[Lurifax]

Just when you have figured out all the switches that never were properly documented they change it 😞 .

I hope they drop in to give some information. We try to deploy a new AutoCAD every 2 years, last time we tried it was 2020 and it failed miserably as the AdskLicensing-installer.exe had several bugs in it when deployed by SCCM. Skipped 2021, now 2022 seems to be a bit challenging...

[malbitz]

So did anybody get this to work in SCCM?  Are you using the batch file Autodesk created?  Mine point to a c drive location like the examples below and then fails.  I took the c:autodesk... out of the batch file and it still fails.  Autodesk support has been less than useless on this issue.  No help at all.  

I have tried:

"c:\autodesk\Revit2022\image\Installer.exe" -i deploy --offline_mode -q -o "c:\autodesk\Revit2022\image\Collection.xml" --installer_version "1.19.0.20"

"image\Installer.exe" -i deploy --offline_mode -q -o "image\Collection.xml" --installer_version "1.19.0.20"

".\image\Installer.exe" -i deploy --offline_mode -q -o ".\image\Collection.xml" --installer_version "1.19.0.20"

Nothing seems to make this work.  Any help would be great!!

[Lurifax]

Hi,

did you also edit the 

<DeploymentImagePath>.\image</DeploymentImagePath>

in collection.xml?

[gndmnlc11]

i tested a autocad 2022 installation with the normal procedure (basically launched the bat file which was automatic created) on a virtual client.

try to look at the %temp% folder of your windows user account (normally C:\Users\%your_user_name%\AppData\Local\Temp). there i found a lot of logs and mst files for the msi packages. i'm still looking at this.

[alan.jamard]

I tested all types of deployments possible with this new version. Neither works during a Task Sequence.
Always the same error :
Exceeded timeout while waiting for process to finish.

Error 0x87d00213.

The new deployment system does not live up to the scripts provided on older versions. And the quality of the uninstall script is so bad. Hardly anything is uninstalled.

It is not possible to have access to an admin image as in the 2020 versions?

[mdavis22569]

@BroomeIT  were you able to get this resolved? 

[gndmnlc11]

i'm trying this with autocad 2022 german:

software orca for msi/mst editing needed.

• installed autcad 2022 on a virtual client with the bat-file
• collected all msi packages and mst files (mst found in the %temp% folder)
• deployed autocad as following
  • required .net framework is already part of my windows 10 image (20h1)
  • both visual c++ required runtimes (2012 and 2019)
  • autodesk save to web an mobile msi, product code {192B349F-C3F7-4BBE-B49E-00DD4BD28373}
  • aca & mep 2022 object enabler msi, product code {C8DFC969-241E-4707-A93B-08C88821D22B}
  • autodesk licensing installer, i created my own msi package (installs AdskLicensing-installer.exe --mode unattended --unattendedmodeui none)
  • autodesk material library 2022 msi, product code {A9221A68-5AD0-4215-B54F-CB5DBA4FB27C}
  • autodesk single sign on component msi, product code {B9F5BDED-021C-4926-8518-4FA7114B7040}
  • autodesk material library base resolution image library 2022, product code {6256584F-B04B-41D4-8A59-44E70940C473}
  • autocad 2022 msi, product code {28B89EEF-5101-0000-0102-CF3F3A09B77D}
  • autocad 2022 language pack german msi with mst file, product code {28B89EEF-5101-0407-1102-CF3F3A09B77D}, mst modified with orca for installation without setup.exe
  • acad private msi with mst file, product code {28B89EEF-5101-0000-3102-CF3F3A09B77D}, mst modified with orca for installation without setup.exe
  • acadps autocad 2022 german with mst file, product code {28B89EEF-5101-0407-2102-CF3F3A09B77D}, mst modified with orca for installation without setup.exe
  • autodesk app manager msi, product code {9C2E49CB-F671-47EC-8093-CC1A8749A92A}
  • autodesk featured apps msi, product code {46EA8955-D629-4B3E-AAF0-D136031D7C95}
  • autocad open in desktop msi, product code {1C66A0B0-784E-4777-97B3-93F843D1C8CF}
  • autodesk genuine service msi, product code {879EB006-4A55-4873-8BC5-2183B2B5E0F5}

it looks fine on my virtual test client.

[david_lowe2]

No, this makes no difference. Looking in the standard windows event logs, the error indicates the installer cannot properly interpret the paths. Even shortening the path depth did not help for me.

[david_lowe2]

I'm creating my own installer routine in Power Shell to just install all the msi components, and making shared components dependencies in SCCM. This used to be really straightforward using supplied classic SCCM templates. Now Autodesk seem to be making life harder for its customers. Totally stupid.

[BroomeIT]

@mdavis22569 not yet this got back burnered a bit for other stuff (When you mange BOTH the OS creation and Deployment AND Application packaging and deployment for BOTH MEMCM and Intune things with no momentum get walked over and ignored pretty fast) but I'll be back around to it before long because we have to get our systems updated because they are switching to user based licensing and the 2015 they are currently running is going to be cut off at the knees after the 31st of July.

I'm at least comforted by the fact I'm not the only one suffering over this dumpster fire of an installation system

[BroomeIT]

So I'm curious how you reconcile things like wanting the AutoCAD Electrical vs AutoCAD MEP, or the other hyper specific variants? I already know the share the common code files but it would seem like you'd need to install way more than what you listed. I'm definitely going to cheat of your paper though and grab some info (especially some of the product codes you already harvested 😉 save me time to look up the other ones you didn't install)

[sdoughtySKQW2]

I use a Powershel Script to launch the install from SCCM: 

#InstallAutocad2022.ps1 Written 6/15/2021  

$ScriptPath = split-path -parent $MyInvocation.MyCommand.Definition
Write-Host $ScriptPath

# Install Software
$argumentlist = " -i deploy --offline_mode -q -o `"$ScriptPath\image\Collection.xml`" --installer_version `"1.19.0.23`" "

Start-Process "$ScriptPath\image\Installer.exe" -Argumentlist $argumentList -Wait

The command in SCCM is Powershell -ExecutionPolicy bypass .\InstallAutocad2022.ps1

[lhall.autodesk]

Just a heads up. If you're like me and you're trusting that the Autodesk scripts in their packages just work fine with SCCM, there's some issues with their installers for trivial things like licensing.

AdODIS-Installer.exe and ADSKLicensing.exe both are getting stuck when trying to run the installs through SCCM because of the way SCCM deploys applications through the NT Authority\System context.

Been scouring through the forums for days and it looks like the issues we might be having is due to this.

[alan.jamard]

Always timeout during the sequence task. Regardless of the changes tested in the installation. How to unlock that to finally have a complete machine out of the bench ...

[Anonymous]

I've been having the same problems in our environment. I see that Autodesk continue to blame SCCM, when it isn't even SCCM that is the problem. Simply trying to install the Autodesk product's under the SYSTEM account, fails.

I have managed to find a workaround for SCCM deployments, but Revit 2022 and AutoCAD Electrical still won't install. The other products appear to install OK now though. What I did, was capture/re-package the installation of the very annoying AdODIS application. From here, I turned this into an MSI and added it as an application in SCCM. I then put this above all Autodesk applications. All Autodesk 2022 apps now install, apart from Revit and AutoCAD Electrical. Trying to work out why these two are still being a problem, it's great when the install fails and it doesn't log anything in the Autodesk log directory ...

It just seems like these problems are re-occurring with Autodesk. It's a shame that they can't listen to their customers and look at the issues being reported to actually improve their products. We aren't all home users, who install the products manually onto one computer.