Post #20,547
12/6/01 7:11:21 PM
|
VNC is a possible answer but for admin tools
if there is enough users get citrix. thanx, bill
tshirt front "born to die before I get old" thshirt back "fscked another one didnja?"
|
Post #20,622
12/7/01 8:12:12 AM
|
Why VNC doesn't fit the bill (ahem, sorry)
VNC only remotes the actual displayed desktop of the target machine.
If you're already looking at Terminal Services, you need multiple remote desktop sessions.
Peter Shill For Hire [link|http://www.kuro5hin.org|There is no K5 Cabal]
|
Post #20,727
12/7/01 8:42:45 PM
|
wall under unix
I can setup multiple vnc logins that present individual xterms independant of the others all running different things, just assumed I could do it with windoze :( thanx, bill
tshirt front "born to die before I get old" thshirt back "fscked another one didnja?"
|
Post #20,804
12/8/01 8:50:32 PM
|
...and why it does, properly configured
For running Windows sessions under Linux, VNC does wonders. You're already running individual sessions as seperate Linux processes. Ironically, Linux can serve Windows better than Windows can, in this sense. See also: [link|http://www.wired.com/news/print/0,1294,45862,00.html|Wired: Penguin enrolls in US schools].
-- Karsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com] What part of "gestalt" don't you understand?
|
Post #20,821
12/9/01 8:28:18 AM
|
Maybe I'm missing something here
But you can't use VNC to turn a Windows server into a multi-user (interactive) box.
That's what Terminal Services does.
Peter Shill For Hire [link|http://www.kuro5hin.org|There is no K5 Cabal]
|
Post #20,825
12/9/01 11:58:01 AM
|
Yes, you are missing something
There are programs (eg win4lin, vmware) which allow you to run Windows under Linux. Given the design of Linux, what you can do once you can do many times at once. So you run VNC in each of those instances of Windows, and access these VNCs from other machines.
Voila! You now have a home-grown but substantially cheaper Terminal Services for Windows, implemented on top of Linux.
Cheers, Ben
|
Post #20,840
12/9/01 6:14:35 PM
|
Er..
Do Billy n'Bally 'spect you to run a new copy of Winders on each open window ?? [umm Hah!] I mean - it IS Ugly out there, no? :-\ufffd
|
Post #20,843
12/9/01 6:57:50 PM
|
Questions
1. You'd still have to buy separate Windows licences for each instance. At \ufffd200 per licence, that stacks up fairly fast. TS client licences are less than that. VMWare licences are also pricey. I've never investigated Win4Lin.
2. How would you manage such things as user profiles and printing? Administratively, this could be more frustrating than you think. 3. How would you manage the network access to these VNC instances via something like the VMWare Host networking? I know that you can have multiple VNC instances running, each one listening on a separate network port - how would you bridge this to each VMWare instance running VNC?
Peter Shill For Hire [link|http://www.kuro5hin.org|There is no K5 Cabal]
|
Post #20,861
12/9/01 10:15:43 PM
|
Licensing
Aye, there's the bugger. I'm not sure how that works out. Last I heard from my source, he'd had a chat with some folks from Redmond, in part discussing the licensing question. Not sure what the final resolution was.
Still, even with the licensing costs, administration of the systems is greatly simplified. You're running an image on top of Linux, with all the tools Linux provides to allow replication and restoration of that image.
Incidentally, a recent presentation I saw (autonomous computing) by IBM, there was mention of running various OS images on zSeries hardware, MS Windows included. Which makes me wonder if IBM's got that particular virtualization issue resolved.
Being able to seamlessly transmit and substitute images of proprietary and free OSs is going to do a fair bit to break up lock-in.
-- Karsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com] What part of "gestalt" don't you understand?
|