Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5147
  • Last Modified:

2008 Terminal Server Printing Issues

We are implementing a new 2008 terminal server (x64) and have a couple of remaining printing issues we were hoping to brainstorm with you all.

First, there are 2 laser printers that we cannot get our ticketing software to see:

HP Laserjet Professional M1212nf MFP
Sharp MX-M450N
 

Essentially, it looks like the Terminal Server is not recognizing the drivers we have installed server-side and is therefore defaulting to the Easy Print method, which Our ticketing software is not compatible with (unfortunately!).  We have verified that the drivers are correct & installed properly on the server.  Also, other laser printers are working correctly within it.

Any ideas in getting the printers recognized so that easy print is not defaulted to?  Unfortunately, we cannot simply install the printers as local printers on the server as multi-domain security permissions prohibit this.  

Second, we have a couple of Practical Automation EXT Series ticket printers that we were able to get working in Terminal Server 2003 by ensuring that the "Advanced Printing Feature" checkbox was unchecked under the printers' properties.  For some reason, the redirected printers in TS 2008 have this box checked and greyed out even though the printers client-side are unchecked.  The result is that jobs error out...thoughts?


Any ideas or insight would be much appreciated.  Thanks!
0
DowntownIT
Asked:
DowntownIT
  • 3
  • 2
1 Solution
 
Davis McCarnOwnerCommented:
For the Sharp, you'll need to change the O/S a few times to get the matched drivers for the TS and all of the clients; but, after you install the same version on everybody, I haven't had any problems: http://www.sharpusa.com/CustomerSupport/ProductDownloads.aspx?downloadtype=Driver&category=HomeOfficePrintersFaxMachines&model=mx-m450n&
And, lucky for you, HP doesn't seem to want you to use their Universal Printer Driver (which plain doesn't work) for that 1210 http://h10025.www1.hp.com/ewfrf/wc/product?product=3965849&lc=en&cc=us&dlc=en&lang=en&cc=us
You would do yourself a big favor to set those printers to static ip's and use a satdard tcp/ip port on everybody rather than sharing them; because, then, you don't have to match versions down to the .000001 for all O/S's.  But; match the drivers across the network and all will be happy, too.
Here is how to make Easy Print secondary rather than primary: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/8dcaaee8-f6c5-48e3-8f29-6ad6d210b93b/ 
0
 
DowntownITAuthor Commented:
We have verified that the drivers are correct & installed properly on the server that is installed on the client, down to the .000001's. We have the group policy already set to disable the easy print driver first.
0
 
Davis McCarnOwnerCommented:
For some reason; though, Windoze still thinks they are different printers.....
I have seen it on HP's; but, never before on Sharp's and one of my clients has al least 6 different models with a 2K8 x64 server.  All XP clients (well, one Vista & one 7 x64) and the Sharps were all painless.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
DowntownITAuthor Commented:
I was able to find a patch for powerbuilder to allow the Easy Print Driver to work with our software.
0
 
DowntownITAuthor Commented:
DONE
0
 
vielmetterCommented:
fixed this by installing the XPS driver update available from HP here:

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=Im-85229-1&lc=en&dlc=en&cc=us&os=4062&product=3965849&sw_lang=

And then subsequently setting the XPS driver on that M1212nf printer to the default. Printing from the XPS M1212nf printer through remote desktop / terminal services functions as expected.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now