89 views
May 12

My only disappointment is that we are currently in the middle of moving our current Solutions Centre from one Office location to the other so it’ll be some while before I get a chance to test this.

It certainly looks quite impressive and it does have some lofty aims, but from a brief look through as well as their well deserved reputation based on Flex Profiles I’m sure this will stand up to it’s promises.

Test Scenario’s
With login VSI you can compare many different scenarios:
• VDI vs. SBC
• VMware, XenServer or Hyper-V running virtual desktops or Terminal/Citrix Servers
• Virtualized XP desktops versus virtualized Vista Desktops
• Performance impact of application streaming technologies
• Impact of (different) virus scanners
• Performance impact of tuning parameters
• Different VDI platforms
• Different Storage platforms
• Impact of changes or updates like service packs or security fixes
• Hardware differences
• x64 vs. 32 bits
• Etc…

I’d be very interested in hearing from anyone who does have the facility to test?

Login Consultants develop presentation virtualization benchmarking tool

Monday, May 12, 2008   |   0 Comments   |   addthis

The consulting firm Login Consultants just opened the beta program of the first benchmarking tool for presentation virtualization: Login Virtual Session Index (VSI).

The product will measures the performance of a remote desktop session served by a Microsoft Terminal Services  / Citrix XenApp server or a VDI virtual machine.

vsi_chart

To run the tool it’s required to have a 4 tiers infrastructure: a domain controller for the authentication a file server for logging user sessions, a server to host the TS/XenApp/VDI service and a workstation to launch the user sessions.

The firm is also working to introduce support for application streaming.

Enroll for the beta here.

virtualization.info: Login Consultants develop presentation virtualization benchmarking tool

written by dcaddick

339 views
Feb 12

Now somewhile back I produced the following post regarding any other alternatives to RDP and ICA and at the time I might have been somewhat flippant about NComputing’s model based on Windows XP SP2, and since then there have been a number of other companies like Miniframe jump on the same bandwagon where they are effectively using a desktop based OS to provide concurrent multi-user sessions and I always thought this did somewhat fly in the face of the EULA?

At the time I was sort of suspecting that MS might have actually been turning something of a blind eye to this in some parts of the world, but now it seems that MS has finally decided to get off the fence (or at least the Lawyers have now made a decision? ;-) and produced this document to clarify things.

So I’d like to clarify here that this is not that I don’t think NComputing can add value, but in doing any due diligence anyone who seriously wants to consider either NComputing, Miniframe or any other method of using XP SP2 in a multi-user model should seriously check this document from MS before going too far down this path?

If I was contemplating, or indeed already using this scenario I would be asking the Vendor to review this document from MS and provide some sort of legal indemnification?

Licensing Windows Client Operating System in Multiuser Scenarios

This posting is provided “AS IS” with no warranties, and confers no rights. The opinions expressed within are my own and should not be attributed to any other Individual or Company or the one I work for.

SPICE might be an alternative to ICA and RDP?

Now this is very interesting news because with all the interest around VDI there is still no real alternative to ICA other than RDP (or VNC…?) and in this I’m not even going to consider Ncomputing’s WoIP, as from a techies point of view this would appear to simply be a rehash of RDP, although I’m prepared to be convinced otherwise?

But it might be exciting to see that there is a real possible alternative to the ICA/RDP stranglehold and this might have the makings of some interesting changes to how things might be approached in the VDI space?

******UPDATE******
As a consequence of this post I have been contacted by Ncomputing and it would appear that their WoIP is actually what they term a combination of UTMA and UXP and does indeed make the connection/transition/session at a lower level in the stack. However, you will not find much detail on the inner workings of this as it’s proprietary, and I’m still trying to understand how this all plays out with regards to the Microsoft Licensing side of things as detailed here in a post on their Forum
http://ncomputing.com/ncomputing/wbb2/thread.php?threadid=963&hilightuser=1087

If/when I find out more I’ll update either here, or as a separate post on my new blog at www.techagility.info
******UPDATE******

SPICE might be an alternative to ICA and RDP?

written by dcaddick

249 views
Oct 09

So from Alessandro comes news of a review of the Virtualization platforms and it’s going to come as no surprise that VMware tops the bill? But what is surprising is the kudos they give XenSource? Easy to use, feature rich offering is quickly catching up to its main rival - that would have to be good news to Citrix? especially seeing as XenSource was listed as being the easier of the two to deploy?

To be honest I think there is a lot to be said about familiarity with a product, if you are familiar with it and can be up to speed quickly in any organization then this will clearly be a benefit? So the fact that VMware has so market share will work in it’s favor - for now at least? ;-)

I wonder how this review might have turned out if Viridian was also listed? Probably not too well at this early stage, but it would be interesting to know how far it has to catch up?

Review: CRN compares most popular virtualization platforms

Monday, October 08, 2007   |   0 Comments

CRN published a basic review of most popular virtualization platforms on the market today, assigning a rating to each one:

  • 1st - VMware Infrastructure 3
  • 2nd - XenSource XenEnterprise 4
  • 3rd - SWsoft Virtuozzo 3.5.1
  • 4th - Virtual Iron 4.0

Reviewer provided following conclusion:

While all four virtualization solutions accommodate the needs of IT development, VMware stood above the others for providing the best end-to-end virtualized environment specifically designed for development.

The biggest challenge for IT is to build communications between a large team working on the same development project. VMware’s ESX server is built for that, including the most features by far. XenSource’s XenServer is the simplest product to use and has new features that enable it to compete on a more level playing field with VMware and SWsoft. XenEnterprise is price-competitive and also scales higher than VMware’s enterprise solution.

SWsoft offers an interface that’s easy to understand, but its capabilities don’t rise to the level many development teams would require. Virtual Iron’s interface just wasn’t friendly enough for engineers to build simple workflows.

Simply put, systems integrators and application providers can certainly use all four products to develop and test systems but on more complex distributed infrastructures, they will be hard-pressed to meet deadlines without VMware’s Lab Manager to monitor workflow, integration schedules and code assets.

Read the whole comparison at the source.

virtualization.info: Review: CRN compares most popular virtualization platforms

written by dcaddick

390 views
Oct 02

So it was with interest I noticed the news about VDM (Virtual Display Manager)being released by iShadow and remembered I’d been asked about the same issues a couple of months back.

The cheapest solution is to make sure you are using the Vista TS Client as this supports monitor spanning - however there are a few caveats listed below

The other alternative is SplitView and this can be used on trial for 30 days?

But certainly VDM certainly looks like it will accommodate just about any need or requirment, as demonstrated here:

VIRTUAL DISPLAY MANAGER

MSTSC Spanning multiple Monitors

For example, this configuration is suitable for multi-monitor spanning:

 (-1024,0)         |
    --+--------------+------------------> x  

    |              |              |  

    |              |              |  

    |              |              |  

    |              |              |  

    +--------------+--------------+ (1024,768)  

                   | y  

                   V

You can access the functionality using command-line options, in one of two ways:

If you know the rectangle dimensions of your virtual desktop:

mstsc /w:2048 /h:768 /v:<servername>

or if you want mstsc.exe to figure-out the dimensions:

mstsc /span /v:<servername>

There are a few limitations of multi-monitor spanning:

* The maximum dimensions of the virtual desktop in a TS-Session is hard-coded to 4096×2048, regardless of the color-depth and the available resources on the remote machine.

* The remote session will see your virtual desktop as one giant display.This reduces the complexity of the multi-display implementation in the remote session, while still allowing the windowed mode of the TS-Client to

be functional and viable.

More at source:

http://blogs.msdn.com/ts/archive/2006/11/10/multi-monitor-support-in-the-vista-ts-client.aspx

written by dcaddick

343 views
Sep 26

Now this is very interesting news because with all the interest around VDI there is still no real alternative to ICA other than RDP (or VNC…?) and in this I’m not even going to consider Ncomputing’s WoIP, as from a techies point of view this would appear to simply be a rehash of RDP, although I’m prepared to be convinced otherwise?

But it might be exciting to see that there is a real possible alternative to the ICA/RDP stranglehold and this might have the makings of some interesting changes to how things might be approached in the VDI space?

 ******UPDATE******
As a consequence of this post I have been contacted by Ncomputing and it would appear that their WoIP is actually what they term a combination of UTMA and UXP and does indeed make the connection/transition/session at a lower level in the stack. However, you will not find much detail on the inner workings of this as it’s proprietary, and I’m still trying to understand how this all plays out with regards to the Microsoft Licensing side of things as detailed here in a post on their Forum
http://ncomputing.com/ncomputing/wbb2/thread.php?threadid=963&hilightuser=1087If/when I find out more I’ll update either here, or as a separate post on my new blog at www.techagility.info
******UPDATE******

Qumranet leaves stealth mode and enters VDI market with Solid ICE

By Alessandro Perilli

After almost two years in stealth mode, one of the most interesting virtualization startup at the moment, Qumranet, launches its first product: a VDI solution called Solid ICE.

Solid ICE is made of a connection broker, but also features a server component which adds resources control capabilities to KVM, and a new remote access protocol, called SPICE, which can be optionally used as replacement for Microsoft RDP.

The connection broker has some interesting capabilities in itself, supporting high availability and exposing a web portal for standard PC clients access which is designed to scale up to thousands of virtual machines. Despite that first version will provide basic capabilities to operate the virtual machine, with enhancements to be released over time.

The new protocol adds further value to Qumranet solution, being designed to deliver on thin clients all those multimedia protocols which usually don’t perform well into a terminal services session (an approach which competes with NEC VPCC one).

Last but not least Qumranet took care to support several thin clients on the market, developing a dedicated MiniOS (probably a special purpose Linux distribution).

Solid ICE will support Windows 2000 Professional, Windows XP and Linux as guest OSes, and it’s expected to be available before the end of this year.

more at source…

written by dcaddick

120 views
Sep 25
From the Windows XP Embedded Team,

It seems like we just went through Daylight Saving Time (see this blog post), but that time of year is coming up again.  To help customers prepare for the upcoming changes Microsoft is hosting a Technical Review webcast today at 2:00PM Pacific time:

Technical Review for Daylight Saving Time & Time Zone Preparedness

We will host a technical product review/ summary webcast is scheduled for 2:00PM Pacific on Monday, September 24th.  This is a technical overview of resources on Microsoft products available to help customers and partners prepare for change to Daylight Saving Time and various time zones.  Information about this Webcast for customers is available at: http://support.microsoft.com/gp/dst_webcasts.     

Live Meeting URL for webcast on Monday, Sept 24th, 2007 @ 2:00PM PDT: https://www.livemeeting.com/cc/lmevents/join?id=msft092407sa&role=attend&pw=ATN783

Daylight Saving Time Again?

written by dcaddick

126 views
Sep 25

In a post by Helge Klein at IT from inside he has done some testing regarding the impact of utilizing ClearType across RDP connections and the upshot of it is that this has the potential to increase your bandwidth usage by 300% or if using 32bit colour this can be as high as 600%. Your mileage may vary- best to test extensively before you turn this on?

This is based on server 2008 CTP, June 2007 so this may improve before the official release?

colour - for my US readers this is how it is spelt in all other English speaking countries other than the US ;-))

ClearType Bandwidth Revisited - Testing 32 Bit Color Depth

In an earlier post I wrote about how bandwidth requirements of the RDP protocol are affected by enabling font smoothing (ClearType over RDP version 6) on Windows Server 2008.

Jan, a reader of that article, posted an interesting comment: he had heard that RDP version 6 was optimized for a color depth of 32 bits and asked me to repeat my tests with that setting, which leads to an interesting question: how is font smoothing bandwidth usage affected by the color depth used?

When I prepared the test environment for my initial article on this subject I consciously chose a color depth of 16 bits, mainly because I thought that 16 bits is the most widely used color depth on production systems. I did not, however, think about how different color depths might change the numbers measured.

more details at source…

written by dcaddick

134 views
Aug 14

So…. Question?

Would I use TS/Citrix or would I use VDI if I was building or designing the Front-Office of a Greenfield site today?

This is a quite a hot topic, because as much as VDI/xDI/DDI is the latest craze that’s sweeping the IT sector, is it really all it’s cracked up to be?

What has changed?

My thoughts are that until relatively recently Corporate IT was rock solid and unchangeable, absolutely rooted in Change Management, driving Mainframes and COBOL – but now we are living in a much faster paced world, whole countries and attitudes are shifting rapidly – and as a consequence Business’s need to respond to an ever faster changing world, it’s markets and it’s pressures – now IT not only NEEDS to be Agile and Flexible – it is paramount above all else (OK, well perhaps Security and Corporate Governance, did I hear Shareholders from the back row? mmm ;-)

Anyway, Agility and Flexibility are the key here, in nearly every conversation I’ve had with C-level execs this comes through time and time again – IT needs to be in step with the business demands, not the other way around

And so with this in mind I can well understand the reasoning behind Brian Madden’s comment:

This VDI/xDI/VCC thing is hot. Even if you don’t believe in it today, the concept of delivering a desktop as a service is going to continue to grow. (In fact, many people are now realizing that some form of this might soon replace all desktops in a corporation—-not just the “special case” scenarios that are popular today.)

Why is it so popular? Well how about this example of quick provisioning:

When I have been to visit a client to initiate a PoC (Proof of Concept) that involves installing components on a Win32 Server and we quickly cover off the pre-requisites (indeed, sometimes this has already been done via email, just not actioned ;-) and I’m told “No problems, we have ESX in the lab, I’ll set it up from a template while we go and grab a coffee and it’ll be ready when we get back”

This sort of thing happens all the time these days, and yet it was unheard of say 3 – 4 years ago? Before the advent of ESX as a provisioning tool like this there would have been a delay of 4 – 6 weeks while the Server was agreed, funded, sourced, racked, cabled and powered, and yet now it can be done in 30 minutes, fantastic, absolutely wicked!!

When management get to start thinking that this same process can be applied to every new starter, and each employee can have a newly provisioned Desktop done in 30 minutes to be accessed by whatever you have to hand it starts to really make sense that maybe, just maybe, IT can start to actually be so much more credible and responsive to the Business? Whether or not it’s the answer to Agility and Flexibility remains to be seen, but this is a powerful example that gets people passionate and thinking about so many different ways to do things that previously were quite possibly unthinkable.

So what’s missing?

Well for the moment the main issues are:

  • What happens when Joe Bloggs tries to login and finds his Desktop isn’t up for some reason?
  • Ideally from a management perspective you do not want individual users tied to individual desktops?
  • It only makes sense to have the desktops turned off when not in use to save capacity and power? How can the user be connected to a virtual desktop that’s powered off (or doesn’t exist)?

So this is what I think all of the various VDI/xDI/DDI Broker’s are trying to achieve:
Being able to deliver a seamless and dynamic login to an appropriate virtual desktop (small, medium or large sir?) that is called in to being or booted on the fly, possibly based on a number of templates, so that the user is served up the correct amount of resources within their virtual desktop, and then when the user is done and wants to logoff all work is saved as needed and the virtual desktop is then either turned off or left in a standby or hibernation mode as required or determined by GPO’s?

NOTE: It is my understanding that this is the ultimate goal of Citrix Trinity Project so that it will be ICA to ICA for the Remote Client right through to the Xen Server EXS Server

Clearly there is a bit more to it than that, but by using “redirected folders” and “Flex Profiles” within the users profile you can have most of the data being saved to where it should go, and by using an OS Streaming system like Neoware’s Image Manager or Ardence you can save yourself quite a bit of disk space instead of having to support a whole SAN full (desktops hard drive x number of users = lots).

But why not use Citrix?

But surely this is the case with Terminal Server/Citrix as it stands today? All a user needs is a valid UserID and Password? When they login the session is created on the fly and when they logoff the session is gracefully closed and disposed of and the resources are handed back to the Server for reuse.

Regardless of how the user gets access (Citrix or VDI), they still need to be provisioned with an Active Directory User ID and password? All of the other normal provisioning needs to be carried out and with VDI the Desktop needs to be booted to be available? and yet any user can initiate a Terminal Server/Citrix session on-demand so surely that’s easier to deal with from an Admin’s point of view?

One of the problems (or at least the perception of a problem) is that the Terminal Server/Citrix approach is a shared service for multiple users, if the Server becomes unstable for any reason it will take 60 – 80 users down in one hit, so for this reason it needs to be robust and maintained under strict Change Management, where as with the VDI/xDI model this is not the case each user has their own clearly defined virtual Desktop resource that is independent of all others.

Now I’m also going to bold enough at this point to suggest that there always seems to be a few issues or problems that tend to effect medium to large Citrix Server Farms, in fact I would go so far as to say that for most experienced Citrix Consultants working for Platinum resellers they could be spending as much as 60 – 70% of their time helping customers fix problems with badly designed, poorly maintained or poorly performing Server Farms.

It is very easy to get one or two Citrix Servers running well and behaving nicely as any Load Balanced pair should be, but after that things can get scary pretty quick, I have heard and seen Farms of 20 - 30 plus servers being replicated simply by swapping out the mirrored drive with no thought to NewSID, or the fact that the original servers Access Data Store has been replicated across all servers!!! (Anyway, I digress…)

Another performance fact/myth is that I have been basing my numbers on the amount of concurrent sessions that I know a DL360 G4/5 can support. I have in the past been lucky enough to build a PoC that was then tested to failure point using Mercury LoadRunner so I am quite comfortable with quoting 60 – 80 users per BL20p G2 having seen it be driven to 90 and 100 users before performance was significantly degraded – but when I stop and think about all the installations I have been asked to review it strikes me that most organizations are getting something like 30 – 40 users per server?

I would be very interested in people’s feedback on this number – because as you’ll see below this can tip the scales very dramatically one way or the other.

Costs (based on 5,000 users):

Let’s have a look at the costs associated with each approach shall we?

Greenfield Design Criteria for 5,000 Users:

Front-Office assumptions:
60% Task based workers suitable for Thin Clients = 3000
30% Knowledge Workers suitable for VDI = 1500
5% Developers or similar suitable for PC’s = 250
5% Mobile Workers with Laptops = 250

Of the mobile workers with Laptops I would think that 60% (or more) of these could be provided with Mobile Thin Clients
60% of 250 = 150 with Mobile Thin Clients and 40% of 250 = 100 with traditional Laptops

Notes:
Please bear in mind that if you compare different Servers i.e DL585 for VDI and DL365 for Terminal Server/Citrix then it’s probably best to compare HW$ per User as opposed to traditional density comparisons of users per server.

I’m more than happy to receive any feedback or flames on how you feel these numbers are wrong, don’t forget “your mileage may vary”? ;-)

VDI Example:
90% of users on VDI = 4500 Users.

Density based on fully loaded DL585 or equivalent = approx. 200 Users per Server at a cost of USD 400 per user excluding Desktop License
(based on 128Gb RAM, quad AMD 8222SE Dual Core 3Ghz, 2 x 72Gb 15K000 Drives, 4Gb Fibre Connector and 4 x core VMware VI License = approx. 80K USD, leaving aside costs of SAN?)

The main issue at the moment is Microsoft’s approach to VDI Licensing for the Desktop – the minimum for this is Retail Vista (not OEM) regardless if you are going to use XP SP2 or Vista. That is off course unless you are lucky enough to have some other form of generous Licensing arrangement with Microsoft courtesy of an SA agreement that was done some time back before Microsoft realised that they wanted to restrict or charge more for Streaming or Virtualized Desktops?

I have heard rumours (and only rumours) that some large Govt. departments here in Australia actually have “per user” Desktop Licenses as part of their SA agreement with Microsoft – if that is indeed the case then they can start heading off and doing VDI today with no real worries – however, I would be carefully checking the wording AND the date at which the current agreement expires as I’m sure that when that SA agreement comes up for renewal there could be a little surprise waiting?

Terminal Server/Citrix Example:
60% of users on Terminal Server/Citrix = 3000
30% on VDI

Density based on fully loaded DL360 G5 or equivalent = approx. 80 Users per server at a cost of USD 212 per user excluding Citrix and TSCAL’s
(based on DL 360 G5 32Gb RAM, Dual Core Xeon 3Ghz, 2 x 72Gb 15K000 Drives and Windows 2003 Ent = approx. 17K USD)

Further benefits may be gained for little additional cost by using Windows Server 2003 for higher user densities

Cost of Citrix Licensing for 80 ConCurrentUsers (CCU) = USD 48K (based on Platinum retail, Ent. would drop this to 36K)

When this is added to the USD 17K for the server = Total of 65K for 80 Users and this equates to a cost of USD 812 per user (662 for Ent. Citrix) – however this is based on CCU and as such this can be aggregated to possibly only needing more like 60 – 70% of the full number of users, if we were to do this then this would bring the Citrix Licensing down to 28K. This brings the cost of 80 Users down to 562.5/user, but now I have to ask myself if I’m aggregating the licensing cost down to make it cheaper - should I still be thinking this Server calculation would be for 80 Users? Possibly, but now it’s on a slippery slope?

Cost of Servers was calculated using HP’s US based web site as of 11/08/07

Conclusion:
So on initial inspection we would appear to have:
VDI = USD 400 per user (exc. costs of Desktop License)
Citrix = USD 562 per user (exc. costs of TSCAL)

And to me this looks like it’s quite favourable to Citrix, when you add the cost of the Desktop License then the advantages of a Citrix deployment with it’s ease of use, readily available skills, mature product set and features, it’s almost a no-brainer?

However, as discussed above, if you change the figures to reflect that you can only achieve a max. of 40 users per server then it starts to tip the other way. Now we have a 17K server and 14K of Citrix Licensing only supporting 40 Users and the server cost per user now becomes USD 775.

Although VDI is currently “in vouge” I would have not thought that VDI can match the “Bang for the Buck” that can be achieved by Terminal Server/Citrix Installations, however I am now thinking that it’s quite likely that other people’s numbers won’t neccessarily be the same as mine and this could be based on a wide number of factors. So this then may be very influential in peoples perceptions and may well have an impact on what the numbers are calculated to be in ROI’s and TCO’s before commencing a project.

Future:

As I was composing this I started to really appreciate that although to date Citrix and VMware have been quite amiable in their relations it could be that the impending acquisition of XenSource (thanks Brian) changes that forever and marks them as clear and direct competitors? Still it’s early days and there should always be some healthy competition? Citrix have always declared that “the Channel is in our blood/DNA” and they have a very healthy track record of taking new and innovative products to their existing customer base.

For those that are contemplating looking hard at a VDI/xDI model now I would suggest that MS will keep the Desktop Licensing for Virtual and Streaming (VECD) pricing model very close to it’s chest until Viridian is ready to be released, and then we could see a major lift in the take up of Virtualization for the Desktop.

And hopefully that should significantly add to the growth that IDC and others are forcasting for Thin Clients? ;-))

Greenfield design - should you use Terminal Server/Citrix or VMware’s VDI?

written by dcaddick