MyQ Desktop Client is capable of monitoring all the print jobs printed over the host computer, and even receiving the print jobs and forwarding them directly to the desired printer.
It uses the same embedded job parser as the MyQ server, so it is able to provide the same level of accounting for locally printed jobs. It can also apply all the rules related to the print job policies, project accounting, and payment accounts.
Print Job Security
The print job security feature allows you to set up a time (in seconds) to log the user out as soon as the client gets to the idle state. If the option to delete all the pending jobs once the client is idle is enabled, that’s another step to protect your users and their print jobs.
With the Client Spooling feature enabled, users' print jobs are not sent to the MyQ server but stay stored at the users' computer. After they authenticate at a printing device and select the jobs to be printed, the jobs are released from the computer directly to the device. This method dramatically decreases traffic to the MyQ server and is suitable especially for small offices with limited network connection to the MyQ server.
When a user prints their job while this feature is activated, only the print metadata are sent to the server and the actual print job does not leave the computer (in fact, it is stored there as a RAW file). It waits until the user is authenticated at a printing device and selects to print the job there. Then, the printing device notifies the server, the server notifies the computer, and the computer sends the job to the printing device where it is printed.
There is a dependency on queue types:
A job from a Direct queue is printed immediately.
A job from a Pull-Print and/or Delegated queue waits until the user has selected it.
A job from a queue marked as private is deleted immediately after printing.
For further information, see Client Spooling in the MyQ Print Server guide.
Be aware that when MyQ Desktop Client receives a job, only the metadata for this job are sent to MyQ.
The data file of the job is stored in MyQ Desktop Client on the machine. There is a limitation that job parameters as Color, Copies, and Format are not transferred to MyQ.
The protocol used for Client Spooling is decided by the Protocol setting in the corresponding MyQ Queue. Supported protocols are RAW, LPR, IPP, and IPPS.
Client Spooling is not available on Kyocera Embedded Lite devices.
Local Print Monitoring
MyQ Desktop Client is able to monitor the number of printed pages on devices connected locally via a parallel port or a USB port. In such cases, the number of printed pages is extracted from the print spooler as it is being processed by the print driver. If the job is rejected due to breaking the policies or insufficient balance, the reason for rejection is reported to server.
If Credit or Quota (cost) is used, then a Price List needs to be assigned to the 'No Terminal' configuration profile.
LPM is supported on LPT, USB, TCP/IP and IPP ports. Monitoring of other ports may work, but it is not guaranteed.
LPM does not work properly with a printer that has the Keep printed document option enabled in the Advanced printer properties.
LPM does not work properly with a printer that has the "Enable advanced printing features" option enabled in the Advanced printer properties. This option is automatically switched off (if possible) for all monitored printers when LPM starts.
For further information, see Monitoring local printers in the MyQ Print Server guide.
Secure Printing (LPR over TLS)
With secure printing enabled, print jobs are sent from MyQ Desktop Client to the MyQ server over the TLS security protocol. This allows printing over MyQ to be end-to-end encrypted. A must in environments where confidential data are often printed.
Offline Operation (LPM and Fallback Printing)
The administrator can setup how the MyQ Desktop Client should behave if the connection to MyQ server is interrupted: automatically printing all the local jobs despite restrictions, rejecting the jobs if the user had any restrictions before the server was disconnected, or strictly rejecting all the jobs.
When using Local print monitoring or Offline accounting in MDC, local printers are automatically created with @ at the beginning of their name.
In case of Local Print Monitoring, it is the name of the port being monitored by MDC.
In case of offline accounting, it is the name of the PC.
The purpose of creating these local printers is that the print job can be accounted but since they were not printed on a printer that is monitored by MyQ, a local printer is created.