Forum Discussion

JoeMatthews's avatar
JoeMatthews
Copper Contributor
Jul 06, 2020

Issues with Universal Print from 3rd July

Hi, We were running a successful install but last Friday we started getting aborted prints for no apparent reason. We are running the lastest build of the print connector. At the moment, no jobs wi...
JoeMatthews's avatar
JoeMatthews
Copper Contributor
Jul 07, 2020

Many thanks Saurabh_Bansal 

I have run version as suggested but we are still seeing jobs with the owner as 'SYSTEM'.

We have an issue with our support agreement which MS are struggling to correct so if anyone has any ideas in the meantime I would really like to hear from you.

 

Joe

Saurabh_Bansal's avatar
Saurabh_Bansal
Icon for Microsoft rankMicrosoft
Jul 07, 2020

JoeMatthews - Wasn't very clear from the initial post that this was related to username :).

 

When using third-party software, we typically recommend partners to provide their own version of connector which can extract username from the Universal Print service.

 

Microsoft's connector runs as a SYSTEM process and thus forwards the job as SYSTEM. There are a few scenarios where connector may send the actual username forward provided connector is joined to local active directory and impersonation is enabled. Impersonation converts the Azure AD username to local active directory username.

 

Impersonation is not recommended and currently unsupported since it can be very complex to set it up and also required presence of local active directory which defeats the purpose of moving to cloud :).

 

You may want to work with PaperCut to identify if there is an alternate option.

 

Resources