Connectors working together to provide High Availability

Connectors working together to provide High Availability



 Apr 09 2020
16 Comments (16 New)
In progress

Connectors working together to provide High Availability.

Now one connector is associated to one printer. If connector is down, printing is not possible. Just like similar solution as we have with multiple PTA agents. 

Status changed to: Not planned
Brass Contributor

Definitely should be prioritised if Universal Print is supposed to be used in a production environment.


Should also help with scale-out, as multiple Connectors could process multiple print jobs in parallel, allowing for higher total print throughput. Similar to how the Dynamics 365 Commerce printing solution works, with their Document Routing Agent.

Copper Contributor

Should be one of most important features because, only this way you can remove the need of having Servers at office for printing.

Otherwise you need to install it on device which always has access to printer, after that you need to think how you will handle printing in case that device or agent will fail. In case printing is critical service in your business.


Looking forward for this feature in near future.

Copper Contributor

Is there any update on this feature?

Copper Contributor

Hello Rani,


As also requested by FrankBeckers, could you give us an update on this feature?

The first customer we've introduced this to asked for the High availability function....


So yeah, pretty high prio if you ask me :)


Many thanks



Copper Contributor

Hi @Rani_Abdellatif,


How is this going?


I'm thinking that we'd have the following configuration at a branch


1. Server connector / Desktop connector / UP Appliance (e.g. ezeep) that caters for connector print jobs

2. Server connector in Azure as a Backup for the connector machine if there is a failure.


Printer routing fails over between Primary (Site Connector) to Secondary (Azure / Data Centre Connector)


Could this be catered for?


If design correctly we could have many connectors in a pool with failover / load sharing capabilities.


Primary = One / Many at Branch - Secondary = One / Many at Azure / DC


Hopefully this is the kind of architecture you will have been thinking about.




@FrankBeckers and @David-SpreenICT,


Thank you for following up. There isn't an update at the moment. The feature is indeed on our backlog and we're working as quickly as we can to get to it. I wish I had more information to share. I will keep this page updated as the status changes.


I also would like to bring up the option to consider Universal Print Ready printers. These printers support Universal Print without the need for a connector which makes setup and management much easier. Please get in touch with your printer OEM to find out if you can upgrade the software on your current printers to be Universal Print Ready.


@Stewart Wallace ,


That is a very interesting setup. Although we don't have the failover feature yet, I will check whether there is any reason this setup might not be recommended.  Having said that, I'm not sure it would work with a connector appliance because I assume that the secondary connector would need to be an appliance too. Connectors from different vendors wouldn't work as failover unit.

As I mentioned in my previous post to Frank and David, please consider Universal Print Ready printers to eliminate the need for connectors. Please get in touch with your printer OEM to find out if you can upgrade the software on your current printers to be Universal Print Ready.

Copper Contributor



Thanks for the swift response Rani,


I appreciate that replacing printers with UP Ready printers is the right way to go. I see the connector as something to use in the short term to bridge the gap between the old and the new, many businesses won't be able to justify the expense of changing all printers to support the new tech in one go.


However, business will make strategic decisions around print services in the future to support UP. The way I see it if the connector can accommodate a cost effective, resilient, flexible solution for migration to UP this will enable the removal / reduction of Branch Office Compute resources allowing business to move another piece of the IT puzzle towards the cloud without huge rip and replace projects.


Cheers, I look forward to the developments in this area :)


@Stewart Wallace, thank you for following up!


Everything you mentioned is very reasonable. Just in case I didn't do a good job at explaining the options you have; I want to make sure that one piece of the information is clear. 

In many cases, you don't need to buy new UP Ready printers to get rid of connectors. Many printer manufacturers released (and are planning to release) software /firmware updates for existing printers that make these printers UP Ready. If such upgrades are available for your current printers, I strongly suggest considering taking that approach. For printers that don't have an available upgrade, then the connector is the way to go.

Copper Contributor

I haven't seen any Product Microsoft launch without having HA. Quite surprising to know they have launched UP. It's a single point failure. Much needed feature as printing is always a headache.

Copper Contributor

Hi everyone, I am planning to move one of our clients from Print Server to Universal Print and they have multiple sites. It seems like I have to have separate windows server running for each site and connected to the network with VPN. We are in a phase of moving the client from domain joined to Azure. Any information would be much appreciated if someone enrolled universal print for a client with multiple sites. 

Copper Contributor

This would be a really great feature to have implemented. I'm working on a setup right now that has many existing non UP supported printers that we want to use with UP.


I'm still playing around with the best options but I'm thinking the best options will be to have two print connectors on the network with the printers and register each printer twice, once from each connector, and do something like name the redundant set as Printer X (backup) or similar. It might be tidier to not share the redundant printer(s) and manually share the backups in the case of the main connector going down.


It would be nice if UP could recognize that the printer being shared from both connectors was the same and treat it as the same device in Entra so if one connector were to go down, from a user perspective, nothing would change.

Copper Contributor

This is exactly the kind of feature we want as enterprise customers who are testing out different solutions. We love our PaperCut and another department is testing out PrinterLogic, but we've found that Universal Print might be the best option for our organization if only they were to have options to run connectors either elastically or as multiple non-elastic redundant or highly available machines. Otherwise we would have to run a physical connector at each of our sites or maintain an Azure VM to run the connector for each or groups of sites.


I would also like to make note that using the connectors as a SaaS service would also be acceptable in my opinion!