Hi all expert here,

I meet a problem coding a ASP code to call a psexec here.
My code as below.

<%
Set oS = Server.CreateObject("WSCRIPT.SHELL")
output = oS.exec("cmd.exe /c psexec -s \\dngew -i C:\RefComm.bat").stdout.readall
response.write output
response.write "<br> finish!"
%>

That is not working when I test with open using the this ASP page.
But if i just type purely the code as :

psexec -s \\dngew -i C:\RefComm.bat

in my DOS(cmd), it work properly.
That is no problem with my ASP code too, because if my code as

<%
Set oS = Server.CreateObject("WSCRIPT.SHELL")
output = oS.exec("cmd.exe /c ipconfig").stdout.readall
response.write output
response.write "<br> finish!"
%>

it working perfectly and return the result at the page.
Any idea with this? Even my senior also no idea about this.

ASP code runs on a server so if you are expecting that code to run something on your desktop you'll be out of luck.

Are you running it on localhost?

Are the SysInternals tools (including psexec) installed on the target machine?

My situation is:

When a user browse this page and update something, the server will do something remotely into other PC machine.

The code should run at server, so server will remote(using psexec) to other PC to call a batch file.

Server already have psexec, and the batch file. Those PC (\\dngew) will remote by server also include psexec and batch file too.

Any idea?
Thanks!!~

Have you looked at the Sysinternal Forum

Personally I've never used PSTools, ran Dameware when I was a system admin.

Does the user IIS is running under have permission to do all of this?

I think either is IIS or Psexec problem.
I did given full access for those psexec and batch file. but that is not working too.