Terminal server printing or TCP/IP

I have been tasked with moving our hosted solution from one provider to another and a question has come up over printing.
Not sure on all the details but this is what I have at the moment.
We currently have our MBS Navision App and database hosted that about 100 users from 7 different locations connect to.
This is hosted by VisionAPP and they use Citrix to connect to the client App. (Looking at moving this to server 2008 RemoteAPP)
The have a VPN tunnel connecting each location to the VisionApp Server.

For printing rather than having loads of redirected printers they have configured TCP/IP printers for each office and they have told me that this saves bandwidth???
My understanding is that the redirected printers will use less bandwidth than TCP/IP printers, but cant seen to find a straight answer.
Who is Participating?
beaconlightboyConnect With a Mentor Commented:
as far as i know redirecting.  Either way you are going to take a hit on performance when print jobs are spooled.
The solution to your problem is driverless printing.  Check out Thinprint.com.  This solution allows you to install a single thinprint driver on the terminal server, and then using thinprint's client application, recieve the print job at the remote site.  The thinprint driver allows you to set the bandwidth used by each port you setup.  This prevents users from experiencing lag during large print jobs.

I have been using thinprint for 7 years and it's great.  We also use microsofts printer export utility to setup all our servers as it's imperative that every terminal server has allt he printers installed on it that each user will need.   visit www.thinprint.com

Just to add some more detail. A typical setup would include

- A terminal server with the thinprint client installed on it.
-- On that terminal server you create thinprint ports.  A port is basically a logical representation of a print queue with bandwidth restrictions.  We have a port for each remote location we have.  We may have 10 printers at that remote site, but they share the same port.  so only 1 job is spooled across at a time.  This is where you save bandwidth.
- At the remote site you setup an XP box with the thinprint client and all the printers installed.  you then map the thinprint client ports to the actual printers.  
DigiPoSUKAuthor Commented:
Will consider thinprint thanks, but what uses les bandwith out of tcp/ip and redirected printing?
DigiPoSUKAuthor Commented:
does anyone else know what uses less bandwith?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.