Papercut, single printserver, azure authentication

[pjhunt]

Hi All,

 

We have moved to azure and are struggling to get our printers added as the machines don't authenticate when adding the printers it asked for username and password,

 

When using mobility print which I thought would be the answer our azure credentials are not being accepted so the printer doesn't add,

 

Can anyone offer any advice, it may be easier to have a teams/phone call or just work through on here,

 

In a pickle as schools start back soon and I currently have no printing, universal print doesn't give us the options we need with staples etc so that's not an option unfortunately

[HereIGoAgain2601]

We used PaperCut Print Deploy to get the printers onto the machine - deployed this via intune. PaperCut server then had authentication set to Azure so the users would logon to print deploy with Azure credentials and then the printer would install.

 

Been working really well for the last 12 months.

 

Happy to help you - PM me if you wish.

[snagrat]

We used PaperCut Print Deploy to get the printers onto the machine - deployed this via intune. PaperCut server then had authentication set to Azure so the users would logon to print deploy with Azure credentials and then the printer would install.

 

Been working really well for the last 12 months.

 

Happy to help you - PM me if you wish.

 

So Print deploy still doesn’t SSO the user in and add the printers automatically?

 

We use Papercut in Azure but then use Printix to handle the deployment of the printers to the machines.

[HereIGoAgain2601]

It didn’t when I set this up 12 months ago, but they may have added it now. I haven’t looked again at it as it hasn’t been a major problem for us, everyone has got used to logging onto everything with their M365 account.

[MicrodigitUK]

What domain is the print server on? Is it joined to the local domain?

 

If it is on the local domain then you will need to implement "Azure AD Connect group writeback" to enable Azure devices to authenticate against it.

 

Alternatively you could set up Azure Active Directory Domain Services (Azure AD DS), and join the print server to that. (This is more complex then the Azure AD Connect option, and has Azure costs!)

 

And if the fist 2 options are a no go you can spin up a Linux CUPS server (not-authenticating) using IPP (Papercut Print deploy). And use PaperCut client to do the print job authentication. This Is the option we went for but there is a lot of config to get a CUPS print server working nicely alongside PaperCut client for authentication.