iPrint Appliance strives to provide a seamless printing experience. Following the practices listed below can ensure a highly efficient and highly available print system.
Print Manager: We strongly recommend not to create an additional Print Manager. The iPrint Initial Configuration Wizard creates a Print Manager. Only one Print Manager per appliance is recommended.
Spam Filters: When using email printing, the print command in the subject line might trigger spam filters. To avoid this issue, configure your email system to allow print-specific emails. Include the approved print users in the spam filter of your email system to prevent unwanted print requests.
Email Polling Interval: By default, the iPrint Appliance server polls the mail server for new email every 30 seconds. If you rely heavily on email printing, you must reduce the polling interval for faster response. However, you must ensure that your mail server is not overloaded by the frequent polling.
DNS Configuration (iPrint Appliance and Remote Renderer): We strongly recommend that you use a DNS resolvable host name for iPrint Appliance and remote renderer. This host name is used by client devices when printing and can cause failures if it is not resolved. The IP address assigned to the iPrint Appliance and remote renderer must have DNS host entry in the DNS server. Ensure that the DNS entries are in the same domain.
Time Sync: It is recommended that you sync the Virtual Machine host and the guest Virtual Machine time to the same source.
Connectivity between iPrint Appliance and External Renderer: We recommend that you have a high-speed connection between iPrint Appliance and the external renderer.
Connectivity between iPrint Appliance and Mail Server: If you rely heavily on email printing, we recommend that you have a high-speed communication link between iPrint Appliance and the mail server, in order to speed up the printing of email jobs.
Applications on Remote Renderer: For best performance, do not run any other applications on the remote renderer machine.
Importing Users from Active Directory Source Using LDAP Sync: You might not be able to import all users from the Active Directory source using LDAP sync. By default, only 1,000 users are returned from Active Directory. This is caused by a default setting in Active Directory that limits LDAP searches to 1,000 results. For more information, see the Microsoft support article: How to view and set LDAP policy in Active Directory by using Ntdsutil.exe.
LDAP Import: Do not create local users under LDAP imported OUs.
Partitions and Replicas Option in iManager: In iManager, you might see the Partition and Replicas option. This feature is not required for iPrint Appliance. Therefore, it is not supported. We recommend that you not use it on the iPrint Appliance eDirectory.
Creating Local Users and Groups in iPrint Appliance: If you want to create a local user or a local group account in iPrint Appliance, ensure that you create the user or group account outside the synced user’s context. This is because when you sync from an LDAP source to iPrint Appliance, the user and group entries are imported into the MySQL database of iPrint Appliance. By default, iPrint Appliance runs a sync to the MySQL database every 8 minutes. If the local user or group account is not found in the MySQL database, the account is automatically deleted during the next sync.
Remote Renderer Fails When Proxy is Enabled: If proxy is enabled on the Windows machine that is running the remote renderer, the renderer might fail to process print jobs. To workaround this issue, you must disable proxy.