Windows NT Local Printers Being Renamed - Big Problem!

[msnews.microsoft.com]

Hello

We are running Terminal Services on a Win2k3 SP2 server.

When a user connects to the terminal server and connects their local
printer, the printer is being renamed to something like this:

Laser1 on WORKSTATION in session 8

This is causing a big problem for us as the app running in the terminal
service environment can only use printer names that are 8 characters or
less. If I log in as an admin, I can rename the printer but only for that
session. The users do not have the permission to rename it, even if they
wanted to.

Any suggestions would be appreciated.

Thanks.

 

[Vera Noest [MVP]]

Changing the name of the redirected printer isn't possible.
The problem lies of course in the application, which should use the
GetDefaultPrinter function, which will retrieve the default printer
in the session, irrespective of the name or the session id.

One way around this (if you can't fix the application) is to use a
3rd party printer management solution, which allows for custom
printer names.

Another workaround would be to completely bypass printer
redirection. Share all local printers and let users connect to
their local printer from within their ts session. Ugly, but it
should work.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"msnews.microsoft.com" <nickjax01@hotmail.com> wrote on 23 aug
2007 in microsoft.public.windows.terminal_services:

> Hello
>
> We are running Terminal Services on a Win2k3 SP2 server.
>
> When a user connects to the terminal server and connects their
> local printer, the printer is being renamed to something like
> this:
>
> Laser1 on WORKSTATION in session 8
>
> This is causing a big problem for us as the app running in the
> terminal service environment can only use printer names that are
> 8 characters or less. If I log in as an admin, I can rename the
> printer but only for that session. The users do not have the
> permission to rename it, even if they wanted to.
>
> Any suggestions would be appreciated.
>
> Thanks.

 

[Nick Jax]

Thanks..I'll give your suggestions a try! I can't fix the app unfortunately
but I'll try your workarounds.


"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9995E6FCDE1F2veranoesthemutforsse@207.46.248.16...
> Changing the name of the redirected printer isn't possible.
> The problem lies of course in the application, which should use the
> GetDefaultPrinter function, which will retrieve the default printer
> in the session, irrespective of the name or the session id.
>
> One way around this (if you can't fix the application) is to use a
> 3rd party printer management solution, which allows for custom
> printer names.
>
> Another workaround would be to completely bypass printer
> redirection. Share all local printers and let users connect to
> their local printer from within their ts session. Ugly, but it
> should work.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "msnews.microsoft.com" <nickjax01@hotmail.com> wrote on 23 aug
> 2007 in microsoft.public.windows.terminal_services:
>
> > Hello
> >
> > We are running Terminal Services on a Win2k3 SP2 server.
> >
> > When a user connects to the terminal server and connects their
> > local printer, the printer is being renamed to something like
> > this:
> >
> > Laser1 on WORKSTATION in session 8
> >
> > This is causing a big problem for us as the app running in the
> > terminal service environment can only use printer names that are
> > 8 characters or less. If I log in as an admin, I can rename the
> > printer but only for that session. The users do not have the
> > permission to rename it, even if they wanted to.
> >
> > Any suggestions would be appreciated.
> >
> > Thanks.