R 301603Z JUN 17
MARADMIN 343/17
MSGID/GENADMIN/CMC WASHINGTON DC DMCS//
SUBJ/WINDOWS 10 MIGRATION INITIATING DIRECTIVE//
REF/A/LTR/DOD CIO/20NOV15//
REF/B/DOC/ACMC/JUN17//
REF/C/DOC/DOD/10FEB14//
REF/D/DOC/MCSC/30JUN17//
NARR/REF A IS THE DEPARTMENT OF DEFENSE (DOD) CHIEF INFORMATION OFFICER (CIO) MEMORANDUM, SUBJ: MIGRATION TO MICROSOFT WINDOWS 10 SECURE HOST BASELINE. REF B IS THE UNITED STATES MARINE CORPS APPROVED WINDOWS 10 SHB DEPLOYMENT PLAN. REF C IS DOD MANUAL (DODM) 4140.01, SUBJ: DOD SUPPLY CHAIN MATERIEL MANAGEMENT PROCEDURES. REF D IS THE FIELDING PLAN FOR THE MARINE CORPS ENTERPRISE DESKTOP STANDARD (MCEDS) WINDOWS 10 (WIN10) SECURE HOST BASELINE (SHB).//
POC/J.F. THOMAS/CAPT/HQMC C4 CP/TEL: 571-256-9078/EMAIL: JEREMY.F.THOMAS1@USMC.MIL//
GENTEXT/REMARKS/1.  Purpose.  This MARADMIN is the initiating directive providing policy, actions, and responsibilities to successfully meet the Department of Defense (DoD) Windows 10 (Win10) migration mandate.  References (a) and (b) direct that all Office Information Technology (IT) Windows End User Devices (EUDs) migrate to the Win10 Secure Host Baseline (SHB) operating system by 31 March 2018.  Tactical and Core Function EUDs will be addressed via SEPCOR.  In early 2017, network infrastructure upgrades in support of the Win10 migration were completed and the Marine Corps migration began in May 2017.
2.  Policy.  No later than 31 March 2018, all Marine Corps EUDs will migrate within the Approved Acquisition Objective (AAO) quantities to the Win10 SHB operating system in order to meet requirements of reference (a), decrease network vulnerabilities, improve network management, and promote standardization across the Marine Corps Enterprise Network (MCEN).  Per reference (c), the AAO delineates quantity of items authorized for peacetime and wartime requirements to equip and sustain the Marine Corps in accordance with current DoD policies and plans.
3.  Actions.  The Win10 migration requires a unity of effort between Headquarters Marine Corps, Command, Control, Communications, and Computers (HQMC (C4)), Marine Corps Forces Cyberspace Command (MARFORCYBERCOM), Marine Corps Systems Command (MARCORSYSCOM), Marine Corps Installations Command (MCICOM), Marine Forces Reserves (MARFORRES), Marine Forces Europe (MARFOREUR), Headquarters Marine Corps, Administration and Resource Management Division, Information Systems Management Branch (HQMC (ARI)), Marine Corps Recruiting Command (MCRC) and Training and Education Command (TECOM), the Supporting Establishment (SE), and the Operational Forces (OPFOR).  MARCORSYSCOM is the supported command for Win10 SHB fielding execution.  HQMC (C4), MARFORCYBERCOM, MCICOM, MARFORRES, MARFOREUR, HQMC (ARI), MCRC, TECOM, the SE, and all OPFORs are the supporting organizations.  Reference (d) provides other detailed information in support of the fielding effort.  Specific Win10 actions required are:
a.  HQMC (C4) shall:
(1)  Coordinate Win10 funding resources:
(2)  Monitor and assess the progress of the migration, and:
(3)  Report to DoD CIO, Department of Navy CIO, and the ACMC on status of the migration.
b.  MARFORCYBERCOM shall:
(1)  Issue a Win10 OPORD that provides tasks and coordinating instructions for the migration to all stakeholders:
(2)  Configure the MCEN to support the migration, and:
(3)  Conduct audits and identify and provide technical support.
c.  MARCORSYSCOM shall:
(1)  Deploy Win10 fielding teams to execute the fielding:
(2)  Develop and maintain a single NIPRNet and SIPRNet Marine Corps Enterprise Desktop Standards (MCEDS) Win10 image:
(3)  Procure EUDs to replace non-Win10 compliant EUD:
(4)  Coordinate delivery of EUDs to the OPFOR and SE through all available Enterprise Staging and Warehouse (ES and W) facilities, and:
(5)  Provide weekly reporting of Win10 migration results to HQMC (C4), and conduct other actions as required to lead the migration.
d.  MCICOM, MARFORRES, HQMC (ARI), and MARFOREUR, MCRC, and TECOM shall:
(1)  Support the MARCORSYSCOM Win10 fielding teams:
(2)  Coordinate EUD migration schedules with MARCORSYSCOM:
(3)  Employ organic personnel when required for the migration:
(4)  Consolidate and submit EUD migration data to MARCORSYSCOM:
(5)  Grant vendor network approved access and permissions, and:
(6)  Ensure fielding teams complete all Win10 migrations prior to 31 March 2018 and other actions as required in support of the migration.
e.  OPFOR and SE shall:
(1)  Coordinate with subordinate commands for unit availability in support of MARCORSYSCOM Win10 fielding teams:
(2)  Identify all EUDs in excess of the AAO:
(3)  Provide access to buildings and workspaces for fielding teams:
(4)  Augment the MARCORSYSCOM fielding teams with organic government personnel:
(5)  Distribute new Win10 EUDs to subordinate commands:
(6)  Ensure personnel availability when scheduled to migrate:
(7)  Ensure all EUDs are migrated before the departure of the Win10 fielding teams from their geographical area, and: (8) Coordinate and monitor the transfer of EUDs between Defense Property Accountability System (DPAS) and GCSS-MC.
4.  Command.  A General Officer Control Board will be established in support of the Win10 migration in order to formalize decisions, reports, and assessments.  Control Board members will include the General Officers from:  HQMC (C4), MARFORCYBERCOM, MARCORSYSCOM, and MCICOM.  The Win10 Control Board will consult with MARCORSYSCOM on decisions that impact the cost, performance, or schedule of the migration.
5.  The HQMC (C4) Win10 portal contains the fielding plan, briefs, planning documents, technical guidance, and reporting criteria.  The portal is available at: https://eis.usmc.mil/sites/espm/Win10Migration/SitePages/Home.aspx
6.  Release authorized by Lieutenant General James B. Laster, Director, Marine Corps Staff.//