YES. You must install MultiCHAX on a local Windows machine. It will not work properly if installed directly on the server.

For Remote Desktop (Windows Server 2008, Windows Server 2012, Windows Server 2016 RDP) Users Only:

If you are using RIGHT NETWORKS or CLOUD9 Remote Desktop SaaS (Software-as-a-Service), click HERE.

Note: MultiCHAX can only be used with Remote Desktop machines as a redirected printer. MultiCHAX must be installed on a local machine. You can print from a Windows Server environment and redirect checks to print using our virtual printers.

System Requirements:

1. Remote Desktop Connection (RDC) 6.1

2. Microsoft .NET Framework 3.0 Service Pack 1 (or newer)

3. Terminal Services enabled

4. In the Remote Desktop Properties Connection properties Local Resources tab, Printers should be enabled

To use Remote Desktop Easy Print, you must change the Group Policy default printer driver behavior. The policy setting is located in the following node of the Group Policy Management Console (GPMC):

Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection

NOTE: If you are using the Local Group Policy Editor, “Policies” is not part of the node path.

To edit your local group policy, enter "gpedit.msc" in the Run command.
To edit your domain group policy, enter "gpmc.msc" in the Run command.
To force the local group policy, enter "gpupdate /force" in the Run command.

Before MultiCHAX can be used, the Remote Desktop Easy Print setup must be completed.

To test if Remote Desktop Easy Print is enabled, open the “printers and faxes” section of your remote desktop login and look for printers marked “redirected.” If your local machine printers are NOT visible as redirected printers, Easy Print is not enabled.

Your printers should look like this within the Remote Desktop: