- I would not rule out the possibility that there might be a Group Policy that you could remotely administer that would control which processes are permitted to run. This would surely involve a bunch of overhead... but I would not rule it out.
- It has been several years since I last looked at this, but I seem to recall that in a networked system, that (A) it is possibly to remotely edit the registry of a system, and (not at all sure on this) that per-process information is available in the registry in a way that I got the impression could be used to kill processes by deleting the appropriate registry keys. I could certainly be wrong on this; this is not something I have ever seriously looked at
- you just might be able to find an activex control to execute an appropriate remote command
- compared to activex, you would probably have a better chance of finding a .NET assembly that could execute an appropriate remote command
... and that is about it. The flexlm protocol does not support management. On unix; systems, lmgrd sends a signal to the appropriate license manager daemon to shut down; I do not know how the communication is done for Windows.
