Analyzing an Existing Infrastructure

Revision no.: PPT/2K403/02

Analyzing an Existing Infrastructure

(70-297)


© CMS INSTITUTE, 2004. All rights reserved. No part of this material may be reproduced, stored or emailed without the prior permission of Programme Director, CMS Institute

2

Lesson 1: Analyzing the Company

• Geographical Considerations

• Information Flow

• Analyze the Current Administration Model

• Future Plans



3

Geographical Considerations

• Local Model

• Regional Model

• National Model

• International Model

• Branch Offices

• Subsidiary Offices



4

Recording Your Analysis

• In what cities does the company maintain offices ?

• Is an office a major corporate headquarters, a branch office, or

a subsidiary office?

• How many users are at each location?

• How are the locations connected?

• How is the company charged for bandwidth?

• If the connections cross international boundaries, are there

special considerations such as tariffs or export laws?

• Estimating Current WAN Connection Usage



5

Information Flow

• What sorts of documents do their departments create? What applications do they use?

• Who are those documents for? Are they stored and accessed only by the people who create them? Are they routed to others in the division or in the company? Are they stored and accessed by others? How many others? Are they printed?

• Are documents made public over the Internet or by other means? If so, are the users responsible for publishing the information or is someone else? Who?

• Where are those documents stored?• Is information stored in a database? What kind of information

and what kind of database? How many users access it? Where is the database located?



6

Analyze the Current Administration Model

• Make a simple organizational flowchart that shows the members of the administrative staff and their relative positions.

• If the company uses a decentralized model, make a chart for each location.

• Identify the person (or people) who govern the IT budget. Find out when the budget is determined and what aspects will affect your project?

• If any services are outsourced, list the service, the vendor, and the cost.

• Describe how IT decisions are made. Are all decisions made from the top? Is there a certain amount of autonomy granted throughout the chain of command? If so, what are the limits of this autonomy? Basically, what you are after is finding out who makes what decisions in regard to changing and servicing the network.



7

Future Plans

• One of the greatest features in Windows 2003 is its

scalability—its ability to allow for growth in size without a

corresponding growth in network overhead.

• Your plans should allow for changes in a company’s focus or

planned acquisitions.

• You should also account for changes in location, including

adding extra locations, and changes to the workforce.



8

Lesson 2: Analyzing the Existing Network Topology

• Network Environment

• Servers and Workstations

• Analyzing Performance Requirements



9

Network Environment

• Routers and Other Networking Equipment

• IP Addressing



10

Servers and Workstations

• The name of the computer, its current IP configuration, and its

location on the network.

• Brand and model of the computer.

• The brand and model of the motherboard, along with the current

basic input/output system (BIOS) revision.

• The processor type and speed.

• The amount and type of memory.

• The size, type, and brand of hard drives and hard drive

controllers.



11

Contd.

• Brand and type of network adapters.

• Brands and model numbers of any attached peripherals. Be sure

to include the driver or firmware version currently in place.

• Any services running on the system.

• Installed software.

• Shared folders or printers configured on the system. Include the

rights and permissions granted to users and groups as well.

• Users that access the system.



12

Analyzing Performance Requirements

• Address Unresolved Problems

• Testing Current Performance



13

Lesson 3: Analyzing the Existing Directory Structure

• Analyze an Existing Windows 2000 Infrastructure

• Analyze an Existing Windows NT 4.0 Infrastructure

• Windows Server 2003 Functional Levels



14

Analyze an Existing Windows 2000 Infrastructure

• Current Domain Model

• Current Organizational Unit Structure

• Current Site and Domain Controller Structure



15

Current Domain Model

• The full name of the domain

• Which domain is the root domain of each tree

• Which domain is the root domain of the forest

• Any shortcut trusts that have been created

• Any forest trusts that link to other forests

• Any one-way trusts linking to Windows NT 4.0 domains



16

Current Organizational Unit Structure

• The objects contained in the OUs

• How permissions are assigned for administration of the OUs

and the objects it contains.

• Any Group Policy Objects linked to the OU.



17

Current Site and Domain Controller Structure

• Whether the server performs other domain or forest roles in

addition to being a domain controller.

• Whether the server is a Global Catalog server.

• Whether the server is a bridgehead server used for replicating

Active Directory information to other sites.

• You may also want to list servers that are not domain

controllers, but that provide other vital services, such as DNS,

DHCP, Web, or mail services.



18

Analyze an Existing Windows NT 4.0 Infrastructure

• Advantages of Keeping Windows NT Domain– All domain objects upgrade to the Active Directory model.

– Users keep their existing passwords and profiles.

– The implementation takes less time and requires fewer resources.

– System security policies are retained.

• Information Required– Domain Name

– Names of Servers in the domain

– Names of Domain Controllers in the domain

– Trust Relationships between domains



19

Windows Server 2003 Functional Levels

• Domain Functional Levels– Windows 2000 Mixed

– Windows 2000 Native

– Windows Server 2003 Interim

– Windows Server 2003

• Forest Functional Level– Windows 2000

– Windows Server 2003 Interim

– Windows Server 2003



20

Practice: Analyze the Existing Directory Structure

• Analyze the Existing Directory Structure



21

Design & Published by: CMS Institute, Design & Development Centre, CMS House, Plot No. 91, Street No.7,

MIDC, Marol, Andheri (E), Mumbai –400093, Tel: 91-22-28216511, 28329198

Email: [email protected]

www.cmsinstitute.co.in

Analyzing an Existing Infrastructure

Documents

Transcript of Analyzing an Existing Infrastructure