- This topic is empty.
-
Posts
-
If I have a label printer connected to my D10DP via USB, connecting to a View session, but the VM is not even detecting a printer connected, what am I missing? I assumed WTOS would just pass through a USB device, similar to the way it does say a flash drive. The only entry I tried in my INI was:
Device=usbprinter AlwaysOnline=yes
No luck with it though. I was hoping to avoid defining a printer by name/port/type/etc. I just wast hoping the VM would a device via USB connected and do the work.
Thanks.
Try adding these two lines.
SessionConfig=ALL VUSB_PRINTER=yes
SessionConfig=PCoIP USBRedirection=PCoIPCG
Getting closer. Using those 2 lines, along with my 1, navigating to the Printer Setup window, I can print a test label. So, the terminal sees the printer. Great. Now, when I connect to my VM, I have a pre-created Windows printer called “Generic / Text Only”, using LPT1 (plugged into the terminal via USB again) and at that point, I can no longer print the test print function on the temrinal. Also, within the Windows VM the printer is grayed out and Offline. This might be a VMware question now.
Ok we think we have it. On the Windows side we changed the printer to use port USB001. Looks like that may get us going as a test print within the Windows VM worked.
Stupid question time:
If another WTOS device, say a V10L, picks up these settings from the INI, but doesn’t have any local printer connected, the settings are moot. There should be no side affects of these settings being acquired. Is this correct?
Is there any compromise with these entries on a V10L at 7.1_122 firmware? The one difference Is ee is the D10DP comes up with the printer as LPT 1, where as the V10L comes up as LPT On Board. Needless to say, on the V10 I can’t print.
Edit:
If I switch it manually to LPT (USB) we’re good.I’d like to control this through the INI obviously.
Just realized the lines we’re using for the D10DP:
Device=usbprinter AlwaysOnline=yes
SessionConfig=ALL VUSB_PRINTER=yes
SessionConfig=PCoIP USBRedirection=PCoIPWon’t work anyway on the V10L since it’s not doing PCoIP, they are doing RDP. Does that leave any chance to utilize 1 ini? If I have to split it it’s not ideal but doable.
Not sure it’s even valid, but, I did try switching the bottom lines to RDP instead of PCoIP. No such luck. Think it still has to do with that default port the V10, again on firmware 7.1_122, wants to use.
Slowly, slowly. So many questions.
1. The field “Printer Identification” is used to match the server-side installed printer driver name.
If the ID is “Generic/Text only”, this driver is used. If you use a HP Laserjet 4 printer and the this is also the printer driver name that is installed on the server, use ID=HP Laserjet 42. no problems for other units
3. typically these units only have USB ports. But as full USB redirection is not supported, Citrix and MS are using a trick. They convert the locally USB printer to a parallel printer. Now they map the parallel port in the session. That’s why you see LPTx in your session. Don’t worry about the “x”. It does not really matter.
4. This is not working as only PCoIP can redirect the USB port.
If you are using RDP, see #1CG
So it sounds as if with V10Ls using RDP, I’m not going to be able to accomplish this? My last steps tried, that flopped, were as follows:
Printer=LPT2 Name=”Generic / Text Only” Enabled=yes
DefaultPrinter=LPT2My understanding through some other documentation was that ThinOS considers the parallel port on a V10 as LPT1, then the first USB connected printer as LPT2.
If a unit has a physical parallel port, then the first USB port will be LPT2.
What happens when you connect the printer to the V10L? What do you see in the V10L’s local printer config as port and ID?
CG
Yeah, our V10Ls have a physical parallel port.
In the local printer config I can print successfully a test print from the Zebra printer when I switch from LPT (On-board) to LPT (USB).
I thought I had it just now by doing this:
On the VM I am connecting to, there is a pre-created printer called “Generic / Text Only”, utilizing that driver, and I switched it to use port TPVM. Here is how my INI was defined:
DefaultPrinter=LPT2
Printer=LPT2 Name=”Generic / Text Only” PrinterID=”Generic / Text Only” enabled=yes
ThinPrintEnable=yes Port=4000The printer though still shows as offline within the Windows VM. Strange because another VM I have sees the printer fine. I gotta be missing something.
I think the terminal and VM are passing off the printer “ok” with the settings I posted above, but, for some reason the printer in Windows doesn’t come out of “Use Offline” without intervention.
- You must be logged in to reply to this topic.