Скачать или смотреть Resolving Windows Server 2019 Scheduled Task Persistence Issues

Discover how to fix the issue of scheduled tasks not persisting after a reboot in Windows Server 2019, using PowerShell scheduled jobs as an effective solution.
---
This video is based on the question https://stackoverflow.com/q/66186007/ asked by the user 'Robert' ( https://stackoverflow.com/u/5339690/ ) and on the answer https://stackoverflow.com/a/66195326/ provided by the user 'Robert' ( https://stackoverflow.com/u/5339690/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Win Server 2019 Scheduled Task persist after reboot error

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Fixing Scheduled Task Persistence Issues in Windows Server 2019

When working with Windows Server 2019, it can be frustrating to encounter issues related to scheduled tasks not persisting after a reboot. Despite the task functioning correctly before the reboot, you may find that it fails to restart after the server undergoes a reboot, particularly when you have newly installed components like Active Directory Domain Services (AD DS). This guide addresses this common dilemma and provides a solution using PowerShell to ensure your scheduled tasks continue to execute seamlessly even after a reboot.

Understanding the Problem

What Happened?

In this particular scenario, a scheduled task was created using PowerShell that worked perfectly on Windows 10. It was designed to execute a script (C:\Terraform\ImportUsers.ps1) repeatedly, but upon rebooting the server, the task would not restart as expected.

The error message indicated:

“The last run of the task was terminated by the user”

Task Scheduler history showed “Task Scheduler Failed to Start” with an additional data error value of 2147943726.

Such errors can occur due to various factors relating to the Windows Server environment, particularly during the integration of services like Active Directory.

The Solution: Using Scheduled Jobs

Instead of using traditional scheduled tasks which can be prone to issues in Windows Server environments, a more reliable method is to utilize PowerShell scheduled jobs. This approach is designed to better handle scenarios that involve reboots, ensuring persistence in execution.

Steps to Create a Scheduled Job

Set Up the Job Trigger:

Use the New-JobTrigger command to create a trigger that specifies when the job should run. For example, you can set it to run once and repeat every minute.

[[See Video to Reveal this Text or Code Snippet]]

Register the Scheduled Job:

Use the Register-ScheduledJob command to register your job. In this step, specify the job name, the script that should run, and the trigger created in the previous step.

[[See Video to Reveal this Text or Code Snippet]]

Key Benefits of Using Scheduled Jobs

Robustness: Scheduled jobs are designed to be more resilient across reboots.

Simplicity: They require less configuration than traditional scheduled tasks and can adapt better to changes in the system state.

Visibility: You can easily monitor and manage scheduled jobs using PowerShell cmdlets.

Conclusion

Transitioning from traditional scheduled tasks to PowerShell scheduled jobs can significantly enhance the persistence and reliability of your automated processes in Windows Server 2019. By following the straightforward steps outlined above, you'll keep your tasks running smoothly, even after reboots.

If you find yourself struggling with scheduled tasks that simply won't stick, consider making this switch for a more stable solution. Embrace the power of PowerShell scheduled jobs, and ensure your scripts continue to execute as intended in your server environment!