As I struggled with the AutoCAD OEM 2024 ODIS installer for several days (we upgraded from 2021 recently), and this thread helped me a lot solving my problems, I wanted to share my findings on how to pass the installation folder to the setup.exe without modifying the XML file.
The setup.exe accepts a command line switch ’ --installdir ':
setup.exe --silent --pf 000 --sn 00000000 --installdir “C:\Program Files\myProductName\”
This did the trick for me. The installer will use this as a base directory and install the files to a subdirectory named [NAME OF PRODUCT] [YEAR OF PRODUCT].
A feature to do a silent install with a minimal GUI (just a progress bar, maybe) would be nice to have, anyway.
2 Likes
Hi Stephan.
Any chance you could provide your command line to uninstall please? Been trying to find a way to uninstall 2024 via a command line but there seems to be a large difference from 2021, which had a setup.exe that you could use to launch an uninstall option, whereas 2024 doesn’t even seem to have setup.exe so I’m really confused?
Many thanks.
Neil
Hi Neil, sure thing:
"[ProgramFiles]\Autodesk\AdODIS\V1\installer.exe" -i uninstall -q -m "[ProgramData]\Autodesk\ODIS\metadata\{96DC9202-13CE-4A6C-B056-6FA3FF6ED336}\bundleManifest.xml" -WindowStyle Hidden -IgnoreExitCodes 1603
The GUID is assigned by you and can be extracted from setup.xml:
1 Like
Thanks Stephan! Good starting point to try and sort it at last!
If you need additional info, feel free to ask. Getting it all automated and running took a bit of an effort. Our team knows that.
Just to give a bit perspective and hopefully optimism: When it works, it works. This command is run thousands of times in a single month, both internally and (a bit less) by customers. It definitely runs a few hundred times per machine (internally for automated testing).
Hi Stephan.
That GUID in the middle of the uninstall is a bit of a pain! I think I’ve worked out a slightly clunky way round it but is ‘setup.xml’ copied to anywhere easy to access in the install directories so we can read that and extract the relevant UPI2 value?
Only instances I can find are hidden behind a GUID subdirectory and you don’t know the GUID to delve into without referencing the GUID in the setup.xml on our OEM build machine!
Hi Stephan.
Many thanks for your uninstall command - I’ve worked it into our InstallShield script by creating and calling a batch file to execute the command in the place where we used to just call setup.exe with the uninstall command switches. At least the batch file causes the InstallShield script to pause while the OEM is uninstalled!
Seems very messy using this ODIS compared to the old one?
Thanks again!
Neil
Glad you got it working!
I looked at our automation and we use a powershell script to extract the UPI2 from the generated setup.xml and then add it to the “uninstall definition” template for our custom installer.
To be honest, ODIS seems to be a bit over-engineered for what it actually does. Lots of moving parts with many places where it can fail - without propagating a useful error message back.
Once tamed, it’s working well enough. And it seems to have stabilized in recent time.
(We have our own installation tech which we use to manage all of our products incl. 3rd party and AutoCAD OEM-based products, so I think, we have at least a bit of insight into the requirements and design of such a system.)
