I have done this in the past by using a batch file to start the executable. It first uses tasklist to check the running processes and if it finds the exe in question it exits with a message that the app is already running and the user name of the owner. If the app isn't running it starts the exe normally.
It's a bit of a kludge, but it does work and is simple to implement. On Tue, Jun 1, 2010 at 11:10 AM, Craig Gauss <gau...@rhahealthcare.org>wrote: > We have one application that is absolute resource hog. Unfortunately the > users will open it over and over again, usually bringing the system to a > crawl. It has been very difficult to train them to only open it once. > Anyone have any ideas on how we could limit the amount of times it is > opened? > > > Craig Gauss, Technical Supervisor/Security Officer > Riverview Hospital Association > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
