HP ePrint Enterprise Guide de dépannage télécharger pdf (Page 19)

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:

1. Manually enter a valid NT user account.

2. Identify why the service account cannot query Active Directory. The two most common reasons are:

a. The HP ePrint Enterprise service account provided during setup is actually a local machine

administrator account (not a domain account). To address this, use a domain account with

administrator rights instead.

b. The provided HP ePrint Enterprise service account, even if a domain account, does not have

enough, or specific, rights to query Active Directory. You will have to enable this to allow the HP

ePrint Enterprise service to automatically find the user login.

2.2.5 Jobs sent to Secure Pull Printers do not appear under the correct user

2.2.5.1 Secure Pull Print using HP Access Control

HPAC SPP job data properties define the buffer size where HPAC SPP will look for the ePrint-specific job

header (for example, ePrintUserName). By default, the maximum search length for HPAC SPP is set to 255.

This needs to be modified to 4000.

To modify the maximum search length, complete the following steps:

Right-click the HPAC SPP Queue

and select Printer Properties.

Section 2.2 Printing problems 13

1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 43 44

Pas de commentaire

HP ePrint Enterprise Guide de dépannage Page 19