TS Printer Redirection Requires Administrator Rights

[pvision]

We are having an odd problem with Terminal Services under Server 2003. I have a remote WinXP workstation using RDP 5.2 connecting to a Win2003Standard server. There is an HP Laserjet 1300 connected to a USB port on the remote workstation.

If I connect via RDP as a domain Administrator, the printer maps fine. If I connected as another user (even one that is a member of the Print Operators group), the printer does not map.

I dont want to give all of these remote users administrator rights on the server, but I am having trouble determining where to assign the proper rights to allow a TS/RDP user to create a client printer on the server.

Any thoughts?

Thank you.

 

[markdmac]

First question is have you installed all required Print Drivers on the Server?

Next, if the printers are conencted via USB it is likely that your users will not be able to print to them by default. You will need to enable a registry setting on the client PC before they connect via TS.

I wrote the following script to do the registry edit. Copy the following text to notepad and save the file with a VBS extension.

'==========================================================================
'
' NAME: TSPrintFix.vbs
'
' AUTHOR: Mark D. MacLachlan , The Spider's Parlor
' URL: [URL unfurl="true"]http://www.thespidersparlor.com[/URL]
' (c) 2003 All Rights Reserved
' DATE  : 12/22/2003
'
' COMMENT: Fixes printing via terminal services to allow DOT4 printers
'
'==========================================================================
myPrompt = MsgBox("This script will set up your printers for use with Terminal Services",vbOKCancel,"Setup Printers for Terminal Services?")
If myPrompt = 1 Then 
	Set WshShell=WScript.CreateObject("WScript.Shell")
	keypath ="HKCU\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR\FilterQueueType"
	WshShell.RegWrite keypath, -1, "REG_DWORD"
	If WshShell.RegRead(keypath) = "-1" Then
		MsgBox "Setup was successful",,"Success"
	Else
		MsgBox "Sorry A Problem Was Encountered" & vbCrLf & "Make sure you have permission to write to the registry.",,"Something went wrong"
	End If	
End If
WScript.Quit

I hope you find this post helpful.

Regards,

Mark

 

[pvision]

Thank you for your reply.

The drivers are loaded on the server, and printer maping works fine if I connect to the Win2003 server as a member of the "administrators" group. It does not work for any other users.

FYI - Apparently Microsoft corrected the USB problem with RDP v5.2.

 

[BluePoet]

Did you ever find out how to resolve this issue? I believe we are at the same point with our users. We have done the above fix and it didnt change anything. If we set our users to admin rights they can print fine as well. I tried to set the print spool directory for everyone to have rights to it but that didnt seem to resolve the issue. Let me know if youve found the fix for this.

Blue

 

[markdmac]

I just want to verify that you guys have run the above script on a user workstation prior to their connection via TS.

I hope you find this post helpful.

Regards,

Mark