Fusion 360 Admin Installer

[ajuelich]

Hello,

I have the Fusion 360 Admin Installer and the Documentation on how to install and update going forward.  The issue is you have an 'install' command and an 'update' command.  If a certain version is installed, then the 'install' command will fail, requiring the 'update' command.  This can just be a pain to manage when there are so many different versions of the Application.

Is it possible to get an MSI for each version?  Or allow for an '--install --update' which will install if it doesn't exist, and if it does exist, update it if necessary.

Thanks!

[Mark.Lancaster]

@ajuelich

As far as I know Fusion 360 automatically updates when you launch the product and there's a update for it.  Don't worry about the machines that already have Fusion 360 on it.

[ajuelich]

Hello,

This is for the Admin Install which becomes Machine-Based.  I know, for a fact, that it does not auto-update.  Each time there is an Update I get can email from Autodesk stating that we have to run the '--update' switch to update existing installs.

Thanks!

[Mark.Lancaster]

@ajuelich

Sorry wasn't thinking about the the Admin installer..  My bad.. 

I found an article and also the guide, where it states to enter this command.  Not sure it that still works or not

"Fusion 360 Admin Install.exe" --process update

 But I see where people have complained about since 2016.  

You may want to post over in the Fusion 360 Forum..  You will get better traction there since you can interact with the Fusion 360 team.

[ajuelich]

No problem.  Thanks!  I'll post in the open Fusion 360 forum to see if I can get some traction.

Thanks for your time!

[Anonymous]

Hey Adam,

Yeah I created a PS script that added a scheduled task on the machines that I deploy Fusion on so that it auto updates (Admin Install.exe --process update), as we had students using Fusion 360 at home that would auto-updates to the latest version, then come into school, and it still be an old version.

Is that what you came to as a solution?

[ajuelich]

When you do that '--update' switch, doesn't the installer in that folder have to update as well?  Or does running that command just go to the Internet and update?

I was thinking I'd have to just create a new package/application each time and ensure that it is already installed on the machine, otherwise the '--update' would fail.

[Anonymous · Accepted solution]

Nope, goes to the internet. I point my update of the scheduled task to the original admin install.exe on my sccm/apps share. It was easier since all machines have read capability from that share and didn't have to copy the admin install.exe to the local drive. Works like a charm over here. The scheduled task runs once a week.

[ajuelich]

Hmmmm, interesting.  I could also do a Package with a re-occurring schedule.

Good to know, though.  Thank you sir!

[thomaswhilbert]

Interesting, I couldn't get the update to work from Kace without downloading the latest admin installer.

[ajuelich]

Ya, same here.  I'm using ConfigMgr but what I did is:

1. Have an older version of Fusion 360 that runs the install switch.  The detection method for that is just that the folder path exists.
2. I then have another application that contains the updated exe and depends on the first application.  It's detection method is based on the GUID in the folder and the version.

With each new update I modify the last Application and keep the Dependencies.  If a machine doesn't have it, it'll run that old installer, and then the latest update.

Not ideal......I hope they improve the behavior soon.