Jump to content

Client Printer Redirection


Recommended Posts

Guest farleynx
Posted

Hello,

 

I have several users connecting to a Win2K3 Terminal Server that need their

local printers mapped. However, I would like to restrict them to only being

able to map their local default printer. The following registry setting

controls that on the client side, but I don't have access to the local

computers in order to make that change.

 

HKCU\Software\Microsoft\Terminal Server

Client\Default\AddIns\RDPDR\RedirectDefaultPrinterOnly

 

I thought I might be able to control this through the group policy so I

created a custom .adm file (see below).

 

;Redirection of A Terminal Server Client's default printer only

 

CLASS USER

 

CATEGORY !!WindowsComponents

 

CATEGORY !!TS_GP_NODE

 

CATEGORY !!TS_CLIENT

 

KEYNAME "Software\Microsoft\Terminal Server

Client\Default\Addins\RDPDR\RedirectDefaultPrinterOnly"

 

POLICY !!RedirectDefaultPrinterOnly

 

EXPLAIN !!RedirectDefaultPrinterOnly_Explain

 

VALUENAME RedirectDefaultPrinterOnly

VALUEON NUMERIC 1

VALUEOFF DELETE

 

END POLICY

 

END CATEGORY ; TS_CLIENT

 

END CATEGORY ; TS_GP_NODE

 

END CATEGORY ; WindowsComponents

 

[sTRINGS]

WindowsComponents="Windows Components"

TS_GP_NODE="Terminal Services"

TS_CLIENT="Client"

RedirectDefaultPrinterOnly="Redirect Client Default Printer Only"

RedirectDefaultPrinterOnly_Explain="Will redirect the client's default

printer only. All other printers will not be available during the Terminal

Services session."

 

The .adm file imported without errors and the setting is available in the

group policy editor. However when I enable the setting and test it, all the

printers are still mapped and the registry setting is not created or modified

on the client.

 

Is this even possible via the method I am using, am I missing something or

is there a better way to achieve the intended result?

 

Thanks,

farleynx

  • Replies 7
  • Created
  • Last Reply
Guest Vera Noest [MVP]
Posted

Re: Client Printer Redirection

 

Are the clients members of your AD domain?

If not, the GPO will not affect them at all.

If they are domain members, to which OU did you link the GPO?

You can use Resultant set of Policies to see which GPOs are applied

to a particular user on a particular client.

 

I'm also a bit puzzled by your use of the value DELETE for

VALUEOFF. I've never seen it used, and it isn't mention anywhere

here:

 

Using Administrative Template Files with Registry-Based Group

Policy White Paper

http://www.microsoft.com/downloads/details.aspx?FamilyID=e7d72fa1-

62fe-4358-8360-8774ea8db847&displaylang=en

_________________________________________________________

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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

wrote on 27 feb 2008 in

microsoft.public.windows.terminal_services:

> Hello,

>

> I have several users connecting to a Win2K3 Terminal Server that

> need their local printers mapped. However, I would like to

> restrict them to only being able to map their local default

> printer. The following registry setting controls that on the

> client side, but I don't have access to the local computers in

> order to make that change.

>

> HKCU\Software\Microsoft\Terminal Server

> Client\Default\AddIns\RDPDR\RedirectDefaultPrinterOnly

>

> I thought I might be able to control this through the group

> policy so I created a custom .adm file (see below).

>

> ;Redirection of A Terminal Server Client's default printer only

>

> CLASS USER

>

> CATEGORY !!WindowsComponents

>

> CATEGORY !!TS_GP_NODE

>

> CATEGORY !!TS_CLIENT

>

> KEYNAME "Software\Microsoft\Terminal Server

> Client\Default\Addins\RDPDR\RedirectDefaultPrinterOnly"

>

> POLICY !!RedirectDefaultPrinterOnly

>

> EXPLAIN !!RedirectDefaultPrinterOnly_Explain

>

> VALUENAME RedirectDefaultPrinterOnly

> VALUEON NUMERIC 1

> VALUEOFF DELETE

>

> END POLICY

>

> END CATEGORY ; TS_CLIENT

>

> END CATEGORY ; TS_GP_NODE

>

> END CATEGORY ; WindowsComponents

>

> [sTRINGS]

> WindowsComponents="Windows Components"

> TS_GP_NODE="Terminal Services"

> TS_CLIENT="Client"

> RedirectDefaultPrinterOnly="Redirect Client Default Printer

> Only" RedirectDefaultPrinterOnly_Explain="Will redirect the

> client's default printer only. All other printers will not be

> available during the Terminal Services session."

>

> The .adm file imported without errors and the setting is

> available in the group policy editor. However when I enable the

> setting and test it, all the printers are still mapped and the

> registry setting is not created or modified on the client.

>

> Is this even possible via the method I am using, am I missing

> something or is there a better way to achieve the intended

> result?

>

> Thanks,

> farleynx

Guest farleynx
Posted

Re: Client Printer Redirection

 

Vera,

 

The client computers are not members of the local domain. That in is where

my problems lie. Is there anyway to restrict what printers are being

redirected from the clients? There is no need to redirect 5 printers when

they only use one, their default printer. This is causing unwanted taxation

on the Printer Spooler as well as the server itself.

 

As far as the VALUEOFF DELETE statement, that will not add or delete the

registry entry if the GPO policy is not configured or disabled. This was

referenced in a document published by Florian Frommherz. (Can't remember

where I got it from otherwise I would provide the link.)

 

Thanks,

farleynx

 

"Vera Noest [MVP]" wrote:

> Are the clients members of your AD domain?

> If not, the GPO will not affect them at all.

> If they are domain members, to which OU did you link the GPO?

> You can use Resultant set of Policies to see which GPOs are applied

> to a particular user on a particular client.

>

> I'm also a bit puzzled by your use of the value DELETE for

> VALUEOFF. I've never seen it used, and it isn't mention anywhere

> here:

>

> Using Administrative Template Files with Registry-Based Group

> Policy White Paper

> http://www.microsoft.com/downloads/details.aspx?FamilyID=e7d72fa1-

> 62fe-4358-8360-8774ea8db847&displaylang=en

> _________________________________________________________

> 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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

> wrote on 27 feb 2008 in

> microsoft.public.windows.terminal_services:

>

> > Hello,

> >

> > I have several users connecting to a Win2K3 Terminal Server that

> > need their local printers mapped. However, I would like to

> > restrict them to only being able to map their local default

> > printer. The following registry setting controls that on the

> > client side, but I don't have access to the local computers in

> > order to make that change.

> >

> > HKCU\Software\Microsoft\Terminal Server

> > Client\Default\AddIns\RDPDR\RedirectDefaultPrinterOnly

> >

> > I thought I might be able to control this through the group

> > policy so I created a custom .adm file (see below).

> >

> > ;Redirection of A Terminal Server Client's default printer only

> >

> > CLASS USER

> >

> > CATEGORY !!WindowsComponents

> >

> > CATEGORY !!TS_GP_NODE

> >

> > CATEGORY !!TS_CLIENT

> >

> > KEYNAME "Software\Microsoft\Terminal Server

> > Client\Default\Addins\RDPDR\RedirectDefaultPrinterOnly"

> >

> > POLICY !!RedirectDefaultPrinterOnly

> >

> > EXPLAIN !!RedirectDefaultPrinterOnly_Explain

> >

> > VALUENAME RedirectDefaultPrinterOnly

> > VALUEON NUMERIC 1

> > VALUEOFF DELETE

> >

> > END POLICY

> >

> > END CATEGORY ; TS_CLIENT

> >

> > END CATEGORY ; TS_GP_NODE

> >

> > END CATEGORY ; WindowsComponents

> >

> > [sTRINGS]

> > WindowsComponents="Windows Components"

> > TS_GP_NODE="Terminal Services"

> > TS_CLIENT="Client"

> > RedirectDefaultPrinterOnly="Redirect Client Default Printer

> > Only" RedirectDefaultPrinterOnly_Explain="Will redirect the

> > client's default printer only. All other printers will not be

> > available during the Terminal Services session."

> >

> > The .adm file imported without errors and the setting is

> > available in the group policy editor. However when I enable the

> > setting and test it, all the printers are still mapped and the

> > registry setting is not created or modified on the client.

> >

> > Is this even possible via the method I am using, am I missing

> > something or is there a better way to achieve the intended

> > result?

> >

> > Thanks,

> > farleynx

>

Guest Vera Noest [MVP]
Posted

Re: Client Printer Redirection

 

What about the users, then? Can you enforce a login script for

them?

If so, you could simply add the registry value to their HKCU part

of the registry. Export the key to a regfile and import it with

regedit /s <your regfile>, or use regini.

 

310516 - HOW TO: Add, Modify, or Delete Registry Subkeys and Values

by Using a Registration Entries (.reg) File

http://support.microsoft.com/?kbid=310516

 

264584 - How to change registry values or permissions from a

command line or a script

http://support.microsoft.com/?kbid=264584

 

_________________________________________________________

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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

wrote on 28 feb 2008 in

microsoft.public.windows.terminal_services:

> Vera,

>

> The client computers are not members of the local domain. That

> in is where my problems lie. Is there anyway to restrict what

> printers are being redirected from the clients? There is no need

> to redirect 5 printers when they only use one, their default

> printer. This is causing unwanted taxation on the Printer

> Spooler as well as the server itself.

>

> As far as the VALUEOFF DELETE statement, that will not add or

> delete the registry entry if the GPO policy is not configured or

> disabled. This was referenced in a document published by Florian

> Frommherz. (Can't remember where I got it from otherwise I would

> provide the link.)

>

> Thanks,

> farleynx

>

> "Vera Noest [MVP]" wrote:

>

>> Are the clients members of your AD domain?

>> If not, the GPO will not affect them at all.

>> If they are domain members, to which OU did you link the GPO?

>> You can use Resultant set of Policies to see which GPOs are

>> applied to a particular user on a particular client.

>>

>> I'm also a bit puzzled by your use of the value DELETE for

>> VALUEOFF. I've never seen it used, and it isn't mention

>> anywhere here:

>>

>> Using Administrative Template Files with Registry-Based Group

>> Policy White Paper

>> http://www.microsoft.com/downloads/details.aspx?FamilyID=e7d72fa

>> 1- 62fe-4358-8360-8774ea8db847&displaylang=en

>> _________________________________________________________

>> 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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

>> wrote on 27 feb 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > Hello,

>> >

>> > I have several users connecting to a Win2K3 Terminal Server

>> > that need their local printers mapped. However, I would like

>> > to restrict them to only being able to map their local

>> > default printer. The following registry setting controls that

>> > on the client side, but I don't have access to the local

>> > computers in order to make that change.

>> >

>> > HKCU\Software\Microsoft\Terminal Server

>> > Client\Default\AddIns\RDPDR\RedirectDefaultPrinterOnly

>> >

>> > I thought I might be able to control this through the group

>> > policy so I created a custom .adm file (see below).

>> >

>> > ;Redirection of A Terminal Server Client's default printer

>> > only

>> >

>> > CLASS USER

>> >

>> > CATEGORY !!WindowsComponents

>> >

>> > CATEGORY !!TS_GP_NODE

>> >

>> > CATEGORY !!TS_CLIENT

>> >

>> > KEYNAME "Software\Microsoft\Terminal Server

>> > Client\Default\Addins\RDPDR\RedirectDefaultPrinterOnly"

>> >

>> > POLICY !!RedirectDefaultPrinterOnly

>> >

>> > EXPLAIN !!RedirectDefaultPrinterOnly_Explain

>> >

>> > VALUENAME RedirectDefaultPrinterOnly

>> > VALUEON NUMERIC 1

>> > VALUEOFF DELETE

>> >

>> > END POLICY

>> >

>> > END CATEGORY ; TS_CLIENT

>> >

>> > END CATEGORY ; TS_GP_NODE

>> >

>> > END CATEGORY ; WindowsComponents

>> >

>> > [sTRINGS]

>> > WindowsComponents="Windows Components"

>> > TS_GP_NODE="Terminal Services"

>> > TS_CLIENT="Client"

>> > RedirectDefaultPrinterOnly="Redirect Client Default Printer

>> > Only" RedirectDefaultPrinterOnly_Explain="Will redirect the

>> > client's default printer only. All other printers will not be

>> > available during the Terminal Services session."

>> >

>> > The .adm file imported without errors and the setting is

>> > available in the group policy editor. However when I enable

>> > the setting and test it, all the printers are still mapped

>> > and the registry setting is not created or modified on the

>> > client.

>> >

>> > Is this even possible via the method I am using, am I missing

>> > something or is there a better way to achieve the intended

>> > result?

>> >

>> > Thanks,

>> > farleynx

Guest farleynx
Posted

Re: Client Printer Redirection

 

Vera,

 

Should the .reg file look something like this?

 

Windows Registry Editor Version 5.00

 

[HKEY_CURRENT_USER\Software\Microsoft\Terminal Server

Client\Default\AddIns\RDPDR]

"RedirectDefaultPrinterOnly"=dword:00000001

 

The logon script entry should look like this?

 

regedit.exe /s C:\Registry Scripts\RedirectDefaultPrinterOnly.reg

 

Does it matter where the .reg file is stored or where the .bat file is

located?

 

Thanks for all your help, Vera.

 

Sincerely,

farleynx

 

"Vera Noest [MVP]" wrote:

> What about the users, then? Can you enforce a login script for

> them?

> If so, you could simply add the registry value to their HKCU part

> of the registry. Export the key to a regfile and import it with

> regedit /s <your regfile>, or use regini.

>

> 310516 - HOW TO: Add, Modify, or Delete Registry Subkeys and Values

> by Using a Registration Entries (.reg) File

> http://support.microsoft.com/?kbid=310516

>

> 264584 - How to change registry values or permissions from a

> command line or a script

> http://support.microsoft.com/?kbid=264584

>

> _________________________________________________________

> 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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

> wrote on 28 feb 2008 in

> microsoft.public.windows.terminal_services:

>

> > Vera,

> >

> > The client computers are not members of the local domain. That

> > in is where my problems lie. Is there anyway to restrict what

> > printers are being redirected from the clients? There is no need

> > to redirect 5 printers when they only use one, their default

> > printer. This is causing unwanted taxation on the Printer

> > Spooler as well as the server itself.

> >

> > As far as the VALUEOFF DELETE statement, that will not add or

> > delete the registry entry if the GPO policy is not configured or

> > disabled. This was referenced in a document published by Florian

> > Frommherz. (Can't remember where I got it from otherwise I would

> > provide the link.)

> >

> > Thanks,

> > farleynx

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Are the clients members of your AD domain?

> >> If not, the GPO will not affect them at all.

> >> If they are domain members, to which OU did you link the GPO?

> >> You can use Resultant set of Policies to see which GPOs are

> >> applied to a particular user on a particular client.

> >>

> >> I'm also a bit puzzled by your use of the value DELETE for

> >> VALUEOFF. I've never seen it used, and it isn't mention

> >> anywhere here:

> >>

> >> Using Administrative Template Files with Registry-Based Group

> >> Policy White Paper

> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=e7d72fa

> >> 1- 62fe-4358-8360-8774ea8db847&displaylang=en

> >> _________________________________________________________

> >> 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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

> >> wrote on 27 feb 2008 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > Hello,

> >> >

> >> > I have several users connecting to a Win2K3 Terminal Server

> >> > that need their local printers mapped. However, I would like

> >> > to restrict them to only being able to map their local

> >> > default printer. The following registry setting controls that

> >> > on the client side, but I don't have access to the local

> >> > computers in order to make that change.

> >> >

> >> > HKCU\Software\Microsoft\Terminal Server

> >> > Client\Default\AddIns\RDPDR\RedirectDefaultPrinterOnly

> >> >

> >> > I thought I might be able to control this through the group

> >> > policy so I created a custom .adm file (see below).

> >> >

> >> > ;Redirection of A Terminal Server Client's default printer

> >> > only

> >> >

> >> > CLASS USER

> >> >

> >> > CATEGORY !!WindowsComponents

> >> >

> >> > CATEGORY !!TS_GP_NODE

> >> >

> >> > CATEGORY !!TS_CLIENT

> >> >

> >> > KEYNAME "Software\Microsoft\Terminal Server

> >> > Client\Default\Addins\RDPDR\RedirectDefaultPrinterOnly"

> >> >

> >> > POLICY !!RedirectDefaultPrinterOnly

> >> >

> >> > EXPLAIN !!RedirectDefaultPrinterOnly_Explain

> >> >

> >> > VALUENAME RedirectDefaultPrinterOnly

> >> > VALUEON NUMERIC 1

> >> > VALUEOFF DELETE

> >> >

> >> > END POLICY

> >> >

> >> > END CATEGORY ; TS_CLIENT

> >> >

> >> > END CATEGORY ; TS_GP_NODE

> >> >

> >> > END CATEGORY ; WindowsComponents

> >> >

> >> > [sTRINGS]

> >> > WindowsComponents="Windows Components"

> >> > TS_GP_NODE="Terminal Services"

> >> > TS_CLIENT="Client"

> >> > RedirectDefaultPrinterOnly="Redirect Client Default Printer

> >> > Only" RedirectDefaultPrinterOnly_Explain="Will redirect the

> >> > client's default printer only. All other printers will not be

> >> > available during the Terminal Services session."

> >> >

> >> > The .adm file imported without errors and the setting is

> >> > available in the group policy editor. However when I enable

> >> > the setting and test it, all the printers are still mapped

> >> > and the registry setting is not created or modified on the

> >> > client.

> >> >

> >> > Is this even possible via the method I am using, am I missing

> >> > something or is there a better way to achieve the intended

> >> > result?

> >> >

> >> > Thanks,

> >> > farleynx

>

Guest Vera Noest [MVP]
Posted

Re: Client Printer Redirection

 

The .reg file looks OK to me. But you have to make sure that the

path to it is valid and accessible to the clients when they logon

(to the client, not to the TS).

Now I'm thinking about this a bit more, that could cause you a

problem. Most likely, your users don't logon with a domain account

when they logon to their workstations, since these are not part of

your domain, is that correct?

If that is the case, you might need to use TSRemoteExec - a

freeware utility to execute any command on the local client from

within a remote session, by Thomas Tran:

 

http://www.mqtechnologies.com/products/TSRemoteExec/

 

_________________________________________________________

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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

wrote on 28 feb 2008 in

microsoft.public.windows.terminal_services:

> Vera,

>

> Should the .reg file look something like this?

>

> Windows Registry Editor Version 5.00

>

> [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server

> Client\Default\AddIns\RDPDR]

> "RedirectDefaultPrinterOnly"=dword:00000001

>

> The logon script entry should look like this?

>

> regedit.exe /s C:\Registry

> Scripts\RedirectDefaultPrinterOnly.reg

>

> Does it matter where the .reg file is stored or where the .bat

> file is located?

>

> Thanks for all your help, Vera.

>

> Sincerely,

> farleynx

>

> "Vera Noest [MVP]" wrote:

>

>> What about the users, then? Can you enforce a login script for

>> them?

>> If so, you could simply add the registry value to their HKCU

>> part of the registry. Export the key to a regfile and import it

>> with regedit /s <your regfile>, or use regini.

>>

>> 310516 - HOW TO: Add, Modify, or Delete Registry Subkeys and

>> Values by Using a Registration Entries (.reg) File

>> http://support.microsoft.com/?kbid=310516

>>

>> 264584 - How to change registry values or permissions from a

>> command line or a script

>> http://support.microsoft.com/?kbid=264584

>>

>> _________________________________________________________

>> 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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

>> wrote on 28 feb 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > Vera,

>> >

>> > The client computers are not members of the local domain.

>> > That in is where my problems lie. Is there anyway to restrict

>> > what printers are being redirected from the clients? There is

>> > no need to redirect 5 printers when they only use one, their

>> > default printer. This is causing unwanted taxation on the

>> > Printer Spooler as well as the server itself.

>> >

>> > As far as the VALUEOFF DELETE statement, that will not add or

>> > delete the registry entry if the GPO policy is not configured

>> > or disabled. This was referenced in a document published by

>> > Florian Frommherz. (Can't remember where I got it from

>> > otherwise I would provide the link.)

>> >

>> > Thanks,

>> > farleynx

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> Are the clients members of your AD domain?

>> >> If not, the GPO will not affect them at all.

>> >> If they are domain members, to which OU did you link the

>> >> GPO? You can use Resultant set of Policies to see which GPOs

>> >> are applied to a particular user on a particular client.

>> >>

>> >> I'm also a bit puzzled by your use of the value DELETE for

>> >> VALUEOFF. I've never seen it used, and it isn't mention

>> >> anywhere here:

>> >>

>> >> Using Administrative Template Files with Registry-Based

>> >> Group Policy White Paper

>> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=e7d7

>> >> 2fa 1- 62fe-4358-8360-8774ea8db847&displaylang=en

>> >> _________________________________________________________

>> >> 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?ZmFybGV5bng=?=

>> >> <farleynx@discussions.microsoft.com> wrote on 27 feb 2008 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > Hello,

>> >> >

>> >> > I have several users connecting to a Win2K3 Terminal

>> >> > Server that need their local printers mapped. However, I

>> >> > would like to restrict them to only being able to map

>> >> > their local default printer. The following registry

>> >> > setting controls that on the client side, but I don't have

>> >> > access to the local computers in order to make that

>> >> > change.

>> >> >

>> >> > HKCU\Software\Microsoft\Terminal Server

>> >> > Client\Default\AddIns\RDPDR\RedirectDefaultPrinterOnly

>> >> >

>> >> > I thought I might be able to control this through the

>> >> > group policy so I created a custom .adm file (see below).

>> >> >

>> >> > ;Redirection of A Terminal Server Client's default printer

>> >> > only

>> >> >

>> >> > CLASS USER

>> >> >

>> >> > CATEGORY !!WindowsComponents

>> >> >

>> >> > CATEGORY !!TS_GP_NODE

>> >> >

>> >> > CATEGORY !!TS_CLIENT

>> >> >

>> >> > KEYNAME "Software\Microsoft\Terminal Server

>> >> > Client\Default\Addins\RDPDR\RedirectDefaultPrinterOnly"

>> >> >

>> >> > POLICY !!RedirectDefaultPrinterOnly

>> >> >

>> >> > EXPLAIN

>> >> > !!RedirectDefaultPrinterOnly_Explain

>> >> >

>> >> > VALUENAME RedirectDefaultPrinterOnly

>> >> > VALUEON NUMERIC 1

>> >> > VALUEOFF DELETE

>> >> >

>> >> > END POLICY

>> >> >

>> >> > END CATEGORY ; TS_CLIENT

>> >> >

>> >> > END CATEGORY ; TS_GP_NODE

>> >> >

>> >> > END CATEGORY ; WindowsComponents

>> >> >

>> >> > [sTRINGS]

>> >> > WindowsComponents="Windows Components"

>> >> > TS_GP_NODE="Terminal Services"

>> >> > TS_CLIENT="Client"

>> >> > RedirectDefaultPrinterOnly="Redirect Client Default

>> >> > Printer Only" RedirectDefaultPrinterOnly_Explain="Will

>> >> > redirect the client's default printer only. All other

>> >> > printers will not be available during the Terminal

>> >> > Services session."

>> >> >

>> >> > The .adm file imported without errors and the setting is

>> >> > available in the group policy editor. However when I

>> >> > enable the setting and test it, all the printers are still

>> >> > mapped and the registry setting is not created or modified

>> >> > on the client.

>> >> >

>> >> > Is this even possible via the method I am using, am I

>> >> > missing something or is there a better way to achieve the

>> >> > intended result?

>> >> >

>> >> > Thanks,

>> >> > farleynx

Guest farleynx
Posted

Re: Client Printer Redirection

 

That is correct, the clients do not logon with a domain account to their

workstations. They only use a domain account when they log onto the TS. The

TSRemoteExec utility sounds like it might do the trick. I will try it out and

let you know what happens.

 

Thanks Again,

farleynx

 

"Vera Noest [MVP]" wrote:

> The .reg file looks OK to me. But you have to make sure that the

> path to it is valid and accessible to the clients when they logon

> (to the client, not to the TS).

> Now I'm thinking about this a bit more, that could cause you a

> problem. Most likely, your users don't logon with a domain account

> when they logon to their workstations, since these are not part of

> your domain, is that correct?

> If that is the case, you might need to use TSRemoteExec - a

> freeware utility to execute any command on the local client from

> within a remote session, by Thomas Tran:

>

> http://www.mqtechnologies.com/products/TSRemoteExec/

>

> _________________________________________________________

> 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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

> wrote on 28 feb 2008 in

> microsoft.public.windows.terminal_services:

>

> > Vera,

> >

> > Should the .reg file look something like this?

> >

> > Windows Registry Editor Version 5.00

> >

> > [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server

> > Client\Default\AddIns\RDPDR]

> > "RedirectDefaultPrinterOnly"=dword:00000001

> >

> > The logon script entry should look like this?

> >

> > regedit.exe /s C:\Registry

> > Scripts\RedirectDefaultPrinterOnly.reg

> >

> > Does it matter where the .reg file is stored or where the .bat

> > file is located?

> >

> > Thanks for all your help, Vera.

> >

> > Sincerely,

> > farleynx

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> What about the users, then? Can you enforce a login script for

> >> them?

> >> If so, you could simply add the registry value to their HKCU

> >> part of the registry. Export the key to a regfile and import it

> >> with regedit /s <your regfile>, or use regini.

> >>

> >> 310516 - HOW TO: Add, Modify, or Delete Registry Subkeys and

> >> Values by Using a Registration Entries (.reg) File

> >> http://support.microsoft.com/?kbid=310516

> >>

> >> 264584 - How to change registry values or permissions from a

> >> command line or a script

> >> http://support.microsoft.com/?kbid=264584

> >>

> >> _________________________________________________________

> >> 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?ZmFybGV5bng=?= <farleynx@discussions.microsoft.com>

> >> wrote on 28 feb 2008 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > Vera,

> >> >

> >> > The client computers are not members of the local domain.

> >> > That in is where my problems lie. Is there anyway to restrict

> >> > what printers are being redirected from the clients? There is

> >> > no need to redirect 5 printers when they only use one, their

> >> > default printer. This is causing unwanted taxation on the

> >> > Printer Spooler as well as the server itself.

> >> >

> >> > As far as the VALUEOFF DELETE statement, that will not add or

> >> > delete the registry entry if the GPO policy is not configured

> >> > or disabled. This was referenced in a document published by

> >> > Florian Frommherz. (Can't remember where I got it from

> >> > otherwise I would provide the link.)

> >> >

> >> > Thanks,

> >> > farleynx

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> Are the clients members of your AD domain?

> >> >> If not, the GPO will not affect them at all.

> >> >> If they are domain members, to which OU did you link the

> >> >> GPO? You can use Resultant set of Policies to see which GPOs

> >> >> are applied to a particular user on a particular client.

> >> >>

> >> >> I'm also a bit puzzled by your use of the value DELETE for

> >> >> VALUEOFF. I've never seen it used, and it isn't mention

> >> >> anywhere here:

> >> >>

> >> >> Using Administrative Template Files with Registry-Based

> >> >> Group Policy White Paper

> >> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=e7d7

> >> >> 2fa 1- 62fe-4358-8360-8774ea8db847&displaylang=en

> >> >> _________________________________________________________

> >> >> 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?ZmFybGV5bng=?=

> >> >> <farleynx@discussions.microsoft.com> wrote on 27 feb 2008 in

> >> >> microsoft.public.windows.terminal_services:

> >> >>

> >> >> > Hello,

> >> >> >

> >> >> > I have several users connecting to a Win2K3 Terminal

> >> >> > Server that need their local printers mapped. However, I

> >> >> > would like to restrict them to only being able to map

> >> >> > their local default printer. The following registry

> >> >> > setting controls that on the client side, but I don't have

> >> >> > access to the local computers in order to make that

> >> >> > change.

> >> >> >

> >> >> > HKCU\Software\Microsoft\Terminal Server

> >> >> > Client\Default\AddIns\RDPDR\RedirectDefaultPrinterOnly

> >> >> >

> >> >> > I thought I might be able to control this through the

> >> >> > group policy so I created a custom .adm file (see below).

> >> >> >

> >> >> > ;Redirection of A Terminal Server Client's default printer

> >> >> > only

> >> >> >

> >> >> > CLASS USER

> >> >> >

> >> >> > CATEGORY !!WindowsComponents

> >> >> >

> >> >> > CATEGORY !!TS_GP_NODE

> >> >> >

> >> >> > CATEGORY !!TS_CLIENT

> >> >> >

> >> >> > KEYNAME "Software\Microsoft\Terminal Server

> >> >> > Client\Default\Addins\RDPDR\RedirectDefaultPrinterOnly"

> >> >> >

> >> >> > POLICY !!RedirectDefaultPrinterOnly

> >> >> >

> >> >> > EXPLAIN

> >> >> > !!RedirectDefaultPrinterOnly_Explain

> >> >> >

> >> >> > VALUENAME RedirectDefaultPrinterOnly

> >> >> > VALUEON NUMERIC 1

> >> >> > VALUEOFF DELETE

> >> >> >

> >> >> > END POLICY

> >> >> >

> >> >> > END CATEGORY ; TS_CLIENT

> >> >> >

> >> >> > END CATEGORY ; TS_GP_NODE

> >> >> >

> >> >> > END CATEGORY ; WindowsComponents

> >> >> >

> >> >> > [sTRINGS]

> >> >> > WindowsComponents="Windows Components"

> >> >> > TS_GP_NODE="Terminal Services"

> >> >> > TS_CLIENT="Client"

> >> >> > RedirectDefaultPrinterOnly="Redirect Client Default

> >> >> > Printer Only" RedirectDefaultPrinterOnly_Explain="Will

> >> >> > redirect the client's default printer only. All other

> >> >> > printers will not be available during the Terminal

> >> >> > Services session."

> >> >> >

> >> >> > The .adm file imported without errors and the setting is

> >> >> > available in the group policy editor. However when I

> >> >> > enable the setting and test it, all the printers are still

> >> >> > mapped and the registry setting is not created or modified

> >> >> > on the client.

> >> >> >

> >> >> > Is this even possible via the method I am using, am I

> >> >> > missing something or is there a better way to achieve the

> >> >> > intended result?

> >> >> >

> >> >> > Thanks,

> >> >> > farleynx

>

  • 4 months later...
Guest Renato Jr
Posted

Client Printer Redirection - farleyn

 

Client Printer Redirection - farleyn

 

Hi all, how are you?

 

A sdescribed at MS Article (http://support.microsoft.com/kb/911913), your workstations must have the 'last' TSClient for to recognize this registry´s settings!!

 

Tks,

 

Renato Jr


×
×
  • Create New...