# Solution to prevent multiple Vision instances from running on one machine **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [October 18, 2023, 1:04pm UTC](https://forum.inductiveautomation.com/t/solution-to-prevent-multiple-vision-instances-from-running-on-one-machine/80640 "2023-10-18T13:04:47Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Bushmatic](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bushmatic/32/87014_2.png) [@Bushmatic](https://forum.inductiveautomation.com/u/Bushmatic)\ **Post date:** [November 8, 2023, 3:58pm UTC](https://forum.inductiveautomation.com/t/solution-to-prevent-multiple-vision-instances-from-running-on-one-machine/80640/8 "2023-11-08T15:58:16Z")
Unfortunately I was not around to check the active sessions at the time. The script shouldn't care if a session exists on another computer, as it uses these 3 things to check for existing sessions: 1. Username (common for all shop floor machines -- this is set up with autologin) 2. Project name (common for all shop floor machines) 3. PC name (unique for each shop floor PC) In this way, it is meant to prevent multiple sessions on any given PC. I did find this post from 2010 which mentions ghost sessions being a real thing in Ignition: > [@Terminate session](https://forum.inductiveautomation.com/t/terminate-session/2188/2): > > What version of Ignition do you have? The Terminate Session button will terminate the session in the Gateway, however if the client session is still open it will create a new one. The button is only for ghost sessions where there is no client open. It seems like this is what happened? Maybe there's a function I can incorporate that will attempt to kill a session without me needing to go into the gateway manually? --- _[View the full topic](https://forum.inductiveautomation.com/t/solution-to-prevent-multiple-vision-instances-from-running-on-one-machine/80640)._