MaksIT Unified Scheduler Service

A modern, fully rewritten Windows service built on .NET 10 for scheduling and running PowerShell scripts and console applications. Designed for system administrators — and also for those who feel like system administrators — who need a predictable, resilient, and secure background execution environment.

---

Table of Contents

• MaksIT Unified Scheduler Service
  • Table of Contents
  • Scripts Examples
  • Features at a Glance
  • Installation
    • Recommended (using bundled scripts)
    • Manual Installation
  • Configuration (appsettings.json)
    • PowerShell Scripts
    • Processes
  • How It Works
    • PowerShell Execution Parameters
    • Thread Layout
  • Reusable Scheduler Module (SchedulerTemplate.psm1)
    • Example usage
  • Security
  • Logging
  • Contact
  • License

Scripts Examples

• Scheduler Template Module
• Hyper-V Backup - Production-ready Hyper-V VM backup solution with scheduling and retention management
• File-Sync - FreeFileSync batch job execution

---

Features at a Glance

• .NET 10 Worker Service – clean, robust, stable.
• Strongly typed configuration via appsettings.json.
• Run PowerShell scripts & executables concurrently (each in its own thread).
• Signature enforcement (AllSigned by default).
• Automatic restart-on-failure for supervised processes.
• Extensible logging (file + console).
• Simple Install.cmd / Uninstall.cmd.
• Reusable scheduling module: SchedulerTemplate.psm1.
• Thread-isolated architecture — individual failures do not affect others.

---

Installation

Recommended (using bundled scripts)

cd /d path\to\src\MaksIT.UScheduler
Install.cmd

To uninstall:

Uninstall.cmd

Manual Installation

sc.exe create "MaksIT.UScheduler Service" binpath="C:\Path\To\MaksIT.UScheduler.exe"
sc.exe start "MaksIT.UScheduler Service"

Manual uninstall:

sc.exe delete "MaksIT.UScheduler Service"

---

Configuration (appsettings.json)

{
  "Configuration": {
    "ServiceName": "MaksIT.UScheduler",
    "LogDir": "C:\\Logs",

    "Powershell": [
      { "Path": "C:\\Scripts\\MyScript.ps1", "IsSigned": true }
    ],

    "Processes": [
      { "Path": "C:\\Programs\\MyApp.exe", "Args": ["--option"], "RestartOnFailure": true }
    ]
  }
}

PowerShell Scripts

• Path — full .ps1 file path
• IsSigned — true enforces AllSigned, false runs unrestricted

Processes

• Path — executable
• Args — command-line arguments
• RestartOnFailure — restart logic handled by service

---

How It Works

Each script or process is executed in its own managed thread.

PowerShell Execution Parameters

myCommand.Parameters.Add(new CommandParameter("Automated", true));
myCommand.Parameters.Add(new CommandParameter("CurrentDateTimeUtc", DateTime.UtcNow.ToString("o")));

Inside the script:

param (
    [switch]$Automated,
    [string]$CurrentDateTimeUtc
)

Thread Layout

Unified Scheduler Service
├── PowerShell
│   ├── ScriptA.ps1     Thread
│   ├── ScriptB.ps1     Thread
│   └── ...
└── Processes
    ├── ProgramA.exe     Thread
    ├── ProgramB.exe     Thread
    └── ...

A crash in one thread never stops the service or other components.

---

Reusable Scheduler Module (SchedulerTemplate.psm1)

This module provides:

• Scheduling by:

  • Month
  • Weekday
  • Exact time(s)
  • Minimum interval

• Automatic lock file (no concurrent execution)

• Last-run file tracking

• Unified callback execution pattern

• Logging helpers (Write-Log)

Example usage

param (
    [switch]$Automated,
    [string]$CurrentDateTimeUtc
)

Import-Module "$PSScriptRoot\..\SchedulerTemplate.psm1" -Force

$Config = @{
    RunMonth = @()
    RunWeekday = @()
    RunTime = @("22:52")
    MinIntervalMinutes = 10
}

function Start-BusinessLogic {
     Write-Log "Executing business logic..." -Automated:$Automated
}

Invoke-ScheduledExecution -Config $Config -Automated:$Automated -CurrentDateTimeUtc $CurrentDateTimeUtc -ScriptBlock {
    Start-BusinessLogic
}

Workflow for new scheduled scripts:

1. Copy template
2. Modify $Config
3. Implement Start-BusinessLogic
4. Add script to appsettings.json

That’s it — the full scheduling engine is reused automatically.

---

Security

• Signed scripts required by default.
• Scripts are auto-unblocked before execution.
• Unrestricted execution can be enabled if needed (not recommended on production systems).

---

Logging

• Console logging
• File logging under the directory specified by LogDir
• All events (start, stop, crash, restart, error, skip) are logged

---

Contact

Maksym Sadovnychyy – MAKS-IT, 2025 Email: maksym.sadovnychyy@gmail.com

---

License

MIT License Copyright (c) 2025 Maksym Sadovnychyy – MAKS-IT maksym.sadovnychyy@gmail.com

---