One of the essential functions of the MyQ Desktop Client application is to identify the MyQ user on the computer where it is installed. Thanks to this identification, MDC can mediate communication between the user and the MyQ server; it can inform the user about the state of their account, it enables the user to manage their print jobs, and it also enables the server to determine the job sender.
Once a job is sent to a queue, the status changes to Paused and the user is set to *unauthenticated until they authenticate themselves in MDC. Once they do, the job's status changes to Ready and the user changes to the now authenticated job owner. If the authentication in MDC fails or if the user is not present in the MyQ server, the user is no longer created (needs to be created in MyQ) and the job is rejected.
Depending on how MDC was set up, the user is either identified as the currently opened OS account or they can identify themselves. The self-identification methods are described in:
The login options are selected within the MyQ Desktop Client setup. If you do not want the users to identify themselves, select the a-2 method.
For each of the user identification options you need to set up a queue on the MyQ server, with the appropriate user detection method:
Windows single sign-on -> Job sender
Login by PIN or Card -> Prompt for a PIN/Card
Login by Username and Password -> Prompt for a user and password
User List -> Prompt to select a user from a list
For information on how to set up the queues, see User detection methods in the MyQ Print Server Guide.