Monday, August 24, 2009

VMware is at a crucial point in its 11-year history

The virtualization leader now faces its most serious challenge yet -- from Microsoft's much-improved Hyper-V R2 hypervisor.

 

Some on Wall Street say the company's stock is overvalued. And a leading IT analyst thinks VMware could be headed for a Novell-like downfall.

It's enough to make the IT world -- even VMware Inc.'s proponents -- wonder whether the company is losing its allure as the go-to virtualization vendor.

"The sky's not falling, but it's drizzling," said Brad Maltz, the chief technology officer of International Computerware Inc., a VMware partner in Marlborough, Mass. "The Microsoft message is getting stronger. It's not something [VMware] can't handle, but it's something they have to keep their eye on."


 

VMware draws Novell comparison
This competition from Microsoft, which just released Hyper-V R2 to manufacturing last month, is the point of origin for all other questions about Microsoft. .

When financial analysts told Reuters that VMware's stock price was poised to go down, it was because the company had "yet to factor in the competitive threat" from Microsoft (and potentially Oracle as well).

 

And when Gartner Research Inc. Vice President David Cappuccio wrote that VMware could lose its leadership role in the virtualization market, he compared the company to Novell Inc. -- the former software giant that Microsoft took down handilyin the 1990s.

And that brings us to VMware's standing today. Long seen as the dominant player in virtualization, VMware leads in features, management tools and market share, but Hyper-V R2 offers expanded management tools and other new capabilities that could change all that.

"Clients we're talking to aren't running away [from VMware] right now, but a lot of them are taking a wait-and-see attitude with Microsoft's Hyper-V R2," Cappuccio said in an interview.

That's got to make VMware take a very close look at history, he said. Back in 1995, Microsoft was a non-player in the Novell-dominated LAN software market. Even when Microsoft came out with a free Windows 95 networking application, Novell didn't worry, because it wasn't enterprise-ready.

But what Novell didn't count on was that technology geeks inside corporate IT departments "fooled around with [Windows 95], and over a few years it became pervasive," Cappuccio said. "The danger for VMware is that is exactly what will happen for enterprise virtualization."


 

Is Microsoft Hyper-V R2 'good enough'?
If Hyper-V R2 proves to be a good enough virtualization alternative for what corporate IT departments need, that's when VMware will need to start worrying, Cappuccio said.

Dave Sobel, CEO of Evolve Technologies, a Microsoft partner and managed services provider in Fairfax, Va., agreed.

"Microsoft is clearly gunning for the virtualization space, and they have a pretty good track record of making a dent in a space that they want to be in," he said.

Another real problem for VMware is that Hyper-V R2's management tools now manage VMware's ESX hypervisor, while VMware's tools won't manage Hyper-V R2. That's big for users who want to use both hypervisors, because only Hyper-V R2 will be able to manage the entire environment, Cappuccio said.

"I would hope [VMware is] paying attention," he added. "My fear is that 'good enough' always wins out in the long run, and if it's good enough and pervasive, VMware may lose out."

What has to worry VMware even more is that improvements in hardware mean that companies can add new servers with additional processors and cores and still use them under their existing licensing agreements. That's great for users, but it hurts VMware's sales of new licenses, said Chris Wolf, an analyst with the Midvale, Utah-based Burton Group.


 

VMware vs. Microsoft in the future
One factor in VMware's favor is its long head start in the market, Wolf said. For VMware's existing customers, the new features in Hyper-V R2 -- including hot-add and remove storage capabilities andLive Migration -- won't be enough to lure them to Microsoft, he said.

"Our clients who have done large-scale deployments don't see Hyper-V R2 as having enough features for them to move," he added. "However, some are saying they'll look at one more release cycle [for Hyper-V] and then do another assessment."

VMware most stands to lose with companies that are not yet using any virtualization and are shopping for the right vendor, Wolf said. Those customers will likely look at VMware, Microsoft and Citrix Systems Inc.'s XenServer to decide on the right choices.

"Microsoft and Citrix both, I think, are going to get a reasonable part of the market," Wolf said.

Hyper-V R2 will likely add new users in the small and medium-sized business sector, because of the new features and an ingrained familiarity with Microsoft products and support, Wolf said.

Still, "virtualization is going to remain a multibillion-dollar business, and VMware is going to remain the market leader for the next few years," he added. "VMware and its position, especially in the data center, remain unchallenged. It's going to take some time for competitors to chip away."


 

Sobel said VMware isn't necessarily on the ropes now, but there are new opportunities for Microsoft.


 

"Microsoft's hypervisor is now equivalent in all the key areas," he said. "The Live Migration stuff takes away the VMware advantage. That has always been held up as the feature that VMware had that made them the leader." And Hyper-V's constant improvements will continue to put pressure on VMware, said Rick Vanover, a corporate system administrator and independent virtualization expert.


 

"VMware is the leader," he said. "[VMware has] to look over its shoulder and nobody else has that burden."

 

 

Article link: http://searchservervirtualization.techtarget.com/news/article/0,289142,sid94_gci1364388,00.html


 

 
     
 
     

 

 

 

Thursday, August 20, 2009

10 things you should do to successfully manage your workplan


Project managers are sometimes diligent about creating an initial workplan (schedule), but then they don't manage it during the project. Although the initial workplan will help you launch your project, issues will come up that require the workplan to be modified and updated. On most projects, you can follow this simple 10-step process to manage the workplan. If you do this weekly, you'll probably find it takes less than one hour per week-maybe only 30 minutes or so.

1: Update and review the workplan with progress to-date
This is probably a weekly process. For larger projects, the frequency might be every two weeks. A simple routine is to have the team members send you status updates on Friday with progress on the activities assigned to them during the week. The project manager then updates the workplan on Monday morning to reflect the current status.
2: Capture and update actual hours (optional)
If you're capturing actual effort hours and costs, update the workplan with this information.
3: Reschedule the project
Run your scheduling tool to see if the project will be completed within the original effort, cost, and duration estimates.
4: Review your schedule situation
See if you're trending past your due date. If you are, you will need to determine how you can get back on schedule.
5: Review your budget situation
Review how your project is performing against your budget. Because of the way financial reporting is done, you may need to manage the budget on a monthly basis.
6: Look for other signs that the project may be in trouble
These trouble signs could include team morale problems, quality problems, a pattern of late work, etc. Look for ways to remedy these problems once you discover them.
7: Adjust the workplan and add more details to future work
When the workplan was created, many of the activities that are further into the future may have been vague and placed into the workplan at a high level. On a monthly basis, this work needs to be defined in greater detail. You should always maintain a rolling three months of detailed activities on your workplan.
8: Evaluate the critical path of the project and then keep your eye on it
It's possible for the critical path to change during the project.
9: Update your project forecast
After you've updated your workplan to reflect the work remaining to complete the project, you should also estimate the cost of the remaining work. This is usually referred to as "forecasting."
10: Communicate any schedule and budget risk
If you're at risk of missing your budget or deadline, communicate this risk to the sponsor and management stakeholders. You don't have to state that you will miss your estimates for sure. However, you should start to communicate the risk while you implement actions to try to get the project back on track.

Note: This list is based on the article "Proactively manage your workplan using this ten step process." It's also available as a PDF download.

Sunday, August 16, 2009

Migration paths from Windows Server 2003 to Windows Server 2008 are summarized below.

Migration paths from Windows Server 2003 to Windows Server 2008 RC0 evaluation software are summarized below. Final migration paths for the RTM versions of Windows Server 2008 will be determined in the coming months.

If you are running*:

You can upgrade to:

  • Windows Server 2003 R2 Standard Edition
  • Windows Server 2003 Standard Edition with Service Pack 1 (SP1)
  • Windows Server 2003 Standard Edition with Service Pack 2 (SP2)
  • Full installation of Windows Server 2008 Standard (with or without Hyper-V)
  • Full installation of Windows Server 2008 Enterprise (with or without Hyper-V)
  • Windows Server 2003 R2 Enterprise Edition
  • Windows Server 2003 Enterprise Edition with Service Pack 1 (SP1)
  • Windows Server 2003 Enterprise Edition with Service Pack 2 (SP2)
  • Full installation of Windows Server 2008 Enterprise (with or without Hyper-V)
  • Windows Server 2003 R2 Datacenter Edition
  • Windows Server 2003 Datacenter Edition with Service Pack 1 (SP1)
  • Windows Server 2003 Datacenter Edition with Service Pack 2 (SP2)
  • Full installation of Windows Server 2008 Datacenter (with or without Hyper-V)

*Note:  With the exception of Windows Server 2008 for Itanium-Based Systems, this table applies equally to 32-bit and x64-based versions. However, cross-platform upgrades (32-bit to 64-bit or the reverse) are not supported.