Skip to main content

launching .msc files with psexec

ever try to launch a .msc w/ psexec?  it’s a frustrating experience unless you know how.  i found myself in this predicament a number of times but wasn’t interested in figuring out at the time since there were many other easier ways to get around it.

can’t let this one slip away.  i will certainly need this later.  as usual, let’s start with the wrong way.

c:\>psexec -u <domain>\<user> -p <password> dsa.msc

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

PsExec could not start dsa.msc:
%1 is not a valid Win32 application.

 

how about this way?

c:\>psexec -u <domain>\<user> -p <password> mmc.exe dsa.msc

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

PsExec could not start mmc.exe dsa.msc:
The parameter is incorrect.

 

the one above, you may or may not see depending on how your paths are setup.  the real secret is getting the mmc.exe to call dsa.msc.  to prevent any odd path problems from getting in the way, this is the way we should execute it.  by the way, i added –d so that we don’t keep the cmd shell in a holding pattern.

c:\>psexec -d -u <domain>\<user> -p <password> %windir%\system32\mmc.exe dsa.msc

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

mmc.exe started with process ID <1234>

 

if you’re logged in via a RDP connection to a server, make sure you’re not running into problems with the console view.  i blogged about this awhile back in this entry.

Labels:

Comments

  1. Anonymous4/20/09, 3:25 PM

    glad i found your posting on this. Was about to give up. great tip thanks!

    ReplyDelete
  2. Anonymous1/21/10, 8:51 AM

    glad i found your posting on this. Was about to give up. great tip thanks!

    ReplyDelete
  3. Unknown8/11/21, 8:39 PM

    Many thanks for this. 12+ years later this is still a valid and useful tip. Thanks.

    ReplyDelete

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
11 comments
more »

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
3 comments
more »

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
3 comments
more »