Forum Discussion

ManagedPrintMax's avatar
ManagedPrintMax
Copper Contributor
May 06, 2020
Solved

Job Owner "System"

Hello There,   When passing through the PrintConnectorApp to a local printer, the username is passing through as "System"   Is there any way to change this to correct username?
  • ManagedPrintMax's avatar
    ManagedPrintMax
    May 11, 2020
    Sorted, the machine needs to be joined to the local AD
DonzaMac's avatar
DonzaMac
Copper Contributor
May 28, 2020

Philip_Demaree 

 

Hi Phil,

 

Is there any desire to change this so an AAD joined machine can pass the UP through to the spooler? We use papercut and need the names passed through for follow me printing. It works currently as the connector is domain joined. We are trying to go full cloud and printing is one of the main things holding us back. Kind of defeats the purpose of cloud print when we need a connector to be domain joined.

Philip_Demaree's avatar
Philip_Demaree
Former Employee
May 28, 2020

DonzaMac Based on my understanding, the issue is that Windows as an operating system still only understands Kerberos (AD) validation, so the Spooler needs to be provided the AD user account associated with the AAD account. Papercut should be able to use the AD account as this is how the legacy Windows Point and Print works. The tricky part is having your AAD/AD Hybrid environment configured correctly so that the association between the AAD account that UP uses and the AD account that Windows uses succeeds. 

 

The Dev team is currently working on how to address this moving forward in regard to a server-less environment that would be AAD-only. Part of this is that the printers themselves need to be able to connect to AAD as AAD-joined devices. The Connector is part of the transition to allow legacy printers to communicate with Universal Print. 

 

Phil

  • SebCerazy's avatar
    SebCerazy
    Iron Contributor
    Jul 15, 2020

    I made sure my Print Server (Server 2019) is hybrid (local AD domain joined & AAD joined)

    Also using Papercut.

    But all jobs sent to local printers (physical or virtual queue) are SYSTEM owned, hence no user can actually release them.

    It worked fine with one early version of connector (0.30.??????)

    Never again. Means nobody can print!

    "Print directly to printer" on the local queue, is NOT possible for virtual queue that holds the jobs till user releases is!

     

    End user devices are ONLY AAD joined

    AAD is SYNCED from local AD, so the whoami always shows the user as it it were AD logged in - MYDOMAIN\myusername

Resources