Microsoft

Windows Server 2012 R2 2016 Upgrade Guide

IT administrator reviewing a Windows Server migration plan beside server equipment

A Windows Server 2012 R2 2016 upgrade is not only an operating system installation. It affects directory services, file shares, applications, virtual machines, backup jobs, monitoring, security controls and the licences used by people and devices to access the server. Treating it as a simple version change can leave an important application unsupported or create a licensing gap.

This guide explains how to assess an older Windows Server environment, decide between Windows Server 2022 and Windows Server 2025, and plan Windows Server CALs and Remote Desktop Services CALs. In many organisations, a side-by-side migration to a new server is safer than an in-place upgrade. The correct route depends on the roles installed, the applications in use, the hardware or virtualisation platform and Microsoft’s current support documentation.

Why older Windows Server versions need a migration plan

Windows Server 2012 R2 and Windows Server 2016 may still run essential workloads, but an ageing platform can become difficult to maintain. The risks are not limited to the operating system itself. Hardware warranties may have expired, backup software may no longer support the installed agents, and business applications may require a newer database, web server or authentication component.

A planned migration gives you time to answer practical questions:

  • Which server roles are actually in use?
  • Which applications depend on a particular hostname, IP address, database engine or service account?
  • Are users accessing the server directly, through shared folders, or through Remote Desktop Services?
  • Do the current backup, antivirus, monitoring and remote-management tools support the target version?
  • Which users or devices need Windows Server CALs, and which also need RDS CALs?

Do not assume that every workload should be moved in the same way. A domain controller, file server, application server and Remote Desktop Session Host have different migration risks. Separating them into documented workloads makes testing and rollback more manageable.

Windows Server migration checklist: inventory first

Start with a written inventory rather than beginning the upgrade wizard. Record the server name, IP configuration, installed edition, virtual or physical status, storage layout, processor and memory allocation, and the current backup method. Note whether the machine hosts one role or several unrelated services.

For each workload, record:

  • Identity: domain controller status, DNS, DHCP, directory synchronisation and service accounts.
  • Files: shared folders, NTFS permissions, share permissions, quotas, DFS paths and login scripts.
  • Applications: business software, databases, licensing services, web applications, print services and integrations.
  • Remote access: Remote Desktop Session Host, Remote Desktop Gateway, published applications and administrative access.
  • Operations: scheduled tasks, certificates, firewall rules, monitoring agents, backup agents and antivirus.
  • Dependencies: applications that use fixed server names, database connections, mapped drives, APIs or specific ports.

Interview the people who use the systems. An administrator may know that a file share exists, while an accounts or engineering team knows which scripts, templates or specialist applications depend on it. Look at event logs, installed programs, scheduled tasks, active connections and backup reports, but do not rely on automated discovery alone.

Also check application and hardware compatibility with the target operating system. A migration can fail because of an old driver, an unsupported database version, a hard-coded path or a vendor application that has not been tested on the new platform. Ask each software supplier for its supported Windows Server versions where the workload is business-critical.

Choose Windows Server 2022 or 2025

For many organisations, the target should be a currently supported Windows Server release rather than another short intermediate step. Windows Server 2022 Standard provides a controlled platform for file storage, user access management, application hosting, network services and virtualised environments. It can suit an organisation that wants a stable Windows-based infrastructure foundation and a clear route to hybrid management.

Windows Server 2025 Standard is another option for organisations starting a new server lifecycle. It provides a centrally managed platform for core infrastructure, business applications, file services, identity services and other network-connected workloads. It is designed for essential workloads that need a dedicated server operating system rather than unmanaged endpoints or fragmented consumer systems.

The choice between Windows Server 2022 and an upgrade to Windows Server 2025 should be based on compatibility and lifecycle planning, not only on the newest available version. Consider:

  • Whether your business applications and management tools support the target release.
  • Whether the virtualisation host, backup platform and security products support it.
  • Whether you need to preserve an older application temporarily on a separate server.
  • Whether your team has time to test the newer release before production use.
  • Whether the chosen edition and licensing model match the number of workloads and access requirements.

An in-place upgrade can reduce the amount of reconfiguration, but it preserves old drivers, settings and accumulated problems. A side-by-side migration creates more work initially, yet allows the old server to remain available while the new workload is tested. It also makes it easier to return to the original service if a cutover problem appears.

For an upgrade to Windows Server 2025 or a Windows Server 2022 upgrade, verify the supported upgrade path for the exact installed edition and role combination before making changes. Do not assume that a direct path from every Windows Server 2012 R2 or 2016 installation is supported. If the path is uncertain, build a new target server and migrate the workload instead.

Hands reviewing server inventory and licensing notes

Review Windows Server CALs and RDS CALs

Licensing is often missed because a technical migration can appear successful even when the access licences have not been reviewed. Separate the operating system licence from client access rights and from Remote Desktop access.

A Windows Server CAL covers access to Windows Server services according to the applicable Microsoft licensing terms. The basic planning choice is between a User CAL and a Device CAL:

  • User CAL: one person can access the server from multiple devices.
  • Device CAL: one device can be used by multiple people.

Choose the model that reflects how your organisation works. User CALs may fit employees who use a desktop, laptop and mobile device. Device CALs may fit a shared workstation, reception desk, warehouse terminal or production-floor computer used by several shifts. Count the relevant users or devices and document the assumptions instead of simply copying the old server’s quantity.

Remote Desktop Services has an additional requirement. Every user or device connecting to Windows Server through RDS needs an RDS CAL as well as the standard Windows Server CAL. The same User or Device logic applies: a User RDS CAL covers one person using multiple devices, while a Device RDS CAL covers one device used by multiple people.

For example, an employee connecting to a Remote Desktop Session Host from a laptop needs both a Windows Server CAL and an RDS CAL. A shared terminal used by several employees may be better modelled with a Device CAL and a Device RDS CAL, subject to Microsoft’s licensing terms and the rest of the environment. Administrative connections and other exceptions should be reviewed carefully rather than assumed.

When moving to a new Windows Server version, check that the CALs cover the deployed server version and that any existing licence rights are applicable. The exact licensing position can depend on how the licences were acquired and on Microsoft’s current terms. If the organisation uses RDS, include the licensing server, deployment configuration and licence installation in the test plan.

Situation Usually review Planning question
File shares, identity or application access Windows Server CALs Are users or devices accessing Windows Server services?
One employee uses several devices User CAL Would licensing by person match the working pattern?
Several employees share one workstation Device CAL Would licensing by device match the working pattern?
Remote Desktop Session Host or another RDS connection Windows Server CAL plus RDS CAL Are both access layers covered?
New Windows Server 2025 deployment Windows Server 2025 CAL and, where applicable, Windows Server 2025 RDS CAL Have the correct version, type and quantity been selected?

Build, test and migrate the new server

Prepare the target server with a clean, documented configuration. Apply the required network settings, updates, security baseline, backup agent and monitoring tools. Use a naming and IP strategy that avoids collisions with the old server. Do not decommission the source simply because the target installation has completed.

For a domain-related migration, plan the order of operations carefully. Confirm that directory replication, DNS resolution, time synchronisation and service account permissions work correctly. If the server is also a file or application server, migrate those workloads separately where possible so that a directory change and an application change do not become one difficult troubleshooting event.

Test with representative users and data. A useful test includes:

  1. Signing in with ordinary user accounts and administrative accounts.
  2. Opening, creating, changing and restoring representative files.
  3. Running the business applications and checking database connections.
  4. Testing printers, scheduled tasks, certificates, scripts and integrations.
  5. Connecting through RDS if remote sessions are part of the design.
  6. Checking backup completion and performing a test restore.
  7. Reviewing event logs, monitoring alerts and security product status.

Document the cutover procedure before the maintenance window. Include the final backup, data synchronisation, DNS or alias changes, application service changes, user communication and validation checks. Define a rollback point and the conditions that trigger it. A rollback plan is only useful if the old service remains intact and its data has not been changed in a way that cannot be reconciled.

Retire Windows Server 2012 R2 or 2016 safely

After cutover, keep the old server available for the agreed verification period. Watch for users who still connect through an old mapped drive, application shortcut, scheduled task or hard-coded hostname. Check backup reports and monitoring dashboards for several cycles, because some failures appear only during a weekly task or month-end process.

Before retirement, confirm that the server no longer provides an active role, relay, certificate, licence service, database, shared folder or authentication function. Remove obsolete DNS records and monitoring entries only after confirming their purpose. Preserve the migration record, configuration exports, backup information and licence documentation according to your organisation’s retention practices.

Do not erase the old installation until the new environment has passed business validation and the rollback decision has expired. When the server is finally removed, update diagrams, asset records, administrator documentation and emergency procedures. A migration is complete when the organisation can operate and recover the service, not merely when the new operating system starts.

Frequently asked questions

Should I perform an in-place Windows Server 2012 R2 2016 upgrade?

It may be possible for a particular installation, but the supported path depends on the edition, installed roles and Microsoft requirements. A side-by-side migration is often easier to test and roll back, especially when the old server hosts several workloads.

Can I upgrade directly to Windows Server 2025?

Do not assume that a direct upgrade from Windows Server 2012 R2 or 2016 is supported. Verify the exact path for your installation. If there is any uncertainty, deploy a new Windows Server 2025 target and migrate the roles and data.

Do I need Windows Server CALs after the migration?

Plan for CAL coverage when users or devices access Windows Server services. Choose User CALs for people using multiple devices or Device CALs for shared equipment, then confirm the version and terms that apply to your deployment.

Are RDS CALs included in Windows Server CALs?

No. An RDS connection requires an RDS CAL in addition to the standard Windows Server CAL. Review both the user or device type and the quantity required.

Where can I get Windows Server licences and CALs?

Genuine Windows Server licences, Windows Server 2025 CALs and Windows Server 2025 RDS CALs are available from KEYFORREST with instant electronic delivery. Check the current product page and confirm the edition, CAL type and quantity before ordering.

author-avatar

About Marios Chaidousis

Marios Chaidousis is a software and licensing specialist covering Autodesk (AutoCAD, Revit, Inventor), Microsoft (Office, Microsoft 365, Windows, Windows Server, SQL Server), Adobe and security software. He helps engineers, professionals and businesses choose the right licence and get the most out of their software.LinkedIn · Facebook · Instagram