L
Louigee
Guest
Recently had an issue where remote clients were having trouble setting
their DEFAULT printer in a Terminal Services Session. When they would
log into either Terminal Server, they would get WHATEVER the
Administrator of the Terminal Server (moi) had set on my previous
login session. They would set their own LOCAL printer as default,
logout and log back in and have their default printer revert BACK to
whatever the administrator of the Terminal Server (moi) had set. Ie.
Default printer setting in Terminal Services was not working.
Scenario: 2 Terminal Servers. Both in their own OU (Org Unit).
Seperate group policy for these Terminal Servers - a locked down group
policy. We inherited this network setup, so its nuances were unknown
to me - as were the ramifications for some of the obtusely worded
policies
A person called "Inn Jinn" on the SBS usenet group suggested this:
1. Open the Terminal Service Configuration snap-in.
2 Right click the RDP-Tcp connection, and click Properties.
3 In the Client Settings tab, ensure that you check the "Use
connection
settings from user settings" and "Default to main client printer"
items.
4 Log off the client and then reconnect to the terminal server
to test
again.
My "Default to main client printer" was GREYED OUT and disabled.
Ouch. Right underneath that bit of information in Inn Jinn's post
was:
"Please also check the following group policies on all level of
containers, such as domain, the terminal server OU and the local
policy on the terminal server. Please ensure that the following group
policies are not enabled.
[Computer Configuration\Administrative Templates\Windows Components
\Terminal Services\Client/Server data redirection\Do not set default
client printer to be the default printer in a session] "
I checked this policy on the LOCKED DOWN policy of the Terminal
Servers. Ouch. It was enabled. I had enabled this the other day in
trying to fix the very same issue. I set the policy to NOT DEFINED.
Ran "gpupdate /force" on both terminal servers and the Domain
Controller. Checked the RDP-Tcp connection. "Default to main client
printer" was now checked.
I tested the Default printer from a remote client. Their default
printer was now defaulting to their own LOCAL default printer for
starters. Changing the default printer to something else, would now
stick after logging out and logging back in. Thanks to Inn Jinn in
the SBS group
Now if only we could set a SINGLE printer (the client's default
printer) to come across the Terminal Server tunnel, THAT would be
awesome.
their DEFAULT printer in a Terminal Services Session. When they would
log into either Terminal Server, they would get WHATEVER the
Administrator of the Terminal Server (moi) had set on my previous
login session. They would set their own LOCAL printer as default,
logout and log back in and have their default printer revert BACK to
whatever the administrator of the Terminal Server (moi) had set. Ie.
Default printer setting in Terminal Services was not working.
Scenario: 2 Terminal Servers. Both in their own OU (Org Unit).
Seperate group policy for these Terminal Servers - a locked down group
policy. We inherited this network setup, so its nuances were unknown
to me - as were the ramifications for some of the obtusely worded
policies
A person called "Inn Jinn" on the SBS usenet group suggested this:
1. Open the Terminal Service Configuration snap-in.
2 Right click the RDP-Tcp connection, and click Properties.
3 In the Client Settings tab, ensure that you check the "Use
connection
settings from user settings" and "Default to main client printer"
items.
4 Log off the client and then reconnect to the terminal server
to test
again.
My "Default to main client printer" was GREYED OUT and disabled.
Ouch. Right underneath that bit of information in Inn Jinn's post
was:
"Please also check the following group policies on all level of
containers, such as domain, the terminal server OU and the local
policy on the terminal server. Please ensure that the following group
policies are not enabled.
[Computer Configuration\Administrative Templates\Windows Components
\Terminal Services\Client/Server data redirection\Do not set default
client printer to be the default printer in a session] "
I checked this policy on the LOCKED DOWN policy of the Terminal
Servers. Ouch. It was enabled. I had enabled this the other day in
trying to fix the very same issue. I set the policy to NOT DEFINED.
Ran "gpupdate /force" on both terminal servers and the Domain
Controller. Checked the RDP-Tcp connection. "Default to main client
printer" was now checked.
I tested the Default printer from a remote client. Their default
printer was now defaulting to their own LOCAL default printer for
starters. Changing the default printer to something else, would now
stick after logging out and logging back in. Thanks to Inn Jinn in
the SBS group
Now if only we could set a SINGLE printer (the client's default
printer) to come across the Terminal Server tunnel, THAT would be
awesome.