Windows NT Default Printer

  • Thread starter Thread starter Steven
  • Start date Start date
S

Steven

Hello MVP's!

Currently all users printers are rolling into their TS sessions successfully
however I would like only there default to role in and stay selected as there
default printer. Right now it brings in too many and the default keeps
changing.
--
Steve
 
This should help:

911913 - How to redirect the default printer of a Terminal Services
client to a Windows Server 2003 Terminal Server session
http://support.microsoft.com/?kbid=911913

_________________________________________________________
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?U3RldmVu?= <Steven@discussions.microsoft.com> wrote on
26 jul 2007 in microsoft.public.windows.terminal_services:

> Hello MVP's!
>
> Currently all users printers are rolling into their TS sessions
> successfully however I would like only there default to role in
> and stay selected as there default printer. Right now it brings
> in too many and the default keeps changing.
 
Hi Vera,

Thank you for your quick response and article. However I do have some
questions.
The article refers to a hotfix and then a registry change. Is the hotfix
roled into the latest service pack or do I call MS for that, article a little
confusing on that part. Second, I'm looking at pushing this out large scale,
I can do the registry change via GPO but hopeing I can do with hotfix, msi,
exe any ideas? Lastly, I checked 4 TS's and 4 clients with latest service
packs and the registry subkeys / path is not found, or at least the last part
\default\addins\rdpdr so I'm wondering if the hkeys are added with the
hotfix. The artcle indicates that they should already be there accept the
DWORD of course. Hope this makes sense and thank you fo ryour help.

--
Steve



"Vera Noest [MVP]" wrote:

> This should help:
>
> 911913 - How to redirect the default printer of a Terminal Services
> client to a Windows Server 2003 Terminal Server session
> http://support.microsoft.com/?kbid=911913
>
> _________________________________________________________
> 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?U3RldmVu?= <Steven@discussions.microsoft.com> wrote on
> 26 jul 2007 in microsoft.public.windows.terminal_services:
>
> > Hello MVP's!
> >
> > Currently all users printers are rolling into their TS sessions
> > successfully however I would like only there default to role in
> > and stay selected as there default printer. Right now it brings
> > in too many and the default keeps changing.
>
 
The hotfix seems to consist of the newest rdp client, version 6.0
So you can just as well install that through Windows Update.

The registry value must be added on the *client*, not on the Terminal
Server.
I've checked a couple of clients, and I don't have the whole registry
path either in HKEY_LOCAL_MACHINE, but it's there in
HKEY_CURRENT_USER.

As the article says, you can create the RedirectDefaultPrinterOnly
value in HKEY_LOCAL_MACHINE or in HKEY_CURRENT_USER, whatever suits
you best.

If you want to configure this for the client, not for specific users
of the client, then you just create the complete path to the registry
key.

If you import the value into the registry from a .reg file, the
complete path is automatically created.

310516 - HOW TO: Add, Modify, or Delete Registry Subkeys and Values
by Using a Registration Entries (.reg) File
http://support.microsoft.com/?kbid=310516

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?U3RldmVu?= <Steven@discussions.microsoft.com> wrote on
27 jul 2007:

> Hi Vera,
>
> Thank you for your quick response and article. However I do have
> some questions.
> The article refers to a hotfix and then a registry change. Is
> the hotfix roled into the latest service pack or do I call MS
> for that, article a little confusing on that part. Second, I'm
> looking at pushing this out large scale, I can do the registry
> change via GPO but hopeing I can do with hotfix, msi, exe any
> ideas? Lastly, I checked 4 TS's and 4 clients with latest
> service packs and the registry subkeys / path is not found, or
> at least the last part \default\addins\rdpdr so I'm wondering if
> the hkeys are added with the hotfix. The artcle indicates that
> they should already be there accept the DWORD of course. Hope
> this makes sense and thank you fo ryour help.
 
Back
Top