Windows 2003 EOL (End Of Live)-Part 1: Getting Started and Using the Microsoft Simulator
In July 14, 2015, less than one year from the date of today, Windows 2003 support ends and many companies still are not taking the necessary steps.
Microsoft has made available a website where we can download the datasheets and use a wizard to generate reports: http://www.microsoft.com/en-us/server-cloud/products/windows-server-2003/
What are the risks and Problems
- Order of Updates (Updates) – only the Windows Server 2008 operating systems and above will receive updates
- With Compliance – credit card Operators and international banking systems (SOX, Basel, etc) did not allow transactions from this version
- Affected security – all new methods of invasion, Protocol failures or OS problems will not receive correction, meaning greater investment in additional tools or poison-reverse methods and applications
- High cost of maintenance – the new servers and hypervisors won’t provide drivers for Windows 2003, preventing hardware refresh and update version of hypervisor/VM tools
How to start from now on
The first step is to conduct an Assessment on the environment to discover all applications, for this we can use the MAP (Microsoft Assessment and Planning) that generates very good reports for migration. It even generates compliance data and directions for hardware virtualization.
To use the MAP was created a MVA last year, the focus was migration from Windows XP, but the tool operation and data generation is similar (Portuguese-Brazil): http://www.marcelosincic.com.br/blog/post/MVA-sobre-MAP-%28Microsoft-Assessment-Planning-and-Toolkit%29.aspx
The second step is to assess compatibility of existing applications, which includes the version of the web server and application components that are in these servers, database versions, etc.
This is where the big risk, many of the IT professionals who convert and companies are focusing on migrate AD, File Server and other parts of Windows, which Microsoft made easy since migration methods are Roles of the operating system. The problems are internally developed applications or not.
For example, SQL Server 2005 running on Windows 2003 will need to be migrated to SQL Server 2008 R2, applications written in .NET 1. x-2. x running on Windows 2003 IIS will need to be assessed very carefully, SharePoint 2003 and 2007 need migrated to SharePoint 2010 or 2013…
These examples make it clear that the work of migration goes far beyond just virtualization!
For this there are many software’s that do the role of parser, as for example, the Dell ChangeBase and AppZero. The first examines all the applications installed (similar to Microsoft ACT) and automatically tests standard methods and natives of compatibility. The second has several additional methods of compatibility and a tracking application, generating an MSI package, which is extremely useful in scenarios where we don’t have an installer and we don’t know the dependencies of an application.
The third step is to analyze the options, where we can evaluate a P2V (physical to virtual machine migration) on-push, migrating sites or database for Microsoft Azure, creation of VMs in the cloud with services and data transfer, etc.
This phase is where we need to create well defined migration plans for each of the applications and functions that today are in Windows 2003. This is the phase where we should concentrate on stopping services, sequence of operations, migration processes, etc.
Leave after the migration of the servers is much more serious than the migration seasons. Until today many companies still have XP and feel the difficulties and costs of maintaining an unsupported operating system. Start now to prepare and will be much easier.
In a next article I will talk more about the MAP and other tools for the Assessment.