Saturday, May 24, 2014

My New Blog

I was just doing a bit of spring cleaning on my LinkedIn profile and remembered about this previous, short-lived attempt at a blog. Unfortunately my attentions were diverted elsewhere and I wasn't able to sustain this effort, but I've recently started again.

Please be sure to check out my new home at http://www.bobbyhyam.com/

Thanks all. This will be the final post at this address.

Bobby

Saturday, March 13, 2010

Licensing Microsoft Windows for Virtual Desktops

Since desktop virtualization first started to come to masses a year or two ago, one of the issues that seems very difficult to find information on and understand is that of how to license the Microsoft desktop operating system in such a deployment. Having demystified it for myself, I explain it to new customers on a regular basis and their next reaction is usually one of distaste as on first glance it looks like a lot of money is being spent on Windows licensing that would not have been in a traditional desktop deployment.

In this posting I will explain the two different ways to license and pay for Microsoft’s desktop operating system in a virtual desktop environment and also examine the facts and logic behind it.

Virtual Desktops – A Quick Primer

Virtual desktops or desktop virtualization is the idea of installing the desktop operating system (in most cases Microsoft Windows) on a virtual machine hosted on a server in the datacenter instead of onto the device that sits under the user’s desk. The user then uses some type of client device, usually a repurposed legacy PC or a thin client) to remotely control that virtual machine.

I will not go into the details of the benefits of this technology but sufficed to say that they are significant and 2010 is the year that CxOs and technology leaders will be looking at desktop virtualization. If anyone is interested in exploring this technology then please feel free to contact me directly.

Two Models to License

Depending on the client that you will use to access the virtual desktop, there are two different licenses that you can purchase. Both are labeled and marketed under the banner of Microsoft Windows Virtual Enterprise Centralized Desktop (VECD). This also used to be referred to as Microsoft Windows Vista Enterprise Centralized Desktop and some of the material you find on their site still uses this branding, but the model is the same regardless.

Scenario 1: Thin Clients or Repurposed Legacy Desktops without Software Assurance

I’ll first explain the model that will apply in most cases. It applies when the organization is planning to repurpose legacy PCs as clients and has not purchased Microsoft’s Software Assurance (SA) option on their Microsoft Windows desktop operating system licenses. If you are unsure if you have, then you probably have not done this. You will usually only have this if:

  1. You have an Enterprise Agreement with Microsoft that covers the desktop operating system.
  2. You actually explicitly went out and purchased SA for every desktop as an add-on the OEM license you got with the PC.

If you are planning to use thin clients either with Windows XP embedded or an alternative operating system then this first model also applies to you regardless of the above.

In this scenario, customers are required to purchase the Microsoft VECD license for every device that will access the virtual desktops. The list price of that license is $110 per device per year and the commitment is three years. Therefore over the course of the three years you would be paying $330 total. Customers have the option of paying annually or upfront in full.

Note that you must buy a VECD license for every unique device accessing the virtual desktop. If a user wants to use their corporate thin client and their home desktop to access the virtual desktop at different times then you must buy two VECD subscriptions. This is the one point of contention that is making virtual desktop ROI more difficult to prove if one of the reasons for implementing it is accessing that desktop from multiple clients in multiple locations.

This license entitles you to run the latest version of the Windows operating system in the Enterprise Edition. As you continue to subscribe and future releases of Windows come to fruition, customers are entitled to those new releases as part of their subscription.

Scenario 2: Repurposed Legacy PCs with Software Assurance

Those customers who have purchased SA on their desktop operating systems either through an Enterprise Agreement or explicitly have less to pay. These customers may purchase VECD for Software Assurance, which is priced at $23 per device per year.

There is one complication here that some may notice. Let’s assume you choose to repurpose legacy PCs with SA and purchase the $23 per device per year license and as those legacy PCs fail you will replace them with thin clients. In this scenario, you would have to transfer from the $23 license to the full VECD license, regardless of the state of your SA because the thin clients do not come with a base Windows operating system license (XPe does not count) and therefore are not covered. As yet, I have not found a way around this.

From July 2010, this $23 charge will disappear and VECD for desktops covered by Software Assurance will be included for free, but in order to access the virtual desktop from non-corporate clients not covered under SA such as home PCs or Macs, you will have to by a Virtual Desktop Access License priced at the original $110 per year for every unique device.

Reactions and Objections

“Double Dipping”

So, by now you might be rethinking desktop virtualization as you have an additional $360 to find for every desktop and it brings into question the TCO value proposition. Some customers have described this as “double dipping” by Microsoft but let’s take a look at what Microsoft is actually taking as part of this deal.

If you purchase regular Microsoft Windows Enterprise Edition desktop operating system licenses with a traditional desktop PC you would be spending around the same sort of money. The difference is that the licensing costs are baked into the cost of that desktop PC. This model takes a hidden cost and makes it visible to the customer, but it doesn’t actually change the amount of your money that Microsoft is taking and at the end of the day it is the same software that you are getting so actually I don’t have a problem with this particular issue.

Microsoft Desktop OS Refresh Cycle in the Real World

There are however a couple of other issues. One might argue that that a new Windows operating system that customers actually find useful and want does not get produced every three years. Many organizations did indeed skip Vista and got eight years out of Windows XP and many are still running it now.

Having said that, if you are one of those people who have got eight years out of Windows XP, the likelihood is that you have not purchased it just once. You have actually purchased it once for every time you have refreshed your desktop hardware because the price of a new license is baked in to the cost of that hardware. Given that the average lifespan of desktop / laptop hardware is four years, you would actually have purchased that operating system twice.

There is no way around this in case you are wondering. OEM licensing that comes with your desktop or laptop lives and dies with that device. It cannot be transferred.

TCO/ROI

The final objection that I’m seeing from customers is that the cost of the licenses that is sometimes overlooked at the early stages of the project discussion brings into question whether desktop virtualization TCO/ROI presented is still relevant. There are several other factors that make up the compelling desktop TCO reduction when virtualizing, which make this a non-issue.

First, an IDC report (if you would like to see it then contact me directly) has shown that in a traditional desktop environment for every $1 spent on desktop hardware, a further $3 is spent on supporting that hardware over the course of its life. The same report shows that virtual desktops only cost $1.20 to support over the same time period. This alone is a saving of 60% in support costs and will more than pay for the backend infrastructure and other capital costs involved in the project.

Add to this the soft benefits in flexibility and business agility that desktop virtualization brings to the table.

Users can now access their own desktop from any internet connected terminal.
  • Desktops can be integrated into disaster recovery strategies that leverage replication to a remote site. The user will have their own desktop in a DR scenario, wherever they may be. This eliminates the largest remaining spanner in the works of a disaster recovery plan post-virtualization of servers - the device the user uses to access applications.
  • New desktops can be provisioned automatically, on demand. New hires no longer sit around waiting for IT to image their desktop. Existing employees need not wait for a day or more for them to prepare a replacement if they lose their client device, it fails or becomes infected with malware. We simply replace that device with another dumb terminal or any old desktop/laptop.
  • Bring branch offices where there is no local IT support into the mix and the benefits begin to multiply.
Conclusion

Licensing the Windows desktop operating system through VECD for virtual desktops is actually relatively simple once explained in the right way. The initial knee-jerk, negative reaction to Microsoft’s model is actually not a valid objection and neither is the one regarding the damage it does to the ROI promised by desktop virtualization.

Desktop virtualization will revolutionize the way we manage our users’ experiences and reduce the cost of supporting those users significantly despite the concerns raised by initial reactions to Microsoft's licensing model.

Friday, January 15, 2010

Why Buy Cisco - Is The Name Worth The Price Tag?

I want to talk about a topic that comes up continuously with many of the organizations I work with. Regularly, either the technical decision maker or the person who ultimately signs the check will see two proposals in front of them. One is for a Cisco-based solution and one is for a solution based on one or more other vendors such as HP Procurve, Riverbed, SonicWall, Nortel, Juniper etc. In many cases the price tag associated with the Cisco-based solution both is higher than the offering from other vendors, yet still Cisco holds a majority market share in many of the areas that it competes in.

I can confirm this position when I see the majority of my customers choosing quite often to purchase Cisco products over their cheaper competitors. For all those IT decision makers and CIOs tasked with bridging the gap between the technologists and the business, I want to ask the question, “What is Cisco’s value proposition and is it worth it?”

The Competition
First of all, let’s look at what the competition offers. There are many different vendors that compete with Cisco. Some are specialists that operate in a specific area such as security (ISS, Mirage Networks), switching (HP Procurve), WAN acceleration (Riverbed) or content delivery (F5). Many of the ‘specialist’ competitors are recognized by independent research organizations such as Gartner and indeed by technical professionals themselves to have the best product to do the job that they are doing. In areas outside of routing and switching, there are few places where Cisco can unquestionably claim to have the best products when looking at that single solution area.

Others competitors such as Nortel and Juniper play in many more areas and offer products across routing and switching, security, voice etc. These have better offerings in the area of integration (described below) but often lack severely in the specialist areas the other type of competitor excels in.

Innovation
Now, let’s look at what Cisco does that’s different from the competition, starting with innovation. Innovating is something most technology companies claim to do and some do indeed deliver on that claim and provide tangible business value from that innovation. Others duplicate the efforts of others and compete on price, driving down the prices of new technologies and bringing them to the masses – a perfectly acceptable business model.

One statement that does hold true is that Cisco is one of the few companies that does innovate and provide tangible business value for the customers that take advantage of the resulting technologies and services.

To give a few brief examples, Cisco has many proprietary networking protocols and technologies that it developed in house. Some such as EIGRP (to be discussed below) have remained and will remain proprietary. Others such as FCoE (also discussed below) have been driven to become open standards and can now be adopted by other vendors.

Let’s take the EIGRP routing protocol as our first example seeing as it is at the heart of what Cisco claims to be best at: routing. Way back when, Cisco saw a problem. There were two widely accepted routing protocols based on open standards: RIP (and RIPv2) and OSPF. RIP was to its credit, a very simple protocol to configure and administer but it had major problems when it came to scalability and its ability to manage traffic when it come to multiple paths. OSPF on the other hand was a highly scalable model but was (and still is) extremely complex to configure.

Cisco developed the Interior Gateway Protocol (IGRP) and later Enhanced IGRP (EIGRP), which was not only very simple to configure for small and medium sized environments like RIP, but it scaled extremely well and went further to provide better traffic management features and faster convergence than OSPF. Some network engineers will tell you that this one protocol in itself is enough to justify buying Cisco routers and switches because of the time it saves you on design, documentation, ongoing maintenance of that documentation and the ease with which changes can be made to that design.

Another example of Cisco’s innovation in this area is with Hot Swap Router Protocol (HSRP). They saw a need for their customers to have redundancy in the components that joined their networks together – the routers. They developed and published this protocol in 1998. Customers saw it in products and could take advantage of this extra layer of availability (which is now considered essential in any enterprise) soon after.

By comparison, the equivalent open standard, Virtual Redundant Router Protocol, was not completed until 2004 – six years later. It’s clear that this provided significant business value and piece of mind to Cisco customers for a long period of time before the market caught up.

I want to discuss one final example. Cisco can be accused of being acquirers rather than innovators. Indeed, they are acquirers and have brought many products to market based on acquisitions, but I’m a strong believer that they are still innovation focused.

We can see this with their latest innovations in the datacenter with the Unified Compute System, Fiber Channel over Ethernet (FCoE) and Unified Fabric. The majority of the datacenter professionals you talk to regard their advances in this area as visionary. I won’t go into all the details here as it’s outside the scope of this discussion.

I wanted to bring up the datacenter example because Cisco did this one a little differently. They actually spun off a new company called Nuova Systems to find ways of simplifying the datacenter without having their efforts influenced by Cisco’s other product lines. Cisco then reacquired this company when the necessary breakthroughs had been made and they now have very solid products coming to market.

So, you might ask, “Why should I care about innovation? The others do the basics that I need at a lower price point.” We’ll examine that question later in more detail.

Integration
Integration is the next natural step in the evolution of any Information Technology system after performing and automating individual tasks. I’d like to refer to an old book written by Bill Gates back in the 1990s called ‘Business at the Speed of Thought’. Some of the ideas are a little dated now and perhaps they were not all his, but the underlying principle that he grasped is still not understood by many CIOs today.

The idea is this: when a piece of information enters the organization, it should be digitized and made available to every part of the organization that can improve its efficiency or productivity from that information and it should be presented such a way that it is useful to those parts of the organization. From this concept comes the idea of business intelligence, data mining other similar activities. In his book, Gates gives examples of how sales data was collected and analyzed to improve performance going forwards as well as how he felt so strongly about this principle that he actually banned paper forms at Microsoft so that all information was in this digital format. I strongly advise anyone in a CIO type of role to give it a read.

Anyway, integrating systems and sharing information leads to more intelligent decisions, better automation and more computers doing work that people do not have to. Cisco is integrating its product lines with each other.

This can be seen in several areas but some are key. Unified Communications in which phones share information with switches and endpoints (PCs) in order to enable telephony information to be integrated with applications. For example, I have seen applications that allow lawyers to automatically record conversations with clients and send them a copy of the recording along with the automated invoice for their time.

Cisco also has a big marketing term, ‘The Self Defending Network’. Some might see it as just that but it is actually a phenomenal and valuable piece of engineering. In summary, all the relevant Cisco products collaborate to defend the network. Routers, switches, firewalls and even agents on PCs all communicate security events to a central threat management system to get a better handle on when an attack is underway and to co-ordinate an automatic response. The network really does defend itself.

These are just some of the things integration holds for the future of networking but Cisco is leading the way here and their customers who recognize the value in integrations like these and choose to invest will reap the benefits with cost savings, better security and competitive advantage.

Skills and Training
Cisco’s certification programs are viewed by many as the best in the industry. They are also the only certification programs created by a commercial technology company that I am aware of that are adopted by universities and colleges as part of their standard curriculums.

The reason this is so is because Cisco training teaches people skills primarily and product knowledge second. The skills such as subnetting and basic routing taught in their baseline CCNA certification are transferrable to other vendors’ products and also survive. Other vendors’ training can be heavily product focused from the word ‘Go’ and therefore the skills their graduates have become outdated as products are refreshed. This is why universities and colleges are apprehensive about adopting them.

As a result of the wide adoption and acceptance of their training and certifications, Cisco certified professionals are relatively easy to find. Granted, top-level CCIEs are still in short supply, but trying to find someone with the same level of experience on products from other vendors can be extremely difficult. The Cisco partner community is also filled with variation, choice and good competition that keeps driving the value on offer higher.

Management
The final area I’d like to examine is management. Some of these points hold true for a single vendor strategy whether it be Cisco, Microsoft, HP etc. But, once you realize the business value offered as described above, it is easy to understand why people choose Cisco over others as their primary, preferred vendor.

Whenever there is a requirement to have skills in multiple vendors’ products, there is always a challenge in finding those people and especially the right people that have the right mix of product knowledge that matches your environment. When you have a firewall from vendor X, a switch from vendor Y and a router from vendor Z, finding the right person who has experience with making them all work together can sometimes be impossible. You are often working to put together a multi-vendor solution with many different moving parts that is probably not entirely documented and tested where the single vendor solution would be.

Furthermore, if you were to run into a problem with your mixed environment and you need to call your three vendors for assistance, it is commonplace for much finger-pointing to take place. Vendor X blames vendor Y, vendor Y blames vendor Z and vendor Z blames the other two. I cannot emphasize enough the impact of this point.

Support tickets are solved so much more quickly when they are quickly elevated to the higher levels by the single vendor because they realize that it must be one of their products that is at fault. This can translate into days of troubleshooting time either by your own staff or expensive consultants who charge by the hour. I have in fact just finished on a project where we lost four days out of ten on an implementation in a foreign country. The result was that the project was pushed back by weeks due to the subsequent scheduling problems it created.

Working with multiple vendors also means managing support and maintenance contracts with multiple vendors. This is at the very least an administrative overhead, but if they operate on different dates and/or models then they end up making budget planning more complex than it needs to be.

One final point on the subject of management… There is no open standard for systems management. Many vendors have their own products: HP has OpenView, IBM has Tivoli, Cisco has CiscoWorks, Microsoft has System Center etc. The net result of this is that yes, they can all monitor any class of device be it owned by that vendor or not, but they all excel at managing their own devices. Other devices are ‘supported’ either through open standards or through third party management packs but never give quite the same great experience as you would get from that vendor’s own management products.

Summary
Cisco products are quite often not considered to be the best of breed in areas outside of their core routing and switching, but they do at least have formidable products in every area they are competing in. They have a strong history of innovating and providing tangible business value through their home-grown products and their acquisitions. This value when viewed with a strategic eye that recognizes long term and soft costs associated with other vendors’ solutions, often delivers lower overall cost and additional useful functionality beyond that of the competitors.

Obviously it is not always the case that Cisco will innovate first, but by adopting a single vendor strategy with Cisco, you can be sure of great, reliable support when you have problems; tested and documented solutions that you can repeat in your organization with confidence; and a management platform that gives deep insight and granular control over the entire breadth of your network. You may not have best of breed or the most money in your pocket immediately after the initial investment, but you can sleep sound knowing that your business assets are secure, available and that you have made a decision that is solid, understandable and difficult for others to criticize.

DISCLAIMER:
The opinions expressed in this article are mine and mine alone. They do not represent the opinions of my employer, Vicom Computer Services, its affiliates, subsidiaries or any of its partners.

Tuesday, January 12, 2010

Welcome

I’d like to thank you for taking the time to read my very first ever blog post. It’s something I have considered doing many times but realized that I needed a topic that I felt passionately about so that I could continuously produce quality content on a regular basis.

I have had the privilege of entering into the IT consulting industry very early in my career and consequently been lucky enough to work with many different people who have a huge range of opinions and methods for approaching very similar problems. I have over the course of the last eight years so far used this experience to pick the best of those methods and repeat them with my customers, but for this blog I wanted to try something a bit different than just being a fountain of best practices.

I travel around to different customers advising them on infrastructure projects they intend to undertake using products from vendors such as Cisco, VMware, IBM and NetApp. Ultimately there is usually a component of the engagement where I have to help those customers to see the value of the individual products and the overall solution so that they buy it.

All the vendors arm you with competitive battle cards telling you specifically why their product is better than their direct competitor and why. They give you extensive datasheets and product brochures that attempt to convince the customer that this latest and greatest and will solve all their problems promising huge ROI and lower TCO.

I have found that in many cases, that a more critical eye will find that actually the picture painted is a little fluffy and that the benefits touted are not necessarily all going to be realized from day one because the real world that the customer lives in sometimes requires that vendor products and recommended ‘best practices’ must be tweaked or re-evaluated somewhat.

In this blog I intend to examine the value that products bring from a business perspective. The focus will not be on particular features necessarily but on what can you actually get out of them as a business.

I’ll also be looking at some ways you can look at IT from a more business oriented angle. I have found that it is very easy for even high caliber IT professionals to get over-excited by a particular technology or process that they have been told is the ‘best practice’ way to carry out a particular task. I’ll be suggesting new ways to approach problems in some of my postings with no reference to specific products in the hope that I can make the readers of this blog more useful to the business and start to help bridge the gap between the business and technology.

Most of what I will write is subjective and I fully encourage comment and further discussion. There are no right or wrong opinions. These are just mine that have developed based on seeing the same problems solved well and badly over and over again.

I hope you enjoy.

DISCLAIMER:
The opinions expressed in this article are mine and mine alone. They do not represent the opinions of my employer, Vicom Computer Services, its affiliates, subsidiaries or any of its partners.