Forum Widgets
Latest Discussions
Universal Print Connector App browser is not supported in Windows Server 2022
I'm trying to install the Universal Print Connector app on a VM running Windows Server 2022 and am getting the message below. It seems that the app is using IE despite Edge being the default browser. AI recommended using WebView2 Runtime to fix this however I had no success with that. Any solutions would be very much appreciated!willrsSep 09, 2025Copper Contributor22Views0likes0CommentsUniversal Print queries
Some simple queries but just wanted some clarification before confirming with the customer. Connector for printers that aren't cloud ready, is it accurate that this is included in the license and there is no additional cost for this? Zebra printers with lots of different label sizes, how user friendly is this set up? Jobs to be very clear if an operator prints a label but wants 99 of that label, this is classified as one job?RJ1982May 23, 2025Copper Contributor46Views0likes0CommentsQuestion: What is the behind-the-scenes process when a network printer is installed?
Quick background: I work for an MSP providing Tier I support to Ricoh printers at a large healthcare facility. The enterprise has not moved to Universal Print - yet. I want to better understand the end-to-end process as it is now as I'm sure it will help me when the client begins to adopt Universal Printing. We have a mix of Windows 10 and 11 computers. They still use a print server and I recently had most of the Ricoh printers on it updated so they are associated with the PCL6 V4 Universal Print Driver from Ricoh. There are still a few left with either model specific V3 PCL drivers or the PCL6 Universal Print Driver (which is V3, too). However, the only V4 drivers on the computers are those built into the OS - Point and Print or Enhanced Point and Print from Microsoft. Users aren't allowed to install print drivers from Windows Update. Here's what I think is the process behind-the-scenes: User navigates to Printers & Scanners and clicks Add Printer. User selects the printer and it's installed. The print driver for that printer is associated by the OS searching in C:\Windows\System32\DriverStore\FileRepository for a folder (either oem..... or prnms.......) that is the most compatible. Hopefully its a driver from Ricoh (in my case) but it may be the Microsoft Point and Print driver. When the user attempts their first print with the new printer, some of the contents of the folder above (DLL files primarily) are moved or copied [I'm unsure which] to C:\Windows\System32\spool\drivers\x64\3. I think this is how it works for both V3 and V4 print drivers but would like clarification. I'm aware that the INF file is copied to C:\Windows\INF, and that CAB files for at least some of the installed printers are located in C:\Windows\System32\spool\drivers\x64\PCC. I don't understand the purpose for either of these. As for the process as I described it above, I'd appreciate any and all feedback so that I can better understand the process.Mike6877Apr 23, 2025Brass Contributor86Views2likes0CommentsUnable to share previously share printers after name change
After updating share names, I am unable to reshare printers. I have tested Readding share, different name. Fails. Unregistering and reregistering printer, share fails Error is below, no useful information. How do we resolve this?AshleySaundersApr 03, 2025Copper Contributor53Views1like0CommentsPrinter Sharing Fails for all printers
Just ran into a situation where I cannot share any printers. After I've registered the printer on my connector, I can see the printer on the Azure portal as usual. However when I go share it, I get the error Same thing happens with other unshared printers. I also checked and the printer share names do not exist already. Any ideas?IanXApr 01, 2025Copper Contributor39Views0likes0CommentsUP Connector Servers added to Printer Column List
Would love to see UP Connector names added to the printer list column for easy viewing and management of multiple connectors. Printers serial number, IP address and MAC address would also be great additions to help print admins quickly access printer information without having to cross reference to other sources.Print_Admin_JakeMar 04, 2025Copper Contributor38Views0likes0CommentsUniversal Print anywhere
I have Universal Print setup on a couple of printers, and it actually works really well on Windows devices and even MacOS, using the Universal Print app, detects those share printers and works fine. I have now created a Universal Print Anywhere (Pull Print) share using those same shared printers. Windows devices works well, but MacOS does not detect them. Is that currently not supported on MAC or am I missing something?BHFeb 20, 2025Brass Contributor68Views0likes0CommentsAny printers compatible with GCC High?
I am experienced with MSUP in the commercial tenant. My current employer has a GCC High tenant. It's unclear if any printer manufacturers support registering in GCCH. I see some manufacturers listing GCC but not GCCH but that seems strange as I think just the registration endpoints have to change. Anyone using GCCH know for sure?ta1234Feb 17, 2025Copper Contributor55Views0likes0CommentsMS Universal Print Windows Sockets Error | error=10053
Hello, I am trying to share queue made in MyQ solution into Universal Print but unfortunately after doing so I receive following error MS Universal Print Windows Sockets Error | error=10053, there is so sign of queue in Azure side and in MyQ status of queue is "Printer is being created in Azure". Outbound connection to all necessary endpoints is allowed. Tls 1.2 is on. Any ideas what could be wrong?kubix233Jul 17, 2024Copper Contributor212Views0likes0Comments
Resources
Tags
- universal print22 Topics
- announcements13 Topics
- Universal Print Connector7 Topics
- UniversalPrint4 Topics
- Cloud Print3 Topics
- question2 Topics
- Universal2 Topics
- Paper Size Mismatch2 Topics
- Intune2 Topics
- Ricoh2 Topics