Terminal Services 2003 printer redirection

[craigholt1]

I have a complete windows 2003 domain, with terminal server 2003. I have several users who logon to this server without issue.

I have installed printers locally and then deleted them so that the printer drivers are stored on the server. (is this the correct method?)

The users have then logged on and there local printers have been setup by terminal services using the redirection which I understand to be a default method.

For no reason this appears to have just stopped working altogether and no printers now work? I have rebooted the server and checked the printer spooler and everything seems fine. Can anyone please help as no printers are currently working??

If anyone successfully helps me I shall make a nice contribution to this site!!! Please help soon.

 

[bkuepers]

A few questions for you...

Is this server a TS only? Are the printers you need mapped printers in the office, or local printers that need to be mapped through the TS client?

It they are remote printers you should just be installing the drivers by going to the printers folder and going into server properties -> Drivers -> and then adding the printers you need. When the users logs on they will just get their printer mapped as long as the port for the printer they want mapped is LPT: or USB:. If they are for example DOT4: ports read the following.

http://support.microsoft.com/default.aspx?scid=kb;en-us;302361

However there are other methods of redirecting printers on a terminal server. Service Pack 1 actually added universal printing which maps printer drivers it doesn't have to one univeral one. In my environment I use mapping with a printsubs.ini file that maps all laserjet printers to a HP LaserJet 4 driver, etc.

If you want a great guide to TS Printing please read here. I've stolen all my knowledge from Brian Madden.

http://www.brianmadden.com/content/content.asp?ID=62

Good luck

 

[craigholt1]

Thanks is advance... this is really getting me stressed.

This is a TS only server. The printers are local printers to the remote users. The drivers are installed on the TS server as they were working before the weekend? I have now upgraded to SP1 so that this new addition should help but this will not work either. Do you think something may have changed config settings?

I look forward to your response.

 

[bkuepers]

My next step would be to check the event log. Are there any errors with the source of termservdevices event 1111? Those usually point to down the right direction to get these things resolved.

For the server to make a match the driver name on the local and the terminal server need to exactly match, even uppercase/lowercase.

Let me know what you find in the event log.