Remotely control computer software

Lab and Classroom Management for Education

A computer lab is a batch of identical machines, and it sits empty for months. Those two facts make education unlike corporate IT.

Updated

School IT has two characteristics rarely seen in corporate environments, and they decide how remote management should be configured.

One: a lab is a batch of identical machines

Fifty identically configured PCs, the same image, the same course software.

Maintenance here is batch work, not per-machine work: installing a new lab environment, changing one setting, clearing up after the previous class. Grouping lets you organise by room; bulk deployment means a replacement machine does not have to be set up by hand. Both are in the Free edition.

Two: it sits empty for months

This is what makes education unusual. Over the holidays the labs are empty, but the maintenance still has to happen — updates, software versions, preparing next term’s environment — all while nobody is on site.

So education is inherently unattended. That also means those machines have to stay reachable through the break:

  • Set the power plan so they do not sleep, or you lose them on day three
  • Set “restore on AC power loss” in BIOS — a breaker trips and nobody is there
  • Stopping at the login screen after an update is especially fatal in an empty lab

The details are in remote work and off-site access — written for a different scenario, but the failure modes are the same ones.

Classrooms and shared terminals

Lectern PCs, library catalogue machines: similar to labs but more scattered — many of them, spread across buildings, and the class has already started when one fails.

Unattended plus grouping is the same answer. What deserves extra attention is audit: shared terminals are touched by anyone, so incidents need to be traceable, and connection logs and recording start at the Team edition.

About budget

School procurement runs on the academic year rather than a corporate fiscal cycle. WorksLink bills per concurrent channel rather than per device — favourable for labs, where there are many machines and few simultaneous maintainers. Several hundred machines may need only a handful of channels.

Editions and pricing are on the pricing page.