3312 A Look Inside Microsoft Windows 2000 And Exchange 2000 Deployment

1
A Look Inside Microsoft Windows 2000 And
Exchange 2000 Deployment Fearon BrownSr.
Program ManagerInformation Technology Group
Microsoft Corporation
2
(No Transcript)
3
Objectives

• Background on Microsofts environment
• Examine Microsofts internal deployment strategy
  for Windows 2000 and Exchange 2000
• Share Best Practices
• What Challenges were Faced
• What Lessons were Learned

4
Microsoft Worldwide

• Information Technology Group
• Core Infrastructure
• Business Units

5
Windows NT 4.0 Domain Architecture
Master User Domains (MUD) (1st Tier domains with
bi-directional trusts)
South Pacific
North America
Far East
Southern Europe
South America
Northern Europe
Central Europe
Middle East
SYS- WIN4
Redmond
Africa
MSNBCI
6
Pre-AD Directory
7
Exchange 5.5 Topology
8
Our Challenges

• Maximize availability, manageability,
  scalability
• Deploy core infrastructure while it is being
  developed
• Windows 2000
• Active Directory
• Exchange 2000

9
Multi-Pronged Approach
Eating our own dogfood
Making the products part of the IT utility
IT Showcase
10
What Is Dogfood?

• Production area run by Exchange development team
• Early production deployment by ITG

11
Exchange Dogfood

• Hosts
• All of Exchange team
• Parts of Office and Windows 2000
• 6,000 users
• Exchange 2000 in production
• 700 users running naked
• Weekly software upgrades
• Direct developer involvement
• Models customer and ITG scenarios

12
ITG Early Deployment

• Hosts
• Initially volunteers
• Ultimately the whole company
• Currently focused on
• Windows 2000
• Active Directory Connector
• Exchange 2000
• JDP/EA customer
• Supported by PSS

13
Multi-Disciplinary team
ITG Project Teams
Windows 2000 Development Team
ZAW
Workstation
Server, Active Directory, Security Administration
Applications
Networking
Exchange 2000
Microsoft Technical Services
Exchange Development Team
14
Getting Started

• Business drivers are core
• Recognize dependencies
• Design the environment
• Forest / Trees / Domains / OUs
• Security
• Administration
• Topology

15
Windows 2000Deployment Phases

• Phase 1 - Deployment Viability
• Phase 2 - Production Domains
• Phase 3 - Scalability
• Phase 4 - Ship Criteria
• Phase 5 - Infrastructure Complete

16
Exchange 2000Deployment Goals

• Scalability in Redmond data center
• Collaboration platform
• OWA Instant Messaging
• Anytime and anywhere access

17
Internal Deployment Status

• Windows 2000
• Over 39,000 users on Windows 2000
• Master user domains upgraded
• Three domains in native mode
• Active Directory Connector
• Keeping 100,000 objects syncd
• Exchange 2000
• Entering production this week

18
Defining The Enterprise

• Domain namespace and directory
• Leveraging the platform
• Integration with Exchange

19
Windows 2000 Domains
corp. microsoft.com
Ireland
Denmark
Australia
UK
France
Japan
20
Organizational Units

• Global OUs for All Domains

ar
itg
Sales
Ops
OCU
IDCU
South America
21
AD Application Integration
User Accounts
SAP
HR Admin
Windows 2000 Active Directory
Feedstore
SQL
External Partners
Partner Admin
datastores
Base AD Admin Tools
Exchange
22
What Is IntelliMirror?Change Configuration
a.k.a.
Benefits
Feature
User Data
MyDocs Folder
My data and documents
Management
Redirection
follow me!
Software Installation
App Publishing
IntelliMirror
My software follows me!
and Maintenance
Assignment
Change and Configuration Management
User Settings
Roaming User Profile
My preferences follow me!
Management
RISAPAA
Administrators can enable
Remote OS Installation
AppSetup Retirement
remote installation!
23
Active Directory Connector

• One Connection Agreement per Windows 2000 domain
• One-way agreements until AD becomes master

ADC
Active Directory
Site A
Connection Agreement
Site Connector
Connection Agreement
Site B
24
Whats Next For ITG?

• Planning
• GC/DC placement
• Routing groups
• Real Time Collaboration components
• Deployment
• Finishing Windows 2000
• Ramping up Exchange 2000
• Stay tuned

25
Questions To Ask Yourself

• Who owns the Directory?
• What will it be used for?
• Who is responsible for operations?
• How will you administer accounts?
• How will policy be used?
• What should your topology be?

26
Planning, Planning, Planning Training, Training,
Training

• Enterprise solutions affect the enterprise
• Anything that extends the production schema is
  not a pilot or test
• Lots of time spent thinking through our designs

27
Create Your Own Example How Did ITG Do It?

• IT Showcase
• Early production experiences
• Process oriented white papers
• A way, not the only way

28
Discussion
29
(No Transcript)