About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Hosting the application server does not usually move the physical printer off the wall. Invoices, pathology labels, warehouse pick lists and signed PDFs still exit through devices on office or branch LANs. Migration planning for printers and scanners means listing every workflow that touches paper or TIFF, deciding whether printing runs from the hosted session or a local agent, and testing before users discover gaps on Monday morning.
Why it matters
Print problems are a common early hypercare theme after go-live because they feel personal: "my desk cannot print" reads as total outage even when the ledger balances — editorial observation, not ticket statistics. Scanners tied to DMS or LOB import folders can fail quietly until a backlog of unprocessed mail appears.
This article does not assert Easy Print behaviour for your session-host build — confirm printer redirection on your Windows Server and client combination before cutover. Steady-state redirection design is covered separately in the redirection article linked below — this article is the migration inventory gate.
Material difference from published coverage: Clipboard, drive and printer redirection: choose the channels users need covers steady-state redirection choices. Print Spooler crashes on Remote Desktop hosts covers spooler faults. This piece is the pre-cutover workflow matrix across sites and device types.
How it works
Build a device–workflow matrix before cutover. Hypothetical examples only:
| Workflow | Device location | Initiated from | Protocol/driver | Owner | Test script |
|---|---|---|---|---|---|
| Accounts invoice PDF | Office MFP (example) | Hosted LOB | Session redirection | Customer IT | Print sample PDF |
| Warehouse labels | Dock VLAN label device (example) | Hosted LOB | Often proprietary; redirection may fail | Customer + app vendor | Print test label |
| Mailroom scan-to-folder | Mailroom scanner (example) | Local utility or LOB | TWAIN / vendor agent | Customer | Scan batch to folder |
Microsoft documents printer redirection per Remote Desktop client (Compare Remote Desktop client features across platforms and devices; Peripheral and resource redirection over the Remote Desktop Protocol). Editorial / practitioner: migration planning may also use network printers reachable from the session host or a print server still on-prem — those paths are not described on the Microsoft client redirection pages. Editorial: scanners are often local-first — a workstation agent uploads to the hosted app — and TWAIN inside RDP should not be assumed without vendor evidence.
Discover Universal Print describes a cloud print service that uses Microsoft Entra ID for identity and has printers registered with Universal Print in the cloud; users need not be on a specific network. It is not the same as session printer redirection. If Universal Print is in scope, plan it as its own workstream aligned to Microsoft's Universal Print documentation — not as a drop-in substitute for redirection in the matrix above (connector deployment is outside what this overview page describes).
Sequence with network planning: printers on isolated VLANs need routes and DNS so hosted sessions can see the queue. Firewall rules between hosting private network and printer subnets are customer/provider joint work — name owners in your residual RACI for office-side duties.
What to choose and why
Choose pilot printing from hosted sessions during UAT, using the same client type production will use — browser client limits differ from native RDP (see the redirection article).
Choose keep a local print server when redirection fails for label devices or when the vendor supports only LAN queues.
Choose defer scanner migration when the vendor has no hosted-compatible agent; document interim manual upload with expiry date.
Read next
Related articles you may want next.
- HostingWhat the office network still owns after applications move to hostingMoving applications to hosting still leaves office networks, printers and internet links to manage. Identify who maintains each connection and responds when staff cannot work.Read article
- HostingClipboard, drive and printer redirection: choose the channels users needA practical policy and pilot checklist for RDP clipboard, local files and printers, including restrictive-setting precedence and client-specific support.Read article
- TroubleshootingPrint Spooler Crashes on Remote Desktop Hosts: Driver ChecksPrint Spooler stops on a Remote Desktop host? Gather crash evidence, check spool files and driver isolation modes, and keep Point and Print protections on.Read article
Risks and limits
Driver mismatch on session hosts. Editorial: common office lasers may work with redirection; industrial devices may not — confirm with vendor and pilot.
IP changes after VLAN renumbering. Queues pinned by IP break when DHCP scopes move during office tidy-up.
Multi-site variance (hypothetical). One site's label workflow may work while another fails — test per site.
Spooler crashes. See the published spooler article; not repeated here.
Related: VPC networking when print paths cross private hosting networks.
Sources
- Microsoft Learn — Discover Universal Print — Entra identity; printers registered with Universal Print.
- Microsoft Learn — Compare Remote Desktop client features across platforms and devices — printer redirection per client.
- Microsoft Learn — Peripheral and resource redirection over the Remote Desktop Protocol — RDP redirection including printing.
- NetLeverage — Clipboard, drive and printer redirection — steady-state overlap; browser versus native printing.
Learning notes
- Printers and scanners usually stay on the office LAN after the app server moves.
- Build a workflow matrix, not just a device list.
- Editorial: redirection helps many office lasers; label and scan paths often need agents — verify per workflow.
- Universal Print is not the same as session redirection.
- Test from the same client channel you will use in production.
This article was originally published on .