Universal Print defaults to letter instead of A4 size on client PC's. Does not correct during print
Hi, Not sure if it makes a difference but running a Sharp MX4141N and MX5070N through the connector software with the UD3 Driver. (Have tried with other drviers) By default when the Universal Print printer is installed on users computers (Via an Intune Policy) the paper size defaults to Letter instead of A4. This means that when a user prints they need to go up to the printer and tell it to change print size to A4. The document printing is in A4 Changing the paper size in Printer Preferences -> Advanced fixes this: But it is a manual process I want them to provision with the correct paper size. Any help would be appreciated.Universal Print Available for Windows 10 Business?
Hello, I noticed Universal Print is only available for Enterprise and Education tenants while in private preview. Will this also be made available on tenants running Microsoft 365 Business? The majority of our SMB clients are migrating to Microsoft 365 Business and could really benefit from this feature. I would be happy to drop 3rd party if this works. Regards, DaveGeneral availability of Universal Print in GCC/GCC High
We are excited to announce that we are bringing Universal Print to government organizations with the general availability of Universal Print in GCC/GCC High. Universal Print in GCC/GCC High aims to offer full feature parity with what exists in the commercial cloud today. To learn more, please view the announcement blog or sign up for the upcoming webinar on October 11th.
Universal Print Connector Version. Print Jobs stuck in pending
Issues with Universal Print from 3rd July - Microsoft Tech Community Saurabh_Bansal What updates are in the latest build of the connector that you linked? (1.26.7633.377) Is there a reason why it isn't released yet like bugs and such? We are running the "current" latest build 1.14.7564.21701 and we are still having issues with print jobs getting stuck in pending. I already submitted a ticket through Azure and the agent said it was a known issue that will be fixed in the future. Was wondering if this new connector would resolve it but you replied about 5 months ago so I'm wondering if there's a better version that is "not released". Thank you!
