Printer Fleet (Canon + HP)
Overview
Section titled “Overview”Status: active, pilot phase, ring rollout planned. Migrating TCR’s printer fleet off the district-owned legacy print server (Windows Server 2012) to direct TCP/IP printing, deployed via Atera RMM PowerShell scripts on the Windows side and Mosyle on the Apple side. Scope: roughly 150 Windows workstations, plus student Chromebooks. Meraki is also in use on the network side.
Why it exists
Section titled “Why it exists”Two separate problems drove this migration:
- The legacy server itself is a liability. It’s district-owned (not TCR’s), runs Windows Server 2012, and Group Policy Objects (GPOs) pushed through it don’t work reliably.
- A print-server architecture is the wrong fit for TCR’s shape. Centralized print servers make sense for a multi-site district managing many campuses — but TCR is a single, all-internal site. Configuring printers directly at the device/browser level is actually simpler for TCR’s situation: it gives more granularity per printer, and can be fully managed through tools TCR already runs (Atera for Windows, Mosyle for Apple), without depending on district-owned infrastructure at all.
The migration has begun: moving devices off the server and onto static IP addresses. Static IPs matter especially for student Chromebooks, which need direct network-level printing rather than a Windows print-server driver relationship.
Rollout methodology
Section titled “Rollout methodology”Single machine → pilot → department → fleet.
Models
Section titled “Models”- Canon imageFORCE C5150 — pilot unit, nicknamed “Breakroom Printer.” Driver zip hosted at
printer.tcrtek.org(Cloudflare R2). Pilot IP moved from10.88.144.5to10.5.0.90. - HP Color LaserJet CP5225n — being added using the same Atera direct-IP PowerShell pattern.
Networking notes
Section titled “Networking notes”- Requires confirming printer static IPs, inter-VLAN routing on TCP port 9100, and Canon driver standardization before scripting the fleet-wide rollout.
- The pilot printer showed offline in Meraki due to a downed link on TCR-Core-3 port 25 — needs physical cable/switch port verification.
- The printer likely needs to move onto the workstation VLAN to resolve segmentation issues.
Vendor coordination
Section titled “Vendor coordination”Coordinated directly with the printer vendor and a district contact (Colter) on delivery logistics and advance-notice requirements.
Excluded programs
Section titled “Excluded programs”Welding, Phlebotomy, BLS, Heartsaver, CPR, and Nurse Aide are excluded from the current rollout pass — deferred to a later phase, consistent with how these programs are excluded system-wide (see the Systems Overview).
Access
Section titled “Access”Not yet documented: Atera script repository location, who can push new printer deployment scripts.
Dependencies
Section titled “Dependencies”Depends on Atera for Windows script deployment, Mosyle for the Apple-side configuration, and Meraki for network-side visibility/VLAN configuration. Explicitly does not depend on the district-owned print server or District AD — that’s the point of the migration.
Backup & recovery
Section titled “Backup & recovery”Not applicable in the traditional sense — driver files are hosted on Cloudflare R2 (printer.tcrtek.org), which is durable object storage.
Digitized from working notes (2026-08-19).