Friday Jul 27, 2007

Hot Desking with Topaz Signature Pads On Citrix

You can use serial based signature capture pads such as the Topaz SigLite 1X5 with Windows Sessions using either Citrix or an RDP client.  Normally these things work just fine, however you will find that if you attempt to hot desk to another Sun Ray you'll get an error trying to use the signature pad stating basically that the COM Port is in use or does not exist.  There are three things that you must do.

You'll want to ensure that you are using the utports script along with a utaction so that the mapping to the com ports is always correct and the port you mapped (i.e. COM1:) gets mapped to the new Sun Ray.

Under Citrix, you must also do net use com1: \\\\client\\com1:

Normally that should be it.   Unless you hot desk.  Citrix holds the ports open and when you hot desk, not only does Sun Ray close the port, the mapping also changes from one physical Sun Ray to another.  This will render the sig pad useless and it won't recover even if you close the app, unmap and remap the com port.  You can add the following line to the wfclient.ini to the [WFClient] section


The only subtlety is which file to edit.  If a normal Solaris user, you'd edit $HOME/.ICAClient/wfclient.ini, if CAM using prototypes you'd edit the copy of wfclient.ini in the prototypes directory, and if using the master files you'd edit /usr/lib/ICAClient/config/wfclient.ini.

 You can now hot desk between Sun Rays and use your signature pad as you move.  Depending on how the application that accesses the pad opens and closes the com port, you might have to stop and start the application however.  Since most users write their own application to use these devices, make sure that you close the port after the signature is captured.

Thursday Feb 15, 2007

Sun Ray Serial Port Mapping

Mapping the serial or com ports from a Sun Ray to a Windows Session using the Sun Ray Connector for Windows doesn't have to be confusing.  Here's a handy little "how to".

First we need to determine what ports we want to map.

On a Sun Ray 2 or 2FS there is one serial port.  On a Sun Ray 170 and 270 there are two ports.  We need to know the path in order to provide it to the Sun Ray Windows Connector.

For Sun Ray 2 or 2FS the serial port is:


For Sun Ray 170 and 270 the serial ports are:



Now we need to pass those ports to the Sun Ray Windows Connector:

/opt/SUNWuttsc/bin/uttsc -r comport:COM1=$DTDEVROOT/unit/dev/term/a Windows_Server

Now what will that look like from your windows session?

Open up a command prompt and type change port /query.  You will see

Note the mapping for COM1.  That means it's going through the Sun Ray Windows Connector down to your Sun Ray.

But does it work?  Yes.  What you don't have serial device to try it?  No problem.  Telnet ssh to the Sun Ray Server.  If you need a  free ssh client for windows, give PuTTY a shot.  Sign in and then su to root (or an account that has privileges to run truss).  Find the child process for utseriald (it will be the one that does not have a parent PID of 1).  Note that while it's not doing anything you'll see a lot of pollsys' going by.  The more Sun Rays you have with serial ports the more of these you will see.

Now go back to your command prompt that you issued the change port /query command in and type dir > COM1

Watch the ssh session that you are running truss in.  You will see a flurry of activity.

 Make sure you break out of your truss before closing the ssh window.

How do you map two ports?  Easy,  we just need to pass both ports to the Sun Ray Windows Connector:

/opt/SUNWuttsc/bin/uttsc -r comport:COM1=$DTDEVROOT/unit/dev/term/a -r comport:COM2=$DTDEVROOT/unit/dev/term/b Windows_Server

Same other steps from above.  Note the difference now in the change port /query command.

You can do your same truss test as above, just for fun send the directory listing out to COM2.

I can hear it now.  That's all well and good but I don't have Sun Ray 2 series or a Sun Ray 170.  Well in this case you'll need to get a supported USB to Serial Adapter.  Let's repeat (some) of the steps with an Inside Out Networks Edgeport/2.

The serial ports live in the same place, they just don't have as friendly of names.  If you want to cheat and make the names really friendly, check out this handy dandy serial port mapping script.

# ls $DTDEVROOT/unit/dev/term

Now we just need to pass those ports to Windows via the Sun Ray Windows Connector (all on one line of course).

/opt/SUNWuttsc/bin/uttsc -m -A 24 -r
comport:COM1=$DTDEVROOT/unit/dev/term/Inside_Out_Networks.V53072798-0a -r  comport:COM2=$DTDEVROOT/unit/dev/term/Inside_Out_Networks.V53072798-0b

Lather, rinse, repeat on the steps above if you want to see it in action.


Think Thin is a collection of bloggers that work with Oracle's Virtual Desktop portfolio of products.


« April 2014