AMERICAS ARMY: THE STRENGTH OF THE NATION

UNCLASS/FOUO

Results of O-6 Coordination

72 comments, 26 pages total

18 Critical: 7 rejected (POA&M or Migration Schedule appropriate, not EXORD) 12 Rejected: Most are not germane to the base EXORD can be addressed with the Implementation Plan 13 General comments and questions for CIO/G-6 and ARCYBER / NETCOM consideration can be addressed with the Implementation Plan 1 Defer to the EGB / LWN GOSC Secretariat to address
Recommend the Reserve Component (Army Reserve & National Guard) be added as voting member in the review processes for enterprise email application and services through the existing Enterprise Configuration Management and Operations Oversight Board to the Reserve Component equities are validated.

UNCLASSIFIED//FOR OFFICIAL USE ONLY DRAFT - 2/3-Star review 2 Dec 2010 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 Copy__of__Copies Headquarters, Department of the Army Pentagon, Washington, DC HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services (U//FOUO) References: a. (U) Memorandum, Chief of Staff of the Army (CSA), subject: LandWarNet Global Network Enterprise Construct Strategy Implementation, dated 2 March 2009. b. (U) Memorandum, Army CIO/G-6, Global Network Enterprise Construct Transformation of LandWarNet, dated 24 June 2009. c. (U) HQDA, Planning Order (PLANORD): LandWarNet Global Network Enterprise Construct (GNEC) Implementation, ALARACT 292/2009, dated 19 October 2009. d. (U) Army Enterprise Infrastructure Directory Services Naming Conventions and Standards Version 5.1, dated 1 February 2007. e. (U) DoD Instruction 8551.1, Ports, Protocols, and Services Management, dated 13 August 2004 f. (FOUO) DoD Ports, Protocols, and Services Management (DoD-PPSM) Exception Management Process, dated 22 June 2010. g. (U) General Order 5, Establishment of U.S. Army Network Enterprise Technology Command/9th Army Signal Command, dated 13 August 2002. h. (U) General Order 2010-26, Establishment of the United States Army Cyber Command, dated 1 October 2010. i. (U) Memorandum, Under Secretary of the Army, subject: Guidance on Implementing Army Efficiency Initiatives, dated 2 September 2010. j. (U) Execute Order (EXORD) 259-10: Campaign on Property Accountability, ALARACT 210/2010, dated 09 July 2010. k. (U) AR 25-1, Army Knowledge Management and Information Technology, dated 4 December 2008. l. (U) DA Pamphlet 25-1-1, Information Technology Support and Services, dated 25 October 2006.

UNCLASSIFIED//FOR OFFICIAL USE ONLY

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88

1. (U) Situation. a. (U) A CSA memo (reference a) established the Global Network Enterprise Construct as the strategy to transform LandWarNet (LWN) into an Army Enterprise framework and designated NETCOM/9th Signal Command (Army) (NETCOM/9th SC(A)) as the Army's enterprise network manager for Generating Force networks. GNEC supports four strategic objectives: 1) enabling warfighting capabilities through the Network; 2) dramatically improving network defense; 3) realizing efficiencies while improving effectiveness; and 4) ensuring Army interoperability with the Department of Defense. Since publishing the CSA memo, the Under Secretary of the Army has directed that information technology (IT) efficiencies be obtained to meet cost savings for FYs 2012-16, specifically, the migration to an Enterprise Email capability and Army data center consolidation (reference i). This EXORD directs Army Enterprise Email migration. b. (U) The scope of this effort includes all Non-secure and Secret Internet Protocol Router Network (NIPRNet and SIPRNet) Exchange systems with the exception of those that deploy with operating forces. 2. (U) Mission. The Army will migrate to the Defense Information Systems Agency (DISA) Enterprise Email service no later than (NLT) 1 October 2011, providing users access to the Enterprise any time from any CAC-enabled computer. End state will be achieved when Army Cyber Command (ARCYBER) reports that all Army email services are being provided through a single DoD enterprise-level email service. 3. (U) Execution. a. (U) Intent. The CSA directed that LandWarNet be transformed into a centralized, more secure, operationalized and sustainable network, capable of supporting an expeditionary Army and making daily operations more efficient. To achieve this goal, the Army will establish conditions and processes that provide ARCYBER a better understanding of all Army email requirements and enable their consolidation under a single DoD enterprise-level email service. b. (U) Concept of Operations. Army migration to DoD enterprise email services will be conducted in three phases: Phase 1, Discovery; Phase 2, Planning; and Phase 3, Execution. In accordance with (IAW) the September 2010 CIO/G-6 Army Enterprise Guidance Board (EGB) decision, these phases may be conducted in parallel between different installations. (1) Phase 1, Discovery. ARCYBER will conduct Discovery activities that support transition planning for Enterprise objectives by determining the as-is, or current, state of Army email requirements and services. All Army organizations will provide the 2

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129

required data as specified in Annex A (Migration POC and Services Data Call) to NETCOM/9th SC(A) through ARCYBER NLT 30 days after receipt of this EXORD. Data requested, collected and submitted must be classified no higher than Unclassified//For Official Use Only (U//FOUO). This phase must be finished prior to completing a Plan of Action and Milestones (POA&M) in Phase 2. This phase is complete for the Army Enterprise when ARCYBER reports that all organizations have complied with the data call.

(2) Phase 2 (Planning): ARCYBER in coordination with (ICW) Army Commands, Army Service Component Commands and Direct Reporting Units will conduct enterprise email service migration planning to: determine the commands and units that will be subject to this order and the level of effort for each organization; and identify any potential resource shortfalls. Every organization currently providing email services will develop a POA&M for migration to the DoD Enterprise Email Service. Subject organizations will also start to prepare for migration to enterprise email services (e.g., reduce mailbox sizes IAW instructions listed in Annex C) IAW technical guidance to be published by ARCYBER NLT 15 December 2010. This phase is complete for an organization when the POA&M, including the detailed site migration schedule, has been validated by ARCYBER. The goal for completing this phase is NLT 30 days prior to the start of Phase 3 (Execution) for each organization. (3) Phase 3 (Execution): Under the direction of ARCYBER, all Army organizations will transition organic email services to the DoD Enterprise Email Service NLT 1 October 2011. HQDA begins implementation 1 February 2011, followed by the rest of the Army. A detailed schedule will be published NLT 90 days after the effective date of this EXORD. Any organizations seeking an extension to complete tasks for email service migration will send the request to Commander, ARCYBER (ATTN: NETCCG). Organizations that have an existing formal agreement with HQDA for a migration date after 1 October 2011 must re-submit their extension request IAW para 3.d.(1). This phase is complete when ARCYBER reports that all Army email services are being provided through a single DoD enterprise-level email service. c. (U) Tasks. (1) (U) HQDA, G-3/5/7 (a) Monitor the waiver process and maintain visibility of all POA&Ms submitted to ARCYBER. (b) Conduct monthly in-progress reviews (IPRs) with ARCYBER, CIO/G-6 and NETCOM/9th SC(A) to ensure that Army enterprise email requirements and specifications are being met. 3

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172

(2) (U) HQDA, CIO/G-6 (a) ICW HQDA G-3/5/7, ARCYBER AND NETCOM/9th SC(A), coordinate all resource issues and/or requirements with the Defense Information Systems Agency (DISA). (b) Monitor the waiver process and maintain visibility of all POA&Ms submitted to ARCYBER NETOPS. Provide details to ARCYBER for all existing agreements between HQDA and organizations that exempt the organization from meeting the 1 October 2011 suspense for Enterprise Email migration. (c) Provide cost recovery schedule 8 to HQDA G-8 Program Analysis and Evaluation and the Assistant Secretary of the Army (Financial Management and Comptroller) (Army Budget Office) by 15 December 2010. Schedule 8 will include all commands currently providing email, establish an Enterprise Email budget line (MDEP MSNS, SAG 432) and provide accountability for projected email efficiency. (3) (U) ARCYBER (a) Act as the Army lead for migration planning, develop detailed site-level migration schedules and assist sites in the actual migration to the DoD Enterprise Email Service. (b) Review, validate and track submitted POA&Ms from all organizations. (c) Review and adjudicate all submitted waiver requests from all organizations within 14 days of receipt from the requesting organization. (d) Provide monthly updates to G-3/5/7 and CIO/G-6 on migration status, to include POA&M and extension waiver issues. (e) Ensure the Army Operations Oversight Board (OOB) conducts periodic updates during its scheduled events and assesses operational impacts to the enterprise. (f) Participate in monthly IPRs with all stakeholders to ensure completion of tasks and continuity throughout. (g) Act as the overall technical lead and project manager for migration to DoD Enterprise E-Mail Services and coordinate unique organization requirements with CIO/G-6 and DISA.

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215

(h) Develop, maintain content for and provide access to the Enterprise EMail web site (https://www.intelink.gov/inteldocs/browse.php?ffolderid=19731/) throughout the migration process. Users must have an Intelink Passport account to access the documentation. (Follow the instructions on the initial page if you have not previously registered at this site.) (i) Develop and publish enterprise email public folder guidance, client configuration and implementation guidance NLT 45 days after effective date of this EXORD. (j) ICW CIO/G-6 and DISA, ensure Information Assurance (IA) guidance is developed and published. (k) ICW Army organizations currently using an Exchange e-mail capability, develop and publish guidance for the creation of command-specific Installation Sequence Lists (ISLs) to be used throughout the planning and migration process. The document template is in Annex B (Installation Sequence List (ISL) Document Template) and at the Enterprise E-Mail web site listed above. (l) Evaluate and consolidate NIPRNet and SIPRNet requirements, evaluate applications, and coordinate approval and adoption of those meeting existing/emerging enterprise criteria. (m) Participate as a voting member in the review processes for enterprise email application and services through the existing Enterprise Configuration Management and Operations Oversight Board. (n) Establish tactics, techniques and procedures for Army responsibilities related to deployment, operation and management of DoD Enterprise Email and supporting mobile services (to include publishing the plan for deployment of edge nodes in coordination with DISA). (4) (U) Army Organizations. Subject commands and units determined in Phase 2 of this operation will: (a) Every organization currently providing email services will develop a POA&M for migration to the DoD Enterprise Email Service. (b) Participate in HQDA and/or ARCYBER working groups as required to execute tasks in this EXORD. (c) Provide a primary and an alternate POC for this EXORD to the CIO/G-6 and ARCYBER POCs NLT seven days after receipt of this EXORD. 5

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258

(d) Implement and report status of mailbox resizing efforts (Annex C) to ARCYBER (ATTN: NETC-CG) on a weekly basis until in full compliance. (e) Submit completed Migration Checklist IAW Annex A to ARCYBER (ATTN: NETC-CG) NLT 45 days after receipt of this EXORD. Once Annex A data are submitted, no additional changes to mailbox-enabled applications or additions of new public folders should be made. Any operationally required changes must be reported to the ARCYBER POC. (f) Validate or make recommendations for changes to Installation Sequence List (Annex B) to ARCYBER (ATT: NETC-CG) NLT 45 days after receipt of this EXORD. (g) If required, submit waiver requests for extension to task(s) in this EXORD, along with associated POA&M, to Commander, ARCYBER (ATTN: NETC-CG) NLT 14 days after receipt of this EXORD. All requests must clearly describe why the extension is required and why it is in the Armys best interest to grant the extension. The waiver request must include: an updated POA&M that clearly articulates the situation causing the delay; proposed remedial actions; estimated completion date and associated time lines; and a primary and alternate POC (name, phone number and email address). (h) Ensure all organic user (Windows) workstations and laptops accessing DoD Enterprise Email are configured within the following requirements: AGM Windows Vista SP2 (or newer), AGM Office 2007 SP2, AGM Tumbleweed Desktop Validator 4.10 and AGM Activclient 6.2. Failure to meet this requirement will result in the inability to access the DoD Email Service. (i) Ensure all organic Microsoft Exchange mailbox servers have a recent backup and have had database maintenance performed within 30 days of scheduled migration date. (j) Migrate organic mailboxes from existing systems into the DoD Enterprise Email Service in accordance with established Installation Sequence Lists. (k) Ensure that all organic users who require a SIPRNET email account (and do not already have an AKO-S account) register for an AKO-S account NLT 15 JAN 2011. This will enable accurate identification and provisioning of all users who require a SIPR email account in the SIPR enterprise email service. Report status of AKO-S registration efforts to ARCYBER (ATTN: NETC-CG) on a weekly basis until 16 Jan 2011.

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301

d. Coordinating Instructions. (1) (U) Organizations with existing waivers must re-submit to ARCYBER for revalidation within 14 days after receipt of this EXORD. The waiver request must include an updated POA&M that clearly articulates the situation causing the delay, proposed remedial actions, estimated completion date and associated time lines, and a primary and alternate POC (name, phone number and e-mail address). (2) (U) General guidance for reducing mailbox sizes in preparation for migration is listed in Annex C (Guidance on Reducing Mailbox Sizes). (3) (U) The migration checklist template in Annex A (Migration POC and Services Data Call) will be used to ensure readiness prior to migration. A Migration Coordination Team, comprised of subject matter experts (SMEs) from ARCYBER, NETCOM/9th SC(A) and other organizations, as required, may conduct an on-site integration coordination visit to validate the organization/site baseline prior to executing migration. (4) (U) Army National Guard retains responsibility to coordinate waivers for NIPRNET and SIPRNET Generating Force Title 32 email services. (5) (U) U.S. Army Special Operations Command (USASOC) retains the responsibility to coordinate waivers for NIPRNET and SIPRNET Special Operating Forces Information Enterprise (SIE) email services. (6) (U) NLT seven days after receipt of this EXORD, all tasked organizations will acknowledge receipt of this EXORD and provide contact information for designated O-6 level and action officer points of contact to the contacts listed in paragraph 5b. 4. (U) Service and Support. a. (U) Support Concept. b. (U) Materiel and services. (1) Equipment disposition guidance. (a) (U) IAW EXORD 259-10, Campaign on Property Accountability (reference j) units are to identify excess IT equipment after migration to DoD Enterprise Email Services.
(b) (U) IT equipment declared excess as a result of the Enterprise Email

migration may be reutilized as a lifecycle replacement and the replaced equipment will 7

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342

then be declared excess. Excess IT equipment will be disposed of IAW AR 25-1 (reference k) paragraph 6-2.k (Redistribution and disposal of IT assets), DA Pamphlet 25-1-1 (reference l) paragraph 11-3 (Redistribution and disposal of IT assets) and command guidance. 5. (U) Command and Signal. a. (U) ARCYBER is the supported command for the purposes of this EXORD. (1) (U) Strategic communications for this initiative are the responsibility of CIO/G-6. (2) (U) DIRLAUTH with ARCYBER is authorized. b. (U) Points of Contact. (1) (U) G-3/5/7 LWN/BC: Ms. Maria Drew, (703) 545-2554 or maria.drew@us.army.mil; and Mr. Michael Dowdy, (703) 545-2601 or mike.dowdy@us.army.mil. (2) (U) CIO/G-6 AONS: LTC Peter Barclay, (703) 602-9250 or peter.c.barclay@conus.army.mil; and Mr. Thomas Trucks, (703) 806-4224 or thomas.trucks@us.army.mil. (3) (U) ARCYBER: COL William "Max" Duggan, (703) 706-2850 or william.duggan@us.army.mil. (4) (U) NETCOM/9th SC(A): Mr. Michael Bomba, (520) 538-6278 or michael.bomba@us.army.mil; Mr. Raymond Turcotte, (520) 538-3733 or ramon.turcotte@us.army.mil, and Mr. Kevin Mott, (520) 538-6530 or kevin.mott@us.army.mil.

ACKNOWLEDGE:

GEORGE W. CASEY, JR. General, United States Army Chief of Staff

OFFICIAL

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381

DANIEL P. BOLGER Lieutenant General, GS Deputy Chief of Staff, G-3/5/7 DISTRIBUTION: Principal Officials of Headquarters, Department of the Army Commander U.S. Army Forces Command U.S. Army Training and Doctrine Command U.S. Army Materiel Command U.S. Army Europe U.S. Army Central U.S. Army North U.S. Army South U.S. Army Pacific U.S. Army Special Operations Command Military Surface Deployment and Distribution Command U.S. Army Space and Missile Defense Command/Army Strategic Command Eighth U.S. Army U.S. Army Network Enterprise Technology Command/9th Signal Command (Army) U.S. Army Medical Command U.S. Army Intelligence and Security Command U.S. Army Criminal Investigation Command U.S. Army Corps of Engineers U.S. Army Military District of Washington U.S. Army Test and Evaluation Command U.S. Army Reserve Command U.S. Army Installation Management Command Superintendent, United States Military Academy Director, U.S. Army Acquisition Support Center U.S. Army Accessions Command Deputy Under Secretary of the Army (Business Transformation) Director, Small and Disadvantaged Business Utilization Director, Enterprise Task Force

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services 1 2 3 4 5 6 7 8 9 10 11

NO INTERNET PROTOCOL OR DERIVATIVE CLASSIFICATION INFORMATION IS TO BE PROVIDED

ACTION: Complete information below. List Primary (P) and Alternate (A) POCs for your organization, theater operations and each NEC-like facility. ORGANIZATION NAME: ___________________________ POINTS OF CONTACT FOR ENTERPRISE EMAIL:
POC ORGANIZATION (P) ORGANIZATION (A) THEATER (P) THEATER (A) NEC [NAME] (P) NEC [NAME] (A) NAME PHONE AKO EMAIL

12 13 14 15 16 17 18 19 20

IMPORTANT NOTICE: REPEAT NEC AND THEATER ROWS AS NECESSARY.

UNIQUE P RODUCTS AND S ERVICES : Identify any applications (include manufacturer and version number) or services that provide unique capabilities that may affect transition to an Enterprise E-Mail Service. S ITE ACCES S INFORMATION. Please provide the POC (Security Managers) to obtain access to your installations, facilities and server rooms (each, as necessary):
LOCATION NAME EMAIL PHONE NUMBER

(P) (A)

21 22

UNCLASSIFIED//FOR OFFICIAL USE ONLY A-1

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

23 24 25 26

EMAIL BAS ELINE CHECKLIS T 1. Approximately how many users on SIPRNET (per location)?
LOCATION NUMBER OF USERS CURRENT STORAGE AMOUNT/MAILBOX SIZE? DO YOU HAVE ANY PUBLIC FOLDERS? TOTAL AMOUNT OF DATA IN THE PUBLIC FOLDERS IDENTIFY ALL SPECIAL INTEREST CUSTOMERS

27 28 29 30

2. Approximately how many organizational and resource mailboxes on SIPRNET (per location)?
LOCATION NUMBER OF ORGANIZATIONAL AND RESOURCE ACCOUNTS CURRENT STORAGE AMOUNT/MAILBOX SIZE?

31 32 33

3. Approximately how many users on NIPRNET (per location)?

LOCATION NUMBER OF USERS CURRENT STORAGE AMOUNT/MAILBOX SIZE? IDENTIFY PURPOSE OF ALL PUBLIC FOLDERS DEFINE PUBLIC FOLDER CAPACITY/USAGE IDENTIFY YOUR SPECIAL INTEREST CUSTOMERS

34 35 36 37

4. Approximately how many organizational and resource mailboxes on NIPRNET (per location)?
LOCATION NUMBER OF ORGANIZATIONAL AND RESOURCE ACCOUNTS CURRENT STORAGE AMOUNT/MAILBOX SIZE?

38 39 40

A-2

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

41 42 43 44 45

5. Identify all special interest customers. SES/General Officers may require a separate storage bin for migration. Identify customized calendar sync and allowed capacities that may affect migration.
SES/GENERAL OFFICERS AND LOCATION IDENTIFY CUSTOMIZED CALENDAR SYNC ALLOWED CAPACITIES

46 47 48 49

6. Blackberry (N) and SME PED (S) and other special interest users (as necessary, begin creating separate storage bin for them or identify storage requirements).
LOCATION IDENTIFY ALL SPECIAL INTEREST CUSTOMERS DO YOU HAVE ANY REL USERS? DO YOU HAVE A FAX OR OTHER GATEWAY SERVICES? IDENTIFY ALL EXCHANGEDEPENDENT APPLICATIONS

50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69

INFORMATION: CONCURRENCE BY THE MIGRATION TEAM WITH THE CONTENTS BELOW IS REQUIRED BEFORE THE INSTALLATIONS MIGRATION CAN BE EXECUTED (DURING THE ON-SITE INTEGRATION VISIT).

1. Introduction. Number of Exchange organizations on the post/installation and their names: 2. Do these organizations have their own TLOU? 3. Are these organizations in an approved CONUS Domain and Migration Plan for collapsing organizations into single instance? A. Remote satellite locations B. Current OWA requirements C. Current Blackberry requirements D. Email-enabled applications E. Other service requirements F. Public folders used G. Unique ports or protocols required A-3

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104

H. Potential issues & solutions: list any migration or O&M issues. 4. Storage Limitations/Rules. A. OWA requirements B. Email-enabled application requirements (please provide specifics: e.g., version number#) C. Blackberry requirements (please provide specifics: e.g., version number) D. Other service requirements (please provide specifics: e.g., version number#) E. Remote satellite locations F. Encrypted email used G. Public folders used H. Unique ports or protocols required I. Planned network changes: None J. Administrative group structure. (Note: one AG per site. TNOSC will name the AG Law Naming Conventions.) (1) Exchange administrators (2) Exchange view-only administrators (potential issues & solutions) 5. Migration Plan TBD* A. Preliminary task: identify pilot migration group. B. Secondary task: identify migration groups. 6. Resource Plan: TBD* 7. Migration Execution A. Migration steps: (1) Configuration of scenarios (migration groups) (2) Configuration of migration tool with scenario (3) Theater approval to proceed past pilot (4) Migration execution and reporting B. Time line: Estimated time line per 10,000 users (migration team estimate) 8. Post-Migration Plan A. Purpose: application migration B. Activities 9. Operation and maintenance plan A. Purpose: decommissioning inventory and schedule B. Activities

A-4

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123

*ITEMS WITH THE ACRONYM TBD WILL BE COORDINATED AND DETERMINED DURING IPRS AND SITE VISITS QUESTIONS, CONCERNS AND COMMENTS LIST ANY ADDITIONAL QUESTIONS, CONCERNS OR COMMENTS HERE: 1.

2.

3.

4.

A-5

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex B (Installation Sequence List (ISL) Document Template) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 The existing Installation Sequence Lists of NIPRNet and SIPRNet site migrations can be downloaded from the following locations. An Intelink Passport account is required to access this area. DoD Enterprise Email Document Folder: https://www.intelink.gov/inteldocs/browse.php?fFolderId=19731 NIPRNet Schedule: https://www.intelink.gov/inteldocs/view.php?fDocumentId=370320 SIPRNet Schedule: https://www.intelink.gov/inteldocs/view.php?fDocumentId=370321 Submit recommended changes to these sequence lists using the table format provided below. If there are issues that affect migration of facilities or large groups of users, organizations can identify those blocks of dates during which they cannot accomplish those migrations below.

SITE

PRIORITY

22 23 24 25 26 27 28 29 30

UNCLASSIFIED//FOR OFFICIAL USE ONLY B-1

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex C (Guidance on Reducing Mailbox Sizes) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39

Consistent with actions described in the basic EXORD, it is necessary to reduce Microsoft Exchange server-side email storage to no more than 100MB per user. The process used to migrate email from the legacy environment to the DoD Enterprise Email Service includes copying all email located in the legacy Exchange server across the wide area network to the new DoD Enterprise Email Exchange server. This process is most effectively performed with as little mail in the users mailbox as possible. For users who do not have a need to access their email outside of the office environment, it is recommended that the users Outlook profile be adjusted to deliver mail to a local PST file located on the users computer. For users who utilize mobile messaging clients (e.g., Blackberry), this is not an option as the Blackberry requires access to the email located on the Exchange server. For these users, it is recommended that all mail older than two weeks be moved off the Exchange server and placed into local PST files. These reductions in local Exchange mailbox sizes will facilitate a smooth transition to the DoD Enterprise Email Service. Additional guidance and direction will be developed on a site-by-site basis for users who cannot decrease their server-side mailbox size (e.g. GO, SES, Commanders, Directors). NOTE: For all users, email can be moved back into their new email server mailbox once the migration is complete. As part of this EXORD, organization POCs must track and report their progress in reducing mailbox sizes to ARCYBER (ATTN: NETC-CG) in consolidated progress reports. Mailbox reduction consolidated progress reports will include the number of users with mailboxes greater than 1GB, between 500MB and 1GB, between 100MB and 500MB, and between 0 and 100MB. This information will be provided by location within each organization. For information on how to back up mail to a PST or CD, please see the following article published by Microsoft: http://support.microsoft.com/kb/287070.

C-1

UNCLASSIFIED//FOR OFFICIAL USE ONLY DRAFT V0.93 18 Oct 2010 Copy__of__Copies Headquarters, Department of the Army Pentagon, Washington, DC HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services (U//FOUO) References: a. (U) Memorandum, Chief of Staff of the Army (CSA), Subject: LandWarNet Global Network Enterprise Construct Strategy Implementation, dated 2 March 2009. b. (U) Memorandum, Army CIO/G-6, Global Network Enterprise Construct Transformation of LandWarNet, dated 24 June 2009. c. (U) HQDA, Planning Order (PLANORD): LandWarNet Global Network Enterprise Construct (GNEC) Implementation, ALARACT 292/2009, dated 19 October 2009. d. (U) Army Enterprise Infrastructure Directory Services Naming Conventions and Standards Version 5.1, dated 1 February 2007. e. (U) DoD Instruction 8551.1; Ports, Protocols, and Services Management, dated 13 August 2004 f. (FOUO) DoD Ports, Protocols, and Services Management (DoD-PPSM) Exception Management Process, dated 22 June 2010. g. (U) General Order No. 5; Establishment of U.S. Army Network Enterprise Technology Command/9th Army Signal Command, dated 13 August 2002. h. (U) General Order No. 2010-26; Establishment of the United States Army Cyber Command, dated 1 October 2010. i. (U) Memorandum, Under Secretary of the Army (USA), Subject: Guidance on Implementing Army Efficiency Initiatives, dated 2 September 2010. 1. (U) Situation. a. (U) The CSA memo, reference a., established the Global Network Enterprise Construct (GNEC) as the Armys strategy to transform the LandWarNet (LWN) to an Army Enterprise framework and established NETCOM/9th Signal Command (Army) (NETCOM/9th SC(A)) as the Army's enterprise network manager for Generating Force networks. The GNEC supports four strategic objectives: 1) enabling warfighting capabilities through the Network, 2) dramatically improving network defense, 3) realizing efficiencies while improving effectiveness, and 4) ensuring Army interoperability with the Department of Defense. Since the publishing the CSA memo, the USA memo, UNCLASSIFIED//FOR OFFICIAL USE ONLY

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

reference i., directed information technology (IT) efficiencies be obtained to meet cost savings for FYs 2012-16, specifically, the migration to an Enterprise E-mail capability as well as Army data center consolidations. This EXORD directs Army Enterprise E-mail migration. b. (U) The scope of this effort includes all Non-secure (NIPRNET) and Secret (SIPRNET) Internet Protocol Router Networks. 2. (U) Mission. The Army will migrate to the Defense Information Systems Agency (DISA) Enterprise E-mail services no later than (NLT) 1 October 2011providing users access to the Enterprise anytime and from anyplace. End state is when Army Cyber Command (ARCYBER) reports that all Army email services are being provided through a single DoD enterprise-level email service. 3. (U) Execution. a. (U) Intent. The CSA memo, reference a., provided guidance to transform LandWarNet to a centralized, more secure, operationalized and sustainable network capable of supporting an expeditionary Army and increase efficiencies for daily operations. To achieve this goal, the Army will establish conditions and processes that provide ARCYBER with a better understanding of all Army email requirements and enables their consolidation under a single DoD enterprise-level email service. b. (U) Concept of Operations. The Army migration to DoD enterprise email services will be conducted in three phases. Phase 1- Discovery, Phase 2- Planning, and Phase 3- Execution. In accordance with (IAW) the CIO/G-6 Army Enterprise Guidance Board (EGB) decision in September 2010, these phases may be conducted in parallel. (1) Phase 1 (Discovery): ARCYBER will conduct Discovery activities that support the transition planning for Enterprise objectives by determining the as-is state of Army email requirements and current email services. All Army organizations will provide the required data as specified in Annex A (Migration POC and Services Data Call) to NETCOM/9th SC(A) through ARCYBER NLT 45 days upon receipt of this EXORD. Data requested, collected, and submitted must be classified no higher than Unclassified//For Official Use Only (U//FOUO). This phase must be completed by an organization prior to developing Plan of Action and Milestones (POA&M) in Phase 2. This phase is complete for the Army Enterprise when ARCYBER reports that all organizations have complied with the data call. (2) Phase 2 (Planning): ARCYBER in coordination with (ICW) ACOMs, ASCCs and DRUs will conduct enterprise email service migration planning to determine the commands and units that will be subject to this order, the level of effort for each 2

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

organization, and identify any potential resource shortfalls. This includes developing a POA&M for the respective organizations. Subject organizations will also start preparation for migration to enterprise email services (e.g. reduce mailbox sizes IAW instructions listed in Annex C) IAW technical guidance to be published by ARCYBER NLT 15 December 2010. This phase is complete for an organization when the POA&M, including the detailed site migration schedule, has been validated by ARCYBER. The goal for completing this phase is NLT 30 days prior to start of Phase 3 (Execution) for each organization. (3) Phase 3 (Execution): Under the direction of ARCYBER, all Army organizations will transition organic email services to the DoD Enterprise Email Service NLT 1 October 2011. HQDA begins implementation effective 1 February 2011, followed by the rest of the Army. A detailed scheduled will be published NLT 90 days after effective date of this EXORD. Any extensions to complete tasks for migrating email services will be requested through Commander, ARCYBER (ATTN: NETC-CG). This phase is complete when ARCYBER reports that all Army email services are being provided through a single DoD enterprise-level email service. c. (U) Tasks. (1) (U) HQDA, G-3/5/7. (a) Monitor the waiver process and maintain visibility of all submitted POA&Ms from all organizations to ARCYBER (ATTN: NETC-CG). (b) Conduct monthly in progress reviews (IPRs) with ARCYBER, CIO/G-6 and NETCOM/9TH SC(A) to ensure army enterprise e-mail requirements and specifications are being met. (2) (U) HQDA, CIO/G-6. (a) ICW HQDA G-3/5/7, ARCYBER, AND NETCOM/9TH SC(A) coordinate all resource issues and/or requirements with the Defense Information Systems Agency (DISA). (b) Monitor the waiver process and maintain visibility of all submitted POA&Ms from Army organizations to ARCYBER NETOPS. (c) Provide cost recovery schedule 8 to HQDA G-8 PA&E and ASA(FM&C) (ABO) by 15 November 2010. Schedule 8 will include all Commands currently providing email, establish an Enterprise Email budget line (MDEP MSNS, SAG 432), and provide accountability for projected email efficiency.

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

(3) (U) ARCYBER (a) Act as the Army lead for migration planning, develop detailed site level migration schedules and assist sites in the actual migration to the DoD Enterprise Email Service. (b) Review, validate and track submitted POA&Ms from all organizations. (c) Review and adjudicate all submitted waiver requests from all organizations within 14 days of receipt from the requesting organization. (d) Provide monthly updates to the G-3/5/7 and CIO/G-6 on migration status, to include POA&M and waiver issues. (e) Ensure the Army Operations Oversight Board (OOB) schedules and conducts periodic updates during their scheduled events and assesses operational impacts on the enterprise. (f) Participate in monthly IPRs with all stakeholders to ensure completion of tasks and continuity throughout. (g) Act as the overall technical lead and project manager for the migration to DoD Enterprise E-Mail Services and coordinate unique organization requirements with CIO/G-6 and DISA. (h) Develop, maintain content, and provide access to the Enterprise E-Mail web site (https://www.intelink.gov/inteldocs/browse.php?ffolderid=19731/) throughout the migration process. Users must have an Intelink Passport account to access the documentation. Follow the instructions on the initial page if you have not previously registered at this site. (i) Develop and publish enterprise e-mail public folder guidance, client configuration, and implementation guidance NLT 45 days after effective date of this EXORD. (j) ICW CIO/G-6, ARCYBER, and DISA, ensure Information Assurance (IA) guidance is developed and published. (k) ICW Army Organizations currently having an Exchange e-mail capability, develop and publish guidance for the creation of command specific Installation Sequence Lists (ISLs) to be used throughout the planning and migration

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

process. Document template is in Annex B (Installation Sequence List (ISL) Document Template), and at the Enterprise E-Mail web site listed above. (l) Evaluate and consolidate NIPRNET and SIPRNET requirements, evaluate applications, and coordinate approval and adoption of those meeting existing/emerging enterprise criteria. (m) Participate as a voting member in the review processes for enterprise e-mail application and services through the existing Enterprise Configuration Management and Operations Oversight Board business practices. (n) Establish Army tactics, techniques and procedures (TTPs) for the Armys responsibilities related to operations and management of the DoD Enterprise Email Service. (4) (U) Army Organizations. Subject commands and units determined in Phase 2 of this operation will: (a) Participate in HQDA and/or ARCYBER working groups as required to execute tasks in this EXORD. (b) Provide a Primary and Alternate POC for this EXORD to the CIO/G-6 and ARCYBER POCs NLT 7 days upon receipt. (c) Implement and report status of mailbox resizing efforts (Annex C) to ARCYBER (ATTN: NETC-CG) on a weekly basis until in full compliance. (d) Submit completed Migration Checklist IAW Annex A to ARCYBER (ATTN: NETC-CG) NLT 45 days upon receipt of this EXORD. Once Annex A data is submitted, no additional changes to mailbox enabled applications and additions of new public folders should be made. Any operationally required changes must be reported to the ARCYBER POC. (e) Validate or make recommendations for changes to Installation Sequence List (Annex B) to ARCYBER (ATT: NETC-CG) NLT 45 days upon receipt of this EXORD. (f) If required, submit waiver requests for extension to task(s) in this EXORD along with associated POA&M to Commander, ARCYBER (ATTN: NETC-CG) NLT 14 days upon receipt of this order. All requests must clearly describe why the extension is required and why it is in the Armys best interest to grant the extension.

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

(g) Ensure all organic user (Windows) workstations and laptops accessing DoD Enterprise Email are configured within the following requirements: AGM Windows Vista SP2 (or newer), AGM Office 2007 SP2, AGM Tumbleweed Desktop Validator 4.10, and AGM Activclient 6.2. Failure to meet this requirement will result in the inability to access the DoD Email Service. (h) Ensure all organic Microsoft Exchange mailbox servers have a recent backup and have had database maintenance performed within 30 days of scheduled migration date. (i) Perform migration of organic mailboxes from existing systems into the DoD Enterprise Email Service in accordance with established Installation Sequence Lists. d. Coordinating Instructions. (1) (U) Waiver requests for extensions will be submitted to ARCYBER (ATTN: NETC-CG). The waiver must include an updated POA&M that clearly articulates the situation causing the delay, proposed remedial actions, estimated completion date and associated timelines, and a primary and alternate POC (name, phone number and e-mail address). (2) (U) General guidance necessary for reducing mailbox sizes in preparation and planning for migration is listed in Annex C (Guidance On Reducing Mailbox Sizes). (3) (U) The migration checklist template listed in Annex A (Migration POC and Services Data Call) will be used to ensure readiness prior to migration. 4. (U) Administration and Logistics. NLT 7 days on receipt of this EXORD, all tasked organizations will acknowledge receipt of this EXORD and provide contact information of designated O-6 level and Action Officer points of contact to the contacts listed in paragraph 5b. 5. (U) Command and Signal. a. (U) ARCYBER is the supported command for the purposes of this EXORD. b. (U) Points of Contact. (1) (U) G-3/5/7 LWN/BC: Ms. Maria Drew, comm: 703-602-7542, maria.drew@us.army.mil, and Mr. Michael Dowdy, comm: 703-602-7348, mike.dowdy@us.army.mil. 6

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

(2) (U) CIO/G-6 AONS: LTC Peter Barclay, comm: 703-602-9520, peter.c.barclay@us.army.mil, and Mr. Thomas Trucks, comm: 703-806-4224, thomas.trucks@us.army.mil. (3) (U) ARCYBER: LTC Timothy Chafos, comm: 703-706-1611, timothy.a.chafos@us.army.mil. (4) (U) NETCOM/9TH SC(A): Mr. Michael Bomba, comm: 520-538-6278, michael.bomba@us.army.mil, and Mr. Raymond Turcotte, comm: 520-538-3733, ramon.turcotte@us.army.mil. (5) (U) Strategic communications for this initiative is the responsibility of the Commander, ARCYBER. (6) (U) DIRLAUTH with ARCYBER is authorized.

ACKNOWLEDGE: OFFICIAL

GEORGE W. CASEY, JR. General, United States Army Chief of Staff

DANIEL P. BOLGER Lieutenant General, GS Deputy Chief of Staff, G-3/5/7 DISTRIBUTION: Principal Officials of Headquarters, Department of the Army Commander U.S. Army Forces Command U.S. Army Training and Doctrine Command U.S. Army Materiel Command U.S. Army Europe U.S. Army Central U.S. Army North U.S. Army South U.S. Army Pacific U.S. Army Special Operations Command Military Surface Deployment and Distribution Command 7

UNCLASSIFIED//FOR OFFICIAL USE ONLY HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

U.S. Army Space and Missile Defense Command/Army Strategic Command Eighth U.S. Army U.S. Army Network Enterprise Technology Command/9th Signal Command (Army) U.S. Army Medical Command U.S. Army Intelligence and Security Command U.S. Army Criminal Investigation Command U.S. Army Corps of Engineers U.S. Army Military District of Washington U.S. Army Test and Evaluation Command U.S. Army Reserve Command U.S. Army Installation Management Command Superintendent, United States Military Academy Director, U.S. Army Acquisition Support Center U.S. Army Accessions Command Deputy Under Secretary of the Army (Business Transformation) Director, Small and Disadvantaged Business Utilization Director, Enterprise Task Force

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

NO INTERNET PROTOCOL OR DERIVATIVE CLASSIFICATION INFORMATION IS TO BE PROVIDED

ACTION: Complete information below. List Primary (P) and Alternate (A) POCs for your organization, theater operations, and for each NEC-like facility. ORGANIZATION NAME: ___________________________ POINTS OF CONTACT FOR ENTERPRISE EMAIL:
POC ORGANIZATION (P) ORGANIZATION (A) THEATER (P) THEATER (A) NEC [NAME] (P) NEC [NAME] (A) NAME PHONE AKO EMAIL

IMPORTANT NOTICE: REPEAT NEC AND THEATER ROWS AS NECESSARY.

UNIQUE P RODUCTS AND S ERVICES : Identify any applications (include manufacturer and version number) or services that provide unique capabilities that may affect transition to an Enterprise E-Mail Service. S ITE ACCES S INFORMATION. Please provide the POC (Security Managers) TO obtain access to your installations, facilities, and server room facilities (each, as necessary):
LOCATION NAME EMAIL PHONE NUMBER

(P) (A)

UNCLASSIFIED//FOR OFFICIAL USE ONLY A-1

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

EMAIL BAS ELINE CHECKLIS T 1. Approximately how many users on SIPRNET (per location)?
LOCATION CURRENT STORAGE AMOUNT/MAILBOX SIZE? DO YOU HAVE ANY PUBLIC FOLDERS? TOTAL AMOUNT OF DATA IN THE PUBLIC FOLDERS IDENTIFY ALL SPECIAL INTEREST CUSTOMERS

2. Approximately how many users on NIPRNET (per location)?

LOCATION CURRENT STORAGE AMOUNT/MAILBOX SIZE? IDENTIFY PURPOSE ALL PUBLIC FOLDERS DEFINE PUBLIC FOLDER CAPACITY/USAGE IDENTIFY YOUR SPECIAL INTEREST CUSTOMERS

3. Identify all special interest customers, SES/GENERAL OFFICERS- may require moving to separate storage bin for migration. Identify customized calendar sync, allowed capacities that may affect migration.
SES/GENERAL OFFICERS AND LOCATION IDENTIFY CUSTOMIZED CALENDAR SYNC ALLOWED CAPACITIES

4. Blackberry (N) and SME PED (S) and other special interest users (as necessary, begin creating separate storage bin for them or identify storage requirements).
LOCATION IDENTIFY ALL SPECIAL INTEREST CUSTOMERS DO YOU HAVE ANY REL USERS? DO YOU HAVE A FAX OTHER GATEWAY SERVICES? IDENTIFY ALL EXCHANGE DEPENDENT APPLICATIONS

A-2

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

INFORMATION: CONCURRENCE BY THE MIGRATION TEAM WITH THE CONTENTS BELOW IS REQUIRED BEFORE THE INSTALLATIONS MIGRATION CAN BE EXECUTED (DURING THE ON-SITE INTEGRATION VISIT).

1. Introduction. Number Of Exchange Organizations on the post/installation and their names: 2. Do these organizations have their own TLOU? 3. Are these organizations in an approved CONUS Domain And Migration Plan for collapsing organizations into single instance: A. Remote satellite locations. B. Current OWA requirements. C. Current Blackberry requirements. D. Email-enabled applications E. Other service requirements. F. Public folders used: G. Unique ports or protocols required. H. Potential issues & solutions: (list any migration or O&M issues) 4. Storage Limitations/Rules: A. OWA Requirements: B. Email-enabled application requirements (Please provide specifics: e.g. version #): C. Blackberry requirements (Please provide specifics: e.g. version #): D. Other Service requirements (Please provide specifics: e.g. version #): E. Remote satellite locations: F. Encrypted email Used: G. Public folders used: H. Unique ports or protocols required: I. Planned network changes: None J. Administrative group structure (Note: One AG Per Site. TNOSC will name the AG Law Naming Conventions) (1) Exchange administrators. (2) Exchange view-only administrators (potential issues & solutions): 5. Migration Plan TBD* A. Preliminary tasks-identify pilot migration group B. Secondary task- identify migration groups A-3

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex A (Migration Points of Contact (POC) and Services Data Call) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

6. Resource Plan: TBD* 7. Migration Execution A. Migration steps: (1) Configuration of scenarios (migration groups) (2) Configuration of migration tool with scenario (3) Theater approval to proceed past pilot (4) Migration executing and reporting B. Timeline: Estimated timeline per 10,000 Users (migration team estimate) 8. Post Migration Plan A. Purpose: application migration B. Activities: 9. Operations and maintenance plan A. Purpose: decommissioning inventory and schedule B. Activities: *ITEMS WITH THE ACRONYM TBD WILL BE COORDINATED AND DETERMINED DURING IPRS AND SITE VISITS QUESTIONS, CONCERNS AND COMMENTS LIST ANY ADDITIONAL QUESTIONS, CONCERNS, OR COMMENTS HERE: 1.

2.

3.

4.

A-4

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex B (Installation Sequence List (ISL) Document Template) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services The existing Installation Sequence Lists of NIPRNet and SIPRNet site migrations can be downloaded from the following location. An Intelink Passport account is required to access this area. DoD Enterprise Email Document Folder: https://www.intelink.gov/inteldocs/browse.php?fFolderId=19731 NIPRNet Schedule: https://www.intelink.gov/inteldocs/view.php?fDocumentId=370320 SIPRNet Schedule: https://www.intelink.gov/inteldocs/view.php?fDocumentId=370321 Recommended changes to these sequence lists should be submitted using the table format provided below. If there are issues that affect migration of facilities or large groups of users, this is where organizations can identify these blocks of dates where they cannot accomplish those migrations.

SITE

PRIORITY

UNCLASSIFIED//FOR OFFICIAL USE ONLY B-1

UNCLASSIFIED//FOR OFFICIAL USE ONLY Annex C (Guidance on Reducing Mailbox Sizes) to HQDA EXORD, LandWarNet Global Network Enterprise Construct (GNEC) Implementation Army Migration to DoD Enterprise Email Services

Consistent with actions described and called out in the basic EXORD, it is necessary to reduce Microsoft Exchange server side email storage to no more than 100MB per user. The process used to migrate email from the legacy environment to the DoD Enterprise Email Service includes copying all email located in the legacy Exchange server across the wide area network to the new DoD Enterprise Email Exchange server. This process is most effectively performed with as little mail in the users mailbox as possible. For users that do not have a need to access their email outside of the office environment, it is recommended the users Outlook profile be adjusted to deliver their mail to a local PST file located on the users computer. For users that utilize mobile messaging clients (e.g. Blackberry), this is not an option as the Blackberry requires access to the email located on the Exchange server. For these users, it is recommended that all mail older than 2 weeks be moved off the Exchange server and placed into local PST files. These reductions in local Exchange mailbox sizes will facilitate a smooth transition to the DoD Enterprise Email Service. Additional guidance and direction for users who cannot decrease their server side mailbox size (e.g. GO, SES, Commanders, Directors) will be developed on a site-by-site basis. NOTE: For all users, email can be moved back into their new email server mailbox once the migration is complete. As a part of this FRAGO, Theater POCs must track and report their progress regarding the reduction of mailbox sizes and provide the NETCOM/9TH SC(A), POC with consolidated progress reports. For information on how to backup mail to a PST or CD, please see the following article published by Microsoft for reference and implementation instructions: http://support.microsoft.com/kb/287070.

C-1