After executing a test script (via TestDirector) on a remote PC, WinRunner remains open. If you don't close WinRunner on that remote PC, 1 active license is used up. And if you repeatedly forget to close WinRunner on multiple remote PCs, you'd soon run out of # of licenses (unless you close WinRunner or pay more $ for more licenses). And if those remote PCs are spreaded out across the world, there is absolutely no way you can manually close WinRunner on those remote PCs.
Does anyone know a way to close WinRunner on a remote PC (after an execution of a test script)? via TestDirector? via TSL? via Windows? via Remote Procedure Calls? via any mean? (other than physically be at the remote PC).
I suspect that you could launch WinRunner using the command line, and it would close when done.
To get a better answer, however, you should really be asking product-specific questions in their own forums, further down the QAForums.com site. This "Automated Testing" forum is for general and cross-tool automated testing questions.
In this case, the WinRunner forum could probably get you a good answer quickly.