Re: Local LPR printer fails to auto attach in Terminal server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Since this is a client setting, you have to configure it on the
client. But you can create a reg file which contains the registry
key and put it in your login script, or even hand it out to users
on a floppy and instruct them to run the regfile to import the
settings in their registry.

But is this really your problem?
This problem is well-known for HP All-in-One printers, which often
create a DOT4 port. For those printers, you have to use the
registry settings described in the article above.
But I imagine that there are also driver issues, which prevent
printer autocreation.
Have you checked the EventLog on the Termianl Server?
If the problem is a DOT4 port, you will not find any Events, since
redirection is not even attempted.
If the driver is missing, you will see multiple events. If that's
the problem, you have to map those printers to a native driver, as
explained here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?UGV0ZXI=?=" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
28 sep 2005 in microsoft.public.windows.terminal_services:

> Is there a way to do this once on a server? We have a few
> hundred machines located throughout the enterprise. Some even
> work from home via dial-up.
>
> "Matthew Chapman" wrote:
>
>> Have you tried this?
>>
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;302361
>>
>> Matt
>>
>>
>> On 2005-09-28, Peter <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>> > I have multiple XP laptops/desktops with local printer
>> > configured using LPR to connect to LAN printers. These
>> > printers do not get auto redirected in Terminal server. Is
>> > there a workaround on this?
>> >
>> >
>> > Technet article:
>> > When a client logs on to Terminal Services, local printers
>> > attached to LPT, COM, and USB ports on the client computer
>> > are automatically detected and a local queue is created on
>> > the server. The client computer printer settings for the
>> > default printer and some properties, such as printing on both
>> > sides of the page, are used by the server.
.

Relevant Pages

  • Re: IE 6 and Proxy Setting Exceptions
    ... searched on the TechNet DVD for this "Internal Client Concepts in ISA Server ... 2006" and I was able to get an understanding for the key, and value settings. ... ProgramName.EXE Disable/DisableEx 1 ...
    (microsoft.public.isa)
  • Re: WSUS Client not yet reported
    ... The client still fails to report. ... Check your server status ... Suggestion 2: Check the IIS settings: ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 - Exchange online; file synch offline
    ... reinstall the Client Deployment component on the Server", ... the problematic workstation into the SBS Domain. ... automatically obtain an IP address from the DHCP on the SBS Server, ... >> Printers and Faxes, click Add a printer, click Next, select "A network ...
    (microsoft.public.windows.server.sbs)
  • RE: HP officejet 5610
    ... As far as I know none support ... Microsoft MVP - Terminal Server ... Virtual Client Solutions ... printers, assuming the client is Vista SP1 or XP SP3 with RDP Client 6.1. ...
    (microsoft.public.windows.terminal_services)
  • Re: Setting up Exchange
    ... I uncheck it once I've confirmed that the settings are as ... >> the SBS Exchange Server, so there is no need to change any settings ... We're only concerned with configuring Exchange to send mail ... >>> on client PC's. ...
    (microsoft.public.windows.server.sbs)