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: 680
  • Last Modified:

HP Thin Client t610 Sporadic and Bad Print Job

We recently deployed new servers and new HP thin clients across two offices supporting approximately 25 staff.  The physical box is from Dell and has hyper v on it with four other virtual servers - one of which is a terminal server.  This is all Server 2012.

The server is located in a COLO, offsite from either of the two offices. The firewalls at either facility are made by Fortinet.

The Thin Clients are the HP T610. The Thin Clients have Windows Embedded that's based off Windows 7.

From our prior set up, most staff have printers in their offices.  Because of this, we purchased third party software - ScrewDrivers - to enable printing over Terminal Services to the Local Printers. All the printers are HP  and have been locally installed on the ThinClients.

We use RD Web Access via Internet Explorer to launch office software.

The problems we are having is sometimes, a print job will work but sometimes it won't.  Sometimes a job will start to print and then stop before printing everything. Other times, I've seen it print a report but that report has random symbols/improper formatting on it.

Trying to troubleshoot this, here's what I've found:
-When printing from the software on the terminal server the jobs all appropriately end up in the queue of the printer they were sent to.
-However, sometimes, it will just say "Spooling" and never leave that state - even hours later.
-If you try deleting the job, it will still say "Deleting - Spooling"
-Only way to get rid of it is to reboot or restart the print spool service

Anybody have any suggestions for this problem? Anybody have any suggestions for best practices for printing in this environment? We do not use Citrix and do not have a dedicated print server (not 100% sure what this is).

Thank you,
Brandon
0
brandonpf
Asked:
brandonpf
  • 2
1 Solution
 
strivoliCommented:
You should kindly check if the printer drivers are updated. Please post a printer's make/model and driver version.
Also, is the connection between the print server (the TS) and the thin client reliable? Try "pinging" a thousand times and see how many packets get lost.
0
 
brandonpfAuthor Commented:
I believe a reliable connection to the terminal server was the issue. Pinging the TS 1000 times resulted in a roughly 20% failure rate. We've since addressed that issue with the internet provider and printing has improved drastically. Thank you.
0
 
strivoliCommented:
You're welcome!
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

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