MicrosoftI've just created a proof of concept test environment with Universal Print (UP). Some comments...
Having no issues discovering printers on my test devices however, to be completely honest, the process to deploy and update the printers.csv file via Endpoint Manager has been nothing short of an unreliable and clunky mess. The initial deployment of the printers.csv file works perfectly fine, however, some devices get the printers installed (after quite some time - 2 hours in my testing) and some devices simply don't, even after manually running syncs through both Endpoint Manager as well as on-device. Trying to push updated printers.csv files to devices is also unreliable. Not to mention, the process of manually managing a printers.csv file just seems so backwards and archaic.
I've also been testing another solution (Printix) on the side. It's miles more mature than UP, specifically in the amount of granularity and control (networks, groups, permissions, auto add/remove printers) and changes made work almost IMMEDIATELY on all of my devices and RELIABLY.
UP has a lot of potential, but A LOT of work needs to be done on the auto deployment component; it's unfortunately not ready for prime time. If any UP product manager is reading this, I'd recommend taking a good hard look at how Printix and other third-party solutions are doing auto deployment.
I'm having an internal meeting with my staff on cloud print implementation later this week and as much as I hate it, will recommend against using UP at this time.
