Is VMware trying to remake itself? To Compete with Microsoft?

With all the rebranding going on with VMware, I find it interesting that the new logo for VMware is similar to Microsoft’s logo. A single name instead of the cool boxes they used to have. Did VMware’s brand loose its focus while we were not watching? Is this why VMware is rebranding everthing? Is VMware really trying to remake itself to be more like Microsoft?

Hail the Microsoft RDS CAL-more than just a renamed TS CAL

The Microsoft TS CAL has become the Microsoft RDS CAL. The change is not only in name, but in functionality and price. The most important new offering is the inclusion of an App-V license. This will make introducing Application Virtualization in Presentation Server more cost effective and may also impact on the choice of Application Virutalization for the desktop.

Disaster Recovery Maturity shown at VMworld 2009

Veeam, Vizioncore, and PhD Virtual all showed there latest released products as well as the future products that integrate with VMware vSphere at much deeper levels that previously available, ala the VMware vStorage API. Talk was also about expanding their products into Microsoft Hyper-V as well as Citrix XenServer. This space has become so important that even the traditional backup vendors such as Symantec (BackupExec) as well as HP (DataProtector) are getting into the act. This shows ecosystem as well as market maturity not seen at last years VMworld.

Is Presentation Virtualization Yesterday's Technology?

How does Terminal Services compare to Hosted Desktops, when you compare TS vs VDI is there a winner? While some may say Presentation Virtualization is yesterday’s technology, Presentation Virtualization is undoubtedly for today and indeed, many tomorrows.

Measuring Hypervisor Footprints

There have been several interesting posts in the blogosphere about virtualization security and how to measure it. Specifically, the discussions are really about the size of the hypervisor footprint or about the size of patches. But hypervisor footprints from a security perspective are neither of these. The concern when dealing with hypervisor security is about Risk not about the size of the hypervisor or the size of a patch it is purely about the Risks associated with the hypervisor in terms if confidentiality, availability, and integrity.