OK I have a weird issue. I have a published application running from 1 server on 3 different remote workstations, each with its own printer. This application is designed to automatically print show tickets using a template to the printer called "2x universal printer", which as we all know is the named ported printer on the 2x server. When all 3 workstations are run, on each client we choose the local printer at the remote workstation in the 2x client config. Basically, whatever the first workstation to connect to the 2x application, all tickets from all 3 clients will print at that first workstations printer. We're running the most recent version of server v8, our license doesn't allow us to upgrade to 9. Any thoughts? We kinda need to get this figured out in the next day or two and our support agreement is out.
Three quick questions: 1 - Does each workstation log in with seperate credentials? 2 - Was the application installed after issuing the 'change user > install' switch? 3 - Does this happen when users run the full desktop?
Thanks for posting. 1. Each one connects to the terminal server with different user credentials, but the domain logins are the same. The terminal server isn't part of the domain. 2. I'll take a look at that, not sure off the top of my head. 3. We don't use the full desktop license, only the application server. And the printers are on the local workstations not the server. Thanks again, I'll check number 2 shortly.
On number 2, change user was not done. Actually terminal services were added after 2x, previously we only needed to run two at a time. Should we reinstall 2x server now that terminal services has been licensed and added?
Not really sure if a reinstall will work, might be worth a try. As to testing against the full desktop, try publishing a desktop (2X will allow a desktop to be published like an application). Then, instead of choosing just the application from the 2X window, the user can choose the published desktop. From the published desktop, the user would then open the application and print using the 2X Universal Printer. If it prints fine from the full desktop, then you can pretty well say that the problem lies with the way the application is written/installed.
Thanks again for your help, sorry for the delays. Things get hairy here sometimes. OK I created the desktop, got two workstations to run it simultaneously, had each open up paint and print an image to their local printers. I set each to ask the user which printer to use. So it looks like its working as prescribed. What I'm going to do next is run the application again and configure each client to ask which printer to use when the application sends a job to "2x universal printer".
OK, so here's an update. Ran from the application, and set each workstation to select a printer instead of automatically printing to the local printer. And for a while it worked. HOWEVER, after about 10 minutes, it stopped asking and started printing to random printers again. So we closed the application, ran the desktop, tried it that way, and same thing, it wouldn't ask and print to random printers again. OY!
Here's the final update for now, in case anyone has the same issue. The current version has issues with ticket and label printers sometimes, and we're the unfortunate recipient of the issue. Plus because our application has to send tickets to a named printer in a template on the app server we can't use RDP with specific printers, so we're basically stuck. But apparently the next version coming out in a month or so has a new print driver, so when it comes out we'll need to buy upgrade assurance to download it. I look forward to trying it out. If it doesn't work thought I'll be pretty steamed.
HI Which version of 2x are you using there has been an update in in 2X VirtualDesktopServer Version 9.0.0 (1071) on 17th Mar 2011 version is available for download from http://downloads.2x.com/#vds Regards,
