Go Premium for a chance to win a PS4. Enter to Win


Installing LAN printer for Remote Desktop access

Posted on 2007-11-29
Medium Priority
Last Modified: 2013-11-21
I have an HP Officejet 7410 All-in-One printer connected to the WLAN at home. I am having trouble installing the driver for this printer on our company's (ironically) HP server running Windows Server 2003 Standard Edition. I'll admit I know very very little about networking and servers. I ran the installation software on the server and it goes through installing the software and then gets to a step where it looks for the printer. I connect to the server using RDP over our VPN connection and have devices set to be accessible in the RD settings (the server Event log even recognizes the printer and the fact that there is no driver for it). How do I get the printer to be seen by windows during the install? I was thinking if I could just get the driver installed that when I log on then everything would be fine, but apparently the installer doesn't agree with me--when it can't find the device it rolls back the installation.  
Question by:nicholasjwolf
  • 2

Expert Comment

ID: 20375673
Ah yes, HP drivers..

I assume you're getting event ID 1111

The way I've got around this in the past is by installing the printer manually using the add printer wizard.  Then browse to the temporary installation folder (created under your temp files in C:\Documents and Settings\<user>\Local Settings\Temp and locate the appropriate ini file.  You need to do this while the installer is running, after it has extracted files, but before it rolls back the installation.   You can install this to LPT1 and then delete the printer after you get it loaded.  This should get the driver installed on the server.
LVL 31

Accepted Solution

Cláudio Rodrigues earned 2000 total points
ID: 20379895
Oh boy, here we go again. People installing printer drivers on Terminal Servers...
Just to let you know, the first rule of thumb on TS is NEVER install a printer driver on it, unless this is your LAST resource AND you clearly understand the risks on doing this.
There are many posts here at EE discussing this and the correct way of dealing with TS and printers.
Some links for you:
And from that post:


The first lesson to learn here is simple: NEVER install ANY printer driver on a Terminal Server, unless this is your last option and you are fully aware of the implications (instability, hangs and in some cases, BSODs).
The way you should deal with printers on TS is to test an out-of-the-box driver (like LaserJet 5 or 6) with your printer. Does it work? If it does, all you need to do is to change the NTPRINT.INF file or to setup your own .INF to be used for printer mapping under TS. It is all explained here:
http://support.microsoft.com/kb/239088 (valid for 2003 as well)

If you ask any Microsoft MVP for Terminal Services about printing best practices, the first one is not to install the driver on the TS, what you did. :-)
If an alternate driver does not work you have two options: get a different printer or load on the TS a product like UniPrint, SimplifyPrinting or ThinPrint. These eliminate the need for any driver whatsoever on the TS and will work with any printer on the client side, including host based ones like this HP.


Hope this helps.

Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services

Author Closing Comment

ID: 31411729
"Oh, boy here we go again..." seemed a bit condescending, but I can relate to the frustration of having to discuss something multiple times. However, this just irked me a bit and I felt as if my question was not welcome. I DO appreciate the very thorough response. Thank you Claudio.
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 20390261
Hey Nicholas!
In no way I meant I was tired of answering the same question all over. The idea was to show that this is one of the top misconceptions with TS in general so people can get right away this is something that we all should pay attention all the time.
I am happy this answered your question and that you are now one more that clearly understands why installing printer drives on TS is not a good thing. :-)


Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When I recently replaced my image transfer kit on my office HP color laserjet 5550dn printer, I had a slight problem.  The left bracket that holds the transfer kit got stuck in the upright locked position instead of being at a 45 degree angle facing…
When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…
Please read the paragraph below before following the instructions in the video — there are important caveats in the paragraph that I did not mention in the video. If your PaperPort 12 or PaperPort 14 is failing to start, or crashing, or hanging, …

916 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question