Windows Server 2003 Migration to Microsoft Azure

Selecting Workloads a Windows Server 2003 Migration to Microsoft Azure

Extended support for Windows Server 2003 will be withdrawn on July 14, 2015. After that date there will be no more patches, updates, or security updates for that old version. If you’re still running Windows Server 2003 it is now critical to start planning to move off of it and onto a more modern platform. With most upgrades there is usually a single path, only one way to go. This time, for the first time, you have some choices available to you!!

Migration to Microsoft Azure

Even If you’re NOT Running Windows Server 2003

Whether you use Windows Server 2003, 2008, or any of the other versions released over the past decade now may be the time to make a change, especially if you want to save money, reduce support costs, and eliminate headaches.
One of your choices is, of course, the latest version, Windows Server 2012 R2. With over 300 features that didn’t even exist back in 2003 this is a great choice for those who wish to keep running and maintaining their own servers on their own premises. New Microsoft CEO Satya Nadella refers to Windows Server 2012 R2 as the “Cloud OS” because you can use it to enable and enjoy all the advantages of private cloud computing.
For this migration, for the first time, you have flexible choices regarding how your future state environment will look and function. While many think it’s a matter of choosing either on-premise Windows Server 2012 R2 or Microsoft Azure cloud services, it’s really more of a matter of how you take advantage of the hybrid cloud opportunity to combine both.

Transforming Your Data Center

According to Microsoft’s marketing, “Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. You can build applications using any language, tool or framework. And you can integrate your public cloud applications with your existing IT environment.”
It is this last point that is most important to anyone transitioning away from Windows Server 2003. Since Microsoft Active Directory can span both on-premise and cloud-based servers, it becomes easy to maintain one database of security and access rights and approach the combination as a single entity. This, in essence, creates a “Datacenter without boundaries” in which you can burst beyond the capacity of your local service to the highly-elastic resources of Azure. Azure also provides complete data center redundancy, a level of resilience that would cost far more if you did it yourself, which is just one illustration of the cost-effectiveness of the Azure solution. Speed and high security make it a highly desirable place to migrate your workloads.
But which workloads? Which should go to the Azure cloud and which to your local on-premise Windows Server 2012 R2 units?

The Migration Process – Microsoft Best Practices

Microsoft recommends a simple, yet elegant, four-step migration process:
1) Discover – Catalog your software and workloads
2) Assess – Categorize applications and workloads
3) Target – Identify the destination(s) for each of your workloads
4) Migrate – Make the actual move
A potential fifth step would be the ongoing management of your new environment to constantly assure optimum performance.


Discovery tends to become more extensive, and more tedious, than most anticipate it will be, but it’s crucial to be as comprehensive as possible. Missed applications and workloads can become headaches later on. Once the entire inventory has been documented, it is important to assess the applications, the workflow related to each data entity, and potential impacts upon users from various scenarios.
The four likeliest targets for your workloads are:
1) Windows Server 2012 R2 Server running on your premises
2) Microsoft Azure
3) A Cloud OS Network, likely running on your premises
4) Office 365
Obviously, productivity and communication related activities will likely be migrated to Office 365. This may include email moving to Microsoft Exchange Online, document management moving to SharePoint Online, and instant messaging, voice, video, and shared application communications moving to Lync Online.
Choosing between the other three targets will be determine by factors including speed, ease of migration, cost, and desired functionality. One good example would be websites, which would be better served by the speed available from the Azure data centers, as well as the elasticity of the storage, processing power and memory which could all contribute to keeping sites responsive even during times of peak demand.

Experience is Your Best Tool

When determining where to target your workloads, turn to the extensive Azure experience of the team at Hanu Software. Our entire team stands behind our commitment to help you migrate “Any Workload, Any Application, from Any Platform to Azure!” Talk to us today about your Windows Server 2003 migration plan.

Azure Managed Services