2

How do I prevent user from opening multiple instances of an executable on the server (Windows 2008 R2). For example we have users opening a program installed on the server from their PC's (Windows 7 Enterprise); in many cases they open the executable go to a different location and open the executable again on another PC. This creates multiple instances which causes more then one license to be used by that user.

** I was just told the problem has been solved. One of the Process Engineers created a program that identified all running instances and can close an instance out on command. This is still a manual way to fix the problem however but I don't make those decisions. Thank you to all that have contributed.

RCawdor
  • 21

2 Answers2

2

Run tsconfig.msc and set "Restrict each user to a single session" to Yes.

Greg Askew
  • 39,132
1

I would replace the shortcut to the program with a shortcut to a launcher script. The launcher script would check to see if the process has been launched by the user launching the script. If yes, then give the user the option to kill the process, or just show a message that the user cannot launch again.

I'm looking for ways to script switching moving the running program to the current session, but I haven't found luck down that route yet. The best I can come up with is using an option message to ask the user if they want to switch to the session with the program running, and if yes, use tscon <session id> /v to switch the user to that session.

Related: Connecting to specific session using remote desktop

Community
  • 1
austinian
  • 1,729
  • 2
  • 15
  • 30