Marine Corps Microsoft Windows 11 Adoption and Reporting Requirements

1.  Purpose.  The purpose of this message is to outline the actions required to ensure successful migration to Windows 11 (WIN11) and the expeditious decommissioning and disposal of legacy end user devices (EUD).
2.  Situation.  Per ref (a), the Marine Corps must transition to WIN11 NLT 14 Oct 2025.  The WIN 11 OS provides key improvements in cybersecurity with built-in hardware isolation, advanced encryption and data protection, improved network and system security and other safeguards against evolving cybersecurity threats, all of which contribute to increased readiness of the force.  The USMC will accomplish this task via a WIN11 Operating System (OS) on line update to network connected WIN11 Compliant EUDs.  All EUDs that cannot support WIN11 OS are identified in ref (d).  These EUDs will be replaced via tech refresh of hardware procured by Marine Corps Systems Command (MCSC) and Program Executive Office (PEO)-Digital.  Approximately 118,000 EUDs (of a total of 176,000 devices) are non-WIN 11 compliant and must be replaced.  WIN11 migration applies to all providers delivering EUDs e.g., Aviation, Logistics, Intel and all Command and Control (C2) and other Program of Record (POR) systems.  Commanders and service owners are responsible as defined below.
3. Mission.  In accordance with ref (A), DoD CIO directs all service components to plan, resource, and execute the migration from Microsoft WIN10 to WIN11 in advance of WIN10 End-Of-Support (EOS) date 14 Oct 2025.
4. Execution.
4.A.  Commander's Intent
4.A.1.  Over the past several months, significant efforts have been made to organize an efficient transition to the WIN 11 OS with the required technical refresh of EUDs.  Across the enterprise, we have planned correctly, we have programmed correctly, and we budgeted correctly.  Now we are in execution.
4.A.2.  Effective execution will require Commanders to take custody of their allotted replacement EUDs once delivered to their issue points and ensure compliance with ref (D) in a timely manner.
4.B.  Tasks
4.B.1.  MARFORCYBER
4.B.1.A.  Execute operational command and control of USMC WIN11 migration in coordination with DCI and PEO Digital.
4.B.1.B.  As of 14 Oct 2025, be prepared to isolate MCEN non-transitioned EUDs, to include POR EUDs, for which no approved Plan of Action and Milestones (POA&M) have been submitted.
4.B.2.  Commanders
4.B.2.A.  Commanders should refer to the WIN 11 Migration Dashboard for the status of deliveries of tech refresh WIN 11 compliant EUDs destined for their commands.  The WIN 11 Dashboard can be found at the following Sharepoint link:  https:(slash)(slash)app.mil.powerbigov.us/groups/me/reports/040967fb-7fc2-4d67-aa8-7e9d9b6f16a2/ReportSection30f3524a87c7f509e611
4.B.2.B.  Based on published fielding plans commanders will coordinate with MARFORCYBER for those EUDs not meeting the 14 Oct 2025 date.  Acceptable responses will include identification of Long-Term Servicing Channel (LTSC) option for POR EUDs.
4.B.3.  DCI IC4
4.B.3.A.  Maintain metrics on WIN11 transition progress and report to leadership as required.
4.B.4.  MCSC / PEO Digital / PEO for Manpower, Logistics and Business Solutions (MLB) / PEO Land Systems.
4.B.4.A.  Publish Fielding Plans (FP) by phase and TAMCN ensuring distribution to receiving units prior to shipping.
4.B.4.B.  Ensure EUDs are properly accounted for in GCSS-MC and marked with WIN11 compliance to include primary end items or components of systems in accordance with the published MI per ref (D).
4.B.4.C. Optimize automated reporting capabilities to provide commanders WIN11 migration situational awareness and feedback opportunity to the service for coordination and rapid adjustments.
4.B.4.D.  Ensure all POR EUDs connected to the MCEN running the Microsoft Windows OS have the Windows endpoint compatibility check benchmark installed IOT report status to the Continuous Monitoring and Risk Scoring (CMRS) website per DoD CIO requirements.
4.B.5.  DC CD&I
4.B.5.A.  Support reconciliation of AAO(s) within Total Force Structure Management System (TFSMS) with commanders and validate and oversee MCSC shipment plans in support of commander's AAO(s).
5.  Administration and Logistics.  Refer questions to the point of contacts (POCs) listed above.
6.  Command and Signal.
6.A.  Reporting shall commence upon release of this message.  Stakeholders and organizational units should refer to the following URL.
https:(slash)(slash)app.mil.powerbigov.us/groups/bd9d37f72b51-4923-b799-bae98b92bc0a/reports/040967fb-7fc2-4d67-aa8-7e9d9b6f16a2/ReportSectionf3c80fcd0e5d900c47be
7.  Release authorized by LtGen M. G. Glavy, Headquarters Marine Corps, Deputy Commandant for Information.