Summary
Support for Windows Server 2016 Essentials ends on January 12, 2027.
This is an end-of-support (EOS) milestone for Windows Server 2016 Essentials. After this date, Windows Server 2016 Essentials is no longer supported under the standard product lifecycle, and customers should complete their transition to a supported platform.
Windows Server 2016 Essentials is the last version that includes the full classic Windows Server Essentials experience. This communication explains how the end of support affects that experience, what customers should evaluate, and the actions to take before January 12, 2027.
How this affects me
You are affected if your environment runs Windows Server 2016 Essentials.
Standard security updates and general technical support for Windows Server 2016 Essentials end after January 12, 2027.
Microsoft support for Windows Server 2016 Essentials features, including Remote Web Access and related Essentials-specific functionality, ends on the same date.
Any Windows Server 2016 Essentials capability that continues to function after end of support should be treated as unsupported. Customers should not depend on continued availability, reliability, or support after the end-of-support date.
Impacted services
The following Windows Server 2016 Essentials features and components are supported only through January 12, 2027:
Anywhere Access
Remote Web Access (RWA)
remotewebaccess.com domain and dynamic DNS integration associated with Remote Web Access
What you should do
If you still use Windows Server 2016 Essentials, begin your transition before January 12, 2027.
Plan your migration now. Inventory server roles, applications, users, remote access requirements, client backup dependencies, certificates, DNS dependencies, and integrations that rely on Windows Server 2016 Essentials.
Move to a supported platform. Select a currently supported Windows Server release, a cloud-based alternative, or another supported architecture that meets your workload, security, and operational requirements.
Replace Essentials-specific remote access. Do not plan to use Remote Web Access or remotewebaccess.com as a supported access method after January 12, 2027. Establish and test a supported remote-access approach before the end-of-support date.
Remove dependencies on remotewebaccess.com. If your environment depends on the Microsoft-provided domain or DNS integration, move to a supported domain, DNS, and certificate approach that is appropriate for your environment before migration is complete.
Recreate Essentials-specific management and protection workflows. Identify anything that depends on the Essentials Dashboard, client backup and restore, connector functionality, health monitoring, or related integrations, and validate supported replacement workflows.
Test the cutover before end of support. Validate remote access, identity and permissions, backup and recovery, DNS, certificates, application connectivity, and administrative operations in the target environment.
Consider cloud-based alternatives where appropriate. Assess whether workloads should remain on-premises, move to cloud infrastructure, or be replaced by supported cloud services based on business and technical requirements.
Frequently asked questions (FAQ)
What is happening to Windows Server Essentials?
Windows Server 2016 Essentials is the final standalone release of the Windows Server Essentials product experience. Support ends on January 12, 2027. After that date, it will no longer be supported under the Microsoft product lifecycle.
What happens after January 12, 2027?
Windows Server 2016 Essentials is out of support under the standard lifecycle.
Standard security updates and general technical support end, and Windows Server 2016 Essentials is no longer supported. A server may continue to run, but an unsupported environment carries increasing security, compliance, compatibility, and operational risk.
Customers should migrate before this date rather than rely on continued operation after end of support.
Can I still use Remote Web Access or remotewebaccess.com after January 12, 2027?
Microsoft support for Remote Web Access and remotewebaccess.com as part of Windows Server 2016 Essentials ends on January 12, 2027.
After January 12, 2027, these services will no longer be available as supported Windows Server 2016 Essentials capabilities. Customers should transition all remote access and DNS dependencies before the end-of-support date and should not plan for continued availability of Remote Web Access or remotewebaccess.com after support ends.
Are Extended Security Updates (ESU) available for Windows Server 2016 Essentials?
No. Extended Security Updates (ESU) are not available for Windows Server 2016 Essentials.
Customers running Windows Server 2016 Essentials should complete their migration to a supported platform before support ends on January 12, 2027.
ESU offerings for Windows Server 2016 apply only to Windows Server 2016 Standard and Datacenter editions and do not extend support for Windows Server 2016 Essentials.
I still rely on Windows Server 2016 Essentials features. What should I do now?
Begin migration planning now.
Identify every dependency in your environment, define the supported target state, and complete testing and cutover before January 12, 2027.
Do not wait until the end-of-support date to replace Remote Web Access, remotewebaccess.com dependencies, client backup workflows, or other Essentials-specific functions.
Any environment that remains dependent on Windows Server 2016 Essentials after that date should be treated as unsupported.
What should I consider when selecting a replacement?
Choose the target architecture based on the capabilities your organization uses today.
Evaluate:
Server workloads
Remote access requirements
Identity and access management
Device and client management
Backup and recovery requirements
Application dependencies
Security and compliance requirements
Operational ownership and support models
There is not necessarily a one-for-one replacement for the Windows Server Essentials experience, so validate the complete workflow rather than replacing only the operating system.
Where can I get help planning my migration?
Use current Microsoft lifecycle, Windows Server, and migration documentation, and work through your organization's established Microsoft support channel or qualified technology partner as needed.
Migration guidance should be selected based on your target architecture and workload requirements rather than assuming a single replacement path.