Psexec doesn't execute vb script remotely

Thanks. Tried. Doesn't work either. The output:

C:\SysinternalsSuite>psexec -accepteula \\remote_computer cscript \\network_share\DHCP.vbs

PsExec v1.85 - Execute processes remotely
Copyright (C) 2001-2007 Mark Russinovich
Sysinternals - www.sysinternals.com


Microsoft (R) Windows Scripting Host Version 5.0 for Windows
Copyright (C) Microsoft Corporation 1996-1997. All rights reserved.

CScript Error: Loading script "\\erminml\instalacija\DHCP.vbs" failed.
cscript exited on remote_computer with error code 3.


C:\SysinternalsSuite>psexec -accepteula -e -c \\remote_computer cscript DHCP.vbs

PsExec v1.85 - Execute processes remotely
Copyright (C) 2001-2007 Mark Russinovich
Sysinternals - www.sysinternals.com


Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

cscript.exe exited on remote_computer with error code 0.

I also noticed that Scripting Host Version is different with these two commands. First one is the version on the remote computer, and the second is version on my local computer.

Any suggestions? Anyone?
This would help me a lot cause I have about 500 NT workstations to change from static IP to dynamic IP (DHCP).

I'm not sure if version 5.0 would make any difference, but if possible, try to upgrade that machine to 5.6.
Also, directly from the target machine (the first one that didn't work), paste this into a Start --> Run box, and see if it works:
cscript \\erminml\instalacija\DHCP.vbs

I would keep playing with that until it works, then transpose that into the PSExec line....test that from a command prompt on your PC, then put it into the script.  Sometimes it can take a bit of fiddling to get a PSExec command to work properly.

Regards,

Rob.

for update your scripting engine
http://www.microsoft.com/technet/community/columns/scripts/sg0903.mspx#EBD
Automating TCP/IP Networking on Clients:
http://www.microsoft.com/technet/scriptcenter/topics/networking/01_atnc_intro.mspx#E6BAC

Gas

Thanks for response.
When I run the: cscript \\erminml\instalacija\DHCP.vbs locally from target machine it works like charm. That means that machine is able to access the network share where the script resides. Also the script works when I copy the .vbs file to remote machine hard drive and then use psexec. But when I use psexec to copy file to remote machine or to execute script from network share, it doesn't work.
I don't get it.

Regards,

Ermin

By the way, the above does *not* copy the DHCP.vbs file to the remote computer, it just uses cscript to call the VBS file on the remote UNC path.

Regards,

Rob.

Hmmm, that's odd.  The PSExec v1.83 that I use works perfectly with the command I posted, with no need for the -c and -f switches, as long as the UNC paths are correct.

And Microsoft now own it.....as they do....buy out the good things!

Regards,

Rob.

Right Rob,
don't touch my Russinovich
I explain better:
sometime psexec has problem with the -c option or UNC path ... because something is miscofigured (user permission/firewall/path not correct etc.)

so a little batch should be help (keep it easy)
if I can copy the file is half of the work (avoid unc problem)
and psexec it as system to have "enough" rights, interactive so I can see something on the target...
is only a workaround   to: "cscript exited on remote_computer with error code 3"

Ciao Gastone