We are using Terminal Server's Easy Print function and are having trouble printing Mekorma checks.
The Mekorma print engine is not supported with the Microsoft EasyPrint driver. Please change the EasyPrint driver policy to first find a suitable printer driver to install to the target printer. The Mekorma Print Engine makes API calls for the Mekorma print job that other applications do not call. Also of consideration, there is a layered system where the .net print document class, operating system and local print driver require information to be translated. The Microsoft EasyPrint driver likely provides instruction the printer cannot understand based on the way our software utilizes the API and communication among software components. Please use the printer manufacturer's native print driver and disable the Microsoft EasyPrint driver in order to print Mekorma checks.
Configuring the Group Policy:
Log in as Admin and go to the Group Policy settings that have been added for Terminal Services printing. These policy settings are located in the following node of the Local Group Policy Editor: At the start key type gpedit.msc
The path is: Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection
To: For Use Terminal Services Easy Print printer driver first <-- We recommend that you set this to: Disabled
Disabled: If you disable this policy setting, the Terminal Server will try to find a suitable printer driver to install to the client printer. If the terminal server does not have a printer driver that matches the client printer, the server will try to use the Terminal Services Easy Print driver to install the client printer. If for any reason the Terminal Services Easy Print driver cannot be used, the client printer will not be available for the Terminal Services session.
3. Log out and log back in.
4. Once you log back in you will see that your printer is using its native print driver (from Control Panel), and Mekorma MICR checks will print.
The technical website for this information is: http://technet.microsoft.com/en-us/library/cc753853(v=ws.10).aspx
Please note:
A policy value set as "Not Configured" will IGNORE any previous settings made by policies lower in the chain.
So if your LOCAL policy sets a Target Group, and your Organizational Unit policy has client-side targeting (and group names) set to "Not Configured", the LOCAL policy setting will remain in force.