# ThinManager AppLink Path - Client Auto Launch **URL:** \ **Category:** Ignition\ **Created:** [May 26, 2020, 4:14pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047 "2020-05-26T16:14:52Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![DSI600](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@DSI600](https://forum.inductiveautomation.com/u/DSI600)\ **Post date:** [May 26, 2020, 4:14pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/1 "2020-05-26T16:14:52Z")
We are using ThinManager and can’t get the correct AppLink path for individual clients to auto startup the client. I have Vision Client Launcher installed on the RDS server that has ThinManger. Each client will also open different projects depending on where they are in the plant. Right now I think I would use: “C:\Program Files\Inductive Automation\Vision Client Launcher\visionclientlauncher.exe” I would assume that I would need to pass parameters to it like it does from creating a shortcut on the desktop? This is what I am currently trying: “C:\Program Files\Inductive Automation\Vision Client Launcher\visionclientlauncher.exe” -Dapplication=App1%20Test Anyone use ThinManger with the Vision Client Launcher before? ---
**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\ **Post date:** [May 26, 2020, 4:28pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/2 "2020-05-26T16:28:40Z")
I don’t have experience with ThinManager, but the syntax you’re using for launching from the command line is slightly incorrect - you don’t need to have the `-D` before the parameter. Also be sure that the project has been added to the launcher as an application before launching from the command line. Manual reference: [https://docs.inductiveautomation.com/display/DOC80/Vision+Client+Launcher#VisionClientLauncher-CommandLine/Terminal](https://docs.inductiveautomation.com/display/DOC80/Vision+Client+Launcher#VisionClientLauncher-CommandLine/Terminal) ---
**Author:** ![DSI600](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@DSI600](https://forum.inductiveautomation.com/u/DSI600)\ **Post date:** [May 26, 2020, 4:40pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/3 "2020-05-26T16:40:13Z")
Thanks that worked. “C:\Program Files\Inductive Automation\Vision Client Launcher\visionclientlauncher.exe” application=App1%20Test ---
**Author:** ![mblystone](https://avatars.discourse-cdn.com/v4/letter/m/9de053/32.png) [@mblystone](https://forum.inductiveautomation.com/u/mblystone)\ **Post date:** [April 9, 2021, 2:33pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/5 "2021-04-09T14:33:52Z")
I wouldn’t call this solved. I have tried this exact method to try and launch a Vision Client and it does not work. I’ve added the application to launcher. Tried the path with and without “-D”. Copied the exact path from the application properties. Tried using a batch file. No matter what I try I either get a windows error or Client Launcher error. The Client Launcher error states that “Specified Vision Client does not exist”. I’m aware it’s as much a Thinmanager problem as it is an Ignition problem, but this shouldn’t be classified as “Solved” ---
**Author:** ![DSI600](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@DSI600](https://forum.inductiveautomation.com/u/DSI600)\ **Post date:** [April 9, 2021, 3:22pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/6 "2021-04-09T15:22:29Z")
Its a two step process. You have to set up app link and run client laucher to add the app first for each user. 1 - “C:\Program Files\Inductive Automation\Vision Client Launcher\visionclientlauncher.exe” Run that first for each Thin Client and set the app. 2 - “C:\Program Files\Inductive Automation\Vision Client Launcher\visionclientlauncher.exe” application=xxxxxx%20xxxxxx Then set App Link to #2 after #1 is completed. ---
**Author:** ![mblystone](https://avatars.discourse-cdn.com/v4/letter/m/9de053/32.png) [@mblystone](https://forum.inductiveautomation.com/u/mblystone)\ **Post date:** [June 30, 2021, 8:27pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/7 "2021-06-30T20:27:11Z")
Yep, still doesn’t work. This still shouldn’t be “Solved”. ---
**Author:** ![elliot.lohr](https://avatars.discourse-cdn.com/v4/letter/e/3bc359/32.png) [@elliot.lohr](https://forum.inductiveautomation.com/u/elliot.lohr)\ **Post date:** [March 31, 2022, 1:04pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/8 "2022-03-31T13:04:51Z")
Hello, having a similar issue. I seem to have no problem running the Vision Client Launcher from a Thin Client, but when I specify the application I want it to run I get this issue: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/e/9e4a0f31ca3b1ea5f19dd8e392d8c6107dbefbfe.png) I have verified that when ran from the command line that there are no syntax errors, the application runs fine, but when launched from a thin client this comes up. Anyone ran into this before? ---
**Author:** ![simon.thibeault](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@simon.thibeault](https://forum.inductiveautomation.com/u/simon.thibeault)\ **Post date:** [January 10, 2026, 5:33pm UTC](https://forum.inductiveautomation.com/t/thinmanager-applink-path-client-auto-launch/35047/9 "2026-01-10T17:33:42Z")
we tried the same command line (application) but received an access is denied message: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/0/a0e47d234fa941c75c1fc7e223167307e328b389.png) It does work fine when we launch manually.