Try this, remove $. Not sure why is it being used?
Vendor=`nexec -i 18.104.22.168 cmd /c "echo . | powershell D:\\bltest\\test.ps1"`
Tired command given by you but it gave following error
Info Oct 3, 2016 3:36:37 AM nexec: No host to execute the command on
You most likely have a syntax issue...The correct syntax would be:
nexec -i 22.214.171.124 cmd /c "echo. | powershell D:\\bltest\\test.ps1
Have you done the basic tests like whether the agent is up or not and similar one?
why would any of the errors above mean that the host is not up ?
Error is received that "Nexec : Error accessing <host> Remote host is unknown" -> name resolution error
Info Oct 3, 2016 3:36:37 AM nexec: No host to execute the command on -> incorrect command syntax
BSSXXXXXCS02% nexec PCXXXXXINF01 wmic datafile where name="c:\\windows\\system32\\drivers\\srv.sys" get Version /value
nexec: Error accessing host PCXXXXXINF01: Remote host is unknown
//PCXXXXXINF01/: Remote host is unknown
any clue on this error? i can live browse the server from console...
Is the server registered in console with same name PCXXXXXINF01?
Are you able to ping/telnet to host PCXXXXXINF01, check if dns resolution works nslookup PCXXXXXINF01
any clue on this error?
Remote host is unknown -> means whatever is trying to talk to the agent can't resolve the name.
i can live browse the server from console...
the console connects to the appserver. so the appserver resolves the target. when you are using nexec, then your client system is resolving the target, unless you are going through a nsh proxy. can your client system resolve the target ?