Member Avatar for Dani
Dani 5,664 The Queen of DaniWeb

I found this in a few different places around the 'net - hopefully it's helpful:

Prevent a User From Running or Stopping a Scheduled Process in Windows XP

This step-by-step article describes how to prevent a user from running or stopping a scheduled process in Windows XP.

There are occasions where is not advisable to run a scheduled process before the intended date and time, or when an administrator doesn't want a user to add new scheduled processes to the computer. You can use the following procedures to enable maximum control over what can be done with the Scheduler service.

  • Click Start > Run, type mmc, and then click OK.
  • On the File menu, click Add/Remove Snap-in. On the Standalone tab, click Add.
  • In the Available Standalone Snap-ins list, click Group Policy, and then click Add.
    In the Select Group Policy object box, click Local Computer to edit the local Group Policy object, or click Browse to find the Group Policy object that you want.
  • Click Finish, click Close, and then click OK. The Group Policy snap-in opens the Group Policy object for editing.
  • Expand either the User Configuration or Computer Configuration branch, and then expand Administrative Templates, Windows Components, Task Scheduler.
  • Double-click Prevent Task Run or End, click Enabled, and then click OK.
  • 1 Contributor
  • 0 Replies
  • 138 Views

Dani AI

Generated

As noted, Microsoft provides a Group Policy method to restrict users from manually starting or stopping scheduled tasks. A few practical points help avoid surprises when you put that into practice.

That policy mainly stops manual Run/End actions from the Scheduled Tasks UI for the targeted users. It does not prevent the system from executing tasks at their scheduled times, and it will not stop users who already have administrative rights. Advanced users or scripts might still be able to trigger tasks unless additional controls are applied, so treat the policy as a UI-level restriction, not a full lock-down.

If the target machines run Windows XP Home (which lacks the Group Policy editor) or you need a stronger block, consider adjusting NTFS permissions on the Scheduled Tasks folder (typically C:\Windows\Tasks) to deny creation or modification for specific accounts. Do not remove or deny access for SYSTEM or Administrators; doing so can break scheduled services. Also consider enabling auditing on that folder so changes are logged and can be reviewed.

Always test changes before rolling them out. Apply the setting to a test user or workstation, log off and back on, and confirm the behavior. If machines are domain-joined, apply the setting via a domain GPO scoped to the correct OU or user group instead of relying on local edits. Because Windows XP is no longer supported, plan to migrate those systems when possible and keep backups of the Tasks folder and important configuration before making permission or policy changes.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.