I am having trouble with TS session printing for some remote users. For some reason when they make a successful remote conneciton to my TS (2003 R2) and then try to print a document to a local printer (attached to the clients computer) the document stays in the queue on their printer as "Remote Downlevel Doc" and never actually prints. I have tried installing the printer driver on the TS, as well as, configuring printer mapping on the TS. I have read around and have yet to find a solution to my issue. It seems that the document does get processed and sent to the remote users printer queue; however, it just stays in the printers print queue and never prints. The user has to stop the print spooler on his/her desktop and clear the spooler folder of the document and then restart the spooler just to be able to print anything (after the TS remote document get stuck in the queue). I have checked all of the basics regarding printer redirection by making sure that the RDP client is configured properly, as well as, checking the necessary options within the TS Configuration (client settings). Any help to resolve this issue would be greatly appreciated.

BTW, all remote clients are running Windows XP Pro SP2

This is a common symptom when using a printer driver which is not compatible with Terminal Services.
Uninstall the driver from the TS and then map the printer to a native driver, using the info in this article:

Windows 2000 or Windows Server 2003 Terminal Services server logs even...1111, 1