![]() I could not find any references to this rather critical element of infrastructure in any of the related documents. The impact on supporting tooling (setup update tech), customer support processes, documentation is significant. If our observation is true that setup.exe cannot be used directly for “silent installation” then that’s a rather important point which I would’ve expected to be communicated. There are references to many different kinds of GUIDs. The deployment consists of an installation image (more or less what the OEM installation wizard creates) and a special Collection.xml which contains actions for “Installer.exe”. The process also changed for AutoCAD 2023 and it seems that for silent installation, it is now required to create a deployment and use their new “Installer.exe” to run a “deploy” action which then runs in “silent” mode. We were unable to get it running in “silent” mode. ![]() ![]() In version 2023 the generated setup.exe does not react on any of the known commandline args. Until version 2022 it generated a setup.exe which could be launched in “silent” mode. ![]() I even separated the 3rd party installers and combined them for all Autodesk products so it removes all the duplicates.It seems Autodesk changed the way the generated installer works. AutoCAD2023.1.2Update.exe -q Note: A full list of compatible commands can be shown by using the -help parameter. Silent Install To silent install and Autodesk package, you can add the -q argument to your script/install command. User signs in the first time and they install one at a time. Solution: Note: You may need to consult with your system administrator to perform the below steps. Right now I have mine setup with 5 versions of Revit, 1 version of AutoCAD, 1 version of Navisworks Manage and they are all set to required. I haven't done this with mine yet, but I want to have the parts create a blank file somewhere so it will think it's still installed even if the parts are missing. You set the detection to see if the installed folder exists and set the deployment with each part as a dependency. For Revit, I had it move the parts to Revit_20xx, then extract Revit20xx.7z.001 to c:\autodesk, then delete the Revit_20xx folder, then runs the install command provided by the deployment creation installer, then it finally deletes the install folder. Set the detection to see if the file exists and do not assign the deployment to any groups. Step 3 create bat file to create c:\Autodesk\ and then copy part1.7z.001 to c:\autodesk. ![]() Step 2 add folder to archive and split by 7500MB parts. I opened a ticket with Microsoft and requested to have it escalated. If you want to give the user more visibility into what is going on, you can bundle the custom installer you made in ServiceUI.exe so they can see the progress better.For the custom install your silent install will look like this: custom-installer-name.exe -i install -q.Your install packages will also be smaller for the Intune portion, but you will end up burning more disk space because the custom installer will leave the deployment files cached under C:\Autodesk. Intune temporarily caches files under C:\Windows\IMECache\. The reason for this is that future patches may want the original files from the deployment location which Intune will automatically clean up after the installation finishes. Use the Custom Install in the Autodesk Management Portal to build the installer Link.Here are my recommendations if you're deploying to off-network devices, want to be able to push updates to off-network devices without requiring VPN, or you do not have a deployment share that can be accessed in the context of the device: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |