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

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

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.   DETECTION status messages take 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 m