cloudek. Request a service session

CLOUDEK · WINDOWS SERVER 2016

Windows Server 2016 end-of-support hub

Microsoft’s lifecycle information places Windows Server 2016 extended support in January 2027. Use this hub to find the guide for each server role, build a review order, and check the official lifecycle sources before scheduling work.

Sources checked: 13 November 2026.

The date, and a source discrepancy to verify

Microsoft’s Windows Server 2016 lifecycle page shows an Extended End Date of 1/13/2027 6:59:59 AM PT and notes that its dates are displayed in Pacific Time. Microsoft’s Windows Server release information lists the extended support end date as 2027-01-12. These Microsoft pages do not show the same calendar date and timestamp. Confirm the applicable lifecycle entry with Microsoft before setting a change deadline; this hub does not resolve the discrepancy.

The lifecycle product page lists Windows Server 2016 Datacenter, Essentials, MultiPoint Premium and Standard, and says Windows Server 2016 containers follow the same lifecycle. The release-information table lists Datacenter, Essentials and Standard for version 1607. Both sources were checked on 13 November 2026.

Microsoft’s lifecycle definitions say that, for Fixed Policy products, end of support is the end of Extended Support, when support and servicing are no longer available. Review the applicable Microsoft documentation and your own support requirements; this page does not assess a server or tenant.

Windows Server 2016 role-by-role migration checklist

Use each guide to review the role-specific path, validation steps, dependencies and rollback considerations. A guide is a planning aid, not an environment assessment.

RoleWhat to checkGuide
Domain controllerReview the directory migration sequence, health checks and rollback points.Domain controller migration guide
Active Directory Certificate ServicesReview CA backup, key handling, restore and certificate publishing checks.AD CS migration guide
Active Directory Federation ServicesReview farm topology, relying parties, certificates and validation steps.AD FS migration guide
DHCP, DNS and NPSReview configuration export, dependencies, destination checks and rollback.DHCP, DNS and NPS guide
Hyper-V host or clusterReview cluster version path, workload compatibility, maintenance and recovery.Hyper-V upgrade guide
Remote Desktop Services / RD GatewayReview deployment roles, upgrade sequence, certificates and user access tests.RDS and RD Gateway guide
WSUSReview database and content handling, client redirection and a test group.WSUS migration guide
File serverReview shares, permissions, data consistency, client paths and rollback.File server migration guide
Print serverReview queues, drivers, ports, access controls and pilot printing.Print server migration guide
Exchange on Windows Server 2016Review Exchange support and migration separately from the operating system lifecycle.Exchange and Windows Server guide

What to do, and in what order

  1. Inventory. Record versions, roles, workload owners, dependencies, support constraints and recovery requirements. Start with the server inventory analyzer.
  2. Resolve the applicable lifecycle date. Check Microsoft’s current lifecycle record for each edition and product; keep the date discrepancy above in view.
  3. Map dependencies and choose a path per role. Use the role guides and the Windows Server migration plan builder to organize review. Confirm every path against current Microsoft guidance and workload requirements.
  4. Plan verification and recovery. Assign owners for backups, test environment, rollback, monitoring and user acceptance before approving a change window.
  5. Sequence the work and review updates. Use the Patch Tuesday calendar to support update planning, and revisit the plan when dependencies or support information changes.

Guides and planning tools

Official sources