Engage

Twitter
Logo
Twitter
Logo
Facebook
Logo
Twitter
Logo
Twitter
Logo
Twitter
Logo
Facebook
Logo
Twitter
Logo
Twitter
Logo
Twitter
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
Logo
Facebook
2,149,873
Like Us
Twitter
468,084
Follow Us
YouTube Google+ Blog RSS Instagram

Cyberspace milestone reached for Air Force Network

SCOTT AIR FORCE BASE, Ill. (AFNS) -- Air Force Network Integration Center members here completed the migration of all user accounts onto the Air Force Network, March 31.

This accomplishment marked a major milestone in the Air Force's progression to the Department of Defense's Joint Information Environment, a network construct that should eventually unite the entire military around a single set of shared infrastructure and information technology services.

"This is truly a significant milestone for Air Force cyberspace," said Gen. William Shelton the commander of Air Force Space Command. "Completing this portion of the migration not only paves the way to the JIE (Joint Information Environment) for us, it is also critically important to our future enterprise and to the defense of Air Force networks on a global scale."

Prior to the AFNET vision, unique mission requirements, operational concerns and mission-related preferences drove many Air Force organizations to create separate individual networks to support their email and applications. This patchwork of networks led to high operational and maintenance costs, not to mention standardization and security challenges across the service.

"Until now, organizations across the Air Force have been operating what were essentially their own independent networks, consequently driving unique and unit specific requirements," said Markus Rogers, the director of network architectures and lead of AFNET migration. "The AFNET means enterprise-class situational awareness, network scalability and an ability to command and control our network."

The AFNET migration project consolidated 646,000 email boxes and 12,318 servers at 275 sites from multiple Air Force major commands, field operating agencies, direct reporting units and geographically separated unit networks. It created a centrally-managed standardized structure under the operational control of the 24th Air Force commander.

This large-scale project took a team of more than 200 military, civilian and contractor personnel from AFNIC and the 690th Cyberspace Operations Group five years to complete.

"We made major strides over the past five years to get to this point, creating a resilient, flexible and defensible network under the purview of a single commander that dramatically improves cyber security and significantly reduces vulnerability to attack," Shelton said.

One challenge to the AFNET migration process was obtaining the critical infrastructure to standardize and connect the disparate networks into the new AFNET architecture.

"We underestimated the complexity of such an enormous task when we started the first migration at Keesler Air Force Base in March 2009," Rogers said. "We learned a lot from the challenges of those initial migrations and changed our approach accordingly."

As a result, Rogers and his team increased resources and streamlined the process. The AFNET migration team improved mail migration rates from 2,500 per base per week up to 10,000 per base per week and migrated eight bases concurrently.

"Ultimately at the four year mark, we had migrated 50 percent of the Air Force, and this past year, we set records migrating the remaining 50 percent onto the AFNET," Rogers said.

Rogers said long-term use of a single AFNET should provide a consistent user experience.

"It simplifies operations and maintenance," Rogers said. "It also decreases the manpower required to manage a centralized structure and should reduce training costs. Ultimately, it should improve warfighters' access to data and information services, regardless of location."

This active migration milestone completes the transfer of all Air Force user accounts and workstations across the Air Force. The AFNIC and 24th Air Force migration teams will continue to work with the MAJCOMs in the legacy shutdown phase to transfer their functional system servers onto the AFNET by the end of July.

USAF Comments Policy
If you wish to comment, use the text box below. AF reserves the right to modify this policy at any time.

This is a moderated forum. That means all comments will be reviewed before posting. In addition, we expect that participants will treat each other, as well as our agency and our employees, with respect. We will not post comments that contain abusive or vulgar language, spam, hate speech, personal attacks, violate EEO policy, are offensive to other or similar content. We will not post comments that are spam, are clearly "off topic", promote services or products, infringe copyright protected material, or contain any links that don't contribute to the discussion. Comments that make unsupported accusations will also not be posted. The AF and the AF alone will make a determination as to which comments will be posted. Any references to commercial entities, products, services, or other non-governmental organizations or individuals that remain on the site are provided solely for the information of individuals using this page. These references are not intended to reflect the opinion of the AF, DoD, the United States, or its officers or employees concerning the significance, priority, or importance to be given the referenced entity, product, service, or organization. Such references are not an official or personal endorsement of any product, person, or service, and may not be quoted or reproduced for the purpose of stating or implying AF endorsement or approval of any product, person, or service.

Any comments that report criminal activity including: suicidal behaviour or sexual assault will be reported to appropriate authorities including OSI. This forum is not:

  • This forum is not to be used to report criminal activity. If you have information for law enforcement, please contact OSI or your local police agency.
  • Do not submit unsolicited proposals, or other business ideas or inquiries to this forum. This site is not to be used for contracting or commercial business.
  • This forum may not be used for the submission of any claim, demand, informal or formal complaint, or any other form of legal and/or administrative notice or process, or for the exhaustion of any legal and/or administrative remedy.

AF does not guarantee or warrant that any information posted by individuals on this forum is correct, and disclaims any liability for any loss or damage resulting from reliance on any such information. AF may not be able to verify, does not warrant or guarantee, and assumes no liability for anything posted on this website by any other person. AF does not endorse, support or otherwise promote any private or commercial entity or the information, products or services contained on those websites that may be reached through links on our website.

Members of the media are asked to send questions to the public affairs through their normal channels and to refrain from submitting questions here as comments. Reporter questions will not be posted. We recognize that the Web is a 24/7 medium, and your comments are welcome at any time. However, given the need to manage federal resources, moderating and posting of comments will occur during regular business hours Monday through Friday. Comments submitted after hours or on weekends will be read and posted as early as possible; in most cases, this means the next business day.

For the benefit of robust discussion, we ask that comments remain "on-topic." This means that comments will be posted only as it relates to the topic that is being discussed within the blog post. The views expressed on the site by non-federal commentators do not necessarily reflect the official views of the AF or the Federal Government.

To protect your own privacy and the privacy of others, please do not include personally identifiable information, such as name, Social Security number, DoD ID number, OSI Case number, phone numbers or email addresses in the body of your comment. If you do voluntarily include personally identifiable information in your comment, such as your name, that comment may or may not be posted on the page. If your comment is posted, your name will not be redacted or removed. In no circumstances will comments be posted that contain Social Security numbers, DoD ID numbers, OSI case numbers, addresses, email address or phone numbers. The default for the posting of comments is "anonymous", but if you opt not to, any information, including your login name, may be displayed on our site.

Thank you for taking the time to read this comment policy. We encourage your participation in our discussion and look forward to an active exchange of ideas.
comments powered by Disqus