[GH-ISSUE #1990] Add Validation to Verify that Tasks Exist #1244

New issue

Open

opened 2026-03-02 02:22:06 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 02:22:06 +03:00

Owner

Originally created by @ZzBombardierzZ on GitHub (Aug 29, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1990

Is your feature request related to a problem? Please describe.

When using something like DeepFreeze, RebootRestore RX, Time Freeze, etc, tasks will be created once but then aren't validated ever again to make sure they still exist.

In DeepFreeze, Thawed means edits to the computer will be saved after the restart. If a machine is Frozen, it will not save any data changed after a reboot.

Installed TRMM while DeepFreeze is Thawed.
Enable DeepFreeze (Freeze the computer).
Add a new task in TRMM admin webpage.
Task seems to add and apply while the machine is Frozen.
Machine reboots.
Machine forgets the task was ever added.
The machine never runs the task again.

In addition to the above, a user could simply delete a scheduled task from the Windows Task Scheduler, and I believe it would never be added/checked again? I'm not sure if you run the task manually if it re-adds it to the computer Task Scheduler or if it just runs it the one manual time.

Describe the solution you'd like
Once a day (or more frequent), check if all the tasks assigned to the computer in Tactical are actually on the computer.

Describe alternatives you've considered
A button in the computer's Tasks list to "Resync" tasks.

Or a task option to run the task from the server to the agent, instead of running from Windows Task Scheduler and then sending the results (agent to server). This would also support Mac and Linux in Tasks, but I imagine this is way more overhead on the server, and I also imagine the Mac and Linux Tasks coming soon will be implemented in another way.

Additional context
In this screenshot, you can see one of the computers that have DeepFreeze on it. The actual results are worse than this Issue makes it seem, but my main concern from this write-up is what's happening with Highlighted / Orange circled one: "Synced with agent Awaiting output Has not run yet Monday, Wednesday, Friday at 01:50PM every 1 weeks".

Originally created by @ZzBombardierzZ on GitHub (Aug 29, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1990 **Is your feature request related to a problem? Please describe.** When using something like DeepFreeze, RebootRestore RX, Time Freeze, etc, tasks will be created once but then aren't validated ever again to make sure they still exist. In DeepFreeze, Thawed means edits to the computer will be saved after the restart. If a machine is Frozen, it will not save any data changed after a reboot. 1. Installed TRMM while DeepFreeze is Thawed. 2. Enable DeepFreeze (Freeze the computer). 3. Add a new task in TRMM admin webpage. 4. Task seems to add and apply while the machine is Frozen. 5. Machine reboots. 6. Machine forgets the task was ever added. 7. The machine never runs the task again. In addition to the above, a user could simply delete a scheduled task from the Windows Task Scheduler, and I believe it would never be added/checked again? I'm not sure if you run the task manually if it re-adds it to the computer Task Scheduler or if it just runs it the one manual time. **Describe the solution you'd like** Once a day (or more frequent), check if all the tasks assigned to the computer in Tactical are actually on the computer. **Describe alternatives you've considered** A button in the computer's Tasks list to "Resync" tasks. Or a task option to run the task from the server to the agent, instead of running from Windows Task Scheduler and then sending the results (agent to server). This would also support Mac and Linux in Tasks, but I imagine this is way more overhead on the server, and I also imagine the Mac and Linux Tasks coming soon will be implemented in another way. **Additional context** In this screenshot, you can see one of the computers that have DeepFreeze on it. The actual results are worse than this Issue makes it seem, but my main concern from this write-up is what's happening with Highlighted / Orange circled one: "Synced with agent Awaiting output Has not run yet Monday, Wednesday, Friday at 01:50PM every 1 weeks". ![image](https://github.com/user-attachments/assets/161604f6-59f4-488f-b394-d5e35cfa7e56)

kerem commented

2026-03-02 02:22:06 +03:00

Author

Owner

@wh1te909 commented on GitHub (Sep 4, 2024):

mac/linux task scheduling will be handled on the server, and eventually windows will be migrated to this as well as the current method has issues like this. in the meantime I can look into adding missing tasks back to the task scheduler

@wh1te909 commented on GitHub (Sep 4, 2024): mac/linux task scheduling will be handled on the server, and eventually windows will be migrated to this as well as the current method has issues like this. in the meantime I can look into adding missing tasks back to the task scheduler