+1 for batch file creating .lock file. I added a little more logic and would have it call a KiXstart script so they'd get a nice little message as well as a couple other features.
Dave From: Craig Gauss [mailto:[email protected]] Sent: Tuesday, June 01, 2010 8:52 AM To: NT System Admin Issues Subject: RE: Limit the amount of times an application can be opened? Thanks for all the ideas! I think I am going to look into the batch file route. Craig Gauss, Technical Supervisor/Security Officer Riverview Hospital Association ________________________________ From: John Aldrich [mailto:[email protected]] Sent: Tuesday, June 01, 2010 10:24 AM To: NT System Admin Issues Subject: RE: Limit the amount of times an application can be opened? Use a batchfile to create a ".lock" file and check for the existence of that file and if it exists, have the batch file exit. [cid:[email protected]][cid:[email protected]] From: Craig Gauss [mailto:[email protected]] Sent: Tuesday, June 01, 2010 11:10 AM To: NT System Admin Issues Subject: Limit the amount of times an application can be opened? 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/> ~
<<inline: image001.jpg>>
<<inline: image002.jpg>>
