Are you trying to install RSCD agent on a box, do you mean you are trying to do this using BLadelogic ?
If yes, how are you doing it ?
What are the routing rules based on ?
Yes,I am trying to install RSCD agent on a box using Bladelogic.
But this functinality(Agent Installer Job) is available in version 18.104.22.168.
And my routing Rule is like this:
Thanks for your Support.
Untitled.jpg 52.6 K
The PsExec server you have specified does not Psexec on the path
Check that, the rule has failed. see the snapshot you provided.
As shown in your error, you might need to put the PSTools (psexec files) in the correct path on designated server , which you have configured in the agent installer job.
Generally we need to put files in C:\Windows\System32 on psexec server.
sure - i would check the psexec location as jayendra mentioned.
Thank you for your prompt response. I have already copied the PStools files in C:\Windows\System32 folder.
I am using the same application server as Psexec server and target device is part of same domain as app server but still unified agent deployment is getting failed with error :
"No Rule Defined for Servers
------ All remote host authentication routing rules evaluated to false for server 'IP'."
And in authentication rules is getting failed while trying to update. Please suggest.
when you validate the psexec host, do you still get an error ?
While validating remote host authentication from infrastructure management, I am getting below error:
Command: blpsexec -s localhost -c -? on host: mastervm
returned no stderr
Manually psexec is working fine on psexec server
if you look in the rscd log on the helper (maybe on debug logging level) you should see the commands that are being run - you can try and manually nexec those to see if that gives any more information. so psexec.exe is directly in the c:\windows\system32 directory ?
1 of 1 people found this helpful
Ran into the same issue yesterday.
i found that the switches run while validating the remote host authentication are not present in the latest psexec 2.2.
downloaded the 2.11 psexec and we are golden.
check you version of psexec
bsa was qualified w/ 2.11, 2.2 came out after our QA and has not been qualified yet.
Would have been great to document that importance sub details inside BSA documentation... about Version dependency.
I just lost, 2-3 H, diging, why it was not working...
Have you ask your own team to improve documentation ?
Special Thanks to DC Kidson