DAP Deployment Ring Procedure of Changes and Updates

For the DAP service to support clients properly maintenance of the system and configurations applied will be an ongoing and iterative process. Deploying updates, configurations, and software to the organization requires ITC to build sets of users to roll out the changes in phases. Typically, these users ranged (in order) from the most adaptable and least risky to the least adaptable or riskiest. With standard vendor supplied operating system security patches, a similar methodology exists, but construction of the groups is a little different.

Deployment rings in DAP are similar to the deployment groups most organizations constructed for major application upgrade roll out to software.  They are simply a method by which to separate machines into a deployment timeline.  Each deployment ring should reduce the risk of issues derived from the deployment of the updates by gradually deploying the update to entire campus.  The following chart provides a high-level summary of the deployment ring principle used by DAP.

 

General Deployments:

  • Test Systems: Designated systems used explicitedly for the purpose testing changes and updates.  These systems should include a reasonable representation of the campus systems and devices.
  • ITC Systems:  Members of the ITC department
  • Early Campus Adopters: Individuals who would like to receive new features and functionality early.
  • Campus Computers:  All DAP systems.

Monthly Operating System Security Patches as provided by Microsoft and Apple.  Full Operating System upgrades are not included in monthly security patches.

 

Details

Article ID: 68820
Created
Wed 12/12/18 10:47 AM
Modified
Fri 1/25/19 4:32 PM