Web Development and Database

Administration
LEVEL II

Module Title: ADMINISTRATE NETWORK AND HARDWARE

PERIPHERALS

Course Code: EIS WDDBA2 03 1221

Unit of Competence: ADMINISTRATE NETWORK AND HARDWARE
PERIPHERALS

Module Title: ADMINISTRATING NETWORK AND HARDWARE

PERIPHERALS

LG Code: EIS ITS203 0811

TTLM Code: EIS ITS2M03 0811

LEARNING OUTCOMES

At the end of the module the learner will be able to:

• Confirm requirements of client Obtain required peripherals

• Connect hardware peripherals

• Install peripherals to a network Configure peripheral services

• Administer and support peripheral services

• Maintain peripherals and fix common problems
• Use and maximize operating system

• Support input and output devices

MODULE CONTENTS

1. Client peripheral requirement

1.1. Identify client peripheral requirement

1.2. Documenting and verifying
1.3. Obtain and store
2. Connecting hard ware peripherals
2.1. Plan installation scheduling

2.2. Replacing old peripherals

2.3. Configure a newly installed peripheral

2.4. Testing installed peripheral

3. Install network peripherals

3.1. Planning network peripheral location

3.2. Connecting peripheral to the network and to the computer safely

3.3. Testing connected network peripheral

4. Configuring peripheral services

4.1. Installing software

4.2. Configuring security on accessing peripherals

5. Administer and support peripheral devices

5. 1. Prioritizing peripheral access

5.2. Configuring network settings

5.1.1. Create maintenance procedure

5.1.2. Create usage logos

5.1.3. Create cost centre usage statistics

6. Maintain and solve common peripheral problem

6.1. Scheduling and applying preventive maintenance

6.2. Replacing consumable components

6.3. Identify failed peripherals or services

6.4. Troubleshooting defective peripherals

7. Using and maximizing operating system

7.1. Configuring operating system

7.2. Installing application software

7.3. Upgrading application software

7.4. Uninstalling application software

7.5. Using graphical user interface

7.6. Customizing graphical interface

7.7. Using command line interface

8. Support input/output devices

8.1. Identifying input/output devices

8.2. Setup and check input/output devices

8.3. Installing drivers

8.4. Testing input/output devices

Administrate network and hardware peripherals

1. Client Peripheral requirement
1.1. Identify client peripheral requirement

1.
A.

B.
C.

D.

E.
2.
3.
2. Connecting hardware peripherals
2.1. Plan installation schedule
Purpose
Installation Plan and Record covers the installation of the hardware peripherals and related
support services to assist the client in the installation. The purpose of the Installation Plan
and Record document is to provide a reference for resources working on the project at any
time and for any duration.
The Hardware Specialist is responsible for the development of the Hardware Installation Plan; the
specialist can use the following inputs while preparing the plan:

System configuration
• Hardware configuration
• Hardware specification
• Existing hardware layout
• Existing hardware configuration

2.2. Replacing peripherals

Note: Know the reasons for and implications of installing hardware components
Reasons for installing hardware components
There must be a good reason for an organization to decide to spend money on installing new hardware
components. The benefits should outweigh the costs.
Powerful, newly developed components are expensive, so there always needs to be a balance
between how much performance is needed and how much can be spent. Good reasons for installing
new hardware components include:
 Routine maintenance
 Fault repair
 Upgrade
Routine maintenance
Routine maintenance is where old hardware is replaced before it wears out or breaks down. The
most powerful reason for routine maintenance is to keep equipment working without problems.
Broken equipment can cost a business a lot of money in terms of time wasted and lost business. If
an IT system breaks down, the immediate result is that an employee is not as productive because
they are unable to do their job until the equipment is repaired. However, the company still has to
pay them. The knock-on effect is that they won’t meet their deadlines or be able to deal with
customers, which could result in the company losing business. The cost of routine maintenance will
nearly always be less than the cost of the lost business.
Fault repair
If equipment does develop a fault or break down, it needs to be repaired or replaced. With computer
systems it is often sensible to replace the components that break, rather than replacing the whole
system. For example, if a keyboard develops a fault after a user spills coffee over it or a DVD drive
becomes unreliable, the cost of replacing the component will be less than the cost of replacing the
whole computer system.

Upgrade
An upgrade is when a component is installed into a computer to improve performance. An upgrade
often means that an existing component is replaced with a new one, but sometimes the upgrade will
add to existing components. For example, a new memory stick (RAM) may be fitted into an empty
socket, with the existing RAM, that was already fitted into another socket, still used and not
replaced. Upgrades can be a cost-effective reason for installing new hardware components, but they
always need to be considered carefully first. For instance, a new version of Microsoft® Windows®
will probably need better hardware than that found in the existing computer systems.
The most immediate need would be to fit more memory (RAM) to the computer. This would help,
but there might be other parts of the system, such as the processor, that are not powerful enough to
run the new software properly. In this situation it could be a better use of money to buy new system
units, rather than upgrade the components.
Reasons for upgrading
There are a number of reasons why an upgrade may be needed:
• User requirements
• Compatibility
• Increased capacity
• Increased speed
• Increased reliability • Software requirements.
Note: Understand risks involved and precautions needed when installing hardware components You
need to recognize the risks involved in installing hardware, particularly the risks to the equipment
and the data. To work safely as an IT technician, it is important to understand the precautions you
need to take in order to reduce these risks, because equipment and data are very valuable and must
not be damaged. A. Risks to systems Electrostatic discharge
We all have static electricity on our bodies. This is totally normal and quite harmless to us, but can
damage the sensitive electronic circuits found in components. Electrostatic discharge (ESD) is when
static electricity which has built up on you is released (discharged) through a component. The
discharge could cause damage to the component by burning out some of the very tiny and sensitive
circuits.
The danger of causing ESD damage is reduced by earthing yourself before touching any component.
This can be done using an earthing wrist strap or other method, such as touching unpainted metal
on a computer that’s plugged into a mains electrical socket or unpainted metal on a radiator or water
pipe. Equipment damage
Any time you take apart a system unit or work on it in any way, there is a risk that you will cause equipment
damage. Some of the ways in which equipment might be damaged include:
• Turning a screw too hard and stripping the thread
• Dropping a component
• Loosening the cable in a plug
• Bending a pin in a plug or socket Risk to data
• There are two main risks to data when installing hardware components: Data loss Data
corruption.
Before you start work on any computer system that involves a data storage device, such as the
hard disk, you need to back up the data (and check the backed up data can be brought back), in
case it gets damaged during your work.
Service loss
ICT professionals do their best to avoid service loss. Maintaining the services the computer systems
provide is a very high priority because that is what the systems are there for. Any loss of service
makes users less productive, which means that there is cost to the organization from loss of business,
loss of reputation or simply from paying staff who cannot do their jobs properly.
B. Precautions
 Checking health and safety regulations
As an ICT professional you will need a good understanding of the health and safety regulations
from early on in your career, so that you understand the good practices demanded by law. In
particular, you need to:
• Report any accidents
• Take reasonable care of your own health and safety when moving heavy components
• Not cause any electrical hazards
• Make sure that workstations meet safety requirements.
 Anti-static equipment
You should always use any anti-static equipment that is provided such as:
Anti-static packaging
Wrist straps Antistatic
mats.
 Use of appropriate tools
You should always use the right tools for the job when working with computer equipment.
 Backing up data
As a precaution, you should always ask the user about any data on the system and carefully back up
the data if there is any possibility that the upgrade might result in this important data being corrupted
or lost.
 Tasks
The following tasks need to be carried out before any installation can take place: test
selection
For example, a new DVD driver needs to be tested to ensure it works properly.
Tests might include checking that the DVD drive:
o has been recognized in Device Manager with no errors
o can read a manufactured DVD
o can read a DVD created by another computer in the organization o can write to a
DVD that can then be read by another computer in the organization.
• test configuration
• reading instructions
• following procedures
The procedures ensure that: o the installation is carried out properly o the
IT technician records his or her actions o the hardware is properly
tested o Users sign off to agree they are satisfied with the work
completed.
Safety check.
There are several possible safety risks involved with a newly installed piece of
computer hardware. For example: o electricity, from unsafe mains wiring or
overloaded mains sockets o sharp edges left on the component, which users might
cut themselves on o unsafe placing of equipment o Leaving the equipment set up
so the user is uncomfortable when working the kit (e.g. a monitor that is at the wrong
height for the user or a printer that requires them to lean too far to reach).

2.3. Installing hardware components

A. Fit components
The computer usually needs to be dismantled before you can fit the new component. ICT professionals take
great care when dismantling to:
 Disconnect from electricity mains to keep them safe
 Avoid causing damage by not rushing and being careful 
Remember how the parts fit together, perhaps by writing notes 
Keep screws and other components safe.

B. Reassemble the computer

After the new hardware component is fitted, the computer needs reassembling in this sequence:
1. Clean any dusty parts. This is easiest when the computer is apart. Fluff and dirt can cause
components to overheat and become unreliable. You should always look at components inside
the case to see if they need cleaning. You can use an air-spray can (sometimes called an air duster)
to blow the dust away or a vacuum cleaner with a small nozzle.
2. Reconnect components that were dismantled. This not only ensures the components go back in
the right places, but also that the leads and cables are reconnected. Anything wrong here will
result in a component not working.
3. Carry out safety checks. Check for electrical danger, sharp edges and unsafe placing of
equipment.
4. Test components. Check that the components work using the tests you selected in preparation for
the hardware upgrade. The selected tests should ensure that everything is checked – if any tests
are missed, it is possible that a component will give problems later.
5. System testing. Make sure the computer works with all the peripherals and the network.
C. Other tasks
There may be some other tasks when the computer is reassembled:
• Restoring data. This will be needed if the hard disk has been replaced or formatted. If the data is not
restored it will not be on the disk, so the user will not be able to access their work.
• Software installation. This is often needed for hardware upgrades, such as a new scanner. The software
will allow the user to control the hardware properly, e.g. changing the scan resolution, and to edit the
scanned images.
• Software configuration. This may be needed to set the defaults for a new printer driver, so that the printer
uses a quick and economical print quality setting (unless the user chooses otherwise). 2.4. Testing
After rebuilding a computer system, it needs to be tested. The most basic test is to switch the system
on to check it starts without errors. The other tests will be the ones you selected when planning the
hardware installation.
ICT professionals are also likely to use tools and utilities to check that all is well with the system after
an installation. Using tools
Hardware tools, such as cable testers, are used to solve some problems, such as if a network cable has any
faults.
Software tools that an ICT professional may use to test a system include:
• Utility software
Utility software includes hard drive diagnostic tools, USB analyzers and many others which can be
used to examine parts of a computer system.
• Run-time analyzers
A run-time analyzer is used to find out what programs are running, how much of the computer
resources they are using.
• Windows® includes a hard drive diagnostic tool named Chkdsk that can be used to check a hard drive
for errors.
• Other tools are available, such as PC Tools, which can be used to improve a computer’s performance or to
examine parts of a computer system.

Test procedures

A test procedure is a set of steps to guide you through what needs to be done to thoroughly test the
installation. It is designed to help you work more effectively and to make sure you test everything
that needs testing.
Test procedures are created in-house and could include these steps:
1. Gathering test information. The first step is to run the tests required by the procedure and
find out what happens. You should record all the results of your tests in a log so that you know
which pass and which fail, thereby requiring further action.
2. Validating the test information. The next step is to check the data you gathered from the
tests to make sure it is correct. This is usually done by running the tests again.
3. Responding to test information. This step is important because you need to be able to
recognize when a test shows problems or is successful. For example, if ping is used to test a network
connection then ‘Request timed out’ shows the test was not successful.
4. Checking specification. The final step is an important end to testing. You need to check
the specification for the installation to make sure that it has been met. For example, if a user
requested an upgrade to make their display run at 1920 x 1200, then the ICT professional should
check that the graphics card and screen can do this.
2.5. Troubleshooting

Installations don’t always go as planned. Sometimes after an installation there can be the
requirement to troubleshoot problems as a result of failed tests or following feedback from the user.
Troubleshooting involves finding out what is wrong and how to make the new hardware installation
work properly. There are a number of reasons why a hardware installation may have been
unsuccessful, including: • Loose connections • Jumper settings
• Power supply.

Power On Self Test (POST)

When a system starts up it carries out a Power On Self Test (POST) to check all the hardware is
working properly before the operating system is loaded. The POST starts by showing how much
memory is in the system and the main devices attached and then loads Windows® or whatever
operating system the computer uses.
POST will beep if anything is badly wrong with the hardware. The beeps give a signal which an
ICT professional can look up to find out what’s wrong. For example, one beep then three beeps then
one beep from a Dell means there is a problem with the RAM, which is probably not in the socket
properly. Beeps are useful as an ICT professional can interpret this information, even if there is no
screen display.
Diagnostic software
You can use diagnostic software to thoroughly test hardware in a computer system and give a report on any
problems found.
An example of diagnostic software is BurnInTest Standard, which can test your computer
components, such as the processor, hard drive, optical drive, sound and graphics cards, RAM,
network connections and ports. This software will even report on the temperature of your processor.
The results from tests can be saved to disk or printed.

2.6 Documentation
Documentation needs to be kept up to date, recording any new hardware installations or upgrades. This
ensures that:
• The organization knows which components are in which systems • Users
know how to get the best from their hardware
• Warranties can be implemented for faulty kit.
Installation records
Many organizations like to keep installation records so they know which component parts are in
which computers. This information can be useful to help identify unreliable components, which
should be avoided in future purchases. Updated manuals
The details recorded in technical and user manuals following installations can be used to help other members
of the IT support team.
The user manuals might be supplied by the manufacturers, but are more often written by larger
organizations to help users get the most out of their computer systems. Significant changes in
hardware will mean these manuals will need to be revised.
Technical manuals
Technical manuals are used by ICT professional technicians to help understand the computer
systems they support. The technical manuals will be supplied by the manufacturers, often with extra
material written by and to be used by ICT professionals.
There are many types of technical manuals used to record experiences with IT problems, hardware settings
and other useful information.
Technical manuals are best when kept up to date with compatibility issues, fixes and other useful
experiences.

User manuals
User manuals are read by people who use the computer systems to do their work, so need to be easy
to understand, well illustrated and as free of technical jargon as they can be. They can be updated
regularly to identify best practice, useful tips, shortcuts and other advice to help productivity.
For example, an organization might have an online system to book staff holidays and record staff absences.
The user manual for this system would include how to:
• Log onto the system
• Move between screens
• enter different types of absence
• change previous entries.
3. Install Network peripherals
3.1. Planning network peripheral location
Network planning is the process of defining business requirements and growth plans to build a
framework for connecting computers and other equipment in your organization. Thinking about
these needs before jumping into the actual implementation eases the process, and increases the
likelihood that your chosen network solution will match your requirements now and in the future.

This article provides practical advice to help address the needs of organizations that have a network
and are in the process of upgrading it. The article should also be useful to organizations installing a
network for the first time.

How do I get started?

The first step in developing a plan is assessing your current network requirements and considering how
your business is likely to change over time. Here are some ideas to help you start the process:

Consider Usage Requirements

Determine the number of people that will be using the network to get a rough idea of the computers
and peripherals it must support. Consider how users will interact with the system to define the
features you will need. For example, what sort of access is required to the network (e.g. will each
user have their own computer? or will several users be sharing the same computer?) Will any users
need to access the network remotely (e.g. from home or other office sites)?

Gather Input

Factor the needs of the various teams and departments within your organization into your network
plan. Start by defining the requirements of each group and determine the relative costs of
incorporating the different requirements into the network plan. This may be in terms of money or
time saved.

Plan for the future

Detail or factor in, to the best of your knowledge, the direction your organization is likely to take in
the near future (3-5 years). As you think about expansion, identify any plans that might affect your
network needs (e.g. new staff or volunteers, office expansion, remote working, or the installation of
new software packages). Doing this now will be less expensive and time consuming than replacing
an inadequate network later.
4. Decide who will manage the network

As your network solution becomes more defined, you will need to decide whether you have the
resources in-house to install and maintain it yourself or whether you require a consultant or external
company to handle it. Networking products have become easier to use and administer over the years,
so small organizations are finding that internal day- to-day management of the network is becoming
increasingly cost effective.
External support will also likely be required, and it is worth considering using remote network
administration tools to reduce the number of on-site visits necessary to keep the network running
smoothly.

Security Issues

Ensure you build security features into your network plan to protect your organisations most
important asset - its information. Common network security precautions include passwords, virus
protection, an external firewall and data encryption.

Other Considerations

You may enhance the foundation of your network plan by addressing other issues that may affect the
integration, use and maintenance of your network. These include:

Information Management

Consider how to manage information on your server so that users can easily find what they need.
Create standardized naming conventions for files on the server and establish rules for the creation
of new files and folders.

Remote Access

If some staff members travel frequently or work from locations outside your office, you may want
to build remote access capabilities into your network. This can be done through remote dial-in, or
securely over the Internet using a VPN.

Staff Training

While working with a network is relatively simple, it may demand that employees adopt new habits.
A training program will enable workers to take full advantage of your network's timesaving and
productivity enhancing features. Ensure training time is built into your network rollout timetable
and offer follow up sessions to address ongoing staff challenges and concerns.

Network pre-installation checklist

This checklist of questions will help you cover the main areas when it comes to planning and installing a
new or upgraded network.

Planning
 • How many people will use the network?
• How many users are local or on-site?
• How many users are remote or off-site and will require access to the network?
• How many on-site computers will be connected to the network?
• How many on-site devices (computers, servers, scanners, printers, etc) will require a network card?
• How do you intend remote users to access the network?
• Which server based applications (e.g. databases, email) do you plan to run on the network? What are
the minimum hardware requirements of these server based applications?
• What are the specifications of the servers you intend to install on the network (e.g. amount of
memory, processor speed etc.)?
• Have you purchased sufficient licenses to run all the software on servers and client machines?

Network hardware requirements

• What other devices will your network support (e.g. back-up devices, Uninterruptible Power
Supplies, Network printers, etc.)?
• Do you have enough network points for these network devices?
• Do the hubs or switches have enough ports for the number of connections you will require? And is
there room for growth?

Network design What network

topology will you use?

• Do all workstations have the correct Network interface cards (NICs) to support this technology?
• Which network operating system will you use (e.g. Windows 2000 Server, Linux, Novell etc.)?
• Which type of cabling will you use (e.g. CAT 5, fiber optic) or will a wireless network be suitable?
• Where will network cables be located?
• Are there any buildings or leasing regulations that may affect cable placement?
• Where will you locate the following devices, servers, hubs or switches, printers, firewalls and
routers, modems etc.?
Security, back-up and power

• What security measures will you be putting in place? Virus protection, user passwords, firewalls,
data encryption etc.
• Do you need to physically secure your server (e.g. lock it away in a cupboard)?
• How will you back up data on your network?
• What is the capacity of your back up solution?
• Is it large enough to support all the data on your servers and network devices?
• Does your back up solution have the capacity to grow as your data grows?
• How frequently will files be backed up and how long will you keep backed up files?
• Where will you store backed up tapes (e.g. fireproof safe, off site)?
• What devices will require an uninterruptible power supply (e.g. server(s) )? Is there
sufficient ventilation around your servers?

Support services
 • Do you have resources allocated for the following areas (e.g., consultants, in-house IT staff etc)?
o Network installation o Cable
installation o Network technical
support o Network management o
Network security o
Network
maintenance o Training

Undertaking a significant upgrade to your network or migrating to a newer or different operating system can
be a daunting and challenging task.

Effective planning can limit the system downtime, reduce network crashes and ensure a seamless transition
and minimal disruption to users.

Physical and Logical Topologies

Both the physical and logical topologies of the existing network need to be documented. A technician
gathers the information during the site survey to create both a physical and logical topology map of
the network. A physical topology, as shown in Figure 3-1, is the actual physical location of cables,
computers, and other peripherals. A logical topology, as shown in Figure 3-2, documents the path
that data takes through a network and the location where network functions, such as routing, occur.

Fig. 3-1
 Fig. 3-2
Remark: Connecting peripherals to the network and the
computer safely and Testing connected network peripheral is
almost the same as that of connecting other peripherals which
is discussed in section 2.3 and section 2.4 respectivels.

Using and maximizing operating system

An operating system provides the fundamental link between the hardware that makes up the PC
and the user. Without an operating system, all the greatest, slickest PC hardware in the world is but
so much copper, silicon, and gold wrapped up as a big, beige paperweight. The operating system
creates the interface between human and machine, enabling you to unleash the astonishing power
locked up in the sophisticated electronics of the PC to create amazing pictures, games, documents,
business tools, medical miracles, and much more. All operating systems are not created equal. They
don't look the same or, on the surface, act the same. But every OS shares essential characteristics
that, once you have the concepts, help lead you to answers when troubleshooting: "I know that the
OS formerly known as Y must enable me to

An operating system (OS) is a program that performs four basic functions. First, it must
communicate, or at least provide a method for other programs to communicate, with the hardware
of the PC. It's up to the OS to access the hard drives, respond to the keyboard, and output data to the
monitor. Second, the OS must create a user interface—a visual representation of the computer on
the monitor that makes sense to the people using the computer.
The OS must also take advantage of standard input devices, such as mice and keyboards, to enable
users to manipulate the user interface and thereby make changes on the computer. Third, the OS,
via the user interface, must enable users to determine the available installed programs and run, use,
and shut down the program(s) of their choice. Fourth, the OS should enable users to add, move, and
delete the installed programs and data. In a nutshell, the OS should be able to do the following:

• Communicate with hardware

• Provide a user interface
• Provide a structure for accessing applications
• Enable users to manipulate programs and data

Installing or upgrading an OS is like any good story: it has a beginning, a middle, and an end. In
this case, the beginning is the several tasks you need to do before you actually do the installation or
upgrade. Let's look at the nine tasks you need to complete before you insert that CD or DVD.
Here's the list:

access programs; therefore, no matter how odd the interface, the option must be here!"
Functions of the Operating System Installing
and Upgrading Windows
• Identify hardware requirements.
Hardware requirements help you decide whether a computer system is a
reasonable host for a particular operating system. Requirements include the CPU
model, the amount of RAM, the amount of free hard disk space, and the video
adapter, display, and storage devices that may be required to in- stall and run the
operating system.
• Verify hardware and software compatibility.
Assuming your system meets the requirements, you next need to find out how well
Windows supports the brand and model of hardware and the application software you
intend to use under Windows.
• Decide whether to perform a clean installation or an upgrade.
• Determine how to back up and restore existing data, if necessary.
• Select an installation method.
• Determine how to partition the hard drive and what file system to use.
• Determine your computer's network role.
• Decide on your computer's language and locale settings.
• Plan for post-installation tasks.

How can I install Windows XP Pro on my computer?

As a Microsoft Windows support professional, one of your tasks may be to install the operating system. This
article provides a step-by-step tutorial on installing Windows XP Pro.
Step #1: Plan your installation

When you run the Windows XP Professional Setup program, you must provide information about
how to install and configure the operating system. Thorough planning can make your installation of
Windows XP Professional more efficient by helping you to avoid potential problems during
installation. An understanding of the configuration options will also help to ensure that you have
properly configured your system.

I won't go into that part right now but here are some of the most important things you should take into
consideration when planning for your XP installation:

• Check System Requirements

• Check Hardware and Software Compatibility
• Determine Disk Partitioning Options
• Choose the Appropriate File System: FAT, FAT32, NTFS
• Decide on a Workgroup or Domain Installation
• Complete a Pre-Installation Checklist After you made sure you can go on, start the

installation process.

Step #2: Beginning the installation process

You can install Windows XP in several methods - all are valid and good, it all depends upon your needs
and your limitations.

• Manual installations usually come in 3 flavors:

• Boot from CD - No existing partition is required.
• Boot from the 6 Setup Boot Disks, then insert the CD - No existing partition is required
• Boot from an MS-DOS startup floppy, go to the command prompt, create a 4GB FAT32 partition
with FDISK, reboot, format the C partition you've created, then go to the CD drive, go into the I386
folder, and run the WINNT.EXE command.
• Run an already installed OS, such as Windows NT 4.0 Server. From within NT 4.0 go to the I386
folder in the W2K installation CD and run the WINNT32.EXE command.
• If you want to upgrade a desktop OS such as Windows 98 into Windows 2000
Professional you can follow the same procedure as above (You cannot upgrade Windows 98 into
W2K Server).

There are other non-manual installation methods, such as using an unattended file along with a
uniqueness database file, using Sysprep, using RIS or even running unattended installations from
within the CD itself, but we won't go into that right now.

It doesn't matter how you run the setup process, but the moment it runs - all setup methods look alike.
Step #3: The text-based portion of the Setup program

The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be
asked to accept the EULA and choose a partition on which to install XP, and if that partition is
new, you'll be asked to format it by using either FAT, FAT32 or NTFS.

1. Start the computer from the CD.

2. You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If
you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a
CD for that matter). Make sure you have one handy.

3. If you want, you can press F2 to run the ASR sequence. For that you need a good backup created by
the Windows XP backup program, and the ASR floppy disk. If you plan to install a new copy of XP
- don't do anything.
4. Setup will load all the needed files and drivers.

5. Select To Setup Windows XP Professional Now. If you want, and if you have a previous installation
of XP, you can try to fix it by pressing R. If not, just press ENTER.
6. Read and accept the licensing agreement and press F8 if you accept it.

7. Select or create the partition on which you will install Windows XP Professional.
Depending upon your existing disk configuration choose one of the following: If the
hard disk is unpartitioned, you can create and size the partition on which you will install
Windows XP Professional.
• If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create
 an additional partition in the unpartitioned space.
• If the hard disk already has a partition that is large enough, you can install Windows XP
Professional on that partition. If the partition has an existing operating system, you will
overwrite that operating system if you accept the default installation path. However, files other
than the operating system files, such as program files and data files, will not be overwritten.
• If the hard disk has an existing partition, you can delete it to create more unpartitioned space
for the new partition. Deleting an existing partition erases all data on that partition.

If you select a new partition during Setup, create and size only the partition on which you will
install Windows XP Professional. After installation, use Disk Management to partition the
remaining space on the hard disk.
8. Select a file system for the installation partition. After you create the partition on which you will
install Windows XP Professional, you can use Setup to select the file system with which to format
the partition. Windows XP Professional supports the NTFS file system in addition to the file
allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional,
Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain
access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files
that are on a local Windows XP Professional partition with the Microsoft Windows 95 or Windows
98 operating systems, you should format the partition with a FAT or FAT32 file system. We will
use NTFS.
9. Setup will then begin copying necessary files from the installation point (CD, local I386 or network
share).
10. Note: If you began the installation process from an MS-DOS floppy, make sure you have and run
SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour,
perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will
probably last a few minutes, no more than 5 max.
11. The computer will restart in graphical mode, and the installation will continue.
Step #4: The GUI-based portion of the Setup program
The setup process reboots and loads a GUI mode phase.

It will then begin to load device drivers based upon what it finds on your computer. You don't need
to do anything at this stage.
1. Click Customize to change regional settings, if necessary.

• Current System Locale - Affects how programs display dates, times, currency, and numbers.
Choose the locale that matches your location, for example, French (Canada).
•
Current Keyboard Layout - Accommodates the special characters and symbols used in different
languages. Your keyboard layout determines which characters appear when you press keys on
the keyboard.

If you don't need to make any changes just press Next.

If you do need to make changes press Customize and add your System Locale etc.

Note for other language user like “Spanish” users: Unlike W2K, it is SAFE and it is OK for you to
install Spanish language support at this phase.

To install Spannish support:

TLM Development Manual Date:

Compiled by: ICT Department

•
After pressing Customize go to the Languages tab and select the "Install files for complex script and right-
to-left languages".
A warning message will appear. Press Ok.

Warning: You must now press Apply!!!

• Setup will copy the necessary files from the installation point.

• You can now go to the Regional Options tab and select Spain in the Location drop-down list, and
Spanish in the Standards and Formats drop-down list. Click Ok.
2. Type your name and organization.

3. Type the product key.

4. Type the computer name and a password for the local Administrator account. The local
Administrator account resides in the SAM of the computer, not in Active Directory. If you will be
installing in a domain, you need either a pre-assigned computer name for which a domain account
has been created, or the right to create a computer account within the domain.
5. Select the date, time, and time zone settings.
6. Setup will now install the networking components.

After a few seconds you will receive the Networking Settings window. If you don't have a NIC at
all, setup will skip this step and you will immediately go to the final phase of the setup process.

Press Next to accept the typical settings option if you have one of the following situations:

TLM Development Manual Date:

Compiled by: ICT Department

•
You have a functional DHCP on your network.
• You have a computer running Internet Connection Sharing (ICS).
• You're in a workgroup environment and do not plan to have any other servers or Active Directory
at all, and all other workgroup members are configured in the same manner.

Otherwise select Custom Settings and press Next to customize your network settings.

7. One thing you CAN do is to uninstall the Qos Packet Scheduler. Click it and press the Uninstall
button. If you want to keep it you can simply remove the mark from the QoS check-box. In any way
you can later install or uninstall it if you want.

Keep the TCP/IP, Client for Microsoft Networks and the File and Print Sharing options selected.

8. Highlight the TCP/IP selection and press Properties.

In the General tab enter the required information. You must specify the IP address of the computer,
and if you don't know what the Subnet Mask entry should be - you can simply place your mouse
pointer over the empty area in the Subnet Mask box and click it. The OS will automatically select
the value it thinks is good for the IP address you provided.

If you don't know what these values mean, or if you don't know what to write in them, press cancel and
select the Typical Settings option. You can easily change these values later.

9. In the Workgroup or Domain window enter the name of your workgroup or domain.

• A workgroup is a small group of computers on a network that enables users to work together and
does not support centralized administration.
• A domain is a logical grouping of computers on a network that has a central security database for
storing security information. Centralized security and administration are important for computers
in a domain because they enable an administrator to easily manage computers that are
geographically distant from each other. A domain is administered as a unit with common rules and
procedures. Each domain has a unique name, and each computer within a domain has a unique
name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights
to join a domain - leave the default entry selected and press Next.

If you want to join a domain (NT 4.0 domain of W2K/2003 Active Directory domain) enter the domain's
name in the "Yes, make this computer a member of the following domain" box.

To successfully join a domain you need the following:

• The person performing the installation must have a user account in Active Directory. This account
does not need to be the domain Administrator account. And

TLM Development Manual Date:

Compiled by: ICT Department

•
• The computer must have an existing computer account in the Active Directory database of the
domain that the computer is joining, and the computer must be named exactly as its domain account
is named.

TLM Development Manual Date:

Compiled by: ICT Department

 Or

• The person performing the installation must have appropriate permission to create a domain
account for the computer during installation.

Enter the Active Directory domain name (in the form of xxx.yyy, for example: DPETRI.NET) or the
NetBIOS name of the NT 4.0 domain (in the form of xxx, for example: DPETRI). Press Next.

Note: If you provide a wrong domain name or do not have the correct connectivity to the domain's DNS
server you will get an error message.

A username/password window will appear. Enter the name and password of the domain's administrator (or
your own if you're the administrator on the target domain).

Note: Providing a wrong username or password will cause this phase to fail.

10. Next the setup process will finish copying files and configuring the setup. You do not need to do
anything.
11. After the copying and configuring phase is finished, if XP finds that you have a badly configured
screen resolution it will advise you to change it and ask you if you see the new settings right.

Note: the minimum supported screen resolution in XP is 800X600.

12. Setup finishes and boots Windows XP.

13. A Welcome screen is the first thing you see. The computer checks your Internet connectivity
(required for the mandatory Activation and voluntary Registration processes).

You will be asked to register your copy of XP. You can decline if you want.

14. XP will ask you for the default username that will log onto this computer. You can enter as many
as 5 users, but you can create more after the installation is finished.
15. . That's it! you're done!
16. . After installing the operating system some hardware devices need special system software
known as driver. So to installing drivers for different input /output hardware devices is almost the

TLM Development Manual Date:

Compiled by: ICT Department

 same as that of installing application software which is going to be discussed in the next topic.
(Note: to install you need driver resource CD or the driver other removable storage device).

TLM Development Manual Date:

Compiled by: ICT Department

 2. How to Install Application Software in Windows XP

 Installing programs by using control panel

If you want to install software in Windows XP, just pop in the software CD. If the installation
window appears — as it often does — click Next to run the software and follow the
installation prompts. If you try to install software in Windows XP and nothing happens after
you insert a software CD, follow these steps to open the Add or Remove Programs window.
1. Choose Start- Control Panel.

The Start button is located at the bottom-left corner of your screen, and Control Panel will show up
on the Start menu once you click the Start button.

2. Click the Add or Remove Programs icon.

If you hover your cursor over the icon, a pop-up will read: "Install or remove programs and Windows
components." This confirms that you've found the right icon.

3. Click the Add New Programs button and then click the CD or Floppy button.

The button is located on the left.

4. Click Next to run the software.

The resulting Install Program from CD or Floppy dialog box appears.
5. Follow the prompts for that software installation.
Don't worry about doing any customizing while installing software. Standard installation is normally
recommended and sufficient.
Note: Some computers require you to restart your computer when installing new software. This completes
the setup of the new program.

TLM Development Manual Date:

Compiled by: ICT Department

  Installing a program from the Web
To download and install a program from the Web
1. Click the download link on the software company’s Web site. When prompted, click Save.

2. In the Save As dialog box, click the Save in down arrow, and then click Desktop. Make note of the file
name. Then, click Save.

3. Internet Explorer downloads the file, which may take several minutes. When the download is complete,
click Close.

4. Right-click your system clock, and then click Show the Desktop.

TLM Development Manual Date:

Compiled by: ICT Department

5. Locate the file on the desktop, and double-click it to start the setup program.

6. If the Security Warning dialog box appears, click Run.

7. During setup, click Next to move to the next page of the setup program, and then click Finish
on the last page. If the page prompts you to enter information, you can do so, or you can
simply accept the default information that the setup program entered.

TLM Development Manual Date:

Compiled by: ICT Department

 After the program is installed, you can delete the setup file from your desktop. To open your new
program, click the Start button, click All Programs, and then click the program’s icon.

 Installing a program from a CD

To install a program from CD 1.
Insert the CD into your computer.
Setup will start automatically. If it does not start after several seconds, double-click My
Computer on your desktop (or click the Start button, and click My Computer), right-click your
CD drive, and then click AutoPlay.

2. During setup, click Next to move to the next page of the setup program, and then click
Finish on the last page. If a page prompts you to enter information, you can do so, or you
can simply accept the default information that the setup program entered.

3. Once your program is installed, you can start it by clicking the Start button, clicking All
Programs, and then clicking your new program’s icon.

TLM Development Manual Date:

Compiled by: ICT Department

  How to change or remove a program in Windows XP
How to change an installed program

You can use this feature to change the installation of Windows Installer-based programs such as
Microsoft Office XP. Windows Installer-based programs include a Maintenance Mode option.
With this option, you can add or remove features, change the installation state of the program or of
individual components, or repair and restore the installation.

To change a program, follow these steps:

1. Click Start, click Control Panel, and then double-click Add or Remove Programs.
2. In the Currently installed programs box, click the program that you want to remove, and then
click Change or Change/Remove.
3. Follow the instructions that appear on the screen to make the changes that you want.

How to remove an installed program

To remove a program that is installed on your computer, follow these steps:

1. Click Start, click Control Panel, and then double-click Add or Remove Programs.
2. In the Currently installed programs box, click the program that you want to remove, and then
click Remove.
3. If you are prompted to confirm the removal of the program, click Yes.

TLM Development Manual Date:

Compiled by: ICT Department