Universal Print Connect 2.4.9459.590 Service keeps stop /start
Hi Support, I installed Universal Print Connector 2.4.9459.590 on a Windows Server 2025 Standard server. The Print Connector Service keeps stopping and restarting. When the service starts, I am briefly able to log in, but it stops again shortly after. I have change the ports to 8095 and that did not help. I verified that the required port is not already in use. Could this be an issue with this version of the connector, or is there anything else I should check or configure? Thank you. netstat -ano |findstr "8091" when I run the program I get this after a quick second i am able to get to the site it will stopUniversal Print for BYOD and Contractor printers
Can we have a new role that is one-time use for adding one printer to UP? Many large organizations have remote workers that already have a printer (e.g. employees, contractors or even franchisees). These organizations want to allow users to print on their own existing (personal) printer but have visibility and management of their print jobs. They want to re-use these existing assets to be more environmentally friendly and be more cost effective. This is especially common for organizations using Azure Virtual Desktop or Windows 365. One way to achieve this is to use the UP connector and convert any BYOD attached printer to a UP one. Yes, this will also require support for Windows 11 Home BYOD also, but let's address the contractor Windows 11 Pro devices first. The challenge is it requires Printer Administrator or Global Admin privileges to install the UP connector, and organizations will not give end users this access. The alternative is to do the old school method of setting up a "managed printer" and shipping it to the end user, but then there is no re-use of existing printers and there is even more management overhead.
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 Connector unable to registert
Hi, today i wanted to make some first steps with the Universal Print Feature. Therefore i've read through the prerequisites and tried to install the Universal Print Connector onto a machine. (I've tried different ones). The installation was working fine, afterwards i've started the software, logged in with administrative credentials, typed in a Connector name and hit "register". Now the following error popped up: The last Eventlog item stated the following error: EventID 8 Register connector start: LMPrint Sending connector registration request... Done Checking Registration status... StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Transfer-Encoding: chunked X-Content-Type-Options: nosniff X-MSEdge-Ref: Ref A: 9E743355D74C45BE9F8B05C81A343E73 Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:53:52Z Cache-Control: no-store, must-revalidate, no-cache, max-age=0 Date: Wed, 07 Apr 2021 07:53:52 GMT Content-Type: application/json; charset=utf-8 } Before this there were some other error entrys. (EventID 8, 1 & 2) The first EventID8 Failed to get valid connector registration status StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Transfer-Encoding: chunked X-Content-Type-Options: nosniff X-MSEdge-Ref: Ref A: 46482393AAE84754943C880672969CAF Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:52:36Z Cache-Control: no-store, must-revalidate, no-cache, max-age=0 Date: Wed, 07 Apr 2021 07:52:35 GMT Content-Type: application/json; charset=utf-8 } {"error":"service_error","error_description":"Failed to register the device with the ADRS. Status: BadRequest, Error: {\"ErrorType\":\"UnknownError\",\"Message\":\"Either objectSid or objectGuid should be set.\",\"TraceId\":\"3840065e-b3e6-4454-9ad9-3726ed10551d\",\"Time\":\"04-07-2021 7:52:32Z\"}","registration_id":"47f13c65-d2b0-46b5-904e-3b57d8af0886","http_status_code":500} One of the EventdIDs 1 Retry 4 Exception: StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Transfer-Encoding: chunked X-Content-Type-Options: nosniff X-MSEdge-Ref: Ref A: 05C88060B428496A8BFDCF20FAD5FEB9 Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:53:27Z Cache-Control: no-store, must-revalidate, no-cache, max-age=0 Date: Wed, 07 Apr 2021 07:53:26 GMT Content-Type: application/json; charset=utf-8 } And the #2 Retry Failure: StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Transfer-Encoding: chunked X-Content-Type-Options: nosniff X-MSEdge-Ref: Ref A: 9E743355D74C45BE9F8B05C81A343E73 Ref B: VIEEDGE1913 Ref C: 2021-04-07T07:53:52Z Cache-Control: no-store, must-revalidate, no-cache, max-age=0 Date: Wed, 07 Apr 2021 07:53:52 GMT Content-Type: application/json; charset=utf-8 } At this moment i absolutely don't know why this happen. DotNet is up to date. (on some devices 4.7.2, on another device 4.8) Server 2019, Windows 10 20H2 Server was onprem joined, Win10 Client was AAD Only The User is licensed with Office E5 and Win10 E5 (In the service plan details is no "Universal Print" visible, is this correct?) The Azure Universal Print Portal shows, that we have a number of printjobs available, so this should work. Any help is highly appreciated. 🙂
Connectors disappeared from Azure after reinstall
After an incident were all our two test UP connectors were stuck (all UP printers were showing "last seen" at least 3 days ago and printing wasn't possible anymore. Prints were working on our print server locally but they weren't delivered to Azure), I had to reinstall them. The procedure itself wasn't as simple as described in https://docs.microsoft.com/en-us/universal-print/fundamentals/universal-print-remove-connector-howto For some reason before the final uninstall I had to remove the connector and updater MSI manually with MicrosoftProgram_Install_and_Uninstall.meta.diagcab as they were stuck, and after that the connector removal was possible. Everything was clean both on the server and azure (no printers shared/registered, no connectors left on azure) After reinstalling, the connector didn't ask for a new name but used the old one, and though I'm able to register and share printers, the connector isn't showing up in azure anymore. I wanted to try by renaming the connector but seems this is still not possible. Any suggestion on how to get back the connectors on azure?
The "service" entity and the communication protocol
Hello everyone, we have doing some research on the API and noticed that the entity "services" has no relation to other entities, like printer or connector etc. We looked into the connections of the "Universal Print Connector Tool" using Wireshark and found that the URLs of the services (eg. https://discovery.print.microsoft.com) ) were in at least one initial TCP packet that was exchanged during a print process. Could you provide a little more information about the "service" entity? Additionally, the documentation talks about "the communication protocols that the Universal Print service uses". Which protocol is this? Is there an RFC for it and how does the authentication against this protocol work? Thanks Dennis
