Force feeding Windows Server 2003

1 minute read

Another day at work, another interesting problem. A user was connecting to a terminal server and tried to print to a printer that was installed locally on her PC. Logging into the terminal server via RDC showed no printers available.

First step was to ensure that the printer was a shared local resource. This was alright, however the printer still does not want to show up. Frustrated, I tried to install the printer locally by downloading the printer drivers on the terminal server. Running the install file did nothing so I had to find another way to force the drivers onto the system.

Logging onto the terminal server as Administrator, I found a way to trick the server and force feed it the drivers.

  1. Enter into the control panel and install a new local printer. Install manually and do not search for a printer.
  2. Select a printer port to be "FILE: (Print to File)" and choose your own printer drivers (select have disk).
  3. From the downloaded driver file, select the INF or if it is already in the list of available drivers, select your printer from there.
  4. Continue through with the installation and allow the printer to be installed. Remember to name it something random as this is only temporary and you will delete this printer after.
  5. Once the dummy print to file printer is installed, log off the terminal server and re-log back in.
  6. As you log in, you will notice that Windows has now installed the printer that was having troubles.
  7. Remove the dummy printer so that it doesn't show up in the printer list!

So, that's what I did to make this work. You can also check in the system logs to see that whether or not this method is necessary. In the system log, you will see an 1111 error code stating that the printer driver could not be found and the printer was not installed.

Hope this helps!

Leave a Comment

Your email address will not be published. Required fields are marked *

Loading...