Easy Print driving me crazy
- My Company went to Windows 2008, replacing our Windows 2000 Terminial servers. All seemed well at first until we started printing, when we preview everything looks great, when we click print on Windows XP SP3 with .NET 3.0 SP2 and .NET 3.5 with all windows updates including the new RDC installed it prints but on the pages the fonts are spaced weird and our nice barcode has turned into gibberish. On a local PC I would assume the font is missing that our application uses, would that be the case with EasyPrint? Does the font used have to exist on the local PC?
To try and solve it I installed the local drivers for each printer and used a GPO to make sure Easy Print was tried first, when I do this randomly the TS wont grab their printer, same person disconencts/reconnects to same server and then it works. I put easy print first they can ALWAYS print just all with gibberish instead of bar codes and the fonts are spaced out strange.
3 Terminal Servers runninging Windows 2008 32bit, all dual Xeons with 4 Gigs of Ram Each
211 Windows XP SP3 Workstations
72 Windows Vista SP2 Workstations
All have .NET 2.0, .NET 3.0 SP2, .NET 3.5 installed with RDC 6.1 installed.
Everything connects to a WIndows 2008 Domain setup and group policy is setting the Terminal server policies.
Various Printers, including:
HP Laserjet MP6
HP Laserjet 1160 (the majority)
HP Laserjet P2015s
Kyocera KX-1030D
Kyocera KX-1300DN
Brother HL-7820N
Dell 2330DN
HP Laserjet 1200
HP Laserjet 1300
HP CL-3830
BTW for testing I actually made my Adobe PDF printer the default printer, when printing through Easy Print even the PDF has the same screwy results.
Answers
- Can you please apply this .NET QFE - it should resolve the issue.
- Marked As Answer byChrista AndersonMSFT, ModeratorWednesday, June 17, 2009 7:46 PM
- This is the full list of QFEs for TS Easy Print
http://support.microsoft.com/kb/954744 - FIX: Some pages are printed in the incorrect orientation when you use Terminal Services Easy Print to print a document that contains both portrait-oriented pages and landscape-oriented pages
http://support.microsoft.com/kb/954743 - FIX: After you apply hotfix 954744, printing performance may be significantly slower when you print documents by using Terminal Services Easy Printhttp://support.microsoft.com/kb/946411 - FIX: When you print an XPS file on a Windows XP Service Pack 2 or Service Pack 3-based computer, the characters in the XPS file print incorrectly
All three should be applied on the client machine- Marked As Answer byChrista AndersonMSFT, ModeratorWednesday, July 01, 2009 4:58 PM
All Replies
- Can you please apply this .NET QFE - it should resolve the issue.
- Marked As Answer byChrista AndersonMSFT, ModeratorWednesday, June 17, 2009 7:46 PM
- This is the full list of QFEs for TS Easy Print
http://support.microsoft.com/kb/954744 - FIX: Some pages are printed in the incorrect orientation when you use Terminal Services Easy Print to print a document that contains both portrait-oriented pages and landscape-oriented pages
http://support.microsoft.com/kb/954743 - FIX: After you apply hotfix 954744, printing performance may be significantly slower when you print documents by using Terminal Services Easy Printhttp://support.microsoft.com/kb/946411 - FIX: When you print an XPS file on a Windows XP Service Pack 2 or Service Pack 3-based computer, the characters in the XPS file print incorrectly
All three should be applied on the client machine- Marked As Answer byChrista AndersonMSFT, ModeratorWednesday, July 01, 2009 4:58 PM
- Any idea where I can download these hotfixes without contacting them just to download hotfixes?
I need to mass deploy these to 287 Windows XP Pro SP3 workstations
Most have .NET 3.5 SP1 installed (NO .NET 3.0 at all) and some have both I think.
If I have .NET 3.5 installed do I need to install 3.0 and these hotfixes? - No - these QFEs should work for .NET 3.5 / .NET 3.5 SP1. You will have to contact Microsoft Customer Support to get these - there is no web download.
These patches does not resolve this issue. We went back to native driver and it worked fine. Microsoft needs to resolve this.
