SLApp Helpdesk
Active Directory & backups

Domain controllers and backup jobs, checked every day

Two things nobody looks at until they break: replication between domain controllers, and a backup job that quietly stopped working weeks ago. SLApp Helpdesk has the agent you already have run one read-only check a day on every Windows computer, reads the health of your clients' Active Directory and the results of their backup software, and alerts you when something fails.

Active Directory
Client: AnyShow: All
DomainClientHealthdcdiagReplicationServicesTimeAdmins
contoso.local2 domain controllersContoso, Lda.OKOKOKOKOK4
fabrikam.local2 domain controllersFabrikam, S.A.CriticalOKProblemfailing for 31 hOKWarning74 s off6+1 new

One check a day, nothing new to install

  • Run by the agent you already have. Every Windows computer runs one check a day, at its own time, through the existing command queue — no new agent, and no extra module on the server. It only reads: WMI, the event logs, the registry, the directory over LDAP, and the output of dcdiag and w32tm.
  • Offline is not a failure. A computer that is off at its time is checked as soon as it is back; Check now runs it again after a fix, once every 5 minutes per computer.
  • Out of your way. The daily checks stay out of the Queue lists unless you ask to see them, and are cleaned up after three days.
  • On the computer and in the report. The computer's page shows a health block, and the client report gains Active Directory and Third-party backups sections.

Active Directory health

  • Domain controllers found by themselves — the check recognises a domain controller on its own, and a technician can mark or unmark one.
  • Each domain controller — dcdiag (the tests that fail on any recent event-log error are shown, never alerted), replication with its partners, the AD services (NTDS, DNS, Netlogon, KDC, W32Time, DFSR), SYSVOL and NETLOGON shared, and its clock against the PDC emulator.
  • Each domain — the FSMO role holders, the domain and forest functional levels, account hygiene (enabled users, locked out, password never expires, inactive for 90 days, disabled) and the members of Domain Admins, Enterprise Admins and Schema Admins.
  • History — the last 30 results of each domain controller, and one row per domain that brings its controllers together.
  • Alerts — critical for dcdiag failures, replication failing for more than 24 hours, an AD service stopped, a clock more than 5 minutes off, SYSVOL or NETLOGON not shared, and a new member of a privileged group (naming who); a warning when the check itself fails three days in a row.

Third-party backups

  • Read from the event logs — Veeam Backup & Replication, Veeam Agent for Windows, Windows Server Backup and Acronis: the results of the last 48 hours and the last success ever seen.
  • Jobs appear by themselves, with their expected frequency — daily, weekdays or weekly — guessed from their history. Change it, or ignore a job, whenever you like.
  • Anything else that writes to an event log — add a custom event for a computer: the log, an optional source, and the event ids of a success, a failure and a warning.
  • Alerts — a failed backup (critical), one that ended with warnings, no success for longer than its expected frequency plus a day (critical), and the check itself failing.
  • Synology Active Backup for Business keeps its results on the NAS, so it is detected and noted; a custom event can watch its agent's log.
  • Forget a removed job — it only comes back if it runs again.
Third-party backups
Client: AnyProduct: All productsShow: All
JobProductClientLast resultLast successExpected
Daily VMsCTS-SRV01Veeam Backup & ReplicationContoso, Lda.SuccessToday, 01:42 AMDaily
File serverFAB-SRV01Veeam Agent for WindowsFabrikam, S.A.Failed26 Oct 2026overdueDaily
Windows Server BackupFAB-SRV02Windows Server BackupFabrikam, S.A.Warning29 Oct 2026Weekdays (Mon-Fri)
Offsite copyCTS-SRV02AcronisContoso, Lda.Success25 Oct 2026Weekly
Third-party backups: every job seen in the event logs, its last result, its last success and how often it is expected to succeed.

How it works

  1. 01

    Nothing to set up

    The check starts by itself on every Windows computer with the agent.

  2. 02

    Open the modules

    Infrastructure → Active Directory and Third-party backups list every client's domains and backup jobs, with filters, search and a detail window with every part and its history.

  3. 03

    Adjust where needed

    Mark a domain controller the check missed, set a job's expected frequency, or add a custom event.

  4. 04

    Act on the alerts

    They appear in Alerts and on the Dashboard, and administrators get an email; most close by themselves once the problem is fixed. An administrator can turn each module's alerts off with Generate alerts, at the top of its page.

What it needs

  • The agent on the domain controllers and backup servers — nothing new to install, and no Active Directory PowerShell module.
  • Windows PowerShell 3.0 or later (Windows Server 2012 and later).
  • Acronis writes to the event log only when its event logging is switched on — it is off by default.
  • Technicians mark domain controllers, set frequencies, add custom events and run Check now; forgetting a job, deleting a custom event and resolving an alert by hand are for administrators.
  • It is a daily check, not live monitoring: a problem shows up at the next daily check, or as soon as the computer answers a Check now.

Active Directory & third-party backups

One read-only daily check per Windows computer: AD health and Veeam, Windows Server Backup and Acronis results, with alerts.

Request a demo