A dental clinic with eight PCs. An architecture studio with twelve. A family business where "IT" is whoever is best with computers. These offices don't have an RMM contract or a fleet admin, and they have the same problems every week: a PC that's slow, a disk that's full, updates that didn't install, a printer that vanished.
The AI chat the office manager already uses knows the PowerShell for every one of those. What it can't do is run it. So someone reads the steps off a screen, types them on each machine, and hopes.
Fleet or handful?
The first question decides everything.
A fleet — dozens or hundreds of endpoints, compliance requirements, audits — belongs in audited tooling: an RMM, Intune, PowerShell remoting with change control, Ansible. Use AI there to draft and review scripts that go through your normal process and a pilot group. A chat with admin rights on production endpoints is hard to defend in an audit, and r/sysadmin will tell you so.
A handful — five to fifteen machines, one person looking after them part-time — is different. An RMM rollout is more process than the problem. Here a chat that can actually run things on each PC is a real step up from walking around with a USB stick.
What to hand it
Jobs that are common, low-risk and tedious to do machine by machine:
- "Check free disk space on all office PCs and list any under 15%."
- "Which PCs have Windows updates pending, and which failed last time? Don't install anything yet."
- "Reception PC is slow since Monday. Check startup programs, CPU use and disk health and tell me in plain words."
- "Clear temp files and the Windows Update cache on the PCs you flagged, then check disk space again."
- "Is the scanner service running on the front-desk PC? If not, start it and check it stays up."
What not to hand it
- Anything touching backups or the server that holds the patient/client data, until you've watched it work for weeks.
- Account and permission changes.
- Bulk changes without a dry run: "tell me what you would do on each machine" first, then "do it on one", then the rest.
Review before run
Two habits make this safe enough for a small office:
- Look before change. Every job starts with "check and report; don't change anything". Read the report.
- One machine first. Apply a fix to one PC, confirm it worked, then the others.
How I do it
I build Local Commander, so I'm biased. A small agent goes on each office PC; the person looking after them asks ChatGPT or Claude, and each request runs on the PC it names. Per PC, you choose what it allows (the whole user account or selected folders) and can block commands or cut a PC off at once. The agent runs under a user account, so for admin jobs that account needs admin rights on that PC; giving them is a decision, not a default.
When to graduate
Move to an RMM or proper management when any of these become true:
- More than 15–20 machines, or more than one site with its own network.
- You need patch reporting for an audit, insurance or a client contract.
- Someone other than you needs to see the state of every machine without asking.
- You find yourself asking the chat the same thing every Monday. That's a script or a policy, not a conversation.
Limits, plainly
- Not an RMM: no patch management, compliance reports or asset inventory.
- Every PC needs the agent (and Node.js 20+), and has to be on.
- Commands and files, not the screen. For "which button do I click" calls, use Quick Assist.
- It isn't a sandbox; it acts with the rights of the account it runs under.