Configuring of Print Agent for Exchange to print documents on Exchange Server directly

Do you often receive documents and messages that need to be stored on paper? Does your organization stick to archiving certain messages outside the digital environment? Do your customers and partners send plenty of faxes, orders and invoices that are also printed to become part of your business archive? If you answer ‘yes’ to any of the above, you can definitely benefit from a solution that automates the printing of messages and attachments right on the stage of their processing by your company’s Exchange server. The solution is called Print Agent for Exchange.

The ‘Agent’ part is neither a tribute to 007 nor a trade name promoting some kind of alleged superpower; the core of the solution is an Exchange transport agent. In brief, a transport agent is a piece of software that enables installation and use of additional software on your Exchange server to process incoming and outgoing messages. The components of an Exchange server form the so-called transport pipeline consisting of four principal transport services: the Front End Transport service on Client Access servers, the Transport service and the Mailbox Transport service on Mailbox servers, and the Transport service on Edge Transport servers (in Exchange Server 2013). That is to say, every message goes through four main stages of processing, and transport agents make it possible to add a few extra stages to the process, such as anti-virus scanning or, in our case, printing. Both built-in and additional transport agents use SMTP events that are invoked as emails move through the pipeline. SMTP, or Simple Mail Transfer Protocol, is used by mail servers both for sending and for receiving mail.

It is very important that Exchange transport agents encounter messages on the right stages of transportation process. First, you need to make sure that a transport agent is registered to the correct SMTP event. Basically, it is not possible to change order of SMTP events. However, transport agents also have a priority value that is assigned to them within one SMTP event. In other words, a transport agent assigned to the OnMailCommand SMTP event meets messages before an agent assigned to the OnEndOfHeaders event. If there are two transport agents assigned to the OnMailCommand event, say, Agent A with a priority value of 1 and Agent B with a priority value of 2, Agent A gets down to work first because of a lower integer value.

Print Agent for Exchange is a three-component solution that includes a configuration and management console, the transport agent, and a printing service. The management console can be installed on any of your in-house computers or servers, and the transport agent, as we have stated above, is installed on an Exchange server. What is more, you can deploy Print Agent for the entire organization, including all Exchange servers and workstations, from a single computer with the help of a deployment wizard. As for the printing service, it can be installed on a few computers to render the Exchange printing process more reliable: if one of the computers is shut down, the service will use other available resources and complete printing of documents and messages. Such simple and yet efficient precaution makes Print Agent a no-failure tool for Exchange printing.

Next, once you have successfully installed all the components, it is time to think of what exactly you need to print from your Exchange server. The product enables printing of messages and attached files, including images, HTML, PDF, txt-files, as well as MS Word and MS Excel files. If you also use Exchange as a fax service, you can include fax messages in the Print Agent routine too. Moreover, the Agent can automatically apply a watermark to PDF files before printing in order to enhance the protection of your documents on paper. Needless to say that you can define the printer you would like to use, number of copies, and a broad range of other print settings.

Furthermore, multiple rules can be configured to print certain types of files from Exchange. You can set up a number of filters using various criteria, such as the contents of FROM or Subject fields, the type of attachment, and so on. First, a condition is created, such as ‘when FROM field contains ‘CEO’’. Second, you choose an action to be performed, for instance, ‘print attachment to printer #4’. And third, some exceptions can be added to avoid printing excessive documents, for example, ‘when CC field contains ‘Jane Smith’’.

In addition to deployment and rules setup, the management console also allows monitoring of transport agents on Exchange servers, including such useful statistics as the number of messages processed, rules applied, and errors encountered. Thus, you can fine-tune file printing from Exchange using a single workstation and a unified console, which makes Print Agent a practical and easy-to-use working tool for organizations that need to optimize printing of messages and attachments.

12 thoughts on “Configuring of Print Agent for Exchange to print documents on Exchange Server directly

  1. We are in an office 365 environment and would like to know if it is possible to use your product on the MS O365 product?

  2. I’m trying out Print Agent for Exchange on Exchange 2016. The installation was successful. It work printing out PDF and other attachments but it will not print out Microsoft office product (like Excel and Word). What do I need to do for it to print MS Excel and Word.

    1. Please note, for printing Office file formats, Open Office needs to be installed on the machine where Printing Service is deployed:
      Microsoft Office will not work for this purpose. Login as the account that runs MAPILab Mail Printing Service and perform a manual test print from Open Office: when running for the first time it displays a pop-up registration window that blocks our processes.

  3. Installation goes perfect, everything installed successfully. But it will not work, when i do refresh the Agent state is corrupt, and i can not find why or a solution to fix.

    1. Hello, please provide us the following log files in our trouble ticket system:
      – ‘service.log’ from C:\Program Files (x86)\MAPILab Ltd\MAPILab Mail Printing Service\Log
      – ‘AgentLog.log’ from C:\Program Files (x86)\MAPILab Ltd\Print Agent for Exchange Agent\Logs

  4. I am interested in trialing the Print Agent for Exchange, please can you tell me if it is compatible with Windows server 2016? I have tried installing a couple of times, but the installer is failing just after I click “Install”. Thanks

    1. Hello, Print Agent for Exchange is officially compatible with Windows Server 2016. The installation issues often involve installing a certain DotNet package, but in order to know for certain – we’ll need more information from you on that issue, preferably in a dedicated trouble ticket:

  5. We are having issues setting up the rules. We are trying to add an account but the software does not find it. I can find my account and I can see the account the account in question in AD and Exchange. I have tried changing the scope to the entire forest and still it does not find it.

    1. Hello Marc! Thank you for your question. Does this happen with only one specific account?
      Our software uses the standard people picker UI control, so that could be a general issue. Could you please submit a ticket in our HelpDesk and attach several related screenshots, so we could troubleshoot this issue?

  6. Hello, it is impossible to select a paper tray as part of the rule, unfortunately. You can specify a paper tray only from the printer settings directly. Please let us know if you have other questions or notes.

Leave a Reply

Your email address will not be published. Required fields are marked *

+ 8 = nine