Wait for Remote Computer

FinalBuilder Discussion
1

Hi,

I have a problem with Wait For Remote Computer action. While it works on all the computers in my local lan, for some reason it doesn’t work with computers overseas which I have no problem connecting to them otherwise (RDC, net share etc.). The problem is I always reach timeout. Is there any limitation to this Action (not working on different subnet or similar) that I don’t know of?
Can you suggest an alternative way to query whether a proccess is running on a remote computer? I tried to use PSList but I can’t capture its output.
The flow I’m trying to accomplish is stopping a process ‘nicely’ then querying it whether it’s still alive (in try catch) then in case the query fails, I PSKill it.

Thanks,
NirS

2

Some more observations:

PSlist completes and says the proccess is not found (which is good but who can I capture the output)
WMI Proccess info fails with Access Denied.
Wait for Remote Computer fails when reaching timeout.

3

Ok the WMI Proccess Info runs now, I just had to put the domain name in the credentials, which brings me to the conclusion that maybe the Wait for Remote Computer doesn’t work because I cannot change the default login credentials.
Is there a way to do this?

NirS

4

Ok I figured it out, I used the set the CredUser and CredPass properties of the action in script...

I'll stop my monologue now

5

Thanks for pointing this out, though. Those properties (which only work for WMI, not network shares, unfortunately) should have had their own property page. This has been corrected for the next test build.