Hello,

TL> If those twenty users are solely using Windows perhaps your
TL> best optionwould be to go with the CAM solution suggested bij mr.
TL> Bender.
I am currently deploying a solution in our office based on
http://blogs.sun.com/ThinkThin/entry/cam_chooser_application
scripts utsplash and utmsgbox.

These scripts make a Yes-No-Cancel dialog and override the 3 buttons.
There's a drawback in the original solution: the third button restarts
the sun ray session (i.e. to update the script or clear caches) so we
seem to be limited to only 2 applications. 

In fact, we can run utsplash along with a dtsession, and restart by
RMB/Logoff on desktop or by closing the script's dialog window.
This allows to use a third button for applications as well :)

Here's a couple of variants for logging in to a Windows application
server we used to illustrate both rdesktop and uttsc:

[ x"$USER" = x ] && WUSER=__USERNAME__ || WUSER="$USER"
case "$USER" in
    utcu*) WUSER=__USERNAME__ ;;
esac

APP2RUN1="/usr/local/bin/rdesktop -u ${WUSER} -d MYDOMAIN -f -a 24 -k en-us -z 
-N -r sound:local OFFICE"
APP2RUN2="/opt/SUNWuttsc/bin/uttsc -u ${WUSER} -d MYDOMAIN -m -A 24 -l en_US 
AS-DEVEL-JAVA"

The WUSER hack didn't work for us yet since in non-smartcard mode users
are dynamic and nameless. Perhaps later we could employ a mapping from
Solaris to Windows usernames, i.e. by WUSER=`cat ~$USER/.winname`.

-- 
Best regards,
 Jim Klimov                            mailto:[EMAIL PROTECTED]

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to