Tool Detail

SmartM365 Inventory Orchestrator

A resident PowerShell 7 scheduler that runs the Smart Inventory collectors unattended across several servers, with a WPF GUI to supervise jobs, plan schedules, and review run history.

Inventory Orchestrator Dashboard in demo mode showing a healthy status banner, job and server tiles with no failure, four fictional sample servers online, a 24-hour schedule timeline, and CPU and memory charts for the last 12 hours.
DEMO mode with fictional sample data. No tenant, device, or mailbox was connected.
RUN

Resident scheduler

One resident instance per tenant and server checks due jobs every minute and starts each job in its own detached process, so a long job survives a planned recycle and is adopted again.

SRV

Elected owners

Each job runs on a server elected from live capabilities such as Graph, Exchange Online, Active Directory, or SharePoint Server, with weights, server policies, and shared occurrence claims.

DEP

Dependencies and limits

Dependencies, concurrency keys, timeouts, retries, and missed-run policies keep collectors in order. A job waits instead of running on stale or missing inputs.

LOG

History and mail

Every run is recorded with its status, duration, server, and log. Failure mails, an optional daily summary, and peer monitoring report what needs attention.

Central management GUI

Supervise, plan, and publish

Planning edits schedules, dependencies, retries, timeouts, and assignment modes as a draft. The GUI validates the complete configuration, publishes it with a cross-server lock, keeps before and after versions with an audit row, and can roll back.

The orchestrator has no packaged GitHub release: review and run it from the source on main.

Limits

The orchestrator schedules and supervises collectors; it does not qualify their data. Collector exit codes report technical completion, and business findings stay in each collector's own reports.

The GUI and the residents must use the same live shared folder, not a SharePoint or OneDrive mirror. Offline tests and the demo do not qualify a tenant, a server, or a deployment.