Comments on: Terminal Services vs. VNC http://www.kryogenix.org/days/2002/10/20/terminal scratched tallies on the prison wall Fri, 09 Jan 2009 15:29:41 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Frederic http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-6910 Frederic Wed, 12 Apr 2006 11:03:18 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-6910 The advantage of running VNC across all your servers, windows and linux, is simply this - one client for everything. The advantage of running VNC across all your servers, windows and linux, is simply this - one client for everything.

]]> By: Aquarion http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-5478 Aquarion Tue, 14 Feb 2006 07:56:31 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-5478 VNC (esspecially vncx11) allows you to take over an existing session, the problem with remote X as a admin solution is that you can't just log into the box, do what needs to be done and log out again, you have to have it sitting there all the time. VNC (esspecially vncx11) allows you to take over an existing session, the problem with remote X as a admin solution is that you can’t just log into the box, do what needs to be done and log out again, you have to have it sitting there all the time.

]]> By: Algot Runebjörk http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-5444 Algot Runebjörk Sat, 11 Feb 2006 19:17:59 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-5444 > sil said, > > June 28, 2005 at 7:17 pm > > kevinf: multiple separate VNC sessions to one server certainly > does work, if you’re talking to a Unix server. But why would anyone want to run VNC on a Unix server? X work very well, and there are lots of good X-servers for Windows out there, which will allow you to use xdm and whatever needed to log on directly. Why go over VNC when there is a perfectly good native solution that's been around since X was created? / Algot > sil said,
>
> June 28, 2005 at 7:17 pm
>
> kevinf: multiple separate VNC sessions to one server certainly
> does work, if you’re talking to a Unix server.

But why would anyone want to run VNC on a Unix server?
X work very well, and there are lots of good X-servers for Windows out there, which will allow you to use xdm and whatever needed to log on directly. Why go over VNC when there is a perfectly good native solution that’s been around since X was created?

/ Algot

]]> By: sil http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-5307 sil Thu, 02 Feb 2006 16:17:22 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-5307 phil: I agree with you. The point I was trying to make was not that people are trying to contort VNC into doing what Terminal Services does (although some are), it's that some people are using TS for doing stuff that they could have easily done with VNC, <em>and paying for the privilege</em>. If you get the CALs free and you don't care about multi-platform then I see no problem with TS, given that you've already bought into the Windows concept anyway. phil: I agree with you. The point I was trying to make was not that people are trying to contort VNC into doing what Terminal Services does (although some are), it’s that some people are using TS for doing stuff that they could have easily done with VNC, and paying for the privilege. If you get the CALs free and you don’t care about multi-platform then I see no problem with TS, given that you’ve already bought into the Windows concept anyway.

]]> By: phil http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-5302 phil Thu, 02 Feb 2006 14:12:24 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-5302 So the point we can all agree on is that depending on what you want, you use a different tool. You dont use a hammer to cut wood, so you dont use VNC as a multi session thin client on windows - but you do use it grab the interactive console session remotely for admin work. Its not something you can really compare as they are designed for different purposes. Having said that, if you get your CALs free through an MS partnership or whatever, TS beats VNC hands down for both admin of the console session and multiple sessions - and if you are an MS partner you're not going to mind the one platform limitation! So the point we can all agree on is that depending on what you want, you use a different tool. You dont use a hammer to cut wood, so you dont use VNC as a multi session thin client on windows - but you do use it grab the interactive console session remotely for admin work.
Its not something you can really compare as they are designed for different purposes.

Having said that, if you get your CALs free through an MS partnership or whatever, TS beats VNC hands down for both admin of the console session and multiple sessions - and if you are an MS partner you’re not going to mind the one platform limitation!

]]> By: mike http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-3610 mike Thu, 01 Jan 1970 01:00:00 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-3610 remote desktop rules! remote desktop rules!

]]> By: kevinf http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-3611 kevinf Thu, 01 Jan 1970 01:00:00 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-3611 <p><span class="caps">VNC</span> is not a thin client. To compare it to terminal services is to compare apples to golf balls. <span class="caps">VNC</span> is simply a support tool and that is it…it is a screen scraper. While, terminal services and citrix are thin clients, designed to connect and run applications on the server side. For example.. try connecting with multiple sessions to a server with <span class="caps">VNC</span>. It doesn’t work! It’s not designed to. TServices is not a screen scraper, it uses the same tecknology that allows you ro run mini apps over the net.</p> VNC is not a thin client. To compare it to terminal services is to compare apples to golf balls. VNC is simply a support tool and that is it…it is a screen scraper. While, terminal services and citrix are thin clients, designed to connect and run applications on the server side. For example.. try connecting with multiple sessions to a server with VNC. It doesn’t work! It’s not designed to. TServices is not a screen scraper, it uses the same tecknology that allows you ro run mini apps over the net.

]]> By: sil http://www.kryogenix.org/days/2002/10/20/terminal/comment-page-1#comment-3612 sil Thu, 01 Jan 1970 01:00:00 +0000 http://www.kryogenix.org/adpb/2002/10/20/terminal/#comment-3612 <p>kevinf: multiple separate <span class="caps">VNC</span> sessions to one server certainly does work, if you’re talking to a Unix server. Windows, on the other hand, doesn’t know how to have more than one graphical user unless you purchase the extra Terminal Services stuff. More to the point, Joel wasn’t talking about using TS clients as thin clients to run multiple sessions on one Terminal Server, he was talking about using TS to remotely administer a Windows box, which is <em>exactly</em> what <span class="caps">VNC</span> is for.</p> kevinf: multiple separate VNC sessions to one server certainly does work, if you’re talking to a Unix server. Windows, on the other hand, doesn’t know how to have more than one graphical user unless you purchase the extra Terminal Services stuff. More to the point, Joel wasn’t talking about using TS clients as thin clients to run multiple sessions on one Terminal Server, he was talking about using TS to remotely administer a Windows box, which is exactly what VNC is for.

]]>