Use a .CMD file to launch the exe, have the first line look for a .TXT (or other created file name) file called FILENAME10.HLD Next line have it create a text file...
Have text files created in a manner that each launch creates a new text file, when it gets to 10 have the CMD file abort launching the .EXE Dave From: Vue, Za [mailto:z...@emory.edu] Sent: Friday, July 10, 2009 11:35 AM To: NT System Admin Issues Subject: File Lock Down Server: W23K Other than a 3rd party software, is there a way to lock down a shared .exe to say like 10 connections on Windows 2003? When 10 connections reached the application does not run. Example I have 20 machines running an applications off the network but I only have concurrent 10 licenses. Thank you, Z.V. ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments). ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
