[THIN] Re: Print jobs redirecting to wrong printer

  • From: "Evan Mann" <emann@xxxxxxxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 5 Oct 2005 09:03:13 -0400

Both my server have the printers and faxes folder.  Do you have a GPO
setting disabling this?  My PS4 servers are all default loadings, very
little GPO applied except for UI type modifications.  The only printer
change I made in the registry is the one for giving admins access to all
queues.
 

________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Schneider, Chad M
Sent: Wednesday, October 05, 2005 9:02 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Print jobs redirecting to wrong printer


Why is it that when I go to \\servername, PS 4.0 W2K3 server, I don't
see a printers folder, to look at the printers created on the server?

________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Evan Mann
Sent: Wednesday, October 05, 2005 7:39 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Print jobs redirecting to wrong printer


Add the Print sub key manually.  The documentation doesn't mention that.
 

________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Schneider, Chad M
Sent: Tuesday, October 04, 2005 10:35 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Print jobs redirecting to wrong printer


But I can't find this key on my Citrix PS 4.0 servers....
 
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Print\


________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Schneider, Chad M
Sent: Tuesday, October 04, 2005 9:30 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Print jobs redirecting to wrong printer


CTXPRN_ADMINS_CAN_MANAGE (0x00004000)

Description. To preclude the possibility of an administrative user
inadvertently

printing to a printer in someone else's Terminal Services session, the
default

security descriptor used to auto-create client printers no longer
includes any rights

for the administrator's group. Only the user executing in the correct
session context

has rights to the auto-created printers for the session. Administrators
can still grant

themselves rights to any client printer by taking ownership of the print
queue and

adding the desired rights.

Default Value. Zero, unless the bit value is set in the REG_DWORD
registry value

"DefaultPrnFlags" at HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Print\.

Overriding Presentation Server policy rule. None.


________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Evan Mann
Sent: Tuesday, October 04, 2005 4:39 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Print jobs redirecting to wrong printer


PS4.0 is set so admins have NO access to other users auto-created
queues.  You need to make a registry change to allow this.  I do n ot
know if this is a 4.0 change or it was done in 3.0 and prior.
 
You can read about it on page 249 of the 4.0 Advanced Concepts guide.

________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Joe Shonk
Sent: Tuesday, October 04, 2005 5:31 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Print jobs redirecting to wrong printer



If the user has administrative rights on the server, they can see and
print to other user's auto-created printers.

 

Joe

 

________________________________

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of jgates@xxxxxxxxxxxxxx
Sent: Tuesday, October 04, 2005 1:56 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Print jobs redirecting to wrong printer

 


Started having a weird issue on one of our servers we had a users print
job go to another users printer.  Which caused a data security
violation.  We are using W2K and MF1.8.  I double checked the client
name was unique and it was a unique username.  We're in the process of
moving to MPS 3.0 on W2K3.  Digging through the threads looks like it's
still an issue with 3 and 4.  Has anyone ran across this?   

Thanks, 

Jobe

Other related posts: