asked on
Xenapp 6.5 - printing config
Hi all,
Just configuring a new test farm for Xenapp65. I have just been reading about advances since Presentation 4.5 in regard to printing. In my 4.5 farm I chose to have session printing, but this may not have been the most efficient configuration.
I have about 30 print shares spanning 4 sites (all citrix servers based at one site) mainly HP printers.
I just wanted to see what peoples views were with printing and Xenapp 6.5:
Print drivers - native or UPD?
Session printing or Client Print Redirection?
Just configuring a new test farm for Xenapp65. I have just been reading about advances since Presentation 4.5 in regard to printing. In my 4.5 farm I chose to have session printing, but this may not have been the most efficient configuration.
I have about 30 print shares spanning 4 sites (all citrix servers based at one site) mainly HP printers.
I just wanted to see what peoples views were with printing and Xenapp 6.5:
Print drivers - native or UPD?
Session printing or Client Print Redirection?
Citrix
Last Comment
joharder
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
The CPR will compress the data via citrix and send it through the ICA session. It will use less bandwidth this way.
Depending on your remote sites and how they are configured. You can use session printing which is what we are doing because we have all thin clients out in the field and cannot map printers easily to the clients for CPR.
What we ended up having to do though is tunnel the traffic through a different pipe and QOS it.
Just keep in mind session printing is going to use a ton of bandwidth to the remote sites.
There are some middleware solutions that can be used as well. Also I know a couple people that have used "River Bed" to cut down on their site to site traffic.
There is also the Citrix Universal Print server. It has worked in my test environment but I havent put it into production.
It basically cuts down on your driver management on your Xenapp Servers. One driver to be used for all servers and one print server to manage.
Just my two cents..
-Casey