Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The title really says it all. We're running a windows network and there are some applications which benefit from being killed overnight, but we don't want to have to enforce a reboot to do that.

Is it possible to only kill certain processes with a group policy?

share|improve this question
up vote 4 down vote accepted

The stock functionality in Group Policy doesn't give you a way to execute arbitrary code during Group Policy refresh. (You get "Startup Scripts", "Shutdown Scripts", "Logon Scripts", and "Logoff Scripts".)

You could use Group Policy to deploy a "Scheduled Task" (either through Software Installation Policy w/ a custom package or via a "Startup Script") that would do the killing that you're looking for. That's probably the best way to get your "automated kill" code out onto the machines that need it.

share|improve this answer
Thanks, that gives me the information I need to get further with this. I'm not a sysadmin, and delving into the capabilities of group policy wasn't something I had time for. – adhocgeek Jan 6 '11 at 9:21

I agree with @Even Anderson. We do something similar using scheduled tasks and PsTools.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.