Scheduled tasks are one of the most powerful tools in the IT admin’s toolkit. They can automate everything from running scripts, to updating software, to sending alerts. However, if you’ve ever tried to set up a scheduled task via Group Policy (GP), you might have noticed a rather frustrating limitation: the shortest interval you can set is 5 minutes.

But what if you need something more frequent? Maybe you want to check a service status, monitor a log file, or run a quick script every 2 minutes? The good news is there’s a way to break free from this constraint using an XML trick. In this guide, we’ll walk through how to configure a scheduled task to run more frequently than the default 5-minute limit.

Why Would You Need Sub-5-Minute Intervals?

Automating tasks with intervals shorter than 5 minutes can be essential in scenarios such as:

  • Monitoring network connectivity or internet access in near real-time.
  • Keeping a service alive by pinging it every couple of minutes.
  • Running quick scripts to gather metrics or system health data more frequently.
  • Detecting critical events that require immediate action.

With these use cases in mind, let’s dive into how you can set up a scheduled task with sub-5-minute intervals using Group Policy Preferences and some XML tweaks.

Step 1: Setting Up the Task in Task Scheduler

Before deploying a task through Group Policy, it’s best to create it manually on a test machine. This will allow you to fine-tune the settings and export the task as an XML file.

  1. Open Task Scheduler on your Windows machine.
  2. Create a New Task and configure the actions, triggers, and conditions as needed.
  3. Set the Repeat Task Every interval to the shortest option available (5 minutes).
  4. Save the task.

Note: We’ll reduce this interval below by editing the XML directly.

Step 2: Export the Task to XML

Once the task is set up and working correctly:

  1. In Task Scheduler, find the task you created.
  2. Right-click on the task and select Export.
  3. Save the .xml file to a location where you can edit it (e.g., your Desktop).

This exported XML file contains all the task’s configurations, including the interval settings that we’re going to modify.

Step 3: Editing the XML File to Set a Custom Interval

Now comes the trickier part—editing the XML file to set an interval that’s shorter than what the Task Scheduler GUI allows.

  1. Open the exported .xml file using a text editor like Notepad.
  2. Look for the section that looks like this:
    3. <Trigger>
    <Repetition>
        <Interval>PT5M</Interval>
        <StopAtDurationEnd>false</StopAtDurationEnd>
    </Repetition>
</Trigger>
  3. The <Interval> tag currently specifies a 5-minute interval (PT5M).
  4. Change the value to your desired interval. Here are some examples:
    • 1-minute interval: <Interval>PT1M</Interval>
    • 2-minute interval: <Interval>PT2M</Interval>
    • 30-second interval: <Interval>PT30S</Interval>
  5. Save the XML file after making your changes.

Step 4: Testing the Updated Task

Before deploying it via Group Policy, test the updated task to ensure it runs as expected.

  1. In Task Scheduler, click Import Task.
  2. Select the modified .xml file.
  3. Review the settings and click OK to save.
  4. Confirm that the task now runs at the updated interval (e.g., every 2 minutes).

Step 5: Deploying the Task via Group Policy

Now that your task is ready, you can push it out to multiple machines using Group Policy.

  1. Open the Group Policy Management Console (GPMC).
  2. Navigate to:
    3. Computer Configuration → Preferences → Control Panel Settings → Scheduled Tasks
  3. Right-click and select New → Scheduled Task (At least Windows 7).
  4. Go to the Actions tab and click Import.
  5. Choose your edited .xml file.
  6. Review the settings, then click OK to deploy the task via Group Policy.

The task will now run on all systems where the GPO is applied, at the interval you specified in the XML—whether that’s every minute, every 2 minutes, or every 30 seconds.

Final Thoughts: Why Bother with XML?

While it might seem like a hassle to edit XML files manually, it’s a powerful way to unlock the full potential of scheduled tasks on Windows systems. This method can help you overcome limitations of the GUI and automate tasks that require more frequent attention.

By taking control of the XML, you can deploy highly customized tasks through Group Policy without having to rely on external scripts or software. It’s a nifty trick that every sysadmin should have in their toolbox.

Have you tried this method?

Let us know in the comments if you’ve found other creative ways to overcome the limitations of Group Policy. We’d love to hear how you’ve used these techniques to keep your systems running smoothly!

Happy automating!