R 061300Z JUL 22
MARADMIN 340/22
MSGID/GENADMIN/CMC DC I WASHINGTON DC//
SUBJ/MARINE CORPS MICROSOFT WINDOWS 11 MIGRATION//
REF/A/DOC/20220608//
REF/B/DOC/MCO 5230.21, 20121003//
REF/C/DOC/HTTPS:(SLASH)(SLASH)USMC.SHAREPOINT-MIL.US/SITES/MCSC_MCSES/SITEPAGES/EUS.ASPX//
REF/D/DOC/HTTPS:(SLASH)(SLASH)WWW.MICROSOFT.COM/EN-US/WINDOWS/WINDOWS-11-SPECIFICATIONS?R=1//
NARR/REF A IS DEPARTMENT OF DEFENSE (DOD) CHIEF INFORMATION OFFICER (CIO) MICROSOFT WINDOWS 11 (WIN11) MIGRATION ACTION MEMO WHICH MANDATES MIGRATION TO WIN11 NLT 14 OCT 2025. REF B IS MARINE CORPS ORDER 5230.21 WHICH ESTABLISHES IT PORTFOLIO MANAGER ROLES AND RESPONSIBILITIES FOR MARINE CORPS FUNCTIONAL AREA MANAGERS (FAMS). REF C IS THE MARCORSYSCOM/PROGRAM EXECUTIVE OFFICE (PEO), DIGITAL, END USER SERVICES (EUS) PUBLIC-FACING SHAREPOINT SITE AND DOCUMENT REPOSITORY FOR END USER DEVICES (EUD). REF D IS THE MICROSOFT WEBSITE FOR WINDOWS 11 COMPLIANT EUD SPECIFICATIONS.//
POC/HENRY COSTA/CIV/DC I IC4 ICN/TEL: (571)256-9081/EMAIL: HENRY.COSTA@USMC.MIL//
POC/TREVOR DANIEL/CIV/DC I IC4 ICN/TEL: (571)256-9082/EMAIL: TREVOR.DANIEL@USMC.MIL//
POC/JULIUS PFEIFLE/CIV/DC I IC4 ICC CIO/TEL: (571)256-9094/EMAIL: JULIUS.PFEIFLE@USMC.MIL//
POC/RODDY STATEN/CIV/DC I IC4 ICC CY/TEL: (571)256-8875/NIPR EMAIL: RODDY.STATEN@USMC.MIL/SIPR EMAIL: RODDY.STATEN@USMC.SMIL.MIL//
POC/DIANE CLARKE/CIV/DC I IC4 ICC CY/TEL: (571)256-8867/NIPR EMAIL: DIANE.CLARKE@USMC.MIL/SIPR EMAIL: DIANE.CLARKE@USMC.SMIL.MIL//
POC/CHRISTOPHER JAMISON/LTCOL/ MARFORCYBER G-36/TEL: (667)812-6443/EMAIL: CJJAMI2@RADIUM.NCSC.MIL//
POC/TORWON MITCHELL/CIV/EUS PDM/PEO DES PFM MCSES/TEL: (703)432-7917/EMAIL: TORWON.MITCHELL@USMC.MIL//
GENTEXT/REMARKS/1. Situation. The purpose of this MARADMIN is to inform the Fleet Marine Force (FMF) and Supporting Establishment (SE) of the migration to Microsoft Win11 Operating System (OS).
2. Mission. In accordance with reference a, DOD CIO directs all service components to plan, resource, and execute the migration from Microsoft Windows 10 to Windows 11 in advance of Windows 10 end-of-support (EOS) date 14 Oct 2025.
2.A. Migrating to Win11 will require compliant hardware replacement actions and software configuration changes.
2.A.1. Hardware Replacement Actions.
2.a.1.1. All Win11 non-compliant EUD must be replaced with Win11 compliant EUD prior to EOS date.
2.A.1.2. There are approximately 118k Win11 non-compliant EUD in the enterprise inventory. In order to meet ref a mandates, EUS plans to procure approximately 118k enterprise EUD across fiscal year (FY) 22, FY23, and FY24. Procurement in FY25 will not meet the deadline for migration.
2.A.1.3. Program of Record (POR) and unit/command procured and contractor furnished EUD must be assessed for Win11 compliance as defined in reference d to include processor compatibility.
2.A.1.4. Win11 non-compliant enterprise-managed EUD include Dell Latitude e5470, Dell Latitude 5480, and the HP Pro Book 650 G3. These EUD are no longer authorized for use on the Marine Corps Enterprise Network (MCEN) NIPR or SIPR after 16 Jun 2025.
2.A.2. Software Configuration Changes.
2.a.2.1. The Marine Corps Enterprise Desktop Standardization (MCEDS) image has typically been derived from the Defense Information Systems Agency (DISA) Secure Host Baseline (SHB) framework toolset. DISA will no longer develop the SHB after FY22. In FY23, the MCEDS image will be developed directly from the Microsoft Operating System image and will include DOD and USMC security configurations.
2.A.2.2. The MCEDS image is the only image authorized for use on the MCEN unless otherwise documented in an Authority to Operate (ATO) granted by the Marine Corps Authorizing Official (AO).
3. Execution. All Win11 compliant Marine Corps EUD will be migrated NLT 16 Jun 2025.
3.A. The enterprise Win11 migration will be executed in a two-pronged approach, through fielding of Win11 imaged and compliant enterprise EUD from Enterprise Staging and Delivery (ESD) in Norfolk, VA, and through the electronic delivery of the Win11 MCEDS upgrade via Microsoft Endpoint Configuration Manager (MECM), formerly System Center Configuration Manager (SCCM).
3.A.1. EUD procurement referenced in para 2.a.1.2. Is only applicable to enterprise technical refresh, and does not apply to POR and unit/command procured, or contract furnished EUD.
3.A.2. For Non-MCEN EUD including POR, Win11 MCEDS image will be made available via the Definitive Media Library (DML). There will also be a Win11 MCEDS “Lite” image for use.
3.B.1. Hardware.
3.b.1.1. PEO-Digital will procure and field the below quantities of EUD to FMF and SE units between Jul 2022 and August 2024 (read in two columns):
UNIT
I MEF 25595
II MEF 21574
III MEF 18531
MARFORCENT 773
MARFORCOM 1153
MARFORCYBER 871
MARFOREUR/AF 550
MARFORPAC 347
MARFORRES 10929
MARFORSOC 0
MARFORSOUTH 135
MARFORSPACE 0
MICOM 23983
MCRC 4042
TECOM 5244
Totals 113727
3.B.1.2. All required Win11 compliant EUD will be procured by FY24 and shipped to Fleet and SE by Aug 2024.
3.B.1.3. FMF and SE units will receive additional EUD in excess of numbers listed in para 3.b.1.1. As part of tech-refresh.
3.B.1.4. Beginning Feb 2023, EUD shipped from ESD with be shipped with MCEDS Win11 image loaded.
3.B.1.5. Normal ESD monthly EUD shipping is limited to 5k EUD. In order to support the surge of EUD shipments in FY23 and FY24, ESD will increase its monthly shipment to 10k EUD.
3.B.1.6. Deployment of Win11 compliant EUD to the MCEN is the responsibility of the receiving unit. Receiving units will ensure replacement of Win11 non-compliant EUD models (Dell Latitude e5470, Dell Latitude 5480, and the HP Pro Book 650 g3) prior to replacement of any other models.
3.B.1.7. Fielding conferences will occur to identify the rate of fielding for receiving commands.
3.B.2. Software.
3.B.2.1. EUS will initiate a Win11 MCEDS pilot running from Jul 2022 through Feb 2023.
3.B.2.2. Upon completion of the pilot, the Win11 MCEDS image will then be applied to all existing Win11 compliant EUD, from Feb through May 2023.
3.C. All Project Support Task Order (PSTO) support for Win11 deployment will be funded at the unit level.
4. Tasks.
4.A. DC I IC4.
4.A.1. Coordinate the service-wide migration to the windows 11 operating system with Functional Area Managers (FAMS) and other key stakeholders to ensure all systems and applications are compatible with Windows 11.
4.A.2. Provide Win11 compatibility check benchmark results to DOD CIO for non-connected systems.
4.B. MARCORSYSCOM/PEO Digital.
4.B.1. Provide engineering and acquisition support to implement this directive by ensuring all EUD procurements meet Win11 compliance requirements and by providing the Win11 MCEDS image.
4.B.2. Provide Win11 Migration Plan Of Action and Milestones (POAM) to DC I IC4 NLT 25 July 2022.
4.C. MARFORCYBERCOM.
4.C.1. Provide operational support to implement this directive on the MCEN NIPR or MCEN SIPR.
4.C.2. Be prepared to begin the migration of EUD to the Win11 MCEDS image on the MCEN by Jul 2022.
4.C.3. Execute DOD-required Windows 11 endpoint migration/compatibility reporting using scorecard benchmark (https:(slash)(slash)patches.csd.disa.mil) per ref a. The scorecard benchmark is a DISA-developed script to be deployed via the DOD endpoint security solution/epolicy orchestrator that captures the endpoint Windows 11 compatibility data. This data is reported monthly to the DOD CIO, via the Continuous Monitoring and Risk Scoring (CMRS) system, in support of the DOD cybersecurity scorecard.
4.D. MARFORS AND MCICOM.
4.D.1. Be prepared to coordinate the migration of EUD under your organizational control to the Win11 MCEDS image commencing in Feb 2023 and deploy procured win11 compliant EUD to the MCEN NLT 16 Jun 2025.
4.E. POR. All PORS will assess supportability of migration to the Win11 OS and Win11 compliant EUD.
4.E.1. All POR EUD running the Microsoft Windows Operating System must be reported, whether connected or non-connected, as follows,
4.E.2. All POR EUD connected to the MCEN running the Microsoft Windows Operating System must have the Windows endpoint compatibility check benchmark installed in order to report status to the CMRS website per DOD CIO requirements.
4.E.2.1. Asset Owners/Managers for EUD that are unable to communicate using Windows Endpoint Compatibility Check Benchmark must follow the non-connected reporting process.
4.E.3. All POR EUD not connected to the MCEN but running the Microsoft Windows Operating System must be reported.
4.E.3.1. Unclassified report data will be submitted in a Microsoft Excel spreadsheet file (fill in EUD quantities per Operating System category listed) as an attachment via encrypted NIPR email to DC I IC4 ICC CY POCS listed above.
4.E.3.2. Classified report data will be submitted in a Microsoft Excel spreadsheet file (fill in EUD quantities per Operating System category listed) as an attachment via SIPR email to the same DC I IC4 ICC CY POCS listed above.
4.E.3.3. Monthly reporting of POR status to DC I IC4 ICC CY POC.
4.E.3.3.1. The first POR status report is due 180 calendar days upon release of this MARADMIN.
4.E.3.3.2. Program Managers (PM) must submit a Win11 migration POAM to DC I IC4 ICN POC NLT 07 Nov 2022, detailing how their POR will achieve compliance targets.
4.F. FAMS.
4.F.1. In coordination with system/application managers and end users, complete portfolio review and testing to determine each systems and applications ability to operate on the Win11 OS.
4.F.2. For systems/applications unable to operate on the Win11 OS, FAMS will work with appropriate stakeholders to develop POAMS for system/application migration or disposition.
5. Administration and Logistics. Refer questions to the points of contact listed above.
6. Command and Signal. Release authorized by LtGen M. G. Glavy, Headquarters Marine Corps, Deputy Commandant for Information.//