Once you choose what you have and where you'd like to go, the tool responds with tips to smooth that migration. It offers quite a bit in terms of category and workload options that you need to migrate and helps you work through the needs for each. I recommend you try the free online tool Windows Server 2003 Migration Planning Assistant.
If you use a System Center Configuration Manager (SCCM), you can pull inventory reports from there as well. If you're worried about application compatibility in the leap from Windows Server 2003 to Windows Server 2012 R2, don't be it's nothing as major as the application leap on the desktop from Windows XP to Windows 7 or 8.įor assistance in the discovery phase - to catalog applications and app dependencies - consider using the Microsoft Assessment and Planning Toolkit (MAP), an agentless tool for inventorying and assessing desktop, server, and cloud migrations. Inventory your existing environment first, consider hardware upgrades if needed, review software that may not run on a newer version, then actually migrate. Microsoft has four sets of tools to aid the migration process: Discover, Assess, Target, and Migrate. Doing so will put you uncomfortably close to its end-of-support period, which will come sooner than you realize, and dump you in the upgrade cycle yet again. I don’t recommend moving to an earlier version of Windows Server such as Windows Server 2008. Moving from Windows Server 2003 to Windows Server 2012 R2 is an incredible upgrade in terms of Hyper-V virtualization features, security improvements, Remote Desktop Services (an improvement over Terminal Services), Server Core, IPv6, and PowerShell management. For most organizations, upgrading Windows Server within their data centers is the cheaper choice.īecause Windows Server 2016 isn't shipping yet, you're probably looking at a move to 2013's Windows Server 2012 R2. It's time to either make the move to a new version of Windows Server on-premises or to move to the cloud.
And a dozen years of support is generous. All software (whether paid or free) needs to be updated at times. You've had 12 years of updates and patches, so the old "it's not fair for me to have to pay for a new server OS" argument is getting tired at this point. In fact, many seem to have decided to remain on Windows Server 2003 sans security and maintenance support.
That means you should have already started, if not finished, your migration to a more current version of Windows Server.īut many businesses haven't done anything to move from Windows Server 2003. Mainstream support ended in July 2010, so the writing's been on the wall a long time. After July 14, Microsoft will no longer issue security updates for any version of Windows Server 2003.
0 kommentar(er)
