Cornell University
Tuesday June 23, 2011
Version 1.2Final
Prepared by
David Thompson
Infrastructure Consultant
David.Thompson5555@idea.com
Revision and Signoff Sheet
Change Record Date | Author | Version | Change reference | 06/14/11 | David Thompson | 1.0 | Initial Draft | 06/23/11 | David Thompson | 1.1 | Internal Review | 06/30/11 | David Thompson | 1.2 | Final Version | | | | | | | | |
Reviewers Name | Version approved | Position | Date | Chris Lavelle | 1.1 | | 06/26/2010 | | | | | | | | | | | | |
Table of Contents 1. Introduction 5 1.1 Executive Summary 5 2. Intended Audience 6 3. Migration Overview 7 3.1 Migration Challenges 7 3.2 Key Features of Quest Migration Manager for Active Directory 8 3.3 Migration Process Overview 10 3.4 Team Composition 10 4. Current Active Directory Infrastructure 12 4.1 CORNELL.EDU 12 4.2 Additional Forests/Domains 12 4.3 Development/Lab Environment 13 5. Areas of Remediation 14 5.1 Ongoing Virtualization and Exchange Migration Projects 14 5.2 Existing Microsoft SharePoint Deployments 14 5.3 Existing Microsoft System Center Configuration Manager Deployments 14 5.4 Existing Microsoft SQL Server Deployments 14 5.5 Existing Microsoft Windows Server Update Service (WSUS) 14 5.5 Certificate Services 15 5.6 Centralized Backups – Tivoli Configuration Manager 15 5.7 Schema Extensions (Biometrics) 15 5.8 Workstation Rename Requirement 15 5.9 RADIUS – Authentication Proxy Policy 15 5.10 Deployed VPN Solutions 15 5.11 Stand-Alone Workstation Migrations 15 6. Planning Recommendations 17 Appendix A: Sample High Level AD Migration Project Plan 18
1.Introduction
Cornell Universityis moving towardestablishing a rationalized IT architecture which will provide anEnterprise Shared Services platform for common services such