General discussions about Thinstation - a Linux-based thin client ()

c-l | 27 Jun 2012 16:07

Thinstation possibilities + usage scenario


Hello all,

I just started playing with the new 5.1.1 Thinstation.  Still new to all
this.  I've been able to successfully remote to my Desktop by entering my IP
address into RDesktop.  The most basic test, but at least it works ;)

My final goal for this product is to enable users to easily log on to their
workstation from any of those Thinstation PC's that will be in different
areas (board rooms, etc...).  I work under the assumption that users are
"dumb" and will not know by heart their Computer Name, nor their IP address,
nor they will always remember to leave their station turned on all the time.

All right, here's what I would like to achieve with Thinstation:

- User wants to log into his Windows 7 workstation.
- Opens up that PC (which sits in a common room), thinstation boots using
PXE (client)
- User is presented with a username / password form, enter his information
and hit "log in"
- Then, there is a process that finds the PC associated with the userID (we
use AD - not sure if it's easy to track)
- Once the PC is found, it finds it's IP Address and MAC address
- If the PC isn't turned on, it sends a magic packet to do a WOL
- Once the PC is accessible, it feed the IP address, then username /
password to the RDP session and this connects the user to his station.

So basically I need an easy 1-2-3 process so the user doesn't have to enter
any information more than once and doesn't need to know anything but his own
userid / password.

(Continue reading)

headers

Don Cupp | 27 Jun 2012 19:14

Re: Thinstation possibilities + usage scenario

It's theoretically possible, but the missing piece is this bridge that looks up the users pc. I don't recall any

software package that does this, but if it exists and is made for linux, I'm sure you could integrate it.

From: c-l <christian.lessard-H73XCZ5nTWM8G1Gfu+u36Q@public.gmane.org>
To: thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Sent: Wednesday, June 27, 2012 7:07 AM
Subject: [Thinstation-general] Thinstation possibilities + usage scenario

Hello all,

I just started playing with the new 5.1.1 Thinstation. Still new to all
this. I've been able to successfully remote to my Desktop by entering my IP
address into RDesktop. The most basic test, but at least it works ;)

My final goal for this product is to enable users to easily log on to their
workstation from any of those Thinstation PC's that will be in different
areas (board rooms, etc...). I work under the assumption that users are
"dumb" and will not know by heart their Computer Name, nor their IP address,
nor they will always remember to leave their station turned on all the time.

All right, here's what I would like to achieve with Thinstation:

- User wants to log into his Windows 7 workstation.
- Opens up that PC (which sits in a common room), thinstation boots using
PXE (client)
- User is presented with a username / password form, enter his information
and hit "log in"
- Then, there is a process that finds the PC associated with the userID (we
use AD - not sure if it's easy to track)
- Once the PC is found, it finds it's IP Address and MAC address
- If the PC isn't turned on, it sends a magic packet to do a WOL
- Once the PC is accessible, it feed the IP address, then username /
password to the RDP session and this connects the user to his station.

So basically I need an easy 1-2-3 process so the user doesn't have to enter
any information more than once and doesn't need to know anything but his own
userid / password.

Is this something that would be feasible on Thinstation, or it this too much
to ask? ;)
--
View this message in context: http://old.nabble.com/Thinstation-possibilities-%2B-usage-scenario-tp34080647p34080647.html
Sent from the thinstation-general mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Thinstation-general mailing list
Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Thinstation-general mailing list
Thinstation-general@...
https://lists.sourceforge.net/lists/listinfo/thinstation-general

headers

Ed Heron | 27 Jun 2012 20:10

Re: Thinstation possibilities + usage scenario

On Wed, 2012-06-27 at 07:07 -0700, c-l wrote:
> ...
> My final goal for this product is to enable users to easily log on to their
> workstation from any of those Thinstation PC's that will be in different
> areas (board rooms, etc...).  I work under the assumption that users are
> "dumb" and will not know by heart their Computer Name, nor their IP address,
> nor they will always remember to leave their station turned on all the time.
> ...

  It might be possible with a custom module to prompt for user name and
password, check a look up table for machine name and mac address, check
if machine is up, sending a WOL packet as needed and waiting for the
machine to be accessible, then build a rdesktop command line with
machine name, user name and password.

  That'd be a decent amount of work, though, and you'd have to maintain
that user name / machine name / MAC address data. Or, if you had a
server piece that ran on a nearby router or server, that could serve MAC
addresses from an ARP cache.

  You might want to start by verifying WOL works on your workstations.

  Would your workstations have static IP's or would you use some sort of
dynamic DNS scheme?

  Theoretically, it could be expanded to start VMs (Virtual Machines),
as well.  I wonder if it would be possible and/or desirable to have MS
Windows VMs shutdown after a configurable amount of inactivity...

  Wish I had time to play with it beyond idle speculation...

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

chris nelson | 28 Jun 2012 00:25

Re: Thinstation possibilities + usage scenario

here is a (probably poorly written :) script that i wrote to ask users
for their credentials and then startup freerdp (btw, i have found
freerdp FAR, FAR, FAR superior to rdesktop). it obviously does not do
the WOL or computer lookup for you, but its a start. it takes xfreerdp
options and server as input respectively.

#!/bin/bash
Xdialog --title "CCH Terminal Server" --left --icon=/lib/cch_freerdp/cch.xpm \
--password=2 --ok-label=Connect --3inputsbox "CCH Terminal Server" \
330x350 Username: ""  Password: "" Domain: "CCH" 2> /tmp/tmp.1
ret=$?
input=`cat /tmp/tmp.1`
rm -f /tmp/tmp.1
case $ret in
0)
        Xdialog --title "Connecting" --icon=/lib/cch_freerdp/cch.xpm
--timeout 10 --msgbox "Connecting to CCH Terminal Server Farm\nPlease
wait..." 400x150 &
        user=`echo "$input" | awk '{split($0,a,"/")}END{print a[1]}'`
        pass=`echo "$input" | awk '{split($0,a,"/")}END{print a[2]}'`
        xfreerdp -u "$user" -p "$pass" $1 $2
        ret1=$?
        echo "\n\nret=$ret1\n\n"
        case $ret1 in
        0)
                break;;
        131)
                kill `pidof Xdialog`
                Xdialog --title "Wrong Username or Password"
--icon=/lib/cch_freerdp/cch.xpm --msgbox "Wrong Username or
Password\n\nRemember: Do NOT put\n\"CCH\\\"\nin front of your
username." 400x150 & ;;
        *)
                kill `pidof Xdialog`
                Xdialog --title "Unknown Error"
--icon=/lib/cch_freerdp/cch.xpm --msgbox "Unknown error. Contact
Support.\n\nError Code=$ret1\n" 400x150 & ;;
        esac

        echo "user=$user" > /tmp/t
        echo "1=$1" >> /tmp/t
        echo "2=$2" >> /tmp/t

esac

chris

On Wed, Jun 27, 2012 at 12:10 PM, Ed Heron <Ed@...> wrote:
> On Wed, 2012-06-27 at 07:07 -0700, c-l wrote:
>> ...
>> My final goal for this product is to enable users to easily log on to their
>> workstation from any of those Thinstation PC's that will be in different
>> areas (board rooms, etc...).  I work under the assumption that users are
>> "dumb" and will not know by heart their Computer Name, nor their IP address,
>> nor they will always remember to leave their station turned on all the time.
>> ...
>
>  It might be possible with a custom module to prompt for user name and
> password, check a look up table for machine name and mac address, check
> if machine is up, sending a WOL packet as needed and waiting for the
> machine to be accessible, then build a rdesktop command line with
> machine name, user name and password.
>
>  That'd be a decent amount of work, though, and you'd have to maintain
> that user name / machine name / MAC address data. Or, if you had a
> server piece that ran on a nearby router or server, that could serve MAC
> addresses from an ARP cache.
>
>  You might want to start by verifying WOL works on your workstations.
>
>  Would your workstations have static IP's or would you use some sort of
> dynamic DNS scheme?
>
>  Theoretically, it could be expanded to start VMs (Virtual Machines),
> as well.  I wonder if it would be possible and/or desirable to have MS
> Windows VMs shutdown after a configurable amount of inactivity...
>
>  Wish I had time to play with it beyond idle speculation...
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general@...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

Bryan Keadle (.net | 28 Jun 2012 20:18

Re: Thinstation possibilities + usage scenario

how do you specify using freerdp vs rdesktop?

On Wed, Jun 27, 2012 at 5:25 PM, chris nelson <sleekmountaincat-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

here is a (probably poorly written :) script that i wrote to ask users
for their credentials and then startup freerdp (btw, i have found
freerdp FAR, FAR, FAR superior to rdesktop). it obviously does not do
the WOL or computer lookup for you, but its a start. it takes xfreerdp
options and server as input respectively.

#!/bin/bash
Xdialog --title "CCH Terminal Server" --left --icon=/lib/cch_freerdp/cch.xpm \
--password=2 --ok-label=Connect --3inputsbox "CCH Terminal Server" \
330x350 Username: "" Password: "" Domain: "CCH" 2> /tmp/tmp.1
ret=$?
input=`cat /tmp/tmp.1`
rm -f /tmp/tmp.1
case $ret in
0)
Xdialog --title "Connecting" --icon=/lib/cch_freerdp/cch.xpm
--timeout 10 --msgbox "Connecting to CCH Terminal Server Farm\nPlease
wait..." 400x150 &
user=`echo "$input" | awk '{split($0,a,"/")}END{print a[1]}'`
pass=`echo "$input" | awk '{split($0,a,"/")}END{print a[2]}'`
xfreerdp -u "$user" -p "$pass" $1 $2
ret1=$?
echo "\n\nret=$ret1\n\n"
case $ret1 in
0)
break;;
131)
kill `pidof Xdialog`
Xdialog --title "Wrong Username or Password"
--icon=/lib/cch_freerdp/cch.xpm --msgbox "Wrong Username or
Password\n\nRemember: Do NOT put\n\"CCH\\\"\nin front of your
username." 400x150 & ;;
*)
kill `pidof Xdialog`
Xdialog --title "Unknown Error"
--icon=/lib/cch_freerdp/cch.xpm --msgbox "Unknown error. Contact
Support.\n\nError Code=$ret1\n" 400x150 & ;;
esac

echo "user=$user" > /tmp/t
echo "1=$1" >> /tmp/t
echo "2=$2" >> /tmp/t

esac

chris

On Wed, Jun 27, 2012 at 12:10 PM, Ed Heron <Ed-MBvgLuVkLo/by3iVrkZq2A@public.gmane.org> wrote:
> On Wed, 2012-06-27 at 07:07 -0700, c-l wrote:
>> ...
>> My final goal for this product is to enable users to easily log on to their
>> workstation from any of those Thinstation PC's that will be in different
>> areas (board rooms, etc...). I work under the assumption that users are
>> "dumb" and will not know by heart their Computer Name, nor their IP address,
>> nor they will always remember to leave their station turned on all the time.
>> ...
>
> It might be possible with a custom module to prompt for user name and
> password, check a look up table for machine name and mac address, check
> if machine is up, sending a WOL packet as needed and waiting for the
> machine to be accessible, then build a rdesktop command line with
> machine name, user name and password.
>
> That'd be a decent amount of work, though, and you'd have to maintain
> that user name / machine name / MAC address data. Or, if you had a
> server piece that ran on a nearby router or server, that could serve MAC
> addresses from an ARP cache.
>
> You might want to start by verifying WOL works on your workstations.
>
> Would your workstations have static IP's or would you use some sort of
> dynamic DNS scheme?
>
> Theoretically, it could be expanded to start VMs (Virtual Machines),
> as well. I wonder if it would be possible and/or desirable to have MS
> Windows VMs shutdown after a configurable amount of inactivity...
>
> Wish I had time to play with it beyond idle speculation...
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Thinstation-general mailing list
Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Thinstation-general mailing list
Thinstation-general@...
https://lists.sourceforge.net/lists/listinfo/thinstation-general

headers

Mike Eriksen | 28 Jun 2012 20:38

Re: Thinstation possibilities + usage scenario

On Thu, Jun 28, 2012 at 8:18 PM, Bryan Keadle (.net)
<bkeadle@...> wrote:
> how do you specify using freerdp vs rdesktop?

in build.conf and after the initial build you grab the SESSION setting
from thinstation.conf.sample (as always) and put it into you
thinstation.conf<whatever>

Mike

>
> On Wed, Jun 27, 2012 at 5:25 PM, chris nelson <sleekmountaincat@...>
> wrote:
>>
>> here is a (probably poorly written :) script that i wrote to ask users
>> for their credentials and then startup freerdp (btw, i have found
>> freerdp FAR, FAR, FAR superior to rdesktop). it obviously does not do
>> the WOL or computer lookup for you, but its a start. it takes xfreerdp
>> options and server as input respectively.
>>
>>
>>
>> #!/bin/bash
>> Xdialog --title "CCH Terminal Server" --left
>> --icon=/lib/cch_freerdp/cch.xpm \
>> --password=2 --ok-label=Connect --3inputsbox "CCH Terminal Server" \
>> 330x350 Username: ""  Password: "" Domain: "CCH" 2> /tmp/tmp.1
>> ret=$?
>> input=`cat /tmp/tmp.1`
>> rm -f /tmp/tmp.1
>> case $ret in
>> 0)
>>        Xdialog --title "Connecting" --icon=/lib/cch_freerdp/cch.xpm
>> --timeout 10 --msgbox "Connecting to CCH Terminal Server Farm\nPlease
>> wait..." 400x150 &
>>        user=`echo "$input" | awk '{split($0,a,"/")}END{print a[1]}'`
>>        pass=`echo "$input" | awk '{split($0,a,"/")}END{print a[2]}'`
>>        xfreerdp -u "$user" -p "$pass" $1 $2
>>        ret1=$?
>>        echo "\n\nret=$ret1\n\n"
>>        case $ret1 in
>>        0)
>>                break;;
>>        131)
>>                kill `pidof Xdialog`
>>                Xdialog --title "Wrong Username or Password"
>> --icon=/lib/cch_freerdp/cch.xpm --msgbox "Wrong Username or
>> Password\n\nRemember: Do NOT put\n\"CCH\\\"\nin front of your
>> username." 400x150 & ;;
>>        *)
>>                kill `pidof Xdialog`
>>                Xdialog --title "Unknown Error"
>> --icon=/lib/cch_freerdp/cch.xpm --msgbox "Unknown error. Contact
>> Support.\n\nError Code=$ret1\n" 400x150 & ;;
>>        esac
>>
>>        echo "user=$user" > /tmp/t
>>        echo "1=$1" >> /tmp/t
>>        echo "2=$2" >> /tmp/t
>>
>> esac
>>
>>
>>
>>
>>
>>
>>
>> chris
>>
>> On Wed, Jun 27, 2012 at 12:10 PM, Ed Heron <Ed@...> wrote:
>> > On Wed, 2012-06-27 at 07:07 -0700, c-l wrote:
>> >> ...
>> >> My final goal for this product is to enable users to easily log on to
>> >> their
>> >> workstation from any of those Thinstation PC's that will be in
>> >> different
>> >> areas (board rooms, etc...).  I work under the assumption that users
>> >> are
>> >> "dumb" and will not know by heart their Computer Name, nor their IP
>> >> address,
>> >> nor they will always remember to leave their station turned on all the
>> >> time.
>> >> ...
>> >
>> >  It might be possible with a custom module to prompt for user name and
>> > password, check a look up table for machine name and mac address, check
>> > if machine is up, sending a WOL packet as needed and waiting for the
>> > machine to be accessible, then build a rdesktop command line with
>> > machine name, user name and password.
>> >
>> >  That'd be a decent amount of work, though, and you'd have to maintain
>> > that user name / machine name / MAC address data. Or, if you had a
>> > server piece that ran on a nearby router or server, that could serve MAC
>> > addresses from an ARP cache.
>> >
>> >  You might want to start by verifying WOL works on your workstations.
>> >
>> >  Would your workstations have static IP's or would you use some sort of
>> > dynamic DNS scheme?
>> >
>> >  Theoretically, it could be expanded to start VMs (Virtual Machines),
>> > as well.  I wonder if it would be possible and/or desirable to have MS
>> > Windows VMs shutdown after a configurable amount of inactivity...
>> >
>> >  Wish I had time to play with it beyond idle speculation...
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Live Security Virtual Conference
>> > Exclusive live event will cover all the ways today's security and
>> > threat landscape has changed and how IT managers can respond.
>> > Discussions
>> > will include endpoint security, mobile security and the latest in
>> > malware
>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> > _______________________________________________
>> > Thinstation-general mailing list
>> > Thinstation-general@...
>> > https://lists.sourceforge.net/lists/listinfo/thinstation-general
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Thinstation-general mailing list
>> Thinstation-general@...
>> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general@...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>

--

-- 
Operator of the Danish TS-O-Matic.
http://thinstation.org
Thinstation consultant for hire - payable via PayPal

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

Bryan Keadle (.net | 28 Jun 2012 22:25

Re: Thinstation possibilities + usage scenario

Right, but what session setting? I've only seen "_TYPE=rdesktop". Do I simply change that to "_TYPE=freerdp" to "activate" it? (of course the package must be included in the build, which I have). How do I know that I'm actually using freerdp vs rdesktop?

On Thu, Jun 28, 2012 at 1:38 PM, Mike Eriksen <thinstation.mike-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

On Thu, Jun 28, 2012 at 8:18 PM, Bryan Keadle (.net) <bkeadle-iGCfEHTq0s2sTnJN9+BGXg@public.gmane.org> wrote:
> how do you specify using freerdp vs rdesktop?

in build.conf and after the initial build you grab the SESSION setting
from thinstation.conf.sample (as always) and put it into you
thinstation.conf<whatever>

Mike

>
> On Wed, Jun 27, 2012 at 5:25 PM, chris nelson <sleekmountaincat-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>>
>> here is a (probably poorly written :) script that i wrote to ask users
>> for their credentials and then startup freerdp (btw, i have found
>> freerdp FAR, FAR, FAR superior to rdesktop). it obviously does not do
>> the WOL or computer lookup for you, but its a start. it takes xfreerdp
>> options and server as input respectively.
>>
>>
>>
>> #!/bin/bash
>> Xdialog --title "CCH Terminal Server" --left
>> --icon=/lib/cch_freerdp/cch.xpm \
>> --password=2 --ok-label=Connect --3inputsbox "CCH Terminal Server" \
>> 330x350 Username: "" Password: "" Domain: "CCH" 2> /tmp/tmp.1
>> ret=$?
>> input=`cat /tmp/tmp.1`
>> rm -f /tmp/tmp.1
>> case $ret in
>> 0)
>> Xdialog --title "Connecting" --icon=/lib/cch_freerdp/cch.xpm
>> --timeout 10 --msgbox "Connecting to CCH Terminal Server Farm\nPlease
>> wait..." 400x150 &
>> user=`echo "$input" | awk '{split($0,a,"/")}END{print a[1]}'`
>> pass=`echo "$input" | awk '{split($0,a,"/")}END{print a[2]}'`
>> xfreerdp -u "$user" -p "$pass" $1 $2
>> ret1=$?
>> echo "\n\nret=$ret1\n\n"
>> case $ret1 in
>> 0)
>> break;;
>> 131)
>> kill `pidof Xdialog`
>> Xdialog --title "Wrong Username or Password"
>> --icon=/lib/cch_freerdp/cch.xpm --msgbox "Wrong Username or
>> Password\n\nRemember: Do NOT put\n\"CCH\\\"\nin front of your
>> username." 400x150 & ;;
>> *)
>> kill `pidof Xdialog`
>> Xdialog --title "Unknown Error"
>> --icon=/lib/cch_freerdp/cch.xpm --msgbox "Unknown error. Contact
>> Support.\n\nError Code=$ret1\n" 400x150 & ;;
>> esac
>>
>> echo "user=$user" > /tmp/t
>> echo "1=$1" >> /tmp/t
>> echo "2=$2" >> /tmp/t
>>
>> esac
>>
>>
>>
>>
>>
>>
>>
>> chris
>>
>> On Wed, Jun 27, 2012 at 12:10 PM, Ed Heron <Ed-MBvgLuVkLo/by3iVrkZq2A@public.gmane.org> wrote:
>> > On Wed, 2012-06-27 at 07:07 -0700, c-l wrote:
>> >> ...
>> >> My final goal for this product is to enable users to easily log on to
>> >> their
>> >> workstation from any of those Thinstation PC's that will be in
>> >> different
>> >> areas (board rooms, etc...). I work under the assumption that users
>> >> are
>> >> "dumb" and will not know by heart their Computer Name, nor their IP
>> >> address,
>> >> nor they will always remember to leave their station turned on all the
>> >> time.
>> >> ...
>> >
>> > It might be possible with a custom module to prompt for user name and
>> > password, check a look up table for machine name and mac address, check
>> > if machine is up, sending a WOL packet as needed and waiting for the
>> > machine to be accessible, then build a rdesktop command line with
>> > machine name, user name and password.
>> >
>> > That'd be a decent amount of work, though, and you'd have to maintain
>> > that user name / machine name / MAC address data. Or, if you had a
>> > server piece that ran on a nearby router or server, that could serve MAC
>> > addresses from an ARP cache.
>> >
>> > You might want to start by verifying WOL works on your workstations.
>> >
>> > Would your workstations have static IP's or would you use some sort of
>> > dynamic DNS scheme?
>> >
>> > Theoretically, it could be expanded to start VMs (Virtual Machines),
>> > as well. I wonder if it would be possible and/or desirable to have MS
>> > Windows VMs shutdown after a configurable amount of inactivity...
>> >
>> > Wish I had time to play with it beyond idle speculation...
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Live Security Virtual Conference
>> > Exclusive live event will cover all the ways today's security and
>> > threat landscape has changed and how IT managers can respond.
>> > Discussions
>> > will include endpoint security, mobile security and the latest in
>> > malware
>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> > _______________________________________________
>> > Thinstation-general mailing list
>> > Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> > https://lists.sourceforge.net/lists/listinfo/thinstation-general
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Thinstation-general mailing list
>> Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>

--
Operator of the Danish TS-O-Matic.
http://thinstation.org
Thinstation consultant for hire - payable via PayPal

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Thinstation-general mailing list
Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Thinstation-general mailing list
Thinstation-general@...
https://lists.sourceforge.net/lists/listinfo/thinstation-general

headers

Don Cupp | 28 Jun 2012 22:43

Re: Thinstation possibilities + usage scenario

Yes.

remove the rdesktop package and if everything works, you know. Also the ip entry screen tells you what it is about to run. The logs would also tell you what was run and if LOG_COMMANDS=true, then the exact cmd will be echoed to the logs(at least in 5.1).

From: Bryan Keadle (.net) <bkeadle-iGCfEHTq0s2sTnJN9+BGXg@public.gmane.org>
To: thinstation-general <at> lists.sourceforge.net
Sent: Thursday, June 28, 2012 1:25 PM
Subject: Re: [Thinstation-general] Thinstation possibilities + usage scenario

On Thu, Jun 28, 2012 at 1:38 PM, Mike Eriksen <thinstation.mike-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

On Thu, Jun 28, 2012 at 8:18 PM, Bryan Keadle (.net) <bkeadle <at> keadle.net> wrote:
> how do you specify using freerdp vs rdesktop?

in build.conf and after the initial build you grab the SESSION setting
from thinstation.conf.sample (as always) and put it into you
thinstation.conf<whatever>

Mike

>
> On Wed, Jun 27, 2012 at 5:25 PM, chris nelson <sleekmountaincat-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>>
>> here is a (probably poorly written :) script that i wrote to ask users
>> for their credentials and then startup freerdp (btw, i have found
>> freerdp FAR, FAR, FAR superior to rdesktop). it obviously does not do
>> the WOL or computer lookup for you, but its a start. it takes xfreerdp
>> options and server as input respectively.
>>
>>
>>
>> #!/bin/bash
>> Xdialog --title "CCH Terminal Server" --left
>> --icon=/lib/cch_freerdp/cch.xpm \
>> --password=2 --ok-label=Connect --3inputsbox "CCH Terminal Server" \
>> 330x350 Username: "" Password: "" Domain: "CCH" 2> /tmp/tmp.1
>> ret=$?
>> input=`cat /tmp/tmp.1`
>> rm -f /tmp/tmp.1
>> case $ret in
>> 0)
>> Xdialog --title "Connecting" --icon=/lib/cch_freerdp/cch.xpm
>> --timeout 10 --msgbox "Connecting to CCH Terminal Server Farm\nPlease
>> wait..." 400x150 &
>> user=`echo "$input" | awk '{split($0,a,"/")}END{print a[1]}'`
>> pass=`echo "$input" | awk '{split($0,a,"/")}END{print a[2]}'`
>> xfreerdp -u "$user" -p "$pass" $1 $2
>> ret1=$?
>> echo "\n\nret=$ret1\n\n"
>> case $ret1 in
>> 0)
>> break;;
>> 131)
>> kill `pidof Xdialog`
>> Xdialog --title "Wrong Username or Password"
>> --icon=/lib/cch_freerdp/cch.xpm --msgbox "Wrong Username or
>> Password\n\nRemember: Do NOT put\n\"CCH\\\"\nin front of your
>> username." 400x150 & ;;
>> *)
>> kill `pidof Xdialog`
>> Xdialog --title "Unknown Error"
>> --icon=/lib/cch_freerdp/cch.xpm --msgbox "Unknown error. Contact
>> Support.\n\nError Code=$ret1\n" 400x150 & ;;
>> esac
>>
>> echo "user=$user" > /tmp/t
>> echo "1=$1" >> /tmp/t
>> echo "2=$2" >> /tmp/t
>>
>> esac
>>
>>
>>
>>
>>
>>
>>
>> chris
>>
>> On Wed, Jun 27, 2012 at 12:10 PM, Ed Heron <Ed-MBvgLuVkLo/by3iVrkZq2A@public.gmane.org> wrote:
>> > On Wed, 2012-06-27 at 07:07 -0700, c-l wrote:
>> >> ...
>> >> My final goal for this product is to enable users to easily log on to
>> >> their
>> >> workstation from any of those Thinstation PC's that will be in
>> >> different
>> >> areas (board rooms, etc...). I work under the assumption that users
>> >> are
>> >> "dumb" and will not know by heart their Computer Name, nor their IP
>> >> address,
>> >> nor they will always remember to leave their station turned on all the
>> >> time.
>> >> ...
>> >
>> > It might be possible with a custom module to prompt for user name and
>> > password, check a look up table for machine name and mac address, check
>> > if machine is up, sending a WOL packet as needed and waiting for the
>> > machine to be accessible, then build a rdesktop command line with
>> > machine name, user name and password.
>> >
>> > That'd be a decent amount of work, though, and you'd have to maintain
>> > that user name / machine name / MAC address data. Or, if you had a
>> > server piece that ran on a nearby router or server, that could serve MAC
>> > addresses from an ARP cache.
>> >
>> > You might want to start by verifying WOL works on your workstations.
>> >
>> > Would your workstations have static IP's or would you use some sort of
>> > dynamic DNS scheme?
>> >
>> > Theoretically, it could be expanded to start VMs (Virtual Machines),
>> > as well. I wonder if it would be possible and/or desirable to have MS
>> > Windows VMs shutdown after a configurable amount of inactivity...
>> >
>> > Wish I had time to play with it beyond idle speculation...
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Live Security Virtual Conference
>> > Exclusive live event will cover all the ways today's security and
>> > threat landscape has changed and how IT managers can respond.
>> > Discussions
>> > will include endpoint security, mobile security and the latest in
>> > malware
>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> > _______________________________________________
>> > Thinstation-general mailing list
>> > Thinstation-general-5NWGOfrQmneRv+LV9MX5uuRhgaa4a2kL@public.gmane.orgnet
>> > https://lists.sourceforge.net/lists/listinfo/thinstation-general
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Thinstation-general mailing list
>> Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>

--
Operator of the Danish TS-O-Matic.
http://thinstation.org
Thinstation consultant for hire - payable via PayPal

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Thinstation-general mailing list
Thinstation-general <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Thinstation-general mailing list
Thinstation-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Thinstation-general mailing list
Thinstation-general@...
https://lists.sourceforge.net/lists/listinfo/thinstation-general

headers

Mike Eriksen | 29 Jun 2012 02:12

Re: Thinstation possibilities + usage scenario

On Thu, Jun 28, 2012 at 10:25 PM, Bryan Keadle (.net)
<bkeadle@...> wrote:
> Right, but what session setting?  I've only seen "_TYPE=rdesktop".  Do I
> simply change that to "_TYPE=freerdp" to "activate" it?  (of course the
> package must be included in the build, which I have).  How do I know that
> I'm actually using freerdp vs rdesktop?

Huh? Did you actually look at thinstation.conf.sample after you
rebuilt with "package freerdp" in build.conf??? And use this info for
your thinstation.conf<whatever>?

Mike
--

-- 
Operator of the Danish TS-O-Matic.
http://thinstation.org
Thinstation consultant for hire - payable via PayPal

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

chris nelson | 3 Jul 2012 23:33

Re: Thinstation possibilities + usage scenario

derek,

for one, the support around the product. just take a look at the
sourcefource mailing list activity for the two products. if you have a
problem, you will get a response from a developer within a day at
least with freerdp, rdekstop i would wait days or weeks. i also really
did not like how they handled the forking of freerdp. also, for a very
long time they did not support: 2k8r2 and 2k8std servers, farms or
connection brokered connections. the amount of options freerdp
supports is also far more extensive. it also "feels" faster and more
responsive. but most importantly, it is actively being maintained with
a large group of users and developers constantly putting out more
features.

chris

On Thu, Jun 28, 2012 at 6:12 PM, Mike Eriksen
<thinstation.mike@...> wrote:
> On Thu, Jun 28, 2012 at 10:25 PM, Bryan Keadle (.net)
> <bkeadle@...> wrote:
>> Right, but what session setting?  I've only seen "_TYPE=rdesktop".  Do I
>> simply change that to "_TYPE=freerdp" to "activate" it?  (of course the
>> package must be included in the build, which I have).  How do I know that
>> I'm actually using freerdp vs rdesktop?
>
> Huh? Did you actually look at thinstation.conf.sample after you
> rebuilt with "package freerdp" in build.conf??? And use this info for
> your thinstation.conf<whatever>?
>
> Mike
> --
> Operator of the Danish TS-O-Matic.
> http://thinstation.org
> Thinstation consultant for hire - payable via PayPal
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general@...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

Mike Eriksen | 28 Jun 2012 16:21

Re: Thinstation possibilities + usage scenario

On Wed, Jun 27, 2012 at 4:07 PM, c-l <christian.lessard@...> wrote:
>
> Hello all,
>
> I just started playing with the new 5.1.1 Thinstation.  Still new to all
> this.  I've been able to successfully remote to my Desktop by entering my IP
> address into RDesktop.  The most basic test, but at least it works ;)
>
> My final goal for this product is to enable users to easily log on to their
> workstation from any of those Thinstation PC's that will be in different
> areas (board rooms, etc...).  I work under the assumption that users are
> "dumb" and will not know by heart their Computer Name, nor their IP address,
> nor they will always remember to leave their station turned on all the time.
>
> All right, here's what I would like to achieve with Thinstation:
>
> - User wants to log into his Windows 7 workstation.
> - Opens up that PC (which sits in a common room), thinstation boots using
> PXE (client)
> - User is presented with a username / password form, enter his information
> and hit "log in"
> - Then, there is a process that finds the PC associated with the userID (we
> use AD - not sure if it's easy to track)
> - Once the PC is found, it finds it's IP Address and MAC address
> - If the PC isn't turned on, it sends a magic packet to do a WOL
> - Once the PC is accessible, it feed the IP address, then username /
> password to the RDP session and this connects the user to his station.
>
> So basically I need an easy 1-2-3 process so the user doesn't have to enter
> any information more than once and doesn't need to know anything but his own
> userid / password.
>
> Is this something that would be feasible on Thinstation, or it this too much
> to ask?  ;)

Unless I get this totally wrong it seems fairly easily done - except
the problem if the Windows workstation is turned off.

What you need is a USB key for each user. This contains the IP number
(or DNS name) of the user's Windows workstation in its TS config file.
This obviously requires fixed IP numbers (no DHCP) or something like
dynDNS. You leave the User ID and Password blank in rdesktop so
"somebody" can't "borrow" someone else's key and get unauthorized
access to the rightful owner's workstation.

When needing access to the Workstation, the user plug in his USB key,
reboot the TS client and gets connected directly to his Workstation.

Mike
--

-- 
Operator of the Danish TS-O-Matic.
http://thinstation.org
Thinstation consultant for hire - payable via PayPal

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

headers

Derek Moss | 28 Jun 2012 23:28

Re: Thinstation possibilities + usage scenario

Hi Chris

I'm fascinated to know what you find FAR, FAR, FAR superior about
freerdp compared to rdesktop?

-----------------------------------------------------
Date: Wed, 27 Jun 2012 16:25:23 -0600
From: chris nelson <sleekmountaincat@...>
Subject: Re: [Thinstation-general] Thinstation possibilities + usage
        scenario

here is a (probably poorly written :) script that i wrote to ask users
for their credentials and then startup freerdp (btw, i have found
freerdp FAR, FAR, FAR superior to rdesktop). it obviously does not do
the WOL or computer lookup for you, but its a start. it takes xfreerdp
options and server as input respectively.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/