Skip to main content

executing batch files remotely with psexec …

if you’ve got a batch file of some sort (bat or cmd) sitting out somewhere that you want to execute remotely, you’ll want to make sure you’re following the right syntax to get this to work.

here are some examples that DO NOT work:

psexec \\myDesktop \\myServer\myShare\test.cmd

 

PsExec could not start \\myServer\myShare\test.cmd on myDesktop:
Access is denied.

 

by default, psexec runs the context in localsystem.  since the system most likely doesn’t have access to the share, let’s give psexec some credentials which has access to the share:

psexec \\myDesktop -u myUser -p myPassword \\myServer\myShare\test.cmd

 

PsExec could not start \\myServer\myShare\test.cmd on myDesktop:
Access is denied.

 

ah, this isn’t going to work either, but we’re getting closer.  the access denied message throws me off a little since i know the password is right.  it seems the problem is that psexec will not execute the .cmd or .bat file without knowing the context in which to execute… so we give it one.  cmd.exe.

psexec \\myDesktop -u myUser -p myPassword cmd /c \\myServer\myShare\test.cmd

 

C:\WINDOWS\system32>mkdir c:\testme
cmd exited on myDesktop with error code 0.

 

now there we go… :)

Comments

  1. I (re)discovered the joys of psexec the other day - I had to configure plink (from putty) to run as a service account and you can't edit the service registry as a normal user. PsExec's '-s -i' options allow you to run a normal program as the service user interactively :-)

    ReplyDelete
  2. I really needed this information; thanks for posting.

    ReplyDelete
  3. Is it true always, (as a matter of extending teh full requirements for psexec to work) that the default admin share c$ must be in place on the remote server for psexec?

    ReplyDelete
  4. i believe it's required that the admin$ be available since psexec does an installation of a service and most likely requires access to land files. i haven't tested it outside of those parameters though.

    ReplyDelete
  5. nice work...

    ReplyDelete
  6. How do I run the psexec with bat file along with parameter
    Something like :
    Call psexec \\%sv% -accepteula -d -s C:\windows\temp\Web\WebSCCM.cmd %sv% > \\%sv%\admin$\temp\web\log.txt

    ReplyDelete
    Replies
    1. i love waking up to a challenge but need more to go on.

      can you clarify what this is supposed to do?

      from what i can see, it runs a .cmd file that sits on the remote server. the file appears local to the server.

      also, what is the behavior you're getting?

      Delete
  7. C:\>psexec \\10.155.28.152 -u testadmin -p testadmin cmd /c \\10.155.28.152\Setup\test.bat

    testadmin has got admin rights.

    I am executing the above command and I am still getting
    Couldn't access 10.155.28.152:
    Access is denied.


    Kindly help me

    ReplyDelete
    Replies
    1. either you're passing the wrong credentials, wrong domain context, or the path you supplied is inaccessible. just a guess.

      Delete
    2. Thanks for your reply ..
      But,I am able to ping to 10.155.28.152 and even able to map the share folder to a network drive ..

      Delete
    3. This comment has been removed by the author.

      Delete

Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …