# Lauch Ignition Using Remote Desktop Services **URL:** \ **Category:** Ignition\ **Created:** [April 18, 2017, 10:26am UTC](https://forum.inductiveautomation.com/t/lauch-ignition-using-remote-desktop-services/14072 "2017-04-18T10:26:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![focusengsk](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@focusengsk](https://forum.inductiveautomation.com/u/focusengsk)\ **Post date:** [April 18, 2017, 10:26am UTC](https://forum.inductiveautomation.com/t/lauch-ignition-using-remote-desktop-services/14072/1 "2017-04-18T10:26:07Z")
Hi All, I am currently working on aproject to introduce ACP ThinManager and ThinClients. The plant runs multiple scada platforms (ignition, WW, Factory Talk etc). Using Windows RDS (remote desk. serv.) and ACP ThinManager I can specifically designate an application to run on a specific client. The client will then only lauch the application with no windows desktop accessible in the background. An application is made available via ServerManager. My problem is, as Ignition isn’t a full application, it is not available to add to the remoteapp list. Has anybody used this method before? Ignition currently running on WinXP clients and Win Server2008. With this project it will move to Win7 and Win Server2012, the idea being to standardise all client PCs to a ACP ThinClient architecture. I know I can make a specific URL available via remoteapp, but I want the application only. Any help much appreciated. ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [April 18, 2017, 10:13pm UTC](https://forum.inductiveautomation.com/t/lauch-ignition-using-remote-desktop-services/14072/2 "2017-04-18T22:13:19Z")
I don’t have any direct experience using ThinManager, but I would suspect that using the Native Client Launcher will probably be your best bet. This should let the system recognize the client as a “full application”. You can configure the native client launcher to launch straight into a specific project as well, and bypass the “pick a gateway” and “pick a project” phases. ---
**Author:** ![focusengsk](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@focusengsk](https://forum.inductiveautomation.com/u/focusengsk)\ **Post date:** [April 19, 2017, 8:10am UTC](https://forum.inductiveautomation.com/t/lauch-ignition-using-remote-desktop-services/14072/3 "2017-04-19T08:10:14Z")
Thanks Carl, I will try this out. Am I correct in saying Native Client Launchers are only available from V7.7? Current system runs V7.3, but part of this project is to upgrade to the latest version anyway. Using ThinManager appears to be the direction a lot of companies are headed. I will let you know how testing goes anyway. ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [April 19, 2017, 3:51pm UTC](https://forum.inductiveautomation.com/t/lauch-ignition-using-remote-desktop-services/14072/4 "2017-04-19T15:51:32Z")
The native client launchers were introduced in Ignition 7.5. > Current system runs V7.3, but part of this project is to upgrade to the latest version anyway. Yes. Please do this. ---
**Author:** ![heybales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/heybales/32/3358_2.png) [@heybales](https://forum.inductiveautomation.com/u/heybales)\ **Post date:** [May 10, 2017, 5:09pm UTC](https://forum.inductiveautomation.com/t/lauch-ignition-using-remote-desktop-services/14072/5 "2017-05-10T17:09:43Z")
@focusengsk could you give an update on your testing? I just had a customer request today for this exact solution. Replacing a SCADA system with older technology, but using thin clients.