Running a farm with app server. LoadBalancer > 4 Terminal Servers. We upgraded 6.2 to 7.3 this weekend... now users are reporting printing problems. Some are running 6.x client, others might be running 7.x. I tested both. Basically 1 TS has no 2x Universal Printer. <-- this is the big one b/c we have no idea what to do here. I reinstalled the Agent, but no go. Another TS has the printer but does not seem to print a job. We are testing the other two as we speak.
I've been trying to fix this mess all morning. Basically 2 servers have no 2x printer. I've been wroking with one of them. Removing 2x Agent did not work, as when I reinstall it says "agent did not reply". I finally manually removed the registry keys and folders, got it to reinstall, but same thing. So I am not even up to troubleshooting printers yet. Install says "Complete" and then goes to "Agent did not reply". UPDATE*: Finally, after many tries..I got that too work. Back to printer issue...
So I have the agent running on all servers, but the 2x Universal Printer is not working. If I right-click I get --------------------------- Printer Properties --------------------------- The '2X Universal Printer' printer driver is not installed on this computer. Some printer properties will not be accessible unless you install the printer driver. Do you want to install the driver now? --------------------------- Yes No ---------------------------
Looks like I was able to solve the issue. There were several iterations of the problem/solution before I reached this, so no guarantee this is the complete process -- but here we go: Stop Agent on affected server. Delete 2X folder. If errors, locate the files in use, kill using TaskMgr, and then delete. Delete 2X registry key under HKLM\System\CurrentControlSet\Services Reboot Server Delete Printer Port [XX] from Printer Server properties. Delete 2x Driver from Print Server Drivers. Reboot Server. Disable all Anti-Virus (We had TrendMicro) Run the 2XVDS.MSI installer. CUSTOM install only the Terminal Server Agent. Finish Install. Reboot server. Check LoadBalancer/Gateway for connection Test printer. It was not that clean - we had various issues in the process. Took us a while to get the process down. But this combination of steps did resolve the issue - perhaps not all were needed. I would urge disabeling all AV. Ultimately we knew the driver did not install correctly, we knew old drivers were left behind, and we felt AV was causing a problem.
