Build a Case for Windows Server 2012 Hyper-V
Hyper-V is a credible alternative and competitive threat to VMware for server virtualization and hybrid cloud computing. Be prepared to make the case to properly evaluate this option.
RETIRED CONTENT
Please note that the content on this page is retired. This content is not maintained and may contain information or links that are out of date.Negatives:
- Not evaluating alternatives is a failure of due diligence. You need to continually justify your choices against competing alternatives.
- Conversely, you need to mitigate quick decisions that could prove costly – such as a “sticker shock” reaction to VMware's pricing, leading to an edict to switch to the “cheaper solution,” Microsoft.
- It's not just about virtual servers any more. Decisions about hypervisors need to fit into your broader software defined platform strategy.
Positives:
- Evaluating the case for Hyper-V is a valuable opportunity to revisit, revise, and restate your overall virtualization strategy
- Discovery that Hyper-V virtualization is good enough for your particular use case could lead to significant software licensing savings over time.
- VMware argues that, though their licensing costs may be higher, so too is the value delivered. Even if staying with VMware, this exercise will help you better articulate the specific value add of VMware for your use case.
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Module 1: Identify Drivers and Set Value Measures
The Purpose
- Discuss the current state of hypervisor evolution and the high level merits of both VMware and Microsoft Hyper-V.
- Establish the key motivations for exploring Hyper-V. Who is asking for it and why?
- Establish your current overall policy toward server virtualization.
- Map out the areas of risk and challenge in a potential move to Hyper-V.
Key Benefits Achieved
- Document your overall virtualization policy and goals.
- Level set on where the organization is in terms of current virtualization vendor.
- Establish goals and measures for a Hyper-V evaluation and implementation project.
| Activities: | Outputs: | |
|---|---|---|
| 1.1 | Identify Drivers for the Hyper-V Project |
|
| 1.2 | Assess Current Virtualization and Policies |
|
| 1.3 | Debate the Pros and Cons of VMware |
|
| 1.4 | Identify Risks and Challenges of Hyper-V |
|
| 1.5 | Create an Initial Goals and Measures Statement |
|
Module 2: Define Requirements and Usage Scenarios
The Purpose
- Develop a profile of how virtualization is being deployed in your organization
- Identify requirements for virtualization and management now and in the future.
- Identify deployment opportunities for Hyper-V in your infrastructure.
Key Benefits Achieved
- An agreed-upon vision of where virtualization is going in your organization.
- A mapping of that roadmap to the capabilities of Hyper-V.
- A set of possible deployment scenarios for Hyper-V virtualization going forward.
| Activities: | Outputs: | |
|---|---|---|
| 2.1 | Assess Your Position on the Virtualization Journey |
|
| 2.2 | Map Requirements to Hypervisor Management Stack |
|
| 2.3 | Develop a Position on System Center in Your Enterprise |
|
| 2.4 | Discuss the full range of usage scenarios for Hyper-V |
|
| 2.5 | Prioritize Usage Scenarios for Your Enterprise |
|
Module 3: Analyze and Compare Total Cost
The Purpose
- Discuss all the cost implications of a move to Hyper-V.
- Understand current investment in virtualization.
- Consider costs not only for acquisition and licensing, but also for people and processes.
Key Benefits Achieved
- Nothing is really free. Get a realistic picture of the TCO of managing virtualized servers with System Center.
- Compare that to current and expected investment in VMware.
| Activities: | Outputs: | |
|---|---|---|
| 3.1 | Establish Cost Comparison Boundaries |
|
| 3.2 | Detail Current Licensing and Support Costs |
|
| 3.3 | Build a Licensing TCO for Microsoft |
|
| 3.4 | Evaluate Implementation and Operation Costs |
|
Module 4: Roadmap Opportunities for Test and Deployment
The Purpose
- Develop a roadmap of actions for testing, evaluating, and deploying Hyper-V in selected scenarios.
- Document your business case and action plan in a case document.
Key Benefits Achieved
- A shared understanding and prioritization of risks and requirements involved in deployment.
- Steps to address implementation risks and requirments.
- A documented action roadmap and case for moving forward.
| Activities: | Outputs: | |
|---|---|---|
| 4.1 | Prioritize Risks and Actions Going Forward |
|
| 4.2 | Lay Out Project Steps for Evaluation and Deployment |
|
| 4.3 | Create a Roadmap for Test and Deployment |
|
| 4.4 | Document Findings and Plans in a Case Document |
|