Re: Terminal Services 2003 printer redirection

Maybe there's a problem with security policy that restricts loading device
drivers totally or that group you're running this for. To the point, we use
Desltop Authority (http://www.scriptlogic.com/da) desktop management from
Scriptlogic when working with our Terminal Servers. Print management is the
feature that emphasizes the advances of use of desktop management software.
Usually it's simply impossible to construct printing directions for that very
own case within your environment. We created print management within our
terminal environment very quickly. Today our users' work with printing is
fully abstracted from them.

Haribo wrote:
Hi

I have a real strange problem with a Windows 2003 server running as a
dedicated terminal server. Everything works fine on it bar auto
redirection of printers, all settings are checked to allow and the
config is exactly the same as another couple of servers at different
sites which work OK. When logging on the server will put the usual
driver error if not found in the event log, when added the error then
disappears but no printers are added in Printers and Faxes, it doesn't
created the TS00* ports either. The event logs are completely clean of
any errors and I have tried creating LPT1 LJ4 printers which auto
install on other servers but to no avail. This problem has only just
come to light as nobody has needed to print to their local printers as
all the company printers are installed on the terminal server as local
printers, the issue is now one user is using TS remotely from the
office not just locally as they have moved house. I have trawled
through all the logs and I can definately say that all the options are
set to redirect printers on both the server and client, it just doesn't
work and gives no errors. I have tried running cleanspl and then
re-adding the needed drivers but this makes no difference. Also
redirection makes no difference if connecting locally to the server or
through the firewall remotely. I will soon have to setup the server
again as I need to sort this out sooner rather than later.

Any ideas.

Regards

Harry

.

Relevant Pages

  • Re: Cant print without restarting Print Spooler Service
    ... Once you get the drivers removed download the latest from HP and start over. ... The 3 printers are standalone network devices and are not attached to the ... file server directly. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: general question - Terminal Server 2003
    ... In this case there is only one print driver installed--the TS universal printer driver. ... there are cases when it may make sense *not* to use redirected printers and instead create printers directly on the TS. ... When a user prints the job must be downloaded to the user's workstation and then sent from there to the print server, ... (AD and GPO and Terminal Server and Small Business Server are my ...
    (microsoft.public.windows.terminal_services)
  • Re: Print spooler problems on termnal server.
    ... Only native drivers (i.e. those that came with the Windows 2003 CD ... HP Printers Supported in Citrix MetaFrame Presentation and Terminal ... MCSE, CCEA, Microsoft MVP - Terminal Server ... printers even though no print jobs have been selected. ...
    (microsoft.public.windows.terminal_services)
  • Re: !!HELP!! Pulling my hair on this one. Printer problems. Really need some help on this.
    ... Yes Larry I have already moved them off of the SBS server and onto a high ... When the printers were connecte they did show as being offline. ... have workstations connected are plugged into the same. ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 1111
    ... Whenever I remote it my 'tag along' drivers load up temporarily and then ... Mark wrote: ... I am getting server messages from Event ID 1111, which is casued by Terminal Services trying to redirect local printers, but the server has no printer driver. ...
    (microsoft.public.windows.server.sbs)