Skip to content
Atlas Spool: Print. Deliver. Anywhere.
Direct-IP · No print server · On every plan

Printers, pushed to every Windows endpoint

Atlas Spool is managed direct-IP printing for Azure Virtual Desktop and every Windows endpoint you manage with Atlas Reach. Define a TCP/IP printer once, assign it to a host pool, host, device group, user, or group, and the Atlas AVD Agent installs it as a direct-IP printer on every matching session host and Windows endpoint. No central print server. Print jobs go straight from the device to the printer.

Serverless printing

Take the print server out

The PrinterLogic-style model, built into Atlas AVD: Atlas manages printer definitions and who they are pushed to, while the jobs themselves never touch Atlas.

No central print server

There is no print server in the path to build, patch, license, or fail over. Atlas Spool manages definitions and assignments, not a queue.

Jobs go device → printer

Print jobs travel straight from the session host or endpoint to the printer over TCP/IP. Atlas never receives, spools, or relays document data.

Direct-IP protocols

RAW/JetDirect (9100), LPR (515) or driverless IPP/IPPS (631), chosen per printer to match the device, with the driver installed from the Atlas driver repository or, for IPP, Windows' built-in class driver.

Assign and unassign centrally

Assign a printer and it installs; unassign it and the agent removes it on its next resolve. Optional reachability probing can track each printer's online/offline status.

What Atlas Spool does

Define, assign, install, verify

Printing as policy: define a printer once, target it precisely, and let the agent keep every session host and Windows endpoint consistent.

Define printers once

Register a TCP/IP network printer, address, port, protocol (RAW/9100, LPR or IPP/IPPS), driver, and capabilities, once, centrally. That single definition is what Atlas pushes to every host that needs it.

Assign by scope

Deploy a printer to a host pool, a specific session host or device, an Atlas Reach device group, a user by UPN, or an Entra ID group, and mark a default. The most specific scope wins, so a pool-wide default coexists with a per-user exception.

Installed on every Windows endpoint

The Atlas AVD Agent on each session host and each Atlas Reach-managed Windows device resolves its assigned set on a regular reconcile pass (every 30 minutes by default, or on demand with Refresh printers in Atlas Reach), installs the printers as direct-IP printers, sets the default, and removes printers that are no longer assigned.

Per-device rollout health

The agent reports the install state of every printer on every device (installed, failed, or removed) with the driver or connection error on failure, so a printer that could not install is diagnosable, not silently missing.

Self-service printers

Assign a printer as self-service instead of pushing it, and users add it themselves from "Add printers…" in the Atlas Reach tray icon. Only the printers you assigned to them are offered, and no extra sign-in is needed.

One driver repository

A built-in catalog of universal drivers from Microsoft, HP, Xerox, Canon, Ricoh, Konica Minolta, Lexmark, Kyocera, Brother, Epson and Zebra, plus your own drivers registered by name or uploaded as a package. Every printer installs from it, so every device stays consistent.

In the console

What your team sees

Real Atlas Spool screens: managed printers and their status, the printers your agents discover, and the driver repository Spool installs from.

Managed printers

Every printer, defined once

Each managed direct-IP printer with its address, protocol, driver and status. Open one to assign it by host pool, session host or device, Reach device group, user or group, and to see its per-device rollout.

  • Optional reachability probing shows which printers are online
  • Assignments and per-device install health on every printer
Atlas AVD screenshot. All names, metrics and values are demo data.

Printer discovery

Found by Atlas Reach, managed by Spool

Reach agents report the printers configured on each Windows device, and the same printer seen by many devices is merged into one entry. Convert any discovered printer to a managed one in a single step, so nothing is typed in twice.

  • Status, model and location for every discovered printer
  • Clear view of which printers Spool already manages
Atlas AVD screenshot. All names, metrics and values are demo data.

Driver repository

A driver catalog, built in

Spool installs from a curated driver repository covering the common universal drivers, and you can add your own packages. A printer whose driver is not in the repository cannot be saved, so a bad driver never reaches a device.

Atlas AVD screenshot. All names, metrics and values are demo data.

How it works

From one definition to every Windows endpoint

1

Create the printer

An admin defines the TCP/IP printer once: IP, port, protocol, and driver.

2

Assign it

Deploy it to a host pool, host or device, Reach device group, user, or Entra group, optionally as the default.

3

Agent installs it

On its next reconcile pass the agent installs the matching printers as direct-IP printers and sets the default.

4

State reported back

Each device reports installed / failed / removed, so operators watch the rollout per device.

Included on every plan

Atlas Spool is part of the Atlas AVD platform: available on every plan, billed by use. It runs on the Atlas AVD Agent already on your session hosts and Reach-managed Windows endpoints (the same agent behind Atlas Reach), so there is nothing extra to deploy. Managed printers are billed by use in units (5 units per managed printer per month, every month the printer exists) drawn from the same pooled monthly unit allowance as the rest of your usage.

No print server to run, patch, or license
Direct-IP over RAW, LPR or IPP
Per-device install health, built in

Questions, answered

How does Atlas Spool print without a print server?

Atlas Spool defines each printer as a direct-IP (TCP/IP) printer. The Atlas AVD Agent on every session host and Atlas Reach-managed Windows endpoint installs the printer locally and print jobs travel straight from that device to the printer over the network (RAW/JetDirect 9100 or LPR). There is no central print server in the path. Atlas Spool never receives, spools, or relays document data; it manages the printer definitions, who they are assigned to, and the install state reported back.

What do I need to run Atlas Spool?

Atlas Spool is available on every Atlas AVD plan, billed by use in units, and it uses the Atlas AVD Agent that already runs on your session hosts and Reach-managed Windows endpoints (the same agent behind Atlas Reach). An admin defines the printers and assigns them; the agent does the rest on each device. Printer installs need the Windows agent; macOS and Linux endpoints are not supported for printing.

How are printers assigned to users and hosts?

Assign a printer to a host pool, a specific session host or device, an Atlas Reach device group, a user (by UPN), or an Entra ID group. On each reconcile pass (every 30 minutes by default, or right away with Refresh printers in Atlas Reach) the agent resolves every assignment that matches the device and the signed-in user and installs those printers, sets the default when one is flagged, and removes printers that are no longer assigned. When several assignments mark a default, the most specific target wins.

Which print protocols are supported?

Direct-IP printing over RAW/JetDirect (port 9100), LPR (515), or driverless IPP and IPPS (631). You pick the protocol and port per printer to match the device. RAW and LPR printers take their driver from the Atlas driver repository, either a built-in universal driver or a package you uploaded, which the agent stages into the Windows driver store; IPP and IPPS printers use Windows' built-in Microsoft IPP Class Driver, so they need no driver package.

How do I know a printer actually installed on a device?

The agent reports the observed install state for each printer on each session host and Windows endpoint (installed, failed, or removed) with the driver or connection error on failure. Operators see this per-device rollout health in the Atlas Spool admin surface, so a printer that could not install (for example a driver that failed to install) is diagnosable instead of silently absent.

Can Atlas Spool report on print usage?

Yes, if you turn it on. Print job collection is off by default and is switched on per tenant in the Settings Matrix. While it is on, the agent on each Windows session host reports each finished job's details: who printed, on which printer and machine, when, how many pages and copies, color or black and white, duplex and paper size. The Usage tab on the Atlas Spool page then shows pages by user, printer, session host, host pool or printer location, with cost allocation from your per-page rates and an optional monthly page quota per user. No document content is ever collected, and document names are kept only if you turn on that separate setting. Quotas warn rather than block, every view and export of the report is audited, and records are deleted after the retention period you choose. It is included in Atlas Spool at no extra cost.

Is Atlas Spool generally available?

Yes. Atlas Spool is available on every plan. It is on by default, and the setup wizard lets you opt out.

Is Atlas Spool available on every plan?

Yes. Atlas Spool is part of the Atlas AVD platform and available on every plan (Community and Atlas AVD), billed by use rather than gated to a tier. It runs on the agent already on your session hosts and Reach-managed Windows endpoints, so there is nothing separate to buy or deploy. Managed printers are billed by use in units (5 units per managed printer per month, in every month the printer exists), and those units draw on the same pooled monthly unit allowance as Atlas Ink, Atlas Reach, and the End User Portal, with more prepaid units available at the standard $1 per unit whenever you need them.

Managed printing, without the print server

Start a free trial of Atlas AVD and see how direct-IP printing lands on your session hosts and Windows endpoints.

Atlas Spool is managed direct-IP printing for Azure Virtual Desktop: assign network printers to host pools, hosts and users, no print server. On every plan.