Comparison
Lansweeper vs SolarWinds Web Help Desk
Two tools districts shortlist for device tracking and IT operations, compared the way a buying committee actually reads them: what each is, what each does well, and what to check before signing. We build Chalk, a third option in this space — that context is worth knowing as you read, and it is why every claim below carries its basis.
Lansweeper
The strongest network discovery engine in this comparison — it will find every device on your wire, including the ones nobody told it about, and it will not know that any of them belongs to a seventh grader.
Where Lansweeper is strong
- Genuine network discovery, which almost nothing else in this category has: agentless scanning of Windows over WMI, Linux and macOS over SSH, and printers, switches, routers, firewalls and NAS over SNMP, so the inventory includes devices no one ever entered.
- A passive traffic sensor that discovers assets from network communications, catching devices that active scanning misses entirely — the closest thing to a real answer for shadow IT and unmanaged OT gear.
- An IT Agent for Windows, Linux and macOS endpoints that rarely touch the LAN, and Cloud Discovery across Azure, Intune, Microsoft 365 and Entra ID, AWS and GCP — with a reconciliation engine that merges the same device seen through several sources into one asset record instead of three.
- Vulnerability detection built on CPE correlation and VulnCheck, with CVSS severity and patch status against the software and OS actually in your inventory, alongside hardware and software lifecycle tracking for end-of-sale and end-of-support dates.
- Deployment packages in Lansweeper Classic — install software, run scripts and make remote changes on Windows machines from the same console that inventoried them.
- A full built-in help desk in Classic: tickets from the web console, email, API or import, dispatching rules, SLAs, teams, internal notes and a knowledge base.
What to check before you buy
-
Lansweeper is two products with a documented feature gap between them — Lansweeper Platform in the cloud and Lansweeper Classic on-premises — and which capabilities you get depends on which one you deploy.
Basis: Vendor's own 'Comparing Lansweeper Platform and Lansweeper Classic' documentation page, which lists discovery targets and features per product.
-
ChromeOS discovery is a Lansweeper Classic capability. In the newer Lansweeper Platform the vendor's comparison table marks Chrome OS as 'Planned (Cloud Discovery)'. For a district whose fleet is Chromebooks, that is the whole fleet sitting on the older product.
Basis: Vendor comparison table lists Chrome OS as supported in Classic scanning and Planned for Lansweeper Platform.
-
Even in Classic, ChromeOS scanning is work you do yourself: your license must support Chrome OS scanning, and you build a Google Cloud project, enable the Admin SDK, create a service account and grant it scopes before a single Chromebook appears.
Basis: Vendor's 'Chrome OS scanning requirements' documentation page.
-
The help desk is licensed per agent. Unlimited users can file tickets, but exactly one agent license is included, and every additional technician who answers tickets is a paid seat at $120 per year.
Basis: Vendor's 'Manage helpdesk agents' documentation plus the listed price in Lansweeper's own online store.
-
That help desk belongs to Classic. The cloud Platform documentation covers no ticketing module of its own — service management appears as connectors to Jira Service Management, ConnectWise, Zendesk and Freshservice, meaning a second vendor.
Basis: Lansweeper's documentation index places every help-desk article under Classic, and lists ITSM tools as integrations under Platform.
-
The asset meter has teeth: reaching your licensed asset limit can stop scanning of new and existing assets until you delete assets or upgrade.
Basis: Vendor's 'Manage your licensed asset limit' documentation page.
-
No student, guardian or enrollment concepts, and no SIS or rostering connectors — the identity sources documented are Active Directory, Entra ID, Intune and Microsoft 365. Students arrive by CSV, if at all.
Basis: Absent from Lansweeper's documentation index, which covers directory and cloud identity sources only.
-
Nothing models the 1:1 program itself: no device agreement, no parent signature, no fee for a cracked screen, no family balance, and no funding-source dimension for ESSER, Title or E-Rate reporting.
Basis: Absent from the vendor's documented feature set, which is discovery, inventory, risk and deployment.
SolarWinds Web Help Desk
A long-serving on-premises help desk with unlimited end users and a fair per-technician price — and a rewritten 2026 release that means a migration project either way.
Where SolarWinds Web Help Desk is strong
- Genuinely on-premises and self-hosted, positioned by the vendor as requiring no cloud dependency — which matters to districts with data-residency or board-policy constraints.
- Unlimited end users at every license tier. You pay for technicians only, which is genuinely favorable for a district with thousands of staff and a handful of techs.
- Fully published, transparent pricing with no quote gate — competitively unusual.
- Integrated asset management with ticket-to-asset linking and asset service history, so a technician sees the device from the ticket.
- LDAP and Active Directory sync plus documented SAML 2.0 SSO against AD FS, Okta, Google, and Entra ID.
- A modernized 2026 release line — a redesigned interface across 120+ screens, a security-hardened rebuild, and a published forward roadmap including Teams and Slack integrations and AI ticket summaries.
What to check before you buy
-
If you are still on the 12.x line, you have a forced migration ahead: SolarWinds has published End-of-Life dates for versions 12.4 through 12.8, and the replacement is a rewritten application, so it means retraining as well as an upgrade.
Basis: SolarWinds' own release-history page publishes End-of-Engineering and End-of-Life dates for the 12.x versions and instructs customers to transition to the current release; the 2026.2 notes describe a completely redesigned interface across 120+ screens.
-
No SIS or rostering integration — no OneRoster, Clever, ClassLink, or PowerSchool. Identity comes from LDAP, Active Directory, and SAML only.
Basis: None appear on SolarWinds' Web Help Desk product pages, education use-case page, or documentation; the documented identity story is explicitly directory-based.
-
No student or guardian concepts. Students appear only as ticket submitters — there is no enrollment, no grade, no guardian, and nothing that reacts to a transfer or a withdrawal.
Basis: SolarWinds' education page describes students, faculty, and staff purely as end users submitting tickets.
-
No 1:1 device circulation — no due dates on a student's device, no overdue workflow, no e-signed agreement, no loaner pool, and no lost or stolen lifecycle. Asset reservations are the nearest adjacent feature.
Basis: Web Help Desk's asset management is framed around IT inventory such as projectors and instrumentation; no custody loop appears in the documentation.
-
No student fee assessment or family balances. The parts-and-billing concepts in the product are IT cost accounting, not student charges.
Basis: No fee, charge, or student-ledger concept appears in the product documentation.
-
No funding-source or grant tracking — nothing to attribute devices to ESSER, Title, or E-Rate.
Basis: No such concept appears anywhere in the product documentation.
-
No ChromeOS or Google Admin device ingest surfaced. Discovery is network- and directory-oriented, so Chromebooks arrive by import or by hand.
Basis: No Google Workspace or ChromeOS device-ingest integration appears in SolarWinds' Web Help Desk documentation or integration listings.
-
It consumes SSO but is not an identity provider. It cannot issue SAML or OIDC outward, and cannot give students a portal identity.
Basis: SolarWinds' authentication documentation configures Web Help Desk as a SAML 2.0 service provider against an external IdP.
The third option: Chalk
If you are weighing Lansweeper against SolarWinds Web Help Desk, Chalk belongs on the same shortlist. It is the open-source K-12 IT stack: device inventory that fills itself in from Google Admin, Intune, and Jamf against a roster synced from your SIS, a 1:1 circulation desk with agreements and fees, repairs with parts and costs, a help desk that already knows who is asking, and a built-in SAML/OIDC identity provider.
- Self-host it free forever under AGPL-3.0 — the entire feature set, one binary, your infrastructure — or use the hosted version, priced by fleet size with no per-seat or per-student fees and the price ladder published.
- Built only for K-12: students, buildings, custody, funding sources, and ChromeOS auto-update expiration are native concepts, not custom fields.
- Writes back to Google Admin as a reviewed diff — every OU move, disable, and deprovision previewed before it executes — and serves a OneRoster 1.1 API so other district systems can pull the roster from Chalk.
- Fees are assessed and tracked without touching payment cards, keeping the asset system out of your PCI scope.
See all three on your own roster.
Chalk installs to a populated inventory in about 30 minutes. Self-host free under AGPL-3.0, or let us run it — priced by fleet size, never per seat.