I do appreciate the Batch file answer that uses a FOR command.
Here is another method, presented here simply as an additional option. The approach is rather different than the other answer that is provided.
First, see if you can find the MS Communicator processes with WMIC. e.g.:
WMIC PROCESS LIST FULL
Or, to show information horizontally in a table instead of vertically in Property=Value format, do:
WMIC PROCESS LIST FULL /FORMAT:TABLE
or perhaps, to limit that down:
WMIC PROCESS GET NAME /FORMAT:TABLE
(and ignore the first line)
This doesn't seem to show Window title, but may show lots of other bits of information that may be used to uniquely identify Communicator instances, like Executable names.
Then, you can start getting more aggressive, narrowing down your findings. The following looks for instances that end with "name.exe" (e.g., "filename.exe", "myname.exe")
WMIC PROCESS WHERE "Description like '%%name.exe'" LIST FULL /FORMAT:TABLE
All that was just research to fine-tune your command. (After all, you don't really want to start terminating the wrong processes.)
Finally, once all your research is done, so you know you can list just the stuff you want to terminate, then start killing.
WMIC PROCESS WHERE "Description like '%%name.exe'" DELETE
The really nice part about this method is you quickly find ways to be able to gather lots of information that can be used for automation.
1'*' Can't work in the beginning of the filtered text – Ofiris – 2012-12-10T17:18:44.567