topic Re: Fuscion 360 Update - Detection Method in Fusion Design, Validate & Document Forum

Fuscion 360 Update - Detection Method

Anonymous — Wed, 14 Dec 2016 14:14:42 GMT

Hello,

I need to deploy the new version of Fusion 360 using the Admin Install. In order to successfully deploy this using the Application Method in SCCM I need to point to a change to 'detect' that it was installed. I can't seem to find a file or registry setting that confirms the newer update to confirm that it is installed.

Any ideas?

Thanks!

Re: Fuscion 360 Update - Detection Method

innovatenate — Wed, 14 Dec 2016 18:22:59 GMT

I just sent you a PM with a suggestion that may help.

Let me know if you have any questions or concerns.

Thanks,

Re: Fuscion 360 Update - Detection Method

mikeh361 — Tue, 20 Dec 2016 01:40:08 GMT

I would be interested in the solution as well as I have to also install this in a couple of labs.

Re: Fuscion 360 Update - Detection Method

innovatenate — Tue, 20 Dec 2016 01:54:05 GMT

Sent you a PM too.

Thanks,

Re: Fuscion 360 Update - Detection Method

dp250f — Thu, 13 Apr 2017 15:24:51 GMT

Another Configuration Manager Admin here - same question.

Thanks.

Re: Fuscion 360 Update - Detection Method

innovatenate — Thu, 13 Apr 2017 16:07:20 GMT

See section 4 of the advanced lab installation manual shows how you can detect the currently installed version.

Step 4 of the Fusion Lab Download mentions a batch file that can be used to update Fusion. This is the easiest method I'm aware of to update a Lab install of Fusion, currently.

I hope that helps.

Thanks,

Re: Fuscion 360 Update - Detection Method

dp250f — Thu, 13 Apr 2017 16:33:58 GMT

I had already read that. Valid detection methods for Configuration Manager Application model are File System, Registry, Windows Installer, and script. The Admin Install does not put an entry in the Programs and Features list, FusionLauncher.exe does not contain relevant version information, and Fusion 360 also doesn't seem to put anything I can use for detection in the registry. That's why I posted here. I was hoping there was an official solution which would be easy to use in Configuration Manager but it seems like a "roll your own detection script" situation.

Re: Fuscion 360 Update - Detection Method

Anonymous — Tue, 05 Feb 2019 15:56:59 GMT

@Anonymous

I'm working on the same (2-3 years later). Doesn't look like Autodesk has chosen to make it easy.

The folder that gets tossed into C:\Program Files\Autodesk\webdeploy\production\6a0c9611291d45bb9226980209917c3d (I'm guessing that last folder is randomly generated with each version so it could change depending on when you deploy your installer) isn't reliable.

I'd say use the shortcut in the Start Menu as there is no registry entries. Or if you choose to use that .exe in the Program Files folder you'd have to make a detection script to search for 'FusionLauncher.exe' with logic to recursively go through C:\Program Files\Autodesk\WebDeploy due to what appears to be a randomly generated folder name.

Good luck! Sorry to post on an old thread. Hope it helps others in the future or Fusion devs decide to add that in future installations scripts.

Re: Fuscion 360 Update - Detection Method

harrydresden — Mon, 12 Oct 2020 16:53:28 GMT

I check for the existence of this registry key:

HKEY_CLASSES_ROOT\.f3d

basically "does the system know about the .f3d file extension?"

Re: Fuscion 360 Update - Detection Method

licence_ti — Fri, 24 Sep 2021 01:48:54 GMT

We're having the same problem and I thought looking for the .f3d key was clever but it doesn't seem to want to work for some reason. I attached the screenshot of the Detection Rule window with my reply. If anyone can help, it would be much appreciated. Thanks!

Re: Fuscion 360 Update - Detection Method

rcgalyenKZB9L — Fri, 05 Nov 2021 18:19:38 GMT

1. Why do people send PMs to a thread where multiple people are asking for help? Why would you share a community answer with...oh, IDK...THE COMMUNITY. Whatever... bygones.

2. Anyone have any new ideas regarding ?

Re: Fuscion 360 Update - Detection Method

mikeh361 — Fri, 05 Nov 2021 19:29:41 GMT

We use the json detection method... this is my vbscript detection for ConfigMgr. I should really update it to PowerShell but meh....

Const ForReading = 1 filename = "C:\sccm_cmdline_scripts\Fusion360\fusioninfo.json" strVersion = "2.0.11405" strSearchString = "" set fso = CreateObject("Scripting.FileSystemObject") if (fso.FileExists(filename)) Then set f = fso.OpenTextFile(filename, ForReading) Do Until f.AtEndOfStream strSearchString = f.ReadLine If Instr(1, strSearchString, "build-version") Then exit do End If Loop f.Close If Instr(1, strSearchString, strVersion) <> 0 Then wscript.echo "Success" End If end if 'wscript.echo strSearchString

EDIT: After the install if you run the following again it'll create the .json file:

"Fusion 360 Admin Install.exe" --quiet --process query --infofile C:\sccm_cmdline_scripts\Fusion360\fusioninfo.json

Re: Fuscion 360 Update - Detection Method

gerardsweeney — Tue, 14 Jun 2022 12:56:45 GMT

6 years later, and we're still faced with this garbage.
Honestly - how difficult would it be to put an entry in Programs & Features?
Or even a version key somewhere?
Or are they worried those few Kb of code would inflate the 1Gb installer?

Nonsense like this really does nothing to dent my low expectations of AutoDesk products.