AWS Partner Webcast - Step by Step Plan to Update and Migrate Microsoft Windows Server 2003 to the Cloud for .NET Applications


Published on

More than 10 million Microsoft Windows Server 2003 machines will enter End of Life in July 2015, which terminates all product support and updates.

Now is great time to consider how your applications on these servers can be moved to the cloud.

Review this webinar by Cloudnexa, an AWS Premier Consulting Partner, to find out how to upgrade your server infrastructure and migrate your critical applications to the cloud, step by step.

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

AWS Partner Webcast - Step by Step Plan to Update and Migrate Microsoft Windows Server 2003 to the Cloud for .NET Applications

  1. 1. A Step by Step Plan to Update and Migrate Microsoft Windows Server 2003 to the Cloud for .NET Applications
  2. 2. Introducing MJ DiBerardino Chief Technology Officer Cloudnexa Paul Andrushkiw Josh Hofmann Cloud Architect Cloudnexa Principal Manager Amazon Web Services
  3. 3. Webinar Overview  Submit Your Questions using the Q&A tool.  A copy of today’s presentation will be made available on:  AWS SlideShare Channel@  AWS Webinar Channel on YouTube@
  4. 4. What We’ll Cover  Overview of Amazon Web Services  How to upgrade your server infrastructure and migrate your critical applications to the cloud, step by step.  Insight into operations, management, and visibility for your new cloud architecture using Cloudnexa’s vNOC Management Portal.  Q&A
  5. 5. What is AWS?
  6. 6. AWS Global Infrastructure 9 Regions 25 Availability Zones Continuous Expansion
  7. 7. Solving Problems for Organizations Around the World
  8. 8. “AWS is the overwhelming market share leader, with more than five times the compute capacity in use than the aggregate total of the other fourteen providers.” Gartner “Magic Quadrant for Cloud Infrastructure as a Service,” Lydia Leong, Douglas Toombs, Bob Gill, Gregor Petri, Tiny Haynes, August 19, 2013. This Magic Quadrant graphic was published by Gartner, Inc. as part of a larger research note and should be evaluated in the context of the entire report.. The Gartner report is available upon request from Steven Armstrong ( Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
  9. 9. How Enterprises Use AWS Augment On-Premises resources with cloud capacity Migrate existing apps & data to the cloud Build new apps, sites, services & lines of businesses
  10. 10. A Step by Step Plan to Update Windows Server 2003 and Migrate to the Cloud for .NET Applications March 5, 2014 2013 Proprietary & Confidential
  11. 11. Background: A Common Scenario Windows Server 2003 will reach its end-of-life by July 2015 and customer wants to migrate/upgrade .NET applications to AWS: – Migration Drivers (AWS)  Cost savings  Just-in-time infrastructure  Efficient resource utilization – Upgrade Drivers (Microsoft)  Reduced attack service  Simplified management & scalability  Performance gains including overall footprint, memory management, etc.  New and updated features 2013 Proprietary & Confidential
  12. 12. Engagement Framework
  13. 13. Assess: Requirements Gathering & Analysis  Identify and Define: – – – – – – – Goals & critical success factors for migration Hardware & software requirements IIS application types and requirements Security and monitoring objectives Maintenance practices Fault-tolerance, high availability & SLAs Disaster recovery & business continuity planning 2013 Proprietary & Confidential
  14. 14. Plan: Evaluate & Choose Migration Strategy  Key Decision Points: – AWS Account Structure & Billing – Connectivity and Topology  Isolated vs. Integrated – Migration Approach  Forklift, Greenfield, Cloud-Native, or Hybrid – Component Decoupling  Degree of accepted modification/refactoring to application architecture – Application Coexistence and Cutover 2013 Proprietary & Confidential
  15. 15. Design: Architecture & Deployment Roadmap  Summary architecture deliverable including: – High availability – Disaster recovery – Technology gaps and third-party integrations  Create deployment roadmap: – Identify project phases and milestones – Identify risks and mitigation steps  Document current infrastructure and design decisions – “The first step towards getting somewhere is to decide that you are not going to stay where you are.” 2013 Proprietary & Confidential 15
  16. 16. Deploy: Core Infrastructure Build Establish VPC network topology & appropriate site connectivity Launch base infrastructure resources (Active Directory, antivirus, monitoring, patching, backup, operations management) Configure Microsoft resources to support application infrastructure Integrate AWS & third-party services to support application infrastructure 2013 Proprietary & Confidential
  17. 17. Deploy: Core Infrastructure Build (HA/DR) AWS Route 53 Ireland Eu-west-1 N. California Us-west-1 N. Virginia Us-east-1 Application Resources VPC Singapore Ap-southeast-1 Application Resources Application Resources VPC VPC Application Resources VPC 2013 Proprietary & Confidential
  18. 18. Migrate: Application Environment LEGEND Internet Traffic VPN Traffic Internet AWS Customer’s Route 53 DNS Provider Source Network Elastic Load Balancers Proxy Tier Web Tier Web Tier Elastic Load Balancers Application Tier Application Tier Database Tier Database Tier Customer Datacenter 2013 Proprietary & Confidential
  19. 19. Migrate: Upgrade Considerations  IIS 7 was a complete rewrite/redesign – Modular architecture with hierarchical configuration system – Integrated pipeline replaces ISAPI pipeline  IIS 8 Key Enhancements – Dynamic IP restrictions, SSL host header support, central certificate store, CPU throttling, application initialization module, WebSocket support, et.  IIS 8 Classic Mode – Full support for ISAPI pipeline; acceptable short-term solution  Migration Services & Tools: – IIS Migration Tool, AppZero 2013 Proprietary & Confidential
  20. 20. Manage: Total Operating Environment       AWS Ecosystem Underlying virtual network environment Core infrastructure and infrastructure supporting services Guest Operating System environment Active Directory and Microsoft Stacks Workloads Custom .NET applications 2013 Proprietary & Confidential
  21. 21. Management, Operations, & Development Tools      vNOC Management Suite AWS Console AWS Tools for Windows PowerShell AWS Toolkit for Microsoft Visual Studio AWS SDK for .NET 2013 Proprietary & Confidential
  22. 22. Demo: vNOC Management Suite 2013 Proprietary & Confidential
  23. 23. Benefits to Utilizing AWS + Cloudnexa      Zero upfront infrastructure investment Optimized resource utilization Reduced time-to-market Usage-based costing Knowledge capital Fastest Path to Cloud 2013 Proprietary & Confidential
  24. 24. Questions Contacts: Cloudnexa: AWS Contact:
  25. 25. We’d like your feedback. Please complete a short survey. okaGOwwxIKiifX