One of the things I really hate about trying to deal with MS<br>is the effort required to understand their licensing terms.<br><br>And I get to where I understand them today, <br>they will change tomorrow.<br><br>You can be sure that if lots of folks go around the MS tollbooth,<br>
the tollbooth will be moved. <br>And you all will be declared pirates.<br><br>That being said <br>I am very interested in learning how setup instructions<br>for running with windows apps either in a VM or <br>on separate real hardware.<br>
<br>I am thinking about more of vnc rather than an rdp. <br>In addition to the licensing issues I don't want to think about, <br>there are the windows sysadmin skills I'd need <br>to be comfortable with setting up rdp.<br>
<br>Vnc sounds so much easier, <br>install vnc server on windows,<br>the client on FreeNX <br>(both on the same local network).<br><br>Start up a remote NX session <br>from somewhere across the internet<br>using the !M client connnect to a desktop on the FreeNX server and <br>
run the vncclient on the FreeNX server to connect to a Windows desktop.<br><br><a href="http://openfacts.berlios.de/index-en.phtml?title=NX_Components">http://openfacts.berlios.de/index-en.phtml?title=NX_Components</a><br>
shows a somewhat different set up. Or is this what happens<br>automatically under the covers when we take the simpleminded<br>approach above, or do we have to do configure things differently<br>to get things to work this way.<br>
<br>If they are distinct approaches.<br>Do both approaches work? <br>Which is better?<br><br>There are lots of vnc implementations. <br>The first approach is vnc implementation agnostic. <br>The second seems bound to TightVNC. <br>
s there really that much difference between vnc implementations?<br><br>What is TightVNC security like?<br><br>Last time I looked.<br>Which was a long time ago.<br>RealVNC had no security in the free version.<br>And had better security in the $$ version.<br>
<br><div class="gmail_quote">On Feb 14, 2008 1:05 AM, Chris Fanning <<a href="mailto:christopher.fanning@gmail.com">christopher.fanning@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I imagine that I'm not the only one in the list that has to deal with<br>windows applicactions. Although life would be a lot easier without<br>them, it doesn't look like we can escape from M$ completely (at least<br>
for the moment).<br><br>In my case, I have users sharing the same gnu/linux box runnng KDE<br>sessions and a seperate w2k3 server running window-terminal-server for<br>windows apps via RDP.<br><br>Yesterday a colleague opened his xfce sessions via freeNX and<br>
installed Virtualbox. Within 15 minutes he had installed XP. And that<br>got us thinking about the need for the w2k3 server and the expensive<br>terminal server licences.<br><br>Virtualbox uses SDL (right?), that means we can circumnavigate RPD<br>
(and the licences), couldn't we?<br>Each user could have his on virtual windows running on his kde desktop.<br><br>After reading that SUN has recently bought Virtualvox and intends to<br>use it with xen, we're wondering<br>
Resource management of the virtaulbox instances would be important.<br>Perhaps this is where Xen comes into it. but how?<br><br>I was hoping someone on the list might have an opinion on this.<br><br>Thanks.<br>Chris.<br>________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br> Then please write up the solution in the FreeNX Wiki/FAQ:<br> <a href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ" target="_blank">http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ</a><br>
Don't forget to check the NX Knowledge Base:<br> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br><br>________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br></blockquote></div><br><br clear="all"><br>-- <br>Drew Einhorn