I\'m doing some automation via a combination of windows message sending directly to HWNDs and calls to a COM server exposed by the automated application.
If there is
If you control (write code for) both the server and the client you can add a method to your COM interface that would return the process / thread ID or anything of this nature (e.g. server hostname if it is remote) on the server end. I second @Hans - unless you have access to the server implementation you may be out of luck by design.
I believe the kimgr CoGetServerPID function will give you the process-id of your COM server. However, it only works if the process-id is <65k.