5 Things You Should Do Now That Server 2003 Support Ended
July 15th Has Come and Gone and Server 2003 Support Ended!
This is a guest post by Paul Sachse, Services Engagement Manager for Champion / MessageOps. Paul is one of our migration experts on our team who can help your company migrate from Server 2003 to 2012 simply, seamlessly and successfully. Paul can be reached at 561.997.2900 x164 or via email email@example.com.
They say if it ain’t broke, don’t fix it…but it is and you should
Consider how astoundingly old the Server 2003 OS is, not just in years but in relativity. In the whole life cycle of Windows Server, one could argue that Windows Server 2000 was the first real server OS from Microsoft, and that Server 2003 was the first reliable, widely-deployed Windows Server OS. Just the thought brings a little tear to my eye.
But IT is a lousy place for nostalgia
Software updates and upgrades address vulnerabilities in existing products, but sometimes technology advances so far that an entirely new solution is necessary. When you cling to old technologies or dismiss the necessity of switching because what you’ve got “still works,” you introduce a variety of operational and security vulnerabilities. So while Server 2003 may still be up and running, it really is broken. Permanently broken. See, when you bought your operating system licenses from Microsoft, you purchased the right to use them. Now that right has essentially been revoked, which means you’re running without a licensed OS.
So you don’t care about licenses
Okay, fair enough. What if we told you that pulled support also means less security? Let’s pretend you’re a hacker. Would you rather target an OS that’s actively being developed, patched and protected, or one that has known vulnerabilities and will remain vulnerable? Because a Microsoft-supported operating system receives periodic software updates, your security is also periodically updated. These security updates help protect your PC from new viruses, spyware and other malicious software. An unsupported, obsolete OS is a hacker’s paradise because it makes you a really easy target.
Do the work – migration is worth it
We’re sure you can think of more fun things to do than migrating servers, but this task is long overdue. So do yourself and your business a big favor: follow these 5 steps to migrate from Server 2003 to 2012.
1. Take inventory of all your OS’s and applications.
2. Get a detailed mapping of what server applications depend on each other including how they talk, how much and how often. (There are tools for this if you don’t have the map memorized.)
3. Establish which applications have a path to Windows Server 2012 R2 (or 2008 R2, if you want to stay just a little behind the times).
4. Create a migration plan for each of the apps with a clear path to the new OS. For the applications that are stuck in yesteryear, migrate them to the cloud to isolate them from your network (to the greatest extent possible).
5. Start migrating!
Or let MessageOps do the work for you
If you want to migrate but have no idea where to start (or just can’t be bothered), let us help. We’ve developed a simple and effective method for migrating from Server 2003 to 2012. With it, we’re able to:
- Identify which of your servers are running in 2003
- Pinpoint which applications are running on those servers
- Rank applications based on difficulty of migration, from easiest to hardest
- Determine which application workloads should be migrated to the cloud or an on-site server
- Evaluate the cost of both platforms, compare and determine ROI
- Migrate your applications to Server 2012 based on importance and success factors
We’ll work with you throughout the process to ensure that migration from Server 2003 to 2012 is simple, seamless and successful. Get started now.