Windows 2012 (R2) End of Support

Windows has announced the sunset of Windows 2012 and Windows 2012 R2. The End of Maintenance/Support for both is October 10, 2023 although, security updates will continue through October 10, 2024. As the Expedient End of Support/Service Life (EOSL) date approaches for this software, we want to ensure you clearly understand your options and the potential outcomes associated with each choice. Once the October 10, 2024 date arrives, Expedient will lose the ability to patch the systems, and we expect no new updates from the vendor. We will make every effort to assist, but please note that we will have limited recourse for software updates, potentially exposing your system to security risks, or for software break/fix.

Due to Windows 2012 (R2) no longer being viable code lines, a new OS will need to be selected and migrated to. Expedient currently supports Windows 2016 and above.

Windows Server 2016

Windows Server 2019

Windows Server 2022

The options and steps to take are below:

Option 1: Continue Operating on the Current Version and Accept the Risk

Implication: You may continue using the current software version by choosing this option, however, knowing that the vendor will no longer provide updates to address bugs and security risks is essential. Expedient will offer best-effort support, but our capabilities may be limited.

Our Commitment: We will support you to the best of our ability under these circumstances, prioritizing your system's stability and functionality. However, we cannot support you beyond our best efforts.

Option 2 (Preferred): Work with Your Expedient Support Team to Request Resources for a Migration

Implication: This option is often preferred from a business perspective as it allows us to set up your applications on a new server/VM. This approach ensures compatibility and will enable you to validate that the latest OS version won't disrupt your existing applications.

Steps:

1. Work with your Account Executive to request additional cloud resources and licensing. This would require a PCR.
2. Service Delivery would add the resources and deploy the VM.
3. The client would install their applications and move their data.
4. Once the migration is complete, an additional PCR to remove the added resources would be required to remove and decommission the old server.

Our Commitment: We will collaborate closely with you to plan and execute a seamless migration, minimizing disruptions to your operations.