Your printers, without the print server.
QueuedWrite installs and looks after printers on your Windows PCs from the cloud. Each PC prints straight to the printer, so there is no server to patch, back up or wait on.
Ask about the pilotQueuedWrite is in pilot and taking a small number of early customers.
Add a printer
Head office, 2nd floor
- Accounting copierColor multifunction, by the stairsInstalled
- Front officeBlack and white, receptionAdd
- Print room plotterWide formatAdd
- Shipping labelsLabel printer, warehouse doorNeeds attention
What changes when the print server goes
The printers and the PCs stay where they are. What goes away is the machine in the middle and the work of keeping it alive.
| With a print server | With QueuedWrite | |
|---|---|---|
| Adding a printer to a PC | Group Policy, scripts, or someone walking over | Chosen once in the portal, or added by the user from a list sorted by location |
| Drivers | Loaded on the server, then pushed and hoped for | One library; the right driver is installed on each PC that needs it |
| When the server is down | Nobody prints | Printing carries on. PCs talk to printers directly; only changes wait |
| Knowing a printer needs toner | Someone tells you | Status and supply levels shown beside every printer |
| Who printed what | A separate product | Reports by person, printer, location and color, built in |
What it does today
Everything here is built and running in our pilot. Nothing on this page is a promise about later.
- Printer deployment
- Decide which PCs get which printers: everyone, a group, one PC, or a network range. A small agent on each PC installs the printer, repairs it if someone deletes it, and removes it when you say so.
- Self-service
- People add the printers you offer from a simple page on their own PC, organised by building, floor and room. No admin rights and no help-desk ticket.
- Driver library
- Upload a manufacturer's driver once. You approve each driver publisher before any PC trusts it, and every approval is recorded.
- Printer settings
- Set up a printer once the way you want it (finisher, trays, two-sided, black and white) and apply the same settings to every PC.
- Status and supplies
- See whether each printer is ready, what is wrong when it is not, how much toner or ink is left, and its page counts.
- Print reports
- Pages and jobs by person, printer, location and PC, split into color and black and white. Document names are never collected unless you choose to switch that on.
- Moving over
- See the printers every PC already has, import the queues from your old print server, and bring them under management a few at a time.
- Sign-in and records
- Administrators sign in with their Microsoft work account, so your own multi-factor rules apply. Every change is written to an audit log with the person's name.
Moving over, in order
Nothing is switched off until its replacement is working. You can stop after any step.
Install the agent
One script through Group Policy or your management tool. PCs enrol themselves and keep the agent up to date.
See what you have
Every PC reports the printers it already uses. Your print server's queues are imported from a file.
Take printers over
Add them to the portal a few at a time. A PC that already has the printer keeps it, now managed.
Retire the server
When every queue is direct and managed, the print server has nothing left to do.
What it does not do yet
Better to read this here than to find out later.
- Windows 10 and 11 PCs only. No Mac, Chromebook or phone printing yet.
- No badge or PIN release at the printer. Jobs print when they are sent.
- Printers are installed for everyone who uses a PC, not per person.
- Printers must be on the network. USB printers are reported on, not managed.
- The software is not yet code-signed, so some security tools need an exception during the pilot.
Ask about the pilot
Tell us a little about your setup. We will reply by email with what a pilot would involve for you.
Prefer email? Write to hello@queuedwrite.com.