Ressourcen für IT-Professionals > Forenhomepage > Configuration Manager Admin Console > How to end processes on a client from the admin console.
Stellen Sie eine FrageStellen Sie eine Frage
 

BeantwortetHow to end processes on a client from the admin console.

  • Dienstag, 30. Juni 2009 20:58Reena111 TeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     
    Hello,

    Is it possible to start the performance monitor on a client and actually control the processes like you would using task manager?
    I am trying to do this from the admin console. I need to give one of our techs the ability to view and kill the processes.

    Thanks!

Antworten

  • Mittwoch, 1. Juli 2009 14:55Sherry KissingerMVPTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     Beantwortet
    No, it's all about user context.  using psexec, right-click tools, RogerZander's tools--the account running the action needs to have the rights to perform that action.

    So your idea about a script would work... but the tech would need to have interactive login rights (to the console session, because that's a server) in order to see content in Run Advertised Programs.  Do they have that already, but not the rights to kill a process?  If so, sure.

    They wouldn't be able to remotely trigger the Advertisement from Zander's Client Center for example, because they'd need admin rights to get to WMI to do that action, too.  If they had that, they'd have rights to kill the process.

    Maybe though... we're helping you to treat the symptoms and not the disease.  What process is going bonkers that you need to have a human kill it interactively?
    Standardize. Simplify. Automate.
    • Als Antwort markiertReena111 Mittwoch, 1. Juli 2009 15:00
    •  

Alle Antworten

  • Dienstag, 30. Juni 2009 22:34Jason SandysMVPTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     
    How about using tasklist and taskkill from the command line? Or PsList and PsKill from sysinternals/Microsoft?

    Roger Zander's Client Center also has this ability as does process explorer I think (also from sysinternals/Microsoft).
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
  • Dienstag, 30. Juni 2009 22:53Sherry KissingerMVPTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     
    I 2nd Roger Zander's Client Center.  The tech will find tons more uses for per-client troubleshooting with that gem!
    Standardize. Simplify. Automate.
  • Mittwoch, 1. Juli 2009 14:26Reena111 TeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     

    Hi! Thanks for the suggestions. I just downloaded the Roger Zander's Client Center - very cool.

    All of the tools suggested require the person running them to have admin rights on the computer being connected to... is there a way I can give someone the ability to kill a process on a remote server without giving that person admin rights on the actual server? If not, I will create a script to kill the process and make it an advertised program to be run with admin rights for this tech to use.

    Any more suggestions?

    Thanks!

  • Mittwoch, 1. Juli 2009 14:55Sherry KissingerMVPTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     Beantwortet
    No, it's all about user context.  using psexec, right-click tools, RogerZander's tools--the account running the action needs to have the rights to perform that action.

    So your idea about a script would work... but the tech would need to have interactive login rights (to the console session, because that's a server) in order to see content in Run Advertised Programs.  Do they have that already, but not the rights to kill a process?  If so, sure.

    They wouldn't be able to remotely trigger the Advertisement from Zander's Client Center for example, because they'd need admin rights to get to WMI to do that action, too.  If they had that, they'd have rights to kill the process.

    Maybe though... we're helping you to treat the symptoms and not the disease.  What process is going bonkers that you need to have a human kill it interactively?
    Standardize. Simplify. Automate.
    • Als Antwort markiertReena111 Mittwoch, 1. Juli 2009 15:00
    •  
  • Mittwoch, 1. Juli 2009 15:00Reena111 TeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillenTeilnehmermedaillen
     

    Thanks Sherry! The process is some scheduled task for an internally developed program that for some reason doesn't always stop running and hogs resources so until we get that figured out, the tech just wanted a way to kill it without us giving him admin rights on the server. I'll try the script method. :)

    Thanks!

    Reena