A guide to migrating off Windows Server 2008

A guide to migrating off Windows Server 2008

On January 14, Microsoft formally ended assist for Windows Server 2008 and 2008 R2. That means no extra fixes or patches even when vulnerabilities are discovered, though there have been exceptions previously with actually extreme points.

That means it’s time to migrate your apps, industrial and customized, and the method received’t be trivial. Server 2008 comes from a time when CPUs had two to 4 cores, the place 64-bit computing was nonetheless very early, and the cloud was just about nonetheless a dream.

Suffice it to say that taking a single-tenant, single-thread app and bringing it to the cloud received’t be trivial, and in some circumstances, neither possible and even attainable. Nonetheless, it’s attainable emigrate to Windows Server 2019, the newest model of the OS, or Server 2016 as Microsoft nonetheless gives it, and Microsoft has performed its finest to make the transition clean.

Analyst Tim Crawford of analysis and advisory agency AVOA informed me for my Network World weblog that there have been two kinds of Server 2008 holdouts: both a) their customized apps use capabilities particular to WS2008, or b) those who use a model of an utility that’s solely suitable with WS2008.

And Dave Kawula, an unbiased guide specializing in Windows Server and Microsoft MVP, backs that up, saying he sees quite a lot of very outdated code. “You like to think everyone is on the latest from Microsoft but that’s not the case. Most of the organizations I encounter are four to six years behind where Microsoft is at,” he stated.

Related: Not lifeless but: Windows Server 2008 customers have choices

The lengthy street

If you select emigrate the app from Server 2008 to 2016/2019, which will get very difficult. Even Microsoft stated you’ll have to take the intermediate step of migrating the app and its information to Server 2012 as an interim step as a result of 2016/2019 have migration instruments and steps from a 2012 server however not 2008.

Microsoft stated a typical migration course of includes spinning up a brand new digital machine (VM) with Windows Server 2016/2019, migrating the outdated app to the brand new VM and testing it for compatibility. Microsoft stated its groups have labored to make sure that the compatibility of server roles and options in older working methods will work in all newer variations, so it doesn’t consider there might be vital points.

Kawula calls this a double hop migration, the place you migrate an app to 2012 to do patches there, then carry out a second improve, however not on the identical {hardware}. “You run it on Hyper-V or VMware. Once that thing is virtualized we have a lot more options with it,” he stated.

Server 2008 had the primary actual try at Hyper-V virtualization and Kawula describes it as “very painless. They’ve done a very good job with the tech they have between the old and new virtualization systems.”

Windows Server 2008 was based mostly on the Vista code base, whereas 2016/2019 are based mostly on the Windows 10 codebase. But the true ache was migrating from Server 2003 to 2008 as a result of Server 2003 was based mostly on Windows XP and the step between XP and Vista person mode and kernel mode adjustments had been far more drastic, based on Philip Elder, co-owner of MPECS, a consultancy that makes a speciality of excessive availability options and Microsoft MVP.

Related: 5 causes for containerizing your legacy Windows Server purposes

“When we take into account the changes from Vista to Windows 7, Windows 8 and Windows 10, the changes have been iterative so the base structure for good coding was in place in Vista then carried forward in each new edition,” he stated.

Microsoft stated Server 2008 prospects ought to be mindful the next pointers for the on-premises servers requiring set up of Windows Server 2012 R2:

In-place upgrades ought to stay in the identical construct sort (e.g. 32-bit to 32-bit or 64-bit to 64-bit architectures).
Users can swap upgraded server core installations to Server with Full Desktop on Windows Server 2012 R2 solely. Windows Server 2016 and later don’t assist switching from server core to Full Desktop, so we suggest making that swap earlier than upgrading to Windows Server 2016.
In-place upgrades are solely supported in the identical language.

The hardest kinds of Windows Server utility emigrate are 32-bit purposes with a 32-bit kernel mode driver, based on Microsoft. Windows/Windows Server 32-bit variations requires 32-bit drivers and Windows/Windows Server 64-bit variations requires 64-bit drivers. You can not combine and match 32-bit drivers with 64-bit working methods and vice versa.

Furthermore, beginning with Windows Server 2008 R2 and later, Windows Server has been 64-bit solely. Thus, when you’ve got a legacy 32-bit app that with a 32-bit kernel mode driver, you’ll must a 64-bit model. However, what if the legacy 32-bit app doesn’t require a 32-bit driver? Then, it’ll doubtless “just work.”

Cloudy skies forward

Many firms wish to transfer as many workloads to the cloud whereas holding some purposes and information on-premises. The standards for what stays on-prem is often based mostly on information sensitivity but in addition use. A heavily-used utility may find yourself costing extra to run within the cloud as a result of metering.

Microsoft stated cloud migration is in the beginning an organizational change administration train – be it folks (roles/tasks), course of (utility growth and operational workflows), or expertise (utilizing cloud-based instruments and capabilities).  So earlier than you begin on the apps there must be a technique with a transparent imaginative and prescient and govt assist.

Microsoft advises prospects to prioritize workloads based mostly on enterprise danger and technical complexity – some prospects select to begin with the simplest whereas others decide essentially the most difficult. An organization ought to set up a cloud migration heart of excellence to create a cross-functional crew of IT infrastructure & operations, database directors, architects, safety/compliance, networking, storage, utility growth, and line-of-business teams to set governance requirements, automation insurance policies and workload precedence, amongst different issues.

Related: Microsoft lures Windows 2008 customers to cloud with provide of additional assist

Companies ought to execute cloud migrations in waves.  Microsoft recommends an iterative, wave-oriented strategy to deeper technical assessments and migration. This does suggest taking a conservative strategy throughout the preliminary migration waves, however as utility homeowners get their bearings with cloud migrations, they get higher on the course of and might typically speed up the method.

One of the issues with app migration is id, stated Kawula. Are you going to have the ability to handle on-premises identities within the cloud? He maintains that 99% of the time if it really works in your information heart, it’ll run within the cloud. If not there may be all the time the choice of working the app in a VM however not make it cloud-aware.

But Elder is a bit more cautious, noting Microsoft’s messaging has modified from all within the cloud to hybrid. “The realization on Microsoft’s side is there is just too many apps that will not work in a cloud setting. So they need to give folks time to figure out how to get that into the cloud. I believe hybrid is the best way forward for many organizations,” he stated.

Didier Van Hoye, a technical architect and expertise strategist in addition to MVP stated IT outlets have the choice of shifting Server 2008 apps to Server 2019 in Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) or containerized choices, however a migration is critical to completely make the most of the cloud.

“You can lift and shift that into the cloud, but that is not making the best use of the capabilities of the cloud,” he stated. “Elasticity has to be designed into the app, and it will be VMs, not containers [that do it].Then you can modernize the app to run on more modern OS versions, but it is still in a VM. benefit they might get is that they can adjust memory, CPU, storage easier and faster than they are used, but that depends on how well their virtualization on-premises was or if that was still hardware.”

Tricky navigation forward

While the consensus is that many if not most elderly apps ought to make a comparatively clean translation to the cloud, there are some areas that may journey folks up.

In Kawula’s expertise, he finds homegrown Oracle apps are notably difficult emigrate. “They are written using PowerBuilder and organizations are trying to modernize it with .Net, and that makes it difficult. PowerBuilder is still out there. That’s one of the issues everyone has,” he stated.

Elder additionally stated older databases and their apps will be difficult since they might want Active Directory person IDs for inner access permissions. He added {that a} .Net app requires a selected model of the .Net framework, and every time there’s a new model of .Net the app must be examined in opposition to that model. So in these circumstances, firms are restricted to the .Net model an app vendor has accepted.

Another problem each be aware is trying to containerize apps. Containers are merely scaled down variations of the working system and whereas Server 2019 was designed with containers in thoughts, apps coded for Windows Server 2008 undoubtedly weren’t.

“It’s physically impossible to take Server 2008 code and make it containerized. Trying to stuff it into a 300MB OS is just not going to happen,” stated Elder.

“You have got to rewrite the app for deployment in containers,” stated Kawula. “The way containers function is like mini webservers that are disposable. If an app is written so it can be deployed and not manually installed, then it will play a lot nicer with containers. So with mini-rewrites, you should be able to get there. Again, it depends on the app.”

Van Hoye stated outdated apps are also problematic due to information persistence in them. Data persistence is utilized in stateful apps, which saves information about every consumer session and makes use of that information the following time the consumer makes a request. Containers are stateless and don’t save information.

“Apps that are stateless are better candidates in general vs. stateful apps with a GUI and hardware dependencies,” he stated. “I’m not saying it cannot be done but it becomes more involved and might not cover everything. The app might need refactoring/re-architecting.”

Microsoft gives a comparability of the hybrid, safety, infrastructure and utility platform options of Windows Server 2019 to earlier variations right here. It additionally gives a desk of server purposes that assist Window Server 2016 and one which covers Windows Server 2019.

It’s by no means too late to get began on a migration, particularly since Server 2012 will attain its finish of life on Oct. 10, 2023.

Spread the love