Windows Ready Print (WPP): lista kontrolna gotowości dla administratorów IT

Inventory every printer with its driver type (V3, V4, or IPP/Mopria), then check each model against the Mopria certified-products directory at mopria.org/certified-products. Mopria-certified models keep working under WPP through the IPP Class Driver. In a typical fleet, 20 to 50% of devices are not WPP-compatible today, so a full fleet audit and migration plan is where the work starts.

Not necessarily. WPP requires Mopria-certified printers or an IPP-capable path, and 20 to 50% of a typical fleet is not WPP-compatible today. You can replace those devices, or you can keep them and move the print driver off the endpoint with cloud rendering. Cloud rendering makes any printer work under WPP, Mopria-certified or not, without a hardware refresh.

There are two broad approaches. One is to make the fleet WPP-native: refresh non-Mopria printers, manage a Print Support App for each manufacturer, and confirm the IPP Class Driver covers your finishing and secure-release needs. The other is to remove print drivers from the endpoint with cloud rendering, so printers work whether WPP is on or off. ezeep uses the second approach, which avoids a hardware refresh.

Microsoft's driver-servicing plan runs on set dates. No new third-party drivers have reached Windows Update since January 15, 2026. Windows defaults to the IPP Class Driver from July 1, 2026, and Microsoft has indicated July 2027 as the target for ending third-party driver support. A practical target is to complete production cutover on eligible endpoints by Q1 2027.

On Windows 11 24H2, any user with local admin rights can turn on WPP from Settings. The moment they do, every managed print queue on that endpoint is removed. Audit local admin rights on 24H2 devices before you start planning, because an early, unmanaged cutover is the failure mode most teams do not see coming.

Yes, if you remove print drivers from the endpoint. Cloud rendering keeps drivers off every device, so printing works the same whether WPP is on or off, with no hardware refresh and no per-manufacturer Print Support Apps to manage. ezeep works this way, which turns the WPP migration into a non-event.

Enable WPP through Group Policy at Computer Configuration → Administrative Templates → Printers → Configure Windows Protected Print Mode. Apply the policy to a pilot OU first, not production. The equivalent path in Intune is a Settings catalog configuration profile under Printers. WPP is admin-controlled, so the policy is the only way to turn it on at scale, and turning it off is just as straightforward if a rollback is needed.

Enable WPP on a small non-critical segment of Windows 11 24H2 endpoints with confirmed Mopria-only queues. Confirm which printers reinstall automatically via the IPP Class Driver, validate advanced print functions (secure release, pull printing, quota systems), apply patch KB5043178 for early known issues, and document any broken workflows before broad rollout. A 60-day pilot window catches most edge cases before they become production tickets.

A practical sequence is: complete driver and Mopria inventory in the next 30 days, pilot WPP on a small non-critical segment in the next 60 days, finish the fleet audit and the refresh-versus-architecture decision by end of Q3 2026, begin production cutover on Mopria-ready endpoints in Q4 2026, and complete cutover on all eligible endpoints by Q1 2027. That sits ahead of Microsoft's July 2027 third-party driver end-of-support deadline with buffer.