In a corporate WAN environment, map the printers over the domain/network, don't use them as redirected printers, it makes a huge difference.

most of our users are using VPN and RDP from various locations around the world so what you are suggesting won't work right?

You're using a VPN right, so why can't you map the printers?

Anyways.... the big difference is the size of the print files generated by Sage 300 vs Word or anything else. People love adding huge logos to their invoices and then wonder why the reports take so long.

You can look at Google Cloud Print www.google.com/.../learn as an alternate to access remote printers, we used this with one client with great success.

Which version (and update) of Sage 300 are you using?

we're still on version 2012 PU 4.  Planning to go to latest version early next year.

No, we don't have any images or such things added to reports. Just printing standard ones.

I feel like an idiot asking this but what exactly do you mean by mapping printers?  Is it this process?  Seems rather complicated if it is. 

Workaround Solution: Client to Server Print Driver Mapping

To address this, it's possible for you to correlate the names of printer drivers on your server with the names of printer drivers on your users' clients. For example, you can tell the server that the client print driver “Hewlett Packard LaserJet 5P” is the same as the server print driver “HP LaserJet 5P.” Keep in mind that you only need to do this if (1) you are using client printer mappings and (2) your clients are not running Windows 2000 or Windows XP.

In order to enable printer driver mapping, you need to place a file on your Terminal Server that contains the pairs of client and server driver names. In previous versions of Terminal Server, this was done via a mapping file called “ wtsuprn.inf ” located in the %systemroot%\system32\ folder. However, this file does not exist by default in Windows Server 2003, and Windows does not look for it.....

I'll definitely take a look at the google cloud print option so thanks for that tip.

Ok basic networking: you can share a printer on a network, how depends on the printer and how it is attached to the network. If the printer is attached to a computer then you would type in \\computername\printername and you should see the printer. In printer properties you can set the port to \\computername\printername, or an IP address depending on how the printer is configured - in networking lingo that is refered to as mapping to the printer.

If you have a VPN connection to your TS then on the TS you can still see your network resources since you are connected to the same virtual network.

have you had a look at  print2RDP by blackice

www.blackice.com/Print2RDP.htm