topic Re: Microsoft Terminalserver in Fusion Support Forum

Microsoft Terminalserver

Anonymous — Sat, 16 Dec 2017 15:44:37 GMT

It's possible to instsall Fusion 360 on a terminalserver?

Re: Microsoft Terminalserver

innovatenate — Sat, 16 Dec 2017 18:00:33 GMT

I haven't hear of anyone using on terminal server. Is there any reason not to run in the native OS? My understanding is that standard Windows-based applications do not need modification to run on the Terminal Server. I would think that Fusion 360 would run, but I'm not totally sure. I have run Fusion 360 in a virtual environment. Graphics performance could be an issue.

There is a lab install version of Fusion (it must be manually updated to run normally and updates are fairly often), but if you run into an issue it may be worth trying the lab install version. See link below for more.

https://knowledge.autodesk.com/support/fusion-360/learn-explore/caas/sfdcarticles/sfdcarticles/How-to-install-Fusion-360-in-a-Lab-environment.html

I hope that helps!

Re: Microsoft Terminalserver

Anonymous — Sat, 16 Dec 2017 18:54:02 GMT

Hello Nathan,

in our school we don't have enough clients with native OS.

i will try the installation.

Stefan

Re: Microsoft Terminalserver

Anonymous — Sat, 16 Dec 2017 19:41:34 GMT

we have four terminalserver.

i'm started teh installprocess at the same time.

two of this stops at 82%

th works fine

installationpath: "C:\Program Files\Autodesk\webdeploy\production\6a0c9611291d45bb9226980209917c3d\FusionLauncher.exe"

start as administrator works!

when i connect to TS as an "teacher" (no admin rights)

"Protein engine server stops working"

i can't start

eventvwr (sorry german server):

Name der fehlerhaften Anwendung: adexmtsv.exe, Version: 2017.8.2.0, Zeitstempel: 0x59ad6d57
Name des fehlerhaften Moduls: ucrtbase.DLL, Version: 10.0.10137.0, Zeitstempel: 0x556ec8de
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000000000005e9ee
ID des fehlerhaften Prozesses: 0x3274
Startzeit der fehlerhaften Anwendung: 0x01d376a53af5ee0c
Pfad der fehlerhaften Anwendung: C:\Program Files\Autodesk\webdeploy\production\2fc56ab2b960a23a37c37a3688c13a7f7fa1ecc7\adexmtsv.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Autodesk\webdeploy\production\2fc56ab2b960a23a37c37a3688c13a7f7fa1ecc7\ucrtbase.DLL
Berichtskennung: 78b43c1c-e298-11e7-8673-005056b66191
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

i hop u can help!

Regards Stefan

Re: Microsoft Terminalserver

innovatenate — Sat, 16 Dec 2017 21:55:52 GMT

The below link highlights all of the directories for Fusion 360. Does the teacher's user account and/or group policy allow for access to all of those directories?

I hope that helps.

Re: Microsoft Terminalserver

CB63 — Sun, 17 Dec 2017 00:06:18 GMT

Hi Stefan,

You might try putting the Terminal Server in installation mode using the command change user /install and then install the application. If the application runs for an Administrator or Admin equivalent then it might be that the proper registry keys are not getting migrated to the regular user sessions. After the installation is complete issue the command change user /execute.

Regards,

Chris

Re: Microsoft Terminalserver

Anonymous — Fri, 22 Dec 2017 15:03:44 GMT

same error as before.

i gave domain-user full access to C:\Program Files\Autodesk\webdeploy\

Re: Microsoft Terminalserver

Anonymous — Fri, 22 Dec 2017 15:04:49 GMT

need i to clean uo the installation before?

i try a update with change user /install but this don't fix anything.

Re: Microsoft Terminalserver

CB63 — Fri, 22 Dec 2017 17:04:13 GMT

Hi Stefan,

It might be that Fusion 360 is not a true multi user aware application to run in Terminal Server environment. I spent the better part of 16+ years working with MS Terminal Server and Citrix WinFrame / XenApp.

An alternate method of running Fusion 360 remotely is to load it on a user workstation and then use the Remote Desktop Protocol (RDP) client from the Terminal Server to that workstation hosting Fusion 360. I found this to be a work around for users that ran their own "specialized" applications remotely. They would connect to the Terminal Server and then from there they would hop via RDP to their workstations.

Good luck,

Chris

Re: Microsoft Terminalserver

Anonymous — Fri, 22 Dec 2017 21:06:41 GMT

Hi Chris,

thanks for your answer. We have more thinclients then fatclients.

In next year i will try to install in a room with fatclients.

bye

Stefan