Univeral Printer no Longer Showing for anyone

S

scottyyyc

Junior Member
Hey guys,

So lately we've noticed that the 2x universal printer isn't showing for anyone anymore in our load balanced TS environment, and we're scratching out heads a bit.

It's still enabled in the console, and we've made virtually no changes in the past while. Our clients and farm are reasonably current (10.1 b1227). We're going to try to upgrade to 10.5 tomorrow regardless to see if it fixes the issue, but we'rte a bit perplexed. We've also tried re-installing the TS agents, etc.

The Terminal Servers are 08R2 SP1. Ironically, the 2X UP shows when someone logs into the console (directly via. RDP), just not through the 2X app.

Thoughts? Logs seem relatively clean and clear. Any particular direction I should be heading?
 
Hmmm, I've been able to narrow down the problem a bit.

We seem to have 2 or 3 users at any given time who ARE getting the 2XUP. Investigating a little further, these users are using old versions of the clients (v8 and v9). Anyone using the v10 client isn't getting the 2XUP.

We normally install the client using the 'OverrideUserSettings=1' and the accompanying .2xc file. We've used the same .2xc file for some time now. That being said, I uninstalled the client from my workstation completely (even scrubbed the registry of 2X entries) and re-installed the client fresh without the .2xc file. I manually added in my server name, but still, no UP is added. So it's likely not something with the .2XC file.

I also disabled all client policies on the 2X server, disabling and re-enabled UP on the server, and also this morning tried the new 10.5 client. No luck. But if I put the v9 (build 9.0.1091 FYI) client back on my workstation, it works.

So some sort of bug we've stumbled across with the v10 client? Either way, I'll be upgrading to 10.5 tonight on the server side and testing again, but this will likely turn into a ticket/bug report. If nothing else, I'll have to roll my clients back to v9 for now, as a few people do use UP every now and again, and when they need it, it's important.

Any thoughts in the mean time are appreciated.
 
if you enable Terminal Server logging, reproduce the issue and check the terminal server logs in the log viewer, do you find any errors when trying to connect with a user whose printers are not coming up?

you can enable logging from the farm > terminal servers window by right clicking on enable debug. After applying the settings and reproducing the issue, retrieve the log from the same right click menu and they should open up in the log viewer.

what are the errors you get from there?
 
I gave that a try, but it didn't seem to show any relevant information.

I have a support case open with 2X on the matter.
 
You must log in or register to reply here.
Back
Top