Skip to main content

VDI conparision: Which one to choose, VMware, Citrix?

Or should I say is upgrading to Vista worth ab bargain? I have heard of official protest groups in Holland and elsewhere who want to cxontinue working on XP for another few years. Offering a fat GUI OS via VDI conenction broker is not a smart idea. It was never meant to push an elephant through a thin wire.

Anyways the comparison, if its worthy the discussion actually or within the context of a typical thin computing model, is here:

It's important to note that a VDA does all the work on the back-end servers where the VMs run; therefore, to accurately estimate the cost of a VDA, you'll need to take into account the server and virtualization software expenses. Estimating these costs will require walking through a series of calculations, which can be modified for a customer's specific environment. As an example, based on numbers from VMware, let's assume that a server can run six to eight virtual desktops per core, with dual-socket quad-core processors totaling eight cores, yielding 48 to 64 virtual desktops per server for the back-end hardware. If we use VMware's Virtual Desktop Infrastructure (VDI) solution, built on VMware's VI3 (Virtual Infrastructure 3) server virtualization software for our example, the Enterprise license of VI3 is $5,750, so the cost for VI3 is roughly $100 per VM. According to VMware, Virtual Center (VMware's management console) can support 1,000 users per instance for $6,000, which adds only $6 per VM. For connection broker software such as VMware's Virtual Desktop Manager (VDM) or a connection manager from a third party, you should add another $50 per VM. Since storage for the virtual desktop VMs under VMware lives on a SAN, storage costs should be factored into the equation. Depending on implementation, these can be quite high, so let's assume $150 per VM for this example. Prorating the server hardware costs per VM adds roughly $350 to $400 per VM. That brings the estimated total to $700 per VM, excluding the user interface device (since in our example, the user is connecting from the existing PC acting as a thin client). To include thin-client devices for new users, add $150 to $300 per user for just the thin client or as much as $900 for an integrated all-in-one thin client (which includes the monitor and keyboard), bringing the total cost to between $900 and $1,600.

The simplified bottom-line pricing comparison (using the very rough example numbers given here) is this: Upgrading a physical desktop to Vista might cost $300 to $400 (per desktop) in hardware costs and $200 to $300 in software costs, totaling $500 to $700 per physical desktop. Delivering Vista through a virtual desktop architecture (VMware's VDI in this example) and continuing to use existing PCs as rich clients accessing virtual desktops might cost $700 per VM desktop in infrastructure costs and $23 per VM desktop, if using VECD, totaling $723 per virtual desktop.



Link, heard from Alex first.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op