1 / 14

83 NOS Perspective: AFNETOPS and the AFNET Migration

83 NOS Perspective: AFNETOPS and the AFNET Migration. Lt Col Eric P. DeLange Commander . Chain of Command & AFNETOPS Organization. AFSPC. AF Network Integration Center (Scott AFB). 24 AF. 624 OC. 67 Net Warfare Wing Net Ops & Monitoring, CND/A (Lackland AFB).

diep
Download Presentation

83 NOS Perspective: AFNETOPS and the AFNET Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 83 NOS Perspective: AFNETOPS and the AFNET Migration Lt Col Eric P. DeLange Commander

  2. Chain of Command & AFNETOPS Organization AFSPC AF Network Integration Center (Scott AFB) 24 AF 624 OC 67 Net Warfare Wing Net Ops & Monitoring, CND/A (Lackland AFB) 688 Info Ops Wing Info Ops & Net Engineering (Lackland AFB) 689 Combat Comm Wing Combat Comm & CommMaint/System Tech Eval (Robins AFB) 26 NOG (Lackland AFB) 26 NOS (Gunter Annex) 33 NWS (Lackland AFB) 26 OSS (Lackland AFB) 352 NWS (Hickam AFB) 426 NWS (Vogelweh GE) 68 NWS (Brooks CB, TX) 67 NWG (Lackland AFB) 91 NWS (Lackland AFB) 315 NWS (Fort Meade) 690 NSG (Lackland AFB) 83 NOS (Langley AFB) 561 NOS (Peterson AFB) 690 NSS (Lackland AFB) 690 ISS (Lackland AFB) 299 NOSS (KS ANG) 310 CF (CO AFR) 622 CF (VA AFR) Base Network Control Ctr’s (NCCs) ---- AFNETOPS C2 Process

  3. 67th Network Warfare Wing Operate Operations Of and On the Network Attack Defend 67 NWW 690 NSG Net Ops 67 NWG Full Spectrum 26 NOG Net Defense • USAF’s Cyberspace Force – Combat Wing, Global Presence • Mission: • Operate, Manage, & Defend Global AF Networks • Train and Ready Airmen to Execute Computer Network Exploitation and Attack • Perform Electronic Systems Security Assessments • Conducts the Full Range of Network Warfare • Network Operations (Establish) • Net Defense (Control) • Full Spectrum (Use)

  4. Mission • Command, Control, Operate, Sustain, and Defend assigned Air Force networks to assure global cyber supremacy and enforce Air Force network standards and to develop Airman as cyber warriors.

  5. The AFNET Platform Delivering… Single Sign-On Reduced Cost and System Complexity AF-Wide Collaboration Standardization and Consolidation Career Email Address Air Force Wide Enterprise Standardized and Secure!

  6. UNCLASSIFIED Services in the AFNET AFNET MANAGED Management Tools Network Account Management Security Policy Enforcement/Management Application Monitoring Network Monitoring • C2 and Functional Systems • Functional Services • SharePoint • MS Office Communication Server • List Servers • Fax Servers • Project Management Servers • FTP Servers • Enterprise–wide VPN • Storage Security/Authentication Directory (AD) Anti-Virus Security Patching (SCCM) CAC Certification AF Enterprise Forest Capabilities E-mail Mobile Devices ESD

  7. What the AFNET Migration is NOT! • AFNetis not a“full” tech refresh of base equipment • AFNetdoes not “reprogram” PMO systems • AFNetdoes not provide C&A of base enclaves • AFNet Enterprise Service Desk (ESD) was notnot established to handle all communication issues (LMR, IPTV, etc) • AFNetdoes not provide Continuity of Operations (COOP) • AFNetdoes not “restructure” AF boundaries; Completely separate but related effort • AFNetdoes not remove Single Points of Failure (SPOF) • AFNetdoes not “fix” existing network issues • AFNetdoes not physically “move” base level functional systems to the APC

  8. Legacy Shutdown Components of Migration Legacy shutdown actions occur concurrently during migration/post migration actions • Initial Coordination • Programmatic Coordination • Begins 210 days prior to migration / Duration ~15 days • Infrastructure Preparation • Circuit Upgrades, Facility Improvements, AQ processes • Begins ~180 days prior to migration / Duration up to 150 days (or more) • Source Environment Preparation • Prepare the legacy environments for migration (Administrative & Technical) • Begins ~90 days prior to migration / Duration ~60 days • Target Environment Preparation • Prepare AFNET to support migration of site • Begins ~60 days prior to migration / Duration ~60 days • Migration • Move Legacy Active Directory resources to AFNet • Duration varies from 15 days - up to 150 days (or more) • Post Migration • Environment Clean up, Legacy Func App Transition & Shutdown • Begins ~180 prior to migration / Duration up to 150 days (or more)

  9. Migration Organizational Roles/Responsibilities ‘Key’ stakeholders and what each contributes to the migration of an organization MAJCOM • Coordinate Base Support • Coordinate Migration Schedule • Facilitate Strategic Communication • Funding for Hardware and Allied Support • Contracting Support AFSPC This is a TEAM Sport! • Core Migration Team • O&M for the AFNet • Operational Issue Resolution 24 AF/67 NWW (Includes 690 NSG, 83 NOS, 561 NOS) • Project Management • Operations • Legacy Shutdown AFNIC Base • Executes Checklist • Coord Local Support/Info Dissemination • Provides Dedicated CST Support

  10. UNCLASSIFIED Entrance Criteria • Complete all pre-migration checklists • Key servers in-place, configured, and operational • Proper, documented certification and accreditation • Support orgs prepared to accept responsibility • <1% user accts over mailbox size limit • XP machine POA&M • Cyber Readiness Review (CRR) AFNIC/ECSO Programmatic FACILITATION CRR Technical Checklists Execution Feedback Pre-Migration Administrative Checklists Feedback CRR represents formal hand-off from programmatic actions to operations 690 NSG Operations LESSONS LEARNED

  11. Exit Criteria • Migrate user/machine accts, E-mail, public folders & other services • All mission systems operational pre-migration are still operational post-migration • Accessible via trust or in the AFNet • <1% minor (user-level) tickets and no major (exec/base-level or higher mission impact) tickets related to MIGRATION • Outstanding Help Desk tickets related to Other Services will transfer to the ESU/ESD Exit criteria will be reviewed during outbrief

  12. Post Migration Support Environment Tier 0 Tier 1 Tier 2 Tier 3 User ESD I-NOSC/ESU/APC MCCC/NCC/CFP • “Self-service” • TT Submission/Status • Load own printer • Load appr S/W apps • Etc. • Tier 1 • Create/assign/track TTs • Initial troubleshooting • AD User Acct Mgmt • Tier 2 • Admin/Assist • EITSM Acct Mgmt • Etc. • More complex HW/SW problems • Requires specific construct attention • Netwk Transport, Server, Boundary issues • Local Touch MX req’d • Highly specialized • expertise required • - Engineers • - System integrators • - 3rd-party providers • - Vendors • - FSEs/SMEs • PMO-managed systems • - AFPKI • - AFDS • - ADLS • - AFNet Response Ctr Enterprise Service Desk DSN 510-HELPDESK(510-435-7337) “owns” lifecycle management

  13. Lessons Learned Adherence to Checklist Completion Dedicated Migration CSTs Security Permissions for Mapped Drives Strategic Communications Selecting Pilot Users Identifying Network Bandwidth Issues Identifying Alt Token, Blackberry/Good Mobile, VIP Users Ensuring ATO and CR Process AD Groups and Exchange

  14. Questions?

More Related