W2K Migration Status Report W2k Migration Working Group February 21, 2001.

Slides:



Advertisements
Similar presentations
Auditing Microsoft Active Directory
Advertisements

Establishing an OU Hierarchy for Managing and Securing Clients Base design on business and IT needs Split hierarchy Separate user and computer OUs Simplifies.
COMP091 OS1 Active Directory. Some History Early 1990s Windows for Workgroups introduced peer-to-peer networking based on SMB over netbios (tcp/ip still.
1 Preparing Windows 2000 installation (Week 3, Wednesday 2/25/2006) © Abdou Illia, Spring 2006.
How to Succeed with Active Directory Robert Williams, PhD CEO Secure Logistix Corporation.
70-294: MCSE Guide to Microsoft Windows Server 2003 Active Directory, Enhanced Chapter 1: Introduction to Active Directory.
Introduction to Active Directory
3.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 3: Introducing Active Directory.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.
1 Chapter 1 Introduction to Windows Server Two main goals for Net Admin Make network resources available to users Files, folders, printers, etc.
By Rashid Khan Lesson 4-Preparing to Serve: Understanding Microsoft Networking.
Hands-On Microsoft Windows Server 2003 Administration Chapter 3 Administering Active Directory.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.
3.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 3: Introducing Active Directory.
Understanding Active Directory
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 1: Introduction to Windows Server 2003.
A centralized system.  Active Directory is Microsoft's trademarked directory service, an integral part of the Windows architecture. Like other directory.
Group Policy in Microsoft Windows Active Directory.
Vikram Thakur Introduction to Active Directory Structure.
Lesson 17. Domains and Active Directory. Objectives At the end of this Presentation, you will be able to:
CougarNet Dennis Fouty, Ph.D. Associate Vice Chancellor, University of Houston System Associate Vice President, University of Houston Mary Dickerson, MCSE.
Overview of Active Directory Domain Services Lesson 1.
9.1 © 2004 Pearson Education, Inc. Lesson 9: Implementing Group Policy in Windows 2000 Server Exam Microsoft® Windows® 2000 Directory Services Infrastructure.
Directory services Unit objectives
Module 1: Introduction to Administering Accounts and Resources
MCTS Guide to Configuring Microsoft Windows Server 2008 Active Directory Chapter 3: Introducing Active Directory.
Working with domains and Active Directory
W2k Security At FNAL Jack Schmidt FNAL W2K Migration Working Group Chair April 16.
Windows 2003 Overview Lecture 1. Windows Networking Evolution Windows for Workgroups – peer-to-peer networking built into the OS Windows NT – separate.
Microsoft Active Directory(AD) A presentation by Robert, Jasmine, Val and Scott IMT546 December 11, 2004.
Chapter 6: Windows Servers
Security Planning and Administrative Delegation Lesson 6.
70-294: MCSE Guide to Microsoft Windows Server 2003 Active Directory, Enhanced Chapter 5: Active Directory Logical Design.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 1: Introduction to Windows Server 2003.
DIT314 ~ Client Operating System & Administration CHAPTER 5 MANAGING USER ACCOUNTS AND GROUPS Prepared By : Suraya Alias.
Windows 2000 Presented to CCC by Pat Schneider May 23, 2001.
ACTIVE DIRECTORY : AN INTRODUCTION The Network Team Knox County Schools.
Module 7 Active Directory and Account Management.
11.1 © 2004 Pearson Education, Inc. Exam Designing a Microsoft ® Windows ® Server 2003 Active Directory and Network Infrastructure Lesson 11: Planning.
Active Directory Harikrishnan V G 18 March Presentation titlePage 2 Agenda ► Introduction – Active Directory ► Directory Service ► Benefits of Active.
Active Directory Maryam Izadi. Topics Covered NT Vs 2000/2003 Active Directory LDAP MMC.
1 Windows 2008 Configuring Server Roles and Services.
 Identify Active Directory functions and Benefits.  Identify the major components that make up an Active Directory structure.  Identify how DNS relates.
Page 1 Active Directory and DNS Lecture 2 Hassan Shuja 09/14/2004.
1 Group Policies (Week 11, Monday 3/19/2007) © Abdou Illia, Spring 2007.
Hands-On Microsoft Windows Server 2008 Chapter 4-Part 1 Introduction to Active Directory and Account Manager.
CD W2K Desktop Migration Jack Schmidt 12/5/2001. W2K Migration Plan 1. Migrate users/desktops to provide kerberos authentication. Resources still in NT4.
Module 1: Introduction to Administering Accounts and Resources.
Introduction to Active Directory in Windows 2000/2003.
OVERVIEW OF ACTIVE DIRECTORY
Introduction to Active Directory
Configuring, Managing and Maintaining Windows Server® 2008 Servers Course 6419A.
Active Directory. Computers in organizations Computers are linked together for communication and sharing of resources There is always a need to administer.
CEG 2400 Fall 2012 Directory Services Active Directory Tree Domain.
Unit 7 ITT TECHNICAL INSTITUTE NT1330 Client-Server Networking II Date: 2/3/2016 Instructor: Williams Obinkyereh.
7.1 © 2004 Pearson Education, Inc. Exam Designing a Microsoft ® Windows ® Server 2003 Active Directory and Network Infrastructure Lesson 7: Planning.
MCSE: Windows Server 2003 Active Directory Planning, Implementation, and Maintenance Study Guide, Second Edition (70-294) Chapter 1: Overview of the Active.
9.1 © 2004 Pearson Education, Inc. Exam Designing a Microsoft ® Windows ® Server 2003 Active Directory and Network Infrastructure Lesson 9: Planning.
Meeting Maker – Computing Division Scheduling Calendar Jack Schmidt, John Bellendir June 2 nd, 2005.
PC Manager Meeting February 23, Today Updates Next Meeting Windows Policy Security This Month: Lessons Learned: Building the Symantec Patch (Andy.
W2K Migration Experiences Jack Schmidt Windows Policy Committee.
Module 1: Introduction to Administering Accounts and Resources
(ITI310) SESSIONS 6-7-8: Active Directory.
Active Directory Administration
Objectives Differentiate between the different editions of Windows Server 2003 Explain Windows Server 2003 network models and server roles Identify concepts.
Unit 3 NT1330 Client-Server Networking II Date: 1/6/2016
Unit 7 NT1330 Client-Server Networking II Date: 7/26/2016
Windows Server 2008 Administration
ACTIVE DIRECTORY An Overview.. By Karan Oberoi.
Security Planning and Administrative Delegation
Presentation transcript:

W2K Migration Status Report W2k Migration Working Group February 21, 2001

W2K Migration Working Group Objective- “Provide Windows users with a secure environment to easily share resources across the site and with other labs.”

W2K Migration Working Group Meetings- Every Wednesday from 1-3:30pm since October of Training- Implementing Active Directory and Securing Windows 2000 Server. Web Page-

Members (Major NT Domains) BD – Brian Drendel BSS – Roger Fahnestock, Tom Ackenhusen OSS – Ken Fidler, Al Lilianstrom, Andy Romero, Jack Schmidt D0 – Greg Cisko Networking – Vyto Grigaliunas, David Tang TD – John Konc Successful Migration to W2K requires communication and planning!

Present Structure BSS TDFNALD0 D0Level3DMACS BDControls BEAMS Controls Systems CDF,ESH,F ESS,LS, PPD, VMS File Servers, and Web trust ESE

Child Proposed Structure (Not Complete) Root win.fnal.gov Child OU fermi.win.fnal.gov Child OU bss.win.fnal.govbdcontrols.win.fnal.gov OU computer print queue groups user Admin

Basic Concepts Active Directory- Directory service for W2K. Hierarchical directory that stores information about objects ( Users, Groups, Files, Printers, Computers) on the network. Objects- All objects have attributes that provide descriptive information about the object. A user’s Name is an attribute. Domain- Boundary for an Active Directory. A group of computers that share a common directory database. Domains designate specific security policies and administration. DC- Domain Controller. There are no PDC/BDCs. Domain controllers operate as equals and replicate information to each other. OU- Organizational Units. Container objects designed for managing users,groups, computers and other resources in a domain. Primary purpose is to allow delegation of administrative tasks. Microsoft recommends using OUs to mirror a company’s organizational structure.

Child Proposed Structure (Not Complete) Root win.fnal.gov Child OU fermi.win.fnal.gov Child OU bss.win.fnal.govbdcontrols.win.fnal.gov OU computer print queue groups user Admin

Domain Proposal Domain designs were discussed: –Concensus toward root domain with sub domains and OUs: win.fnal.gov root domain (reviewed by committee) fermi.win.fnal.gov – general domain for desktops bss.win.fnal.gov – separate because of audit requirements bdcontrols.win.fnal.gov – BEAMS control systems. Tighter security than general domain.

Proposal Benefits Root domain provides central place to manage accounts (need to verify) Root domain provides site security policy OUs provide stricter security policies Child domains broken into OUs: –Top level divisions/sections/major experiments –Organizational OUs can be defined by OU administrator –OUs can be configured to be seen only by members. Design provides easier access to site resources Design provides tighter control of DDNS for Networking (machines must register in W2K domain)

Domain Proposal Exceptions D0-Online.fnal.gov –Controls system boxes. Need to be tightly controlled. –No real need for Active Directory or access from outside domains.

Present Status Test domain structure in place. Defining tests –Strong Authentication Issues –Identify Applications –Defining Policies –Examine OU resource access Design Note development

Migration Issues User Account Cleanup- –Possibility of duplicate accounts –Identify dis-usered accounts –Interface to CNAS for new accounts? Hardware –Verify systems meet OS requirements –Remove inactive computer accounts Software –Licensing (buying new os?) –W2K Certification

Timeline Feb 2001 –Examine 3 rd party Tools –SA testing –Domain testing Mar 2001 –Domain testing –SA testing –design note draft Apr 2001 –Release design note to Divisions

Timeline June – Aug 2001 –Create pilot domain –Limited production tests Sept 2001 – Begin Domain Migration Nov 2001 –Review progress

Concerns How to handle standalone systems? –Visitors – provide access to printers –Lab – must have a user account in W2K domain to access resources. Should standalone domains be allowed? Strong Authentication