Craig, you're a champ. Works perfectly. Let me contribute this to the list:
#!/bin/bash # Logon wrapper script based on Xdialog DOMAIN=YOURDOMAIN SCRIPTPATH=/opt/SCRIPTS/win2k8 OPTARGS="-i -A 16 -l us_NL -O -d $DOMAIN -N off -m" UTTSC=/opt/SUNWuttsc/bin/uttsc LOGIN=$($SCRIPTPATH/Xdialog --stdout --no-cancel --smooth --fixed-font --title "Welcome to $DOMAIN Network" \ --password=2 --2inputsbox "Enter your username and \ password." 25 50 "Username:" "" "Password:" "") USERNAME="$(echo $LOGIN | cut -d / -f 1)" PASSWORD="$(echo $LOGIN | cut -d / -f 2)" #make the connect! echo $PASSWORD|$UTTSC $OPTARGS -u $USERNAME IP/OR/HOST You need to put Xdialog in the /opt/SCRIPTS/win2k8 directory. Yes I know the topic is wrong; guess some automation going on here. Patrick. On Wed, Nov 23, 2011 at 3:00 PM, Patrick <[email protected]> wrote: > Awsome, thanks! I will give it a try. > > > On Wed, Nov 23, 2011 at 2:55 PM, Craig Bender <[email protected]>wrote: > >> You need to provide the credentials before you ever see the Windows login >> screen. (Same is true for MS-RDC). Today you can do that buy writing a >> small Zentiy script to run in kiosk mode or you can use Oracle VDI as the >> front-end to your Terminal Server farm. >> >> >> On 11/23/11 4:51 AM, Patrick wrote: >> >>> Hi all, >>> >>> At a customer site we are installing SRSS 5.2.3 with UTTSC: >>> 4_50,REV=2010.09.25.13.34. >>> The customer will be using Windows 2008 R2 Remote Desktop connection >>> broker with 3 windows 2008 terminal servers attached. >>> >>> Kiosk is configured to use the uttsc connector is to connect to the >>> first (.36) of the 3 terminal servers. .37 and .38 being the other two >>> servers. >>> >>> On initial login the customer provides his credentials after which the >>> screen updates and only username seems to be passed to one of the >>> terminal servers. (the rdp session seems to be redirected), The customer >>> needs to provide his password for a second time. >>> >>> We can verify the customer has logged in on the .37 while we connected >>> to the .36 so session brokering in Windows 2008 seems to work nicely; >>> except for the fact we need to provide the password a second time. >>> >>> If we disconnect the sessions and restart the kiosk, we connect to the >>> .36 again; provide credentials then connection broker will instantly >>> provide our latest session on the .37 without asking for a password. >>> This is the behaviour I was looking for in the initial connect aswell. >>> Is this something which needs be fixed on server or client side ? >>> >>> regards, >>> >>> Patrick >>> >>> >>> >>> ______________________________**_________________ >>> SunRay-Users mailing list >>> [email protected] >>> http://www.filibeto.org/**mailman/listinfo/sunray-users<http://www.filibeto.org/mailman/listinfo/sunray-users> >>> >> ______________________________**_________________ >> SunRay-Users mailing list >> [email protected] >> http://www.filibeto.org/**mailman/listinfo/sunray-users<http://www.filibeto.org/mailman/listinfo/sunray-users> >> > >
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
