Hybrid Print Server Infrastructure with Universal Print
Planning and introduction to the deployment of a centralized and secure print server using Windows Server and Microsoft Universal Print.
This technical documentation details the deployment, configuration, and troubleshooting for the implementation of a Hybrid Print Assistant. The main objective is to connect the physical fleet of local devices with the Microsoft Universal Print cloud service suite, optimizing security and centralizing print queue management.
1. Architecture and Critical Limitation of Windows Server Core
Sección titulada «1. Arquitectura y Limitación Crítica de Windows Server Core»During the infrastructure design, the use of Windows Server 2022 Core (without a graphical interface) virtualized on Proxmox VE was evaluated to minimize resource consumption. However, after exhaustive engineering tests, an insurmountable critical limitation was identified:
Universal Print Limitation in Server Core
The official Microsoft Universal Print connector strictly requires a user interface (GUI) to complete the interactive registration and secure login process (OAuth 2.0 / MFA) in the Microsoft Entra ID (Azure AD) Tenant. Since the connector lacks 100% integrated command-line interface (CLI) login tools without a UI, it is impossible to register the connector if the system is a Windows Server Core.
Therefore, the final production architecture strictly requires deployment on Windows Server 2022 with Desktop Experience (graphical interface / GUI).
This guide documents both the basic network/print service installation (which is compatible with Core and useful for other environments) and the mandatory final migration to the version with a graphical interface to successfully complete cloud connectivity.
2. Infrastructure Map
Sección titulada «2. Mapa de Infraestructura»Network Topology and Segmentation
Sección titulada «Topología de Red y Segmentación»- Local Network Segment:
192.168.10.x/24(Subnet dedicated to servers and network printers). - Identity Model: Hybrid (Workstations in Azure AD and Server in local Workgroup).
Server and Identity Matrix
Sección titulada «Matriz de Servidores e Identidades»| Device Role | Hostname | IP Address | Operating System | Description and Status |
|---|---|---|---|---|
| Hypervisor | proxmox-nodo-01 | 192.168.10.10 | Proxmox VE 8.x | Physical server hosting the virtual environment. |
| Print Server | w-server-2022 | 192.168.10.22 | Windows Server 2022 GUI | GUI required to host the Universal Print Connector. |
| Admin Station | pc-admin-01 | 192.168.10.100 | Windows 11 Pro | Management client (Joined to Azure AD). |
| Printers | Miscellaneous | Static Addresses | Ricoh / Zebra | Corporate physical network devices. |
3. Deployment Prerequisites
Sección titulada «3. Prerrequisitos de Despliegue»Before proceeding with the installation modules, ensure you have the following resources available:
- Official ISO: Windows Server 2022 Standard or Datacenter with Desktop Experience.
- Stable VirtIO Drivers: ISO File
virtio-win.iso(Essential for enabling disks and network adapters in Proxmox). - RSAT Tools: Installed on the management station (Especially the “Print Management” graphical console).
- M365 Licensing: Active Universal Print license with a contracted and available monthly print volume.
- Cloud Permissions: Global account with the Print Administrator role in Microsoft Entra ID.
4. Logical Interaction Diagram
Sección titulada «4. Diagrama Lógico de Interacción»graph TD User["Estación Admin (Entra ID)"] -->|WinRM / CredSSP / RSAT| Server["Windows Server (GUI - Workgroup)"] Server -->|TCP/IP Raw / LPR| Printers["Impresoras Físicas (Ricoh/Zebra)"] Server -->|Registro Interactivo GUI / HTTPS| Azure["Nube Microsoft Universal Print"]
