1 / 17

Active Directory

Active Directory. Metropolitan State College of Denver Division of Information Technology. Redesign. HOW DID WE GET HERE?. Operating systems supported over the last 13 years. Novell Netware Banyan Vines Windows Server 3.11 Windows Server 4.0 Windows Server 2000 (Active Directory)

Download Presentation

Active Directory

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. Active Directory Metropolitan State College of Denver Division of Information Technology Redesign

  2. HOW DID WE GET HERE?

  3. Operating systems supported over the last 13 years • Novell Netware • Banyan Vines • Windows Server 3.11 • Windows Server 4.0 • Windows Server 2000 (Active Directory) • Windows Server 2003 (Active Directory)

  4. REASONS WHY THE PROJECT WAS INITIATED? TO ENHANCE AND SECURE ALL OBJECTS WITHIN ACTIVE DIRECTORY FOR EASE OF MANAGEMENT AND SUPPORT

  5. major issues addressed: • Separate Admin1 and Academic Domain • Students should not be accessing services from Admin1 • Create Internal DNS services • Our current DNS services should remain external • New DNS services will be for internal use only. • Organize OU structure • Role based security

  6. WHAT DOES OUR CURRENT ENVIRONMENT LOOK LIKE?

  7. Current Windows Infrastructure • We have a single forest with two domains

  8. WHAT ARE THE ISSUES WITH THE CURRENT DESIGN? • Implicit and mandatory 2-way domain trust • Admin1and academic are members of same forest • All users are considered trusted by the forest model • Students and faculty could access resources (printers, file shares, etc) if left with the default security. • Users from either domain can become members of security groups

  9. EXISTING RESOURCE MODEL

  10. EXISTING SECURITY MODEL

  11. WHERE ARE WE GOING FROM HERE?

  12. PROPOSED DESIGN • Building three new forests of single domains • Administrators and staff will be members of administrative domain • Faculty and students will be members of the student domain • Server based services will be contained in the services domain

  13. Proposed design Structure

  14. Proposed Resource model

  15. Organization Unit Model

  16. What’s Left to do? • Test environment = Completed • Build Production environment = Working on • Test • Create Migration Plan • User/Group migration • Printing • File Sharing • Workstation • SIDS • Citrix • Test • Create schedule for departmental move • Implementation

  17. Thank You

More Related