Active Directory Consolidation Oversight Model

1. Active Directory ConsolidationOversight Model ITMF October 6, 2011 John Salguero, PMP Stephanie Ayers, James Brannon, Jonathan Hardy, Jim Metcalf Shawn Ellis, Executive Sponsor 11

2. Active Directory Consolidation Agenda: • Current Environment • Vision • Strategy • Proposed Future Environment • Benefits to UGA • The Importance of an Oversight Model • ITIL V3 Adherence/Compliance • Change Management • Next Steps

3. Active Directory Consolidation • Current Environment • EITS currently manages multiple campus wide Windows Server Active Directory implementations in a mixed environment • A collection of Active Directory Domains • Each Domain in a separate Forest • Made of a collection of Windows 200x servers in a variety of physical locations

4. Active Directory Consolidation VISION EITS will have one centrally managed, feature rich Active Directory domain that will offer University-wide Identification, Authentication, and Authorization using an appropriately scaled hardware platform.

5. Active Directory Consolidation Requirements: • Scalability • UGA departments business process alignment • IT services and business functionality • EITS SLA • Governance Charter • Technology components • Security • Measurements and metrics • External services and components • Maintenance

6. PROPOSED FUTURE ENVIRONMENT • Consolidate 4 Active Directory Domains into one MSMYID.uga.edu Domains to be decommissioned are: • ADUGA.uga.edu • LABS.ad.uga.edu • AD.uga.edu

7. Strategy Fully featured vs feature rich: • What is your “wish list”of features? • What are the business reasons? • Are there any technical constraints? Service value  Cost  Time Frame

8. Benefits to UGA: • Increase the work efficiency by: • Providing better performance of the whole infrastructure • Unified user experience, unified processes (and support) and same level of service • Ease of administration inside the group • Managed risk and risk mitigation: • Enable EITS to build and deploy an AD continuity plan • A consistent security model will also be deployed across the group • The solution is designed to handle growth • as UGA is growing and/or interacting with other partners

9. The importance of an Oversight Model • Politics • Challenges • Technical Constraints • Business Requirements to be a key driver • Identify Potential Solutions

10. Oversight Model • Policies • Strategy • Measurements, metrics • Implement the strategy – UGA representation required • Communications • Invite UGA System Admins to participate • Migration strategy • Governance Kick off meeting • Governance Committee Creation • Communications Plan

11. Oversight Model Team Members: Future: Current: John Salguero, PMP EITS - IT Assoc. Director Stephanie Ayers, EITS – Lead Architect James Brannon, Franklin College – Systems Admin Jonathan Hardy, Franklin College – IT Sr. Manager Jim Metcalf Terry College – IT Manager

12. ITIL V3 Continual Service Improvement Model Text

13. Change Management • Ensures that changes are deployed in a controlled manner • Steps to handle the change, including handling issues and unexpected events. • Chronological order of steps, with any dependencies. • Responsibilities • Timescales and thresholds for completion. • Escalation procedures. • Minimizes risk and maximizes value.

14. ITIL V3 Adherence/Compliance ITIL maintains that there are three key requirements: • Accountability • Responsibility • Authority OWNERSHIP

15. Oversight Model - RACI MATRIX – ITIL V3 RACI – ITIL V3 – stands for: R = Responsible A = Accountable C = Consulted I = Informed

16. ITIL V3 Adherence/Compliance According to ITIL V3, there are four reasons to measure: • Validate previous decisions • Direct activities to meet targets • Justify that action is required • Intervene at right point and take corrective action

17. ITIL V3 Adherence/Compliance ITIL V3 – Activities might include: • Are customers satisfied? • Active Directory meeting service levels • Active Directory processes achieving desired results • Employee/Sys Admin. compliance • Services needed to be reviewed • Are customers satisfied?

18. Next Steps: • Form formal committee - Kick off Meeting • Gather business requirements – Continued • Fine tune the strategy • Formulate policies • Governance Model Committee • Implement Governance Model for AD • January 2012 • Migration Orientation • 2 times a months starting Oct. 19 • Multiple windows to be provided • Planned phased approach • High level documents for Active Directory • AD Testing Guidelines • Requirements for AD Admin Acct.

19. Next Steps - continued: • Migration Order/Schedule – dates Client by Client • 1st Migration – LABS to MSmyID • 2nd Migration – AD to MSmyID • 3rd Migration – ADUGA to MSmyID • Communication of results – ITMF and UGANet • Decommissioning Old AD Components • Strategy and Documentation to be developed • Dependent on more participation • Elicit more business requirements • Proposed Dates: • LABS – After Jan. 1, 2012 • AD – After Spring Break • ADUGA – After March 13, 2012

20. Active Directory ConsolidationOversight Model Questions???