myTemplate

I've just stumbled upon the following article. The writer actually accuses VMware of being lazy in that they've failed to develop a vSphere client that works out of the box for Windows 7! How messed up do you get? As far as I know, Windows 7 has not had its official release yet and can only be obtained via TechNet and MSDN. So all, let's blame someone for not developing a piece of software for an OS that's not really released yet!

Get a life! Oh, and maybe try buying a domain as well! Or wait, maybe you're too lazy or cheap to buy a domain, hence the reason we're all looking at an IP address in your URL...

Here's the article:

http://99.246.113.36/wtslabs/blog/?p=53

It’s now a done deal. VMware has officially completed their acquisition of SpringSource. SpringSource is an enterprise and web application development company and will now be seen as a division of VMware. The CEO of SpringSource will serve as the division’s general manager.

VMware says that the new division’s “charter” will be to focus on providing developers and customers the best experience for developing enterprise and web applications, as well as helping VMware create integrated products based on SpringSource technologies and VMware vSphere to deliver a simplified ‘build, run and manage’ experience. These new products will help VMware’s cloud computing strategy to deliver PaaS (Platform as Service) solutions that can be hosted by their customers internally or by service providers.

In today’s world where mission critical applications need to be available 24x7 with 99.99% availability, companies are throwing millions of dollars or pounds at implementing redundant and fault tolerant infrastructures. We all know that the money we spend today will save us much more in the future. Some companies make two to three million profit each and every day. In order to be competitive in the current climate, they need business applications such as messaging and collaboration to be available at all times. Imagine if a business with hundreds of employees one day suddenly lost the ability to send and receive email.

This may sound unheard of, but just this very week I’ve dealt with such a case where a company employing almost 10,000 people had no email, collaboration, database systems and even a corporate website for more than 24 hours, just because a critical component failed on their main SAN. Now let’s just say they make on average 2 million pounds profit each day. They had no business trading on the day of the failure, costing them a huge part of that 2 million pounds profit as the 10,000 people they employ had to be paid for that day an no one could do any meaningful work. If they had only spend half of that on a replication solution for their SAN, they could have avoided such a lengthy outage.

I’ve been trying to install VMware vCenter Server on Windows Server 2008 R2 Enterprise Edition. This is because I am working on a few blog articles on protecting the vCenter Server against hardware failures. At the moment, I’m busy working on two blog posts.

1.       Protecting vCenter with VMware vCenter Server heartbeat;

2.       Protecting vCenter with Microsoft Cluster Services (MSCS).

Whilst trying to install vCenter on Windows Server 2008 R2, I ran into some issues I had to resolve before I could do anything useful.