Struggling with managed installation for Autodesk products
Our company uses PowerMill in various sites. While Autodesk is nice enough to provide a deployment package with an installation script, I'm struggling to get it working with the KACE through either managed installation or running a script.
With the Managed installation, I have it assigned to the software inventory that gets installed. For example, Autodesk PowerMill Standard 2025 (25.0.1). I've tried associating the .bat file that autodesk creates (which works fine if you run it on the target system manually). Pretty much from the install share, it launches:
"Installer.exe" -i deploy --offline_mode -q -o "{Configurationfile.xml}"
I've tried various was of invoking this through the MI portion. Running the .bat file form Autodesk through the $(KACE_DEPENDENCY_DIR) (which does work if I manually trigger it), doing a default override with the batch file on the share, doing a default override with the command line from the batch file (that is running the full [Share]\Installer.exe -i deploy --offline_mode etc. Nothing seems to work.
I even tried running it as a script, both by having the KACE copy the script locally, and run it direct from the share, running it as system, running it with admin credentials...nothing seems to want it to trigger.
For some reason, it just seems to be Autodesk products. I've tried with DWG TrueView and Moldflow Communicator (both Autodesk products) and similar results. Other CAD/CAM software we have in our environment seem to have no issues being push-deployed through the KACE.
Has anyone else ever run into issues trying to install products with a batch file? The KACE does have access to the installer directories (like I said, other products seem to deploy without any problems).
Answers (1)
Hi @bgiroux,
We've deploy different Autodesk products from our K1000. However, our approach is local installation rather than network share and our online KACE script runs as system.
Uploaded each package created from Autodesk custom deployment module. Made modifications to the generated batch file in root folder & .\image\Collection.xml. Works perfectly.
The contents of our batch file used:
".\image\Installer.exe" -i deploy --offline_mode -q -o ".\image\Collection.xml" --installer_version "x.x.x.x"
Since your resources are off a network share, I would suggest that you to:
- Check the supplied credentials of online KACE script
- Check your batch file (the path of installer.exe & its resources)
- Check Collection.xml (image source path)
- Check the installation logs (it might help, some pre-requisites check might fail as remnants in windows registry still present if not fully cleaned)
I think MI runs as system account, hence it will fail as you are attempting to access a network resource. Online script should do the trick.
Create an online KACE script, supply proper credentials, Run a batch file & input "\\share\Installer.exe" -i deploy --offline_mode -q -o "\\share\Configurationfile.xml"
