configuring and administering server

7/25/2019 Configuring and Administering Server

1/100

Maichew Polytechnic college

Ver

HARDWARE AND NETWORKSERVICING

LevelIII

LEARNINGGUIDE# 1

Unit of Competence:Confgure andAd!n!"rae Server

Module Title: Confgur!ngand

Ad!n!"er!ng

Server

Un! Code ICT HNS$ %$ 111%

Nominal Duration:1%& Hr"'

Unit of CompetenciesCon(!r "erver ")e*!(!*a!on

Ver!(+ "erver *o)a!,!l!+ and !ner-o)era,!l!+

Con(!gure and e" "erver


2/100


TTLM Development Manual

Level

Configuring and Administering Server Page 1 of .%


3/100

Ver


General O,/e*!veA 0e end o( 0e odule 0e learner !ll ,e a,le o2

!dminister" con#gure and test a server

according to $usiness needs and technical

re%uirements&

Understand 'ingle and multiple processors" memo

Dis( drives and internal)e*ternal storage devices&

Determine 'erver applications +such

as we$ application" DN'" etc&,

'erver specification for different applications

Determine server speci#cations

Determine compati$ility and opera$ility

Con#gure a server as re%uired $y technical

re%uirements


4/100


TTLM Development ManualLevel

Configuring and Administering Server Page & of .%


5/100

Ver


LO12 Con(!r Server S)e*!(!*a!on

Objective

This module will help you to confirm server specification within an information technology

environment and you will also learn about:

Confirming server design with client

dentifying server hardware and software specifications

dentifying and evaluate server resources

Compiling system re%uirements

Int r o d uct ion-hat is a server.De(!n!!on: ! networ( server is a computer designed to process re%uests anddeliver data to other +client, computers over a local networ( or the nternet&

This resource will help you to confirm server specification within aninformation technology environment&

Confirm server design with clientThe first step in $uilding and configuring a server is to confirm that

the information a$out the pro/ect is correct" current and that theclient agrees with documented specifications and design&

0ou will need to reconfirm with the client

o The role of the server"

o 1ow it will function with the remaining T infrastructure" and the

re%uired configuration&

2unctional re%uirements

3un*!onal re4u!reen" capture the intended $ehaviour of the system&This $ehaviour may $e e*pressed as a service" tas( or function that thesystem is re%uired to perform&

The functional re%uirements documents are the 3$lueprint4 for the pro/ectimplementation


Configuring and Administering Server Page $ of .%


6/100

sdafsdfds

Ver


Requirements issues

5ne of the first and most important activities to get on whenconfirming server specifications is to confirm client needs and toensure that they ac(nowledge that re%uirements have $een capturedcorrectly and sign6o7 on the re%uirements

'o one of the tas(s in confirming client needs is to do*uen the

re%uirements& This may include identifying or clarifying

The $usiness case

-hat the client considers the pro/ect4s main o$/ectives are" including the

services that are to $e performed -hat T infrastructure is already in place

8asic specifications

Con9icting or overlapping re%uirements

Maintenance and $ac(up re%uirements

8andwidth issues that may a7ect the pro/ect ole de#nition of parties involved

The nature of the data +eg te*t" multimedia,

'ecurity needs +eg levels of user access and privileges,

!vaila$le support resources

Costing&

Functional requirements specification

The functional specification descri$es what the system will do" as opposedto how it will $e done& This distinction is important $ecause

The client may not $e interested in the details of how a function

is implemented" and the technical details may simply causeconfusion for the client&

The implementation details may need to change during the

design and development of the pro/ect&

0ou don4t want to have to negotiate changes to the functional specificatio

/ustto change details of

implementation&

The technical specification for large pro/ects will $e detailed in

a separate document" and you should not entangle one withthe other&

User requirements

1ow many users are e*pected to use the system.

1ow many people will $e utilising the solution at one time.

-here the users will $e located +eg overseas" interstate or at home.

Technical requirements

-hat types of computers)operating systems will the users operate.


7/100





8/100

Ver


!re their des(tops all the same.

-hat $andwidth restrictions occur presently.

-hat security +login, will they need.

-hat $ac(up policies need to $e in place.

-ho will have administration rights.

-hat will the $usiness do if the system fails at any stage. -ho is the pro/ect sponsor.

-hat does management e*pect the system will do and won4t do.

Hardware

Compati$ility: will the solution wor( with e*isting systems.

'upport for proprietary formats: will the e*isting systems and

architecture support all types of data. -ill the new system $e supported $y e*isting resources within the company

-hat funding is availa$le for new hardware.

-hat is the $ac(up strategy. 1as this $een costed. Does the system need to $e redundant" load $alanced or clustered.

-ill there $e time delays to purchase and install hardware.

-ho will $e $uilding the server.

!re there other pro/ects that you may $e a$le to share hardware costs with

Software

-hat is the true cost of the software.

!re there licensing issues. !s the system is in development" should

you pay for all the licensing now or when the system is in live

mode. Can the software $e licensed for use $y multiple users who use it

on di7erent machines. +Concurrent licensing, 1ow long has the software $een on the mar(et for.

-hat happens if the software company $ecomes insolvent. -ho supports i

-ho owns the source code.

-hat happens if the source code is modified. -ho supports the product the

Does the solution wor( with all other company software systems.

f we$6$ased" does the solution function on all common $rowsers.

f security is a concern" can the software $e delivered in a 3loc(ed down4

format. Does the software support all file formats.

s the software easy to use" or are there ma/or training issues)costs.

'tage sign6o7 ! pro/ect is divided into many stages& ;ach stage will have entry and

e*it criteria that must $e met $efore the pro/ect can progressfurther&


9/100





10/100

Ver


!t the planning stage" the owner of the system or pro/ect steering

committee must sign6o7 on stage e*it criteria" which would includeserver design documentation& This then would trigger the start of thene*t stage of the pro/ect the development stage&

The e*it criteria will normally state that the following items have

$een identified and agreed to: 'erver platforms

5perating systems

!pplications

1ardware and software limitations

Client and developer responsi$ilities

Privacy issues

nitial timelines

8udget

'tate and federal regulations&

dentify specifications5nce re%uirements have $een defined and client needs are clarified" it4stime to start thin(ing a$out identifying products that fit the solution& n thiscase" we need to focus on the possi$le server solutions& emem$er: a"erver consists of

1ardware

'oftware

Networ( connections&

There are di7erent types of server designs that need to $e consideredwhen identifying e%uipment& There are multiple server architectures tochoose from" including

Mainframe architecture

2ile sharing architecture

Client)server architecture

-e$ $ased architecture

Thin client architecture

8lade architecture&

dentify vendor architecture

;ach vendor in the mar(etplace supports specific platforms and server

architecture& -hen selecting e%uipment for the server" you will need to

consider the hardware andsoftware platforms from each vendor&

Hardare)la(or refers to the hardware components that ma(e upthe computer system&


11/100



Configuring and Administering Server Page . of .%


12/100

Ver


"o(are)la(or refers to the operating system or programminglanguage developed for the hardware& There are de#ned termsused in the T industry to descri$e the types of platforms" including

o -intel

o

Lintelo Mac" Macintel

o Mainframe

o UN ensure that there is a suita$lee*pansion slot for installation of the e*pansion card&




15/100

Ver


'oftware

-hen evaluating software" the cost of the product will $e determined$y how many licences are re%uired&

! license is a legal agreement to use software" and the e*act terms of the

agreement vary& !n important part of managing software licences is to

purchase the right types and mi* oflicences& 'oftware licenses are o7ered as follows:

! site licence for a num$er of computers at a particular o7ice

! licence assigned to a specific computer

! licence assigned to one specific user&


16/100





17/100

Ver


Sel(-C0e*:

@& -hat is a server and what advantages do a server gives.

A& -hat is system re%uirement.

B& List some of the hardware and software re%uirement consideration $efore

installing server operating system

& Define hardware and software plat form

& -hat are the common hardware server technologies on.

6. A cross-platform program is one that runs _.

a. only on one operating system c. the same on multiple operating systems

b. differently on every operating system d. differently on one operating system


Configuring and Administering Server Page 1% of .%


18/100

Ver


LO2. Verify server compatibility and inter-operability

En"ur!ng Hardare Co)a!,!l!+

Networ(ing is hardware6dependent" and not all hardware products are

compati$le&

n order for two computers to communicate" they must use the same protoco

Computer hardware raises similar issues& n some instances" two

pieces of hardware simply canEt communicate with each other& 2or

e*ample" consider an analogy to automo$ile parts: two parts might

loo( ali(e and $e a$le to perform the same function" $ut each is

designed to wor( in a di7erent car&

This lesson e*amines the issue of ensuring hardware compati$ility and

what you can do to resolve incompati$ilities&

!fter this lesson" you will $e a$le to:

Determine hardware compati$ility issues&

Ta(e steps to avoid unnecessary hardware pro$lems&

W h e n H ardware Is a P r ob le m

1ardware incompati$ilities are a fact of life&

n todayEs computer industry" hundreds of manufacturers develop

hardware and software&

;ach developer has a uni%ue perspective on the $est way to accomplish

the same tas(" and each will provide a uni%ue solution& Copyright and

patent issues further complicate the matter&

;valuating and selecting hardware is a ma/or part of planning

for networ( implementation&

t is li(ely that you will have to create a networ( out of an e*isting collection

of hardware& n such cases" the li(elihood that pro$lems stemming fromincompati$le hardware will arise is very high& t is sometimes more cost6

effective to discard the old hardware and

start over&

The most common incompati$ilities occur $etween hardware and software&

Changing or upgrading a computer or networ( operating system can lead to

ma/or pro$lems&


19/100


20/100

Ver


R e ad ing t he D o cumen t a tio n

ead all the documentation a$out the products involved& 0our hardware

or software might have a recurring pro$lem or might conflict with

another product&

2re%uently" the manufacturer will document these con9icts and provide a fi*&

f you do not find the solution in the supplied documentation" you might

contact the manufacturer of the product and as( for undocumented con9icts&

'earch the manufacturerEs -e$ site for additional information&

De t e ct io n during In s t alla tio n

-hen you install a new computer or networ( operating system" your

computer will usually attempt to detect the hardware in the system during

the installation process and load the appropriate drivers for it&

Chec( the list of detected hardware and ensure that it matches what is

already in the machine& f you are installing NovellEs ntranet -are" for

e*ample" the install utility will automatically scan your computer for

hardware such as hard dis(s" CD65M drives" and NCs& f the devices are

recogni?ed" the appropriate drivers will then $e loaded for the recogni?ed

devices&

C he c k ing M inimum Re q uir e m e n t s

!s a first step $efore you install" ma(e sure that you e*ceed the minimum

re%uirements for the resources in the computer& These resources include

processor speed" memory" and dis( space& Ta$le lists some minimum

hardware re%uirements for server AFFB

Ta$le @ Minimum 1ardware e%uirements for server AFFB

Re4u!reen

SandardEd!!on

Ener)r!"eEd!!on

Daa*enerEd!!on

We, Ed!!on

Minimum CPU

'peed

@BB M1? @BB M1? for

*GH6$asedcomputersIBBM1? fortanium6

FF M1? for

*GH6$asedcomputersIBBM1? fortanium6

@BB M1?

ecommende

d

F M1? IBB M1? IBB M1? F M1?

Minimum!M

@AG M8 @AG M8 @A M8 @AG M8


21/100



Configuring and Administering Server Page 1& of .%


22/100


23/100



Configuring and Administering Server Page 1$ of .%


24/100

Ver


LO3.Confgure and e""erver

O,/e*!ve"

Descri$e characteristics common to all N5's +networ( operating systems,

Compare and evaluate N5's to select the right one for your Networ(

nstalling 5perating 'ystem

Configuring Domain Controller

'pecifying Computer ole

Configure !ctive Directory Directory 'ervice

Configuring DN' 'ervers

Configuring DN' clients

Testing DN' Configuration

Trou$leshooting DN' Configuration

Configuring D1CP 'ervers

Configuring D1CP clients

Testing D1CP Configuration

Trou$leshooting D1CP Configuration

W0a !" neor: o)era!ng "+"e;Networ( operating systems typically are used to run computers that act asservers& They provide the capa$ilities re%uired for networ( operation&Networ( operating systems are also designed for client computers andprovide functions so the distinction $etween networ( operating systemsand standalone operating systems is not always o$vious& Networ(operating systems provide the following functions:

Confgure "erver

Configuring server hardware and software means setting up the way thehardware and software operates to suit the T environment andorganisational or user re%uirements&

Jenerally" server hardware is configured $efore the server operating systemis installed or afterwards" if hardware components in an operating server are$eing changed or added& 'oftware may $e configured when installed" as partof the installation process" or afterwards" if a default installation has $eenperformed&

'ome specific considerations for configuring server hardware and softwareconfiguration follow&

Server 0ardare *on(!gura!on

'erver hardware configurations will depend on what components ma(e

up the server& Configurations you may need to consider include those for


25/100


26/100

Ver


storage

$oot se%uences

specific devices

edundant components&

Server "o(are *on(!gura!on

Configurations for server software depend on the purpose or functionof the server& Jenerally" a server may $e configured for one or more ofthe following roles:

An a))l!*a!on "erver which runs specific software applications forend users" such as a server that runs a central 5racle Data$ase that isaccessed $y users across an organisation&

A "orage "erver which provides a central storage place fordata that can $e accessed $y computer users around a networ(&

A neor: "erv!*e" "erver which provides specific services such asprint" user authentication and authorisations" dynamic hostconfiguration protocol +DHC


27/100





28/100

Ver


-hen complete" the testing process should verify that all the tests

performed support the acceptance $y the user of the totallyintegrated product&

Tas(s performed during stress and load testing of an integrated platform incl

o ;sta$lishing testing acceptance criteria and procedureso Performing test events

o Diagnosing test results

o esolving software defects&

Test events are designed to esta$lish operational levels at which the

new server starts to fail and to measure how it performs underoverloaded conditions& The failure and performance levels arecompared with the acceptance criteria and are either accepted orre/ected&

Test events aim to reveal failures such as

o Total system crashes

o 8ottlenec(s in interfaces $etween components

o Data corruption

o process overloading

o Performance degradation $elow a usa$le level&


29/100


30/100


31/100





32/100

Ver


o !pplications in9uence: Type of application

esources used

Processing $urden

o Vendor reputation re%uirements

1igh %uality" dependa$ility" e*cellent technical support elia$le server

o 'pend as much as necessary

Component failure: widespread e7ectsCl!en Su))ormportant N5' function

!llows efficient communication" resource sharingN5' client support

tas(s

Creating and managing client accounts

;na$ling clients to connect to the networ(

!llowing clients to share resources

Managing clients4 access to shared resources

2acilitating communication $etween clientsCl!en>Server Coun!*a!on

Logon process

edirector

ntercepts re%uests" determines

where to handle

2ile access protocol -indows


33/100





34/100


35/100





36/100

Ver


UNI? and L!nu@

' a Popular N5'

o Provide resource sharing

o 5lder UN< developed in @H

UN< preceded" led to TCP)P protocol suite development

o Most nternet servers run UN

configuring and administering server

Documents