Hello,
I had a bit of trouble with this also. David and Gadi's tips really
helped. I spent quite a while trying to understand xfreerdp option in a
xterm, most of the time getting only black screens with a mouse pointer...
My current working options look like this:
[WindowsStations]
# settings here apply to stations using "LIKE = WindowsStations":
***********
RDP_OPTIONS = "--no-auth --no-nla --ignore-certificate
--composition -f -a 32 -k 0x00000816 -d lumiar --plugin rdpdr --data
disk:usbdisk:/media/root -- "
RDP_SERVER = vm-xp1
X_COLOR_DEPTH = 24
SCREEN_08 = xfreerdp
A few comments and things I learned:
1. David's line was missing a dash on --no-auth
2. This wouldn't work until I removed the -u '' option
3. That X_COLOR_DEPTH = 24 prevents xinitrc from appending a "-depth 16"
default which renders really bad colors in Windows (like pink patches on
the login screen).
4. I get to keep the RDP_SERVER on a separate variable, which is
important so I can redefine it below with more specific MAC address
clauses on my lts.conf. I do this by using the "--" that is required
before the server name at the very end of RDP_OPTIONS.
5. That -k 0x00000816 is a specific keyboard layout I want to enforce.
Leave it out or change it as needed.
6. For reference, there are several pages online explaining xfreerdp
options, but most are very incomplete. This one is a good resource, and
seems complete:
http://manpages.ubuntu.com/manpages/precise/man1/xfreerdp.1.html
7. When I have some more time I want to experiment with additional
plugins (clipboard, etc). This page
<https://github.com/FreeRDP/FreeRDP/issues/354> mentions that another
double dash is required when using more than one plugin, I'll have to
remember that and see if it doesn't confuse the LTSP scripts. The
example given there is
|xfreerdp -f --no-tls --no-nla --plugin drdynvc --data tsmf -- --plugin
rdpsnd --data pulse -- 192.168.1.16|
Notice that extra "--" before the second plugin. When David said that
xfreerdp ignores everything after the plugin option, this is probably
the workaround: use plugin, then data, then a final --. This probably (I
haven't tested) tells xfreerdp that the command-line conitnues normally
after the double dash.
8. I believe this still needs some work, which is a shame for me to say
because I don't feel I have the skills to contribute (except by sharing
my trials and errors). People using Windows desktops with LTSP got this
switch to xfreerdp forced upon them. There is good reason to do this
(rdesktop is not good to connect with newer Windows versions etc.), but
the practical setup is very difficult, not very documented, tricky to
troubleshoot....
It would be nice if some of this stuff mentioned here found its way into
the LTSP scripts that handle lts.conf, and perhaps a sample could be
included in the default lts.conf.
Anyway I just want to thank everyone involved, I still love LTSP despite
all these woes!
Pedro
------------------------------------------------------------------------------
WINDOWS 8 is here.
Millions of people. Your app in 30 days.
Visit The Windows 8 Center at Sourceforge for all your go to resources.
http://windows8center.sourceforge.net/
join-generation-app-and-make-money-coding-fast/
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
