locked
Windows 7 64Bit, Sysinternals Process Explorer – Run as a service? How? RRS feed

  • Question

  • I would like to run Sysinternals Process Explorer as a service on by 64bit windows 7 workstation.  The old way (XP-Vista) was to use instsrv.exe and srvany.exe from Microsoft 2003 Resource Kit. Is there a “Best Practice” to do this in Windows 7? How do I do this in Windows 7

    Thank you,

     

    Windows 7 64bit Pro/Corp/ent/ or whatever the naming flavor of the week is for not home and not ultimate. 

    4 GB memory

    3 GHz D CPU
    Thanks again.


    You can't fix stupid.
    Monday, December 21, 2009 6:52 PM

All replies

  • I would like to run Sysinternals Process Explorer as a service on by 64bit windows 7 workstation.  The old way (XP-Vista) was to use instsrv.exe and srvany.exe from Microsoft 2003 Resource Kit. Is there a “Best Practice” to do this in Windows 7? How do I do this in Windows 7

    Thank you,

     

    Windows 7 64bit Pro/Corp/ent/ or whatever the naming flavor of the week is for not home and not ultimate. 

    4 GB memory

    3 GHz D CPU
    Thanks again.


    You can't fix stupid.

    hi ,

    take a look at this page , click on the links , plenty of solutions there

    http://technet.microsoft.com/en-us/sysinternals/default.aspx

    oh by the way , the size of your cache file can also speed things up (!)

    have a nice day and happy holidays
    http://www.microsoft.com/security + http://www.microsoft-hohm.com/default.aspx + http://www.getpivot.com/ + http://photosynth.net/ + http://seadragon.com/ + http://windowsteamblog.com/blogs/genuinewindows/default.aspx + http://technet.microsoft.com/en-us/sysinternals/default.aspx
    • Proposed as answer by Dabur972 Monday, December 21, 2009 7:47 PM
    Monday, December 21, 2009 7:47 PM
  • Hi W2K8DT,

    I'd suggest setting up a scheduled task that "Runs with highest privileges", "When I log on", that uses PsExec from Sysinternals to launch Process Explorer as NT AUTHORITY\SYSTEM (which will likely be identical to how you were previously accustomed to it).

    The command-line for the task would be something like:
      c:\path\to\psexec.exe -sid c:\path\to\procexp.exe

    This will have the effect of causing psexec to be launched elevated, which permits it to launch a process as NT AUTHORITY\SYSTEM, all without being prompted for UAC elevation, when you log in.


    Out of curiosity, why do you wish to have Process Explorer constantly running in this fashion?
    • Marked as answer by W2K8DT Tuesday, December 22, 2009 9:33 PM
    • Unmarked as answer by W2K8DT Thursday, May 26, 2016 10:15 PM
    Tuesday, December 22, 2009 11:25 AM
  • Hi W2K8DT,

    I'd suggest setting up a scheduled task that "Runs with highest privileges", "When I log on", that uses PsExec from Sysinternals to launch Process Explorer as NT AUTHORITY\SYSTEM (which will likely be identical to how you were previously accustomed to it).

    The command-line for the task would be something like:
      c:\path\to\psexec.exe -sid c:\path\to\procexp.exe

    This will have the effect of causing psexec to be launched elevated, which permits it to launch a process as NT AUTHORITY\SYSTEM, all without being prompted for UAC elevation, when you log in.


    Out of curiosity, why do you wish to have Process Explorer constantly running in this fashion?

    Great minds think alike.  That is what I ended up doing. 

    Answer to the question why is, we have a separate security group that likes to deploy (radio edit) out to systems without checking with anyone about the effects it may or may not have on the system.  Then we (server admin group) have to fix the (radio edit).  I guess I should be thankful they send it out to the IT staff for dog food testing before feeding it to the customs.  Oh, and when the manage walks by I like to pull up the graphical system information pane.  It makes them happy.  Don’t know what it is about manages and flashing lights and graphics. 

    Thank you for the answer back.

    G


    You can't fix stupid.
    Tuesday, December 22, 2009 9:33 PM
  • Good to hear that it seems you worked something out.

    I guess, my question was more about why you need to have PE running as NT AUTHORITY\SYSTEM, rather than a "regular administrator".  A traditional auto-start configuration (run key, startup group, etc.) would work for that situation.  Are you encountering something you can't do with PE as an admin, that you can do as SYSTEM?
    Wednesday, December 23, 2009 10:54 AM
  • Good to hear that it seems you worked something out.

    I guess, my question was more about why you need to have PE running as NT AUTHORITY\SYSTEM, rather than a "regular administrator".  A traditional auto-start configuration (run key, startup group, etc.) would work for that situation.  Are you encountering something you can't do with PE as an admin, that you can do as SYSTEM?

    Ah, gotcha now.  It works as advertised as a "regular administrator"; at least it has to date.  In 7 Bata and 7 RC I would just fire up PE and other apps and consoles manually when I logged in.  But when I loaded 7 release, this became my main workstation and I wanted my “lazy” startup from XP and Vista.  Basically, set it and forget it startup.   Whenever possible I try to use MS “best practice” I was looking for a KB or PB for user created service in windows 7, but I’m guessing I’m over thinking it. I should have taken my own counsel and (Keep It Simple Stupid).
    thanks again for the answer back.
    G


    You can't fix stupid.
    Monday, December 28, 2009 7:32 PM