Ye the 2 technologies are kinda the same in respect to clients logging into a server to receive a desktop, whether these desktops are virtual machines or one server with TS running.
The multiple VM sounds great but it sounds like it would be a major load on any server?
Would it not be better to have a server that allowed multiple connections, cause i presume these VMs would have to all be on all the time even when not in use?
All new to me really thin computing TS etc
Thanks for your input
That is confusing. What do you mean 'physical desktop'?Originally Posted by duxbuz
XenDesktop uses a single physical machine, and creates multiple virtual machines on that hardware, each user connecting gets one of those individual desktops. This uses more resources, but offers a more seamless and 'normal' desktop experience to the end user, as it prevents any possible interference between instances of software.
XenApp or RDS is a single physical machine, with a single operating system where multiple users connect to that single instance as concurrent users.
Which are you trying to achieve?
The resources needed for VDI are not *massively* different, as they are instead based upon a mix of individual resources and a dynamic use of memory, where only 1 copy of something will get loaded into RAM and shared across the different machines. The biggest bottleneck in VDI is usually the hard disks - as it requires a lot of IOPS to handle any decent amount of load.
Last edited by localzuk; 5th March 2012 at 02:33 PM.
Just to reiterate I think we are going to need to know a little more about what you want to accomplish before suggesting anything further.
Is this for a IT room PC refresh or something?
[QUOTE=localzuk;798753]That is confusing. What do you mean 'physical desktop'?
Physical desktop, i mean physical machine. Currently this is a demo for my boss, I am using a laptop as a desktop rather than a VM
The end product would prob be having maybe 10 thin clients in class rooms.
Also ipads being able to use windows desktop
In which case, either solution does what you want - the difference is the multiple virtual machines or a single terminal services setup. The prior will be able to host less clients than the latter, but a normal desktop machine running this sort of thing would be able to handle a hand full of VDI machines without much issue.Physical desktop, i mean physical machine. Currently this is a demo for my boss, I am using a laptop as a desktop rather than a VM
The question is more one of what exactly the larger picture is though - a demo is fine set up either way, but what is the larger project likely to be used for, if it were?
EDIT: Replied before I clicked reply...
In which case, I'd say for that sort of volume of machines, either solution will work on a single server host quite easily. The cost comes when you start scaling upwards.
Last edited by localzuk; 5th March 2012 at 02:46 PM.
Ta
The end product would prob be having maybe 10 thin clients in class rooms.
Also ipads being able to use windows desktop .
Currently with the demo I seem to be only able to log on with one user at a time, would be nice to show the boss multiple users utilizing the same physical machine (without having to have xenserver and VMs) but I maybe unable to have more than 1 connection to the laptop that I am using to show demo.
Making more sense now
Personaly I will opt for VDI in most uses these days as it gives a bit more flexiablity than traditional RDS and also the Citrix HDX protocal in VDI-in-a-box is great for video playback ect (send me a PM and I can send you some YouTube links).
Mix it in with something like App-V and you will have a rock solid thin client network for years to come. There is a aditional cost in VDI compared to RDS though in the fact it needs more CPU cycles, more RAM and more IOPS but with things like SSDs and Windows Server 8 Hyper-V with memory de dup on the way it could be the thing for you.
Cant try out the VDI demo as it does not support my free esxi.
Woe is me
Hyper-V All the way then!
Only wanted to test it out
It sounds like a "traditional" Windows terminal server will provide all you are looking for. This solution has been around for many years - is without question the most used solution in schools (due to its simplicity and lower cost).
It's not as sexy as "VDI" - but much easier in every sense to build/manage.
Possibly you may (very unlikely) find some applications that don't run on terminal services and may need to expand the above to manage a VDI environment (RemoteApp).
Just install W2008r2 on a one physical/virtual machine, source thin clients from any of a number of manufacturers - that's it...
There are countless companies selling terminal server "add-ons" (Citrix, Ericom, 2x, Kavisa, etc etc) - some better than others - but try the generic Microsoft solution first before spending more money/time.
What the generic Microsoft offering will give you is the ability to log onto the server from as many terminals/PCs as the server can handle and each one will get their own unique desktop.
It doesn't need to be any more complex than this....
Sounds good.
Will look at this.
Kaviza is long goneits all about VDI-in-a-box now.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
