4 Steps to Windows Server 2003 Migration Planning

4 Steps to Windows Server 2003 Migration Planning

No matter how hard you try, no matter how many times you say it, and no matter how many warning signs or clear direction given, some people will still ignore everything. A lot of people seem to just simply say “that’s not meant for me” or “that’s stupid, because it’s so inconvenient” or “I’m in a hurry, so the rules don’t apply.”

Let me give you a good example. At our kids’ school, there are clear signs to show one way driveways, how to properly drop kids off in the mornings, and even outline specific areas not meant for non-school vehicles to ever exist. Yet, day after day, the exact same parents ignore the clearly posted rules. They drive the wrong way down one way driveways, create traffic jams because they can’t be bothered follow rules, and slip past “Do Not Enter” signs with smug smiles. If you’re someone who does this…stop it! The signs and directions are meant to keep the kids safe.

Similarly, Windows Server 2003 reaches final, full end of life on July 14, 2015. There have been many notices issued, articles strewn across the Internet, and clear statements made that once July 2015 hits, there will be no additional security patches provided by Microsoft. This means you should start planning now to migrate apps and services to something else, something newer. The signs, warnings, and directions are meant to keep your company safe.

I sometimes wonder if it’s the method of notification that’s the problem. Just like I prefer email and Twitter over telephone and Facebook, maybe a different medium is preferred, or an alternate vehicle will be more widely accepted.

So, here’s another medium. Microsoft has put together a video outlining a 4-step process for migration planning. Maybe this one will hit home.


Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.