Universal Print - Initial Thoughts

%3CLINGO-SUB%20id%3D%22lingo-sub-1333392%22%20slang%3D%22en-US%22%3EUniversal%20Print%20-%20Initial%20Thoughts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1333392%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20ran%20through%20the%20setup%20today%2C%20super%20simple.%20I%20think%20the%20Azure%20portal%20blades%20make%20sense%2C%20the%20Connector%20is%20simple%2C%20etc.%20We%20had%20things%20up%20and%20running%20for%20testing%20without%20much%20issue.%20I%20printed%20to%20a%20colleague's%20home%20office%20printer%20within%2015%20minutes%20of%20starting%20the%20task%20-%20instant%20gratification.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20real%20value%20is%20when%20printer%20manufacturers%20adopt%20the%20required%20firmware%20changes%20(TLS%2C%20OAuth%2C%20etc.)%20to%20have%20a%20network%20printer%20natively%20compatible%20instead%20of%20requiring%20the%20Connector.%20Trading%20a%20Print%20Server%20for%20a%20Connector%20helps%20in%20limited%20use%20cases%2C%20but%20eliminating%20both%20with%20a%20Universal%20Print%20compatible%20printer%20is%20the%20end%20game%20people%20want.%20It%20is%20also%20the%20only%20way%20to%20get%20to%20true%20%22%3CSPAN%3Edoesn't%20require%20any%20on-premises%20infrastructure%3C%2FSPAN%3E%22%20status%20in%20my%20mind.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20TAP%20program%20for%20any%20of%20the%20printer%20vendors%20where%20we%20can%20try%20out%20and%20provide%20feedback%20on%20their%20new%20firmware%20updates%3F%20We%20have%20every%20manufacturer%20of%20printer%20out%20there%20it%20seems%2C%20so%20if%20any%20have%20programs%2C%20we%20would%20want%20to%20be%20involved.%20Can%20someone%20at%20Microsoft%20point%20us%20in%20the%20right%20direction%3F%20We%20are%20part%20of%20many%20partner%20TAP%20programs%20and%20have%20all%20the%20NDA%20pieces%20in%20place%20already.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Visitor

We ran through the setup today, super simple. I think the Azure portal blades make sense, the Connector is simple, etc. We had things up and running for testing without much issue. I printed to a colleague's home office printer within 15 minutes of starting the task - instant gratification.

 

The real value is when printer manufacturers adopt the required firmware changes (TLS, OAuth, etc.) to have a network printer natively compatible instead of requiring the Connector. Trading a Print Server for a Connector helps in limited use cases, but eliminating both with a Universal Print compatible printer is the end game people want. It is also the only way to get to true "doesn't require any on-premises infrastructure" status in my mind.

 

Is there a TAP program for any of the printer vendors where we can try out and provide feedback on their new firmware updates? We have every manufacturer of printer out there it seems, so if any have programs, we would want to be involved. Can someone at Microsoft point us in the right direction? We are part of many partner TAP programs and have all the NDA pieces in place already.

 

Thank you.

0 Replies