Universal Print set up requirement

Copper Contributor

Hi,

I am new to universal print. Can someone clarify the below points?

Our tenant is a cloud-based environment with Azure AD & Domain services. We don't have an on- prem AD; Intune manages all our windows 10 devices. We do have an Azure IaaS service.

 

In regards to the Universal print setup,

  • If all my printer firmware are compatible with Universal Print service, Then still do I need to deploy a new Windows 10 / Windows 2016 server for Universal Print connector is that correct can you please confirm? If no servers are required then what will be the next step?

 

  • If the current printer firmware doesn't support the communication protocols that the Universal Print service uses then only I need to provision a new Windows 10 / Windows 2016 server for Universal Print connector is that correct can you please confirm?

 

  • What is the specification required for the new windows 2016 server?

 

  • For example, if I have deployed a new IaaS server in Azure after that before installing the Universal Print connector, Do I need to install all the on-premise individual printer drivers to that new server?
  • The reason we do have around ten printers in different locations; I believe in that case, I need to make sure all those ten printers can communicate from the new server & install those 10 Printers to the new server? Is that correct?

 

  • After printers registered to use Universal Print connector then how can I add the individual printers to the correct connector group?
  • For example, the connector name US Printers, I believe the US printers will display in Azure Portal blade and choose the US printers and add individual printers for US group via the azure portal is that the correct method?
  • What happens if the Universal Print connector Server/service is down, what will be the end-user experience?
  • Is there any option to deploy a Universal Print printer to a Windows device via Intune? If yes can you please share some info.
4 Replies

@Nickson_Easow I will try and answer your questions as a whole. 

Universal Print acts as a Print Service accepting print jobs from clients and sending the jobs to the printers. 

 

Printers that are UP- Compatible would be able to register as AAD devices and be registered in the UP portal. These printers would then be notified and would pull down the print jobs directly from UP. Currently there aren't any UP-compatible printers in the market, but we are partnering with the major print IHVs for future devices. 

 

In the meantime, the Connector service is designed to provide the communication between a Windows Server 2016 or later to publish a locally installed printer to UP. It handles all the notifications and retrieval of print jobs from UP on behalf of the local print queue. You would create the local print queues on the server using a printer-specific driver, and then use the Connector to expose and register those printers with UP. 

 

An on-premise AD is not required. The Connector can be installed on a stand-alone or workgroup machine with the local print queues. The Connector is registered with UP using an AAD account with the Global Admin or Print Admin role. Once the printer is registered and shared, the Connector service, and as such the server it is installed on, must be running for the print job to succeed. There is no fail-over solution at this time for the Connector. 

 

As for pushing out printer connections, we are working on that functionality via Intune and other possible options. 

Thanks@Philip_Demaree 

 

Can you please help me for the below

  • What is the specification required for the new windows 2016 server?
  • I need to make sure all our printers can communicate from the new server & install those 10 Printer drivers to the new server? Is that correct?

  • What happen if the Universal Print connector Server is down or the service is not running, what will be the end-user experience?Is that means users cannot print
  • Any other automated option to add universal printer to a windows device via In tune

@Nickson_Easow Answers in order:

1. No specification, any SKU of Server 2016 should work. It can be stand alone or joined to the domain. 

2. Yes, the printers need to installed as local printers on the same network as the physical devices, so that they can print a test page. 

3. The printer should show as Offline on the client if the Connector or the spooler on the server is not running. Users will not be able to print. 

4. This feature is currently being worked on, and should be available in a future release. 

Thanks a lot@Philip_Demaree. Great help and advise