In Serverless Pull Printing, a print job is stored on the client machine until a user authenticates at a Celiveo‐enabled device, and pulls the selected job from the client machine to the printer. Serverless Pull Printing removes the need of a central Print Server by moving all the job‐processing activities from the server machine to the client machine, and by caching the client machine details on device hard disk, this feature is known as High-Availability. With this implementation, the user is independent from external services to perform authentication and print job listing.

Serverless Pull Printing makes use of authentication cache and the Pull Printing directory cache (High-Availability) on the device. The Active Directory or SQL acts as the authentication and and the local machine as storage server for the first user session. In the subsequent user sessions, the Serverless Pull Printing architecture uses the Authentication cache as the primary or a failover mechanism to authenticate users (if the Active Directory/SQL server is down) and the Pull Printing Directory cache is used as the primary mechanism for retrieval of the print job from the last used storage client machine.

The authentication cache stores the user details after the first successful authentication through Celiveo Server Services or through the Direct LDAP/AD profile. The device looks up user details from the authentication cache for user authentication if Secure Server Services or the Direct LDAP/AD server is down in the subsequent user sessions.

After the first session, the print job is retrieved using the IP address of the client machine, which is stored in the Pull Printing Directory cache. The print jobs are retrieved from the client machines running the Serverless Pull Printing client software.

Benefits of Serverless Pull Printing

Serverless Pull Printing removes the need of Print Servers by diverting the job processing load on to the client machines, providing a seamless printing experience:

  • The user can be authenticated on the device even when Active Directory or SQL goes down.
  • The user can print jobs, even if the database server that stores print job details is unavailable.
  • The user can be authenticated on the device and can print jobs, even when both Celiveo Server Services and the database server are down.
Last modified: 14 June 2024


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment