Conflict from autocreated pdf converter in terminal server

[steveoch]

I am running a Windows 2003 terminal server and our office uses 4 different software packages that all use the Amyuni PDF Converter. When users log in to terminal server, their local printers are auto-created within their terminal server session, including auto-creating the Amyuni printers they have on their local machines. These auto-created Amyuni printers cause pdf converter print jobs to fail within terminal server. If we delete all the auto-created Amyuni printers, then we can run the pdf converter just fine. Problem is, they don't stay deleted, and we'd have to continually delete every time someone logs in. Is there a way to set a terminal server group policy that blocks the auto-creation of Amyuni printers? Other suggestions?

[MetroHiSpeed]

My suggestion is to have the users change their Remote Desktop Connections. To do this in XP - open the Remote Desktop Connection dialog box for the server, click the "Options" button, there is a 'Local Resources' tab, in the "Local devices and Resources" group box un-check the Printers check box. This will stop all local printers from being auto created on the Term Server for that user. Vista and Win 7 have similar options for their connections and all your users will have to do this so make sure they save their connection changes. Good luck.

Bob