HP ePrint Enterprise Channel Multi Server 5000 User E-LTU Manual de usuario descargar pdf (Pagina 16)

http://technet.microsoft.com/en-us/library/bb310786(v=exchg.141).aspx

Information about controlling TNEF for Exchange Server 2013 can be found here:

http://technet.microsoft.com/en-us/library/bb310786(v=exchg.150).aspx

2.2.4 Jobs sent to Secure Pull Printers are correctly submitted, but do not print

A job sent from client to a secure printer (HPAC, SafeCom, Pharos, Nuance Equitrac, or Ringdale FollowMe),

correctly rendered (HP ePrint Enterprise server responds positively, and is able to send job to remote

Windows queue), but user is unable to retrieve it at the printer.

This usually happens because the jobs are not sent directly to a printer, but to a Windows share, which then

tries to authenticate users that must pull the job at the printer, given his/her credentials. For this to happen,

the job must be sent with proper user identification in form of PJL (Print Job Language) attributes, which are

embedded in the job. These attribute headers should look more or less like this:

@PJL SET ePrintEmail = "[email protected]"

@PJL SET ePrintNTAccount = "DOMAIN\john.doe"

@PJL SET ePrintUsername = "john.doe"

@PJL ENTER LANGUAGE=PCL

When users are auto-provisioned in the database (see auto-provisioning settings), every valid email address

that arrives at the server is considered a valid new user, which is then automatically inserted in the database.

The HP ePrint Enterprise service account then tries to query the Active Directory with this email address,

looking for that user domain\login information. Whenever this fails (i.e., the HP ePrint Enterprise service

account specified during setup is not authorized to query the Active Directory), the user is provisioned in the

database WITHOUT domain\login information.

To verify this condition, simply enter the administration console and look for the user that experiencing the

problem. Check whether or not the “NT User Account” field is provided:

If “NT User Account” is empty, then the PJL header is probably generating like this:

@PJL SET ePrintEmail = "[email protected]"

@PJL SET ePrintNTAccount = ""

@PJL SET ePrintUsername = ""

In this case the Windows queue receives the job correctly, but the secure pull printing solution cannot identify

the originating user, and therefore can’t retrieve it.

Complete the following steps to correct this:

10 Chapter 2 HP ePrint Enterprise Server

1 2 ... 11 12 13 14 15 16 17 18 19 20 21 ... 38 39

Sin comentarios

HP ePrint Enterprise Channel Multi Server 5000 User E-LTU Manual de usuario Pagina 16