Announcements

Announcement: We’re aware of an issue affecting starting a new topic from category pages and creating new blog posts. New topics can still be started directly from the relevant board. Learn more here.

Silently "Deploying" a Standard Local Install (instead of a deployment)?

Silently "Deploying" a Standard Local Install (instead of a deployment)?

mbradfordY878N
Explorer Explorer
1,485 Views
3 Replies
Message 1 of 4

Silently "Deploying" a Standard Local Install (instead of a deployment)?

mbradfordY878N
Explorer
Explorer

Might be a tricky question, but for some circumstances (long distance/VPN installs...) it's much more reliable and quicker to install locally. I've done so with PDQ Deploy by copying the AutoCAD.exe installer to user PC and running from there with command line. I.e., not a deployment, but a standard install.

 

This displays for the current logged user as "Creates the installer..." and after some time moves to "Preparing to Install..." where it then waits for the user to click Install. Can I get prevent this 'Install' prompt?


I've tried variations of arguments of "...\AutoCAD.exe" /silent or /q or /qb with no luck that I can tell. Any suggestions on how to go this route? For certain scenarios this is working so much better than a deployment.

0 Likes
1,486 Views
3 Replies
Replies (3)
Message 2 of 4

Simon_Weel
Mentor
Mentor

Not sure I get this. You don't want to create a deployment on your Autodesk Account page, but instead created a deployment with PDQ Deploy? And what's the 'autocad.exe' installer?

0 Likes
Message 3 of 4

mbradfordY878N
Explorer
Explorer

Yeah there was no good way I could explain this (or I did a horrible job)
When creating a custom package, you have these two options, that functionally work differently.

mbradfordY878N_0-1696510644480.pngmbradfordY878N_0-1696510644480.png

Install will give you a small single .exe that simply needs to be ran on the PC needing AutoCAD

Deploy will make a Deployment that contains all files and lives in a single place (typically on a shared network)

 

I was looking to use the single .exe to install instead for a unique scenario. I ended up figuring it out: 
The arguments in this case aren't /q, /l, etc., they are "-q" "-l".

 

"AutoCADInstaller.exe -h" will tell you anything you want to know, and using this command line one can silently "deploy" a standalone installer.

 

Of course if anyone wants to tell me I'm wrong or a better way I'm all ears 👂

Message 4 of 4

henkstubbe
Contributor
Contributor

I deploy a few packages first. First is the odis-installer, which is sometimes crap, but I think I have finally stopped it from auto-updating. Then I install the identity manager crap. Then the licensing component.

"%ProgramFiles64Dir%\Autodesk\AdODIS\V1\Installer.exe" --install_mode install --ui_mode basic --offline_mode --manifest "%ScriptPath%\files\setup.xml" --install_source "%ScriptPath%\files\"


This is then the command that I run with our deployment software. No deployment is made in the management environment.

0 Likes