What is PC management software and what should it actually do?

The category covers everything from enterprise device fleets to a room of public machines and the products are not interchangeable. Here is how to tell which kind you need before you buy the wrong one.

By Atilla Yurtseven · · Updated · 9 min read

Key takeaways

PC management software controls a fleet of computers from one place: what runs on them, who can use them, how they are updated and what state they return to. Enterprise tools manage assigned company laptops. Shared-machine tools manage public computers used by strangers, where the priorities are session control, lockdown and returning the machine to a clean state. Buying from the wrong category is the common expensive mistake.

  • Enterprise fleet tools and shared-machine tools solve different problems.
  • For public computers, session control and reset matter most.
  • Deploying software to every machine at once should be one action.
  • Remote view and control saves more staff time than anything else.
  • Match the tool to who sits at the keyboard, not to the feature list.
HandyCafe
Choosing software What is PC management software and what should it actually do?
On this page

PC management software is a category broad enough to be nearly meaningless on its own. It covers the tools a bank uses to police ten thousand laptops and the tools a twelve-seat computer room uses to stop somebody installing a toolbar.

Both are called PC management software. They solve different problems and buying from the wrong half is the expensive mistake this article exists to prevent.

What the category actually means

At its core it is the ability to control a group of computers from one place instead of one keyboard at a time: install and update applications, apply settings and restrictions, watch the status of each machine, fix problems without walking over.

Past a handful of machines, doing this by hand stops working. The tools exist because the alternative is a person with a USB stick and an afternoon.

The split that matters: who sits at the keyboard

This is the question that sorts the market and almost nobody asks it first.

Assigned machines. A known employee uses the same laptop for years. The concerns are security policy, compliance, patching, software licensing and remote support for somebody you can phone. This is the enterprise half of the category.

Shared machines. A stranger sits down for an hour, then leaves and somebody else sits down. Nobody owns the machine. The concerns are completely different: controlling and timing the session, restricting what the user can reach, keeping the machine identical for the next person and not letting one visitor's mess become the next visitor's problem.

Internet cafes, LAN centers, school labs, libraries, training rooms and hotel business centres are all the second kind. Enterprise fleet tools handle them badly, not because they are weak but because they were designed around an assumption that does not hold here.

What shared-machine software has to do

Six things, in rough order of how much time they save you.

Session control. Start and end a session centrally, with a clear state between users. This is the backbone. Everything else hangs off knowing whether a machine is in use and by whom.

Lockdown. Restrict the desktop, the settings and whatever else a stranger should not reach. This is the same idea as kiosk software, applied to a machine that still needs to be broadly useful.

Return to a clean state. Whatever the last person did should not follow them. Accounts signed out, downloads cleared, changes reverted.

Fleet deployment. Getting a program, a game or an update onto every machine should be one action from the counter, not twenty. Tools that distribute only the changed files turn an evening job into a background task.

Remote view and control. The single biggest saver of staff time. Most problems are trivial for somebody who can see the screen and every one you solve from the counter is a walk you did not take. The practical version of this is covered in remote management of client machines.

Reporting. Which machines are used, which are idle, which keep failing. A station that quietly crashes twice a day looks fine until the numbers show it earning half what its neighbours do.

Where billing enters

If the computers are a paid service, add a second layer: timing usage, applying rates, handling members and prepaid balances, taking money and reconciling it at the end of a shift.

Venues frequently try to solve this with two products, a management tool plus a till and then spend the rest of their lives reconciling them. One system that knows both the session and the money is the difference between a clean end-of-night and an argument with a spreadsheet.

Choosing without wasting a month

Ignore the feature grid. Test the workflows you will actually run, on your own machines.

Start a session, restrict it, end it, confirm the machine is clean for the next person. Push a large application to every machine and time how long the room is unusable. Take control of a screen from the counter and fix something. Then look at what the reports tell you about a station that is idle.

A tool that handles those four smoothly will handle your Tuesday. One that needs a workaround for any of them will need that workaround forever. The same test, applied to a paid venue, is laid out in how to choose software for a computer room.

Frequently asked questions

What is PC management software?

Software that controls a group of computers centrally rather than one at a time: installing and updating applications, applying settings and policies, restricting what users can do, monitoring status and fixing problems remotely. It exists because touching every keyboard individually does not scale past a handful of machines.

What is the difference between enterprise and shared-computer tools?

Enterprise tools assume each machine belongs to a known employee and focus on security policy, compliance and software deployment over long periods. Shared-computer tools assume a stranger sits down for an hour. They focus on session control, locking the machine down, timing and billing usage and returning it to a clean state afterwards.

What should software for public computers do?

Control the session from a central point, restrict what the user can reach, track or bill the time, deploy and update applications across the fleet in one action, allow staff to see and control a screen remotely and reset the machine so nothing carries from one user to the next.

How do I update software across many machines?

Push it from a central point rather than walking the room. Good tools distribute only the files that changed, which turns a large update from an all-evening job into a background task. Doing it manually is where most of the maintenance time in a computer room disappears.

Do I need remote control of each screen?

It saves more staff time than any other single feature in a room of public machines. Most problems are small and solved in seconds by someone who can see the screen. Without it, every question means a walk across the room and a queue at the counter.

Does this apply to school and library computers?

Yes. A classroom, a library and an internet cafe have the same core problem: unknown users at shared machines that must work for the next person. The billing part differs. But session control, lockdown and reset are the same requirements.

Managing a room of shared PCs?

HandyCafe covers session control, lockdown, file sync, remote management and reporting across the fleet.