Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1576
  • Last Modified:

Redirected Printers Not Printing via TS

Hi all,

Workstation has Printer attached.  Prints fine from Pc.  Connect to TS via Remote Desktop with Local Printer set to be avilable and it wont priont.  If I monitor the spooler on the PC the job is being sent but nothing comes out.  Could this be related to Printer Owner/Print Group /e etc..?

A
0
Moncapitaan
Asked:
Moncapitaan
  • 10
  • 8
1 Solution
 
kevdinesCommented:
Hi Moncapitaan,

Are the clients Vista and/or 7? If so, is Easy Print working for other printers that don't specifically have the drivers installed on the Remote Desktop Server? If the clients are XP or below, are there any errors about drivers in the logs on the server? Apologies if oyu've already run through this - I couldn't be certain from the original description,

Cheers,

Kev
0
 
MoncapitaanAuthor Commented:
Their all XP.

Sorry what is "Easy Print"?
No errors in Logs.

Thanks
0
 
kevdinesCommented:
'Easy Print' is the cunning way to not need to pre-install the drivers for the specific printer on the RD server. It was introduced with Server 2008, but I think it's a bit fussy with XP clients. It uses the built-in XPS printer driver to send the print job to/from the RD server. I've got a vague recollection that it needs the XP client ot be connecting using the Remote Desktop Client 6.1, and the client needs to have the .NET Framework 3.0 or 3.5 installed too.

If you have access to the client's session on the RD server, can you open the 'Printers and Devices' window, right-click the printer and choose Properties? Take a look and see if the Model is listed as 'Remote Desktop Easy Print'? If so, it's worth checking that the XP client has RDC 6.1 and .NET 3.5 installed,

Cheers,

Kev
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
kevdinesCommented:
It's also worth checking which sort of printer drivers the XP client has installed - a quick bit of googling suggested that PostScript drivers seem to kick up more problems than PCL drivers,

Cheers,

Kev
0
 
MoncapitaanAuthor Commented:
Thanks for the feedback.

The model is listed as the Printer name and it is a PCL driver.

What I did notice in properties, if I click on the Security tab and click the users name the Permissions for the use are greyed out and the only one ticked is Special Permissions.  I dont know if that makes any difference.?

Anything else I can check ?>

Thanks
0
 
kevdinesCommented:
Nah, it seems unlikely to be a permissions issue in that case. Could you just confirm the RD server's operating system please? I was assuming that it was Server 2008 (from the zone that the question is in). If I've got that right, and Easy Print isn't configured on the RD server, then I think you're going to have to manually install the print drivers on the RD server, via the Print Management console.

http://technet.microsoft.com/en-us/library/cc732946.aspx

If you've got a 2008+ RD server, then it might be worth configuring Easy Print as it'll save you time in the long run. There's some info about it here:

http://technet.microsoft.com/en-us/library/cc753853%28WS.10%29.aspx
http://technet.microsoft.com/en-us/library/cc732264.aspx

HTH,

Kev
0
 
MoncapitaanAuthor Commented:
Thanks Kev, Yes it is Server 2008
The Workstations that connect to it via Remote Desktop are running XP if that makes any difference.??
0
 
kevdinesCommented:
Cool - run RSOP.msc on the server then, and see if the Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection\Use Remote Desktop Services Easy Print printer driver first policy has been set (from the 3rd link above). If not, check gpedit.msc (just to make sure that no-one set the policy locally).

If it's still unconfigured in both of those, and the XP client is using RDC 6.1 (check by running mstsc and clicking the icon in the top-left of the title bar, then choosing About). If it's not 6.1, you can download it here:

http://www.microsoft.com/downloads/en/details.aspx?FamilyId=6E1EC93D-BDBD-4983-92F7-479E088570AD&displaylang=en

It turns out that XP only needs .NET Framework 3.0 installed (but having 3.5 certainly won't hurt). If that's already installed too (and there are no .NET Framework errors in the client's eventlogs), then it looks like there's something mighty weird going on with Easy Print on your RD server, especially if that's not reporting any errors in its eventlogs either.

If that's the case, then it looks like you're going to have to manually install the print drivers on the RD server. If you can download an installer from the printer manufacturer, it'll probably be quicker, but I've got a feeling that to do a driver-only install you're going to have to install the Print Server role and run Printmanagement.msc on the RD server to get them installed. It's a PITA for one client's printer, but it might be the only option. What is the make/model of the printer, by the way?

Two last things to check, the 'Microsoft XPS Document Writer' is still there on the XP client, and that the RD server is not a domain controller.

Cheers,

Kev
0
 
MoncapitaanAuthor Commented:
On running RSOP.msc the following is not there :
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection\Use Remote Desktop Services Easy Print printer driver first

It goes as far as:
Computer Configuration\Administrative Templates\[System]/[Login]

GpEdit.msc goes a little further but no \Remote Desktop Services\ option.

A
0
 
kevdinesCommented:
Cool - if it's not appearing in RSOP, it just means that the setting isn't being applied via GPO (which isn't too surprising). The 'Remote Desktop Services' section looks like a red herring actually - that's for Server 2008 R2. If you could take a look in:

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection\Use Remote Desktop Services Easy Print

in both RSOP and gpedit, please? Same deal as before - we're looking to see if the Use Remote Desktop Services Easy Print printer driver first policy has been disabled anywhere. If it hasn't, then you'll need to run through the stuff in the previous post,

Cheers,

Kev
0
 
MoncapitaanAuthor Commented:
Hi Kev,

Ok in RSOP there is no Computer Configuration\Administrative Templates\Windows Components
However in GPEdit there is the whole lot including
Use Remote Desktop Services Easy Print Printer Driver - DISABLED

M
0
 
kevdinesCommented:
Right - it's starting to make a bit more sense now! As I see it, you've got two potential options:

1) Change the Use Remote Desktop Services Easy Print Printer Driver policy to Enabled, to switch on the Easy Print functionality.
2) Manually install the printer drivers for the misbehaving printer on the RD Server

Unless you've got a good reason for disabling the policy, I'd have thought that it would be a better solution to go with 1), as it should mean that you don't run into this problem with the next printer that someone installs. On the other hand, I was (again) thinking about Server 2008 R2 for installing the printer drivers, and it looks like you can still do it the easy way (run control printers from the command line, right-click and choose Server Properties, then add drivers from the Drivers tab). If your RD server is 64-bit, you might need both the 32-bit and 64-bit drivers. No need to install the Print Server role, though.

HTH,

Kev
0
 
MoncapitaanAuthor Commented:
Thanks Kev,

If I enable Easy Print
Is that it, will the printers just work or do I need to do more?

Thanks
M
0
 
kevdinesCommented:
Enabling Easy Print should make it work, provided RDC 6.1 and .NET 3.0+ are on the client,

Cheers,

Kev
0
 
MoncapitaanAuthor Commented:
DUDE, Looks like that did the trick.  I enabled the Easy Print, Upgraded to RDC 6.1 and they printed fine.
Big test is tomorrow when everyone is back in and using the system.

Will update you tomorrow

Thanks Kev

M
0
 
kevdinesCommented:
Good stuff - hope the testing goes/went well,

Cheers,

Kev
0
 
kevdinesCommented:
Hi Moncapitaan,

How are you getting on with this? Fingers crossed it's all up and running now,

Cheers,

Kev
0
 
MoncapitaanAuthor Commented:
Hi Kev,

Well its seems to be a success appart from one glitch I am struggling with on one machine/Printer.

It now prints from Remote Desktop which it didnt prior to activating Easy Print, however the Font is very wrong
on the printout.  Nothing I can find in the printer settings can change this.
To Confirm:
Local Print - Works fine, correct font.
Remote Destop - Works Fine, Dodgy font.

Any ideas?
I am happy at this stage that the original question has been successfully answered.  If you think the font issue
may need further digging, I can close and award this Q and open another with that Q?

Thanks for all your help so far Kev.

M
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 10
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now