Ok Default Printer Issues Server Setup: Windows Server 2003 - 2X v6 bld 419 (Enterprise edition) RDP-TCP connection set to pick client configs for printing. Client Setup: Client is same (v6 bld 419) on Vista (2 IT people doing 2X eval) This happened with v6 bld 416 for us too. 2X client setup to print to default printer. Problem: User has his client set up identical to mine (I exported my *.2xi file & imported it to his so...) and we are both using the same printer and driver (installed as local TCP/IP port). He consistently gets the 2X UPD as his default printer (actually happens with mstsc too). Both of us are admins on our own PCs and the Server. The system installs all of his printers; however, just goes to the UPD driver. Troubleshooting done so far: I used his computer with my credentials and all worked as expected (correct default printer)- To me that ruled out his client config. Had him use my computer with his credentials and all worked as expected (correct default printer) - To me that ruled out User ID issues too. Uninstalled 2X Client, cleaned out registry, and reinstalled...same problem. Went to a totally different machine (XP) installed 2X client - neither of us had any default printer issues. Does anyone have any ideas on what would cause this? I just cannot figure out anything else to try. Thanks & Have a Great Weekend All (or hope ya had one)
I've got the exact opposite problem. I just want to use the 2X UPD and instead it installs all my printers and will only print to the default printer on the client.
Thanks for the reply Nixiu I had already resolved my issue, sorry I didn't post that. I simply rebuilt the print spooler (ran cleanspl.exe from the resource kit...careful doing that guys, it wipes out EVERYTHING). joejohns, I'm sure you've already tried; however, not sure how much work you do with Terminal Servers...anyway, make sure that you set the terminal server's rdp-tcp connection to not allow the client configuration (start>run>tscc.msc) or set the GPO to not allow them
