IT 401: SYSTEM ADMINISTRATION & MAINTENANCE

INSTRUCTOR: MS. GLENDA JERUELA

SYNCHRONOUS CLASS SCHEDULE: EVERY MONDAY, 4:00-5:30 PM | ASYNCHRONOUS CLASS SCHEDULE: EVERY WEDNESDAY, 4:00-5:30 PM
TOPIC OUTLINE

FUNDAMENTALS OF TASKS OF SYSTEM PRACTICAL GUIDES TO

SYSTEM ADMINISTRATION ADMINISTRATOR SYSTEM ADMINISTRATION
 WHAT
DOES A
SYSTEM
ADMINISTRATOR
DO?
A SYSTEM ADMINISTRATOR

 looks after computers, networks,

and the people who use them;
 administers hardware, system
software, application software,
configurations, or security; and
 influences how effectively other
people can or do use their
computers and networks.
DOES SYSTEM ADMINISTRATION MATTER?

Yes, it does!
MAIN REASON:

 The widespread use of the

Internet, intranets, and the move
to a web-centric world has
redefined the way companies
depend on computers.

 The Internet is a 24/7 operation,

and sloppy operations can no
longer be tolerated.
SIX (6) BASIC PRINCIPLES OF SYSTEM
ADMINISTRATION

Simplicity
Clarity
Generality
Automation
Communication
Basics First
PRINCIPLE #1: SIMPLICITY

 It means that the smallest

solution that solves the entire
problem is the best solution.

 It keeps the systems easy to

understand and reduces complex
component interactions that can
cause debugging nightmares.
PRINCIPLE #2: CLARITY
 It means that the solution is
straightforward. It can be easily
explained to someone on the project
or even outside the project.
 It makes it easier to change the system,
as well as to maintain & debug it. In the
system administration world, it’s better
to write five lines of understandable
code than one line that’s
incomprehensible to anyone else.
PRINCIPLE #3: GENERALITY

 It means that the solutions aren’t

inherently limited to a particular
case. Solutions can be reused.

 Using vendor-independent open

standard protocols makes systems
more flexible and makes it easier to
link software packages together for
better services.
PRINCIPLE #4: AUTOMATION

 It means using software to replace

human effort.

 It improves repeatability and

scalability, w/c is key to easing the
system administration burden, and
eliminates tedious repetitive tasks,
giving SAs more time to improve
services.
PRINCIPLE #5: COMMUNICATION

 It ensures that everyone is working

toward the same goals. Lack of
communication leaves people concerned
and annoyed. Communication also
includes documentation.
 Documentation makes systems easier to
support, maintain, and upgrade. Good
communication & proper documentation
also make it easier to hand off projects
and maintenance when you leave or take
on a new role.
PRINCIPLE #6: BASICS FIRST

 It means that you build the site on

strong foundations by identifying
and solving the basic problems
before trying to attack more
advanced ones.
 Doing the basics first makes adding
advanced features considerably
easier and makes services more
robust.
 PRACTICAL GUIDES TO SYSTEM
ADMINISTRATION
1. How do people get
Use a trouble-ticket system help?

Manage quick requests right 2. What is the scope of

responsibility of the SA
Adopt three time saving policies team?
Start every new host in a known state
3. What’s our definition
other tips of emergency?
WHAT TO
DO WHEN …
1.1 BUILDING A SITE FROM SCRATCH
 Think about the organizational
 Build a software depot, or at least plan a
structure you need.
small directory hierarchy that can grow
 Check in with management on the into a software depot.
business priorities that will drive
 Establish your initial core application
implementation priorities.
services:
 Plan your namespaces carefully.  Authentication and authorization
 Desktop life-cycle management
 Build a rock-solid data center.
 Email
 Build a rock-solid network designed to  File service, backups
grow.  Network configuration
 Printing
 Build services that will scale.  Remote access
1.2 GROWING A SMALL SITE

 Provide a helpdesk;  Think about your organization and

 Establish checklists for new hires, whom you need to hire, and provide
new desktops/laptops, and new service statistics showing open and
servers. resolved problems.
 Consider the benefits of a  Monitor services for both capacity
network operations center and availability so that you can
(NOC) dedicated to monitoring predict when to scale them.
and coordinating network  Be ready for an influx of new
operations. computers, employees, and SAs.
1.3 GOING GLOBAL
 Design your wide area network
(WAN) architecture.  Architect services to take account of
 Follow three cardinal rules: scale, long-distance links—usually lower
scale, and scale. bandwidth and less reliable.
 Standardize server times on  Qualify applications for use over
Greenwich Mean Time (GMT) to high-latency links.
maximize log analysis capabilities.
 Ensure that your security and
 Make sure that your helpdesk really permissions structures are still
is 24/7. Look at ways to leverage SAs adequate under global operations.
in other time zones.
1.4 REPLACING SERVICES

 Be conscious of the process.

 Don’t hard-code server names
 Factor in both network into configurations, instead,
dependencies and service hard-code aliases that move
dependencies in transition
planning.
with the service.
 Manage your Dynamic Host  Manage your DNS time-to-live
Configuration Protocol (DHCP) (TTL) values to switch to new
lease times to aid the transition. servers.
1.5 MOVING A DATA CENTER

 Schedule windows unless everything is  Perform a fire drill on your data backup
fully redundant and you can move first system.
half of a redundant pair and then the
 Develop test cases before you move, and
other.
test, test, test everything after the move is
 Make sure that the new data center is complete.
properly designed for both current use
 Label every cable before it is disconnected.
and future expansion.
 Establish minimal services—redundant
 Back up every file system of any
hardware—at a new location with new
machine before it is moved.
equipment.
1.5 MOVING A DATA CENTER CONT.

 Identify a small group of customers

 Test the new environment— to test business operations with the
newly moved minimal services, then
networking, power,
test sample scenarios before moving
uninterruptable power supply everything else.
(UPS), heating, ventilation, air
 Run cooling for 48–72 hours, and
conditioning (HVAC), and so then replace all filters before
on—before the move begins. occupying the space.
 Perform a test-run.
1.6 MOVING TO/OPENING A NEW BUILDING

 Four weeks or more in advance, get  Communicate to the powers that be that
access to the new space to build the WAN and ISP connections will take
infrastructure. months to order and must be done soon.

 Use radios or walkie-talkies for  Prewire the offices with network jacks
communicating inside the building. during, not after, construction.

 Use a personal digital assistant (PDA)  Work with a moving company that can
or non-electronic organizer. help plan the move.

 Order WAN and Internet service  Designate one person to keep and
provider (ISP) network connections 2– maintain a master list of everyone who is
3 months in advance. moving and his or her new office number,
cubicle designation, or other location.
1.6 MOVING TO/OPENING A NEW BUILDING CONT.
 Pick a day on which to freeze the
master list. Give copies of the frozen  Give each person a sheet of 12 labels
list to the moving company, use the list preprinted with his or her name and
for printing labels, and so on. If new location for labeling boxes, bags,
someone’s location is to be changed and personal computer (PC). (If you
after this date, don’t try to chase down
don’t want to do this, at least give
and update all the list copies that have
been distributed. Move the person as people specific instructions as to
the master list dictates, and schedule a what to write on each box so it
second move for that person after the reaches the right destination.)
main move.
1.6 MOVING TO/OPENING A NEW BUILDING CONT.

 Give each person a plastic  Always order more boxes

bag big enough for all the PCthan you think you’ll be
cables. Technical people can
moving.
decable and reconnect their
PCs on arrival; technicians  Don’t use cardboard boxes;
can do so for nontechnical instead, use plastic crates
people. that can be reused.
1.7 HANDLING A HIGH RATE OF OFFICE MOVES
 Connect and test network connections
 Work with facilities to allocate only
ahead of time.
one move day each week. Develop a
routine around this schedule.  Have customers power down their
machines before the move and put all
 Establish a procedure and a form that
cables, mice, keyboards, and other bits that
will get you all the information you
might get lost into a marked box.
need about each person’s equipment,
number of network and telephone  Brainstorm all the ways that some of the
connections, and special needs. Have work can be done by the people moving.
SAs check out nonstandard equipment Be careful to assess their skill level; maybe
in advance and make notes. certain people shouldn’t do anything
themselves.
1.7 HANDLING A HIGH RATE OF OFFICE MOVES CONT.
 Have a moving company move the
equipment, and have a designated SA
move team do the unpacking,
reconnecting, and testing. Take care in
 Formalize the process, limiting it to one
selecting the moving company.
day a week, doing the prep work, and
 Train the helpdesk to check with having a move team makes it go more
customers who report problems to see smoothly with less downtime for the
whether they have just moved and customers and fewer move-related
didn’t have the problem before the problems for the SAs to check out.
move; then pass those requests to the
move team rather than the usual
escalation path.
1.8 ASSESSING A SITE (DUE DILIGENCE)

 Reassure existing SA staff and

management that you are here not to
pass judgment but to discover how this  Have a private document repository, such
site works, in order to understand its as a wiki, for your team. The amount of
similarities to and differences from sites information you will collect will overwhelm
with which you are already familiar. This your ability to remember it: document,
is key in both consulting assignments document, document.
and in potential acquisition due-
diligence assessments.
1.8 ASSESSING A SITE (DUE DILIGENCE) CONT.

 Create or request physical-equipment

lists of workstations and servers, as  Analyze the ticket-system statistics
well as network diagrams and service by opened-to-close ratios month to
workflows. The goal is to generate
multiple views of the infrastructure.
month. Watch for a growing gap
between total opened and closed
tickets, indicating an overloaded staff
 Review domains of authentication, and or an infrastructure system with
pay attention to compartmentalization chronic difficulties.
and security of information.
TO BE CONTINUED …

 Other Tips on System

Administration will be continued  NOTE: The quiz for today only
on the succeeding lesson. covers up to slide 28.
 REFERENCES

1. Limoncelli, T.A., Hogan, C.J., & Chalup, S.R. (2007). The Practice of
System and Network Administration, 2nd ed., Addison-Wesley.
Indiana, USA.
2. Bergstra, J., & Burgess, M. (2007). Handbook of Network and
System Administration. Elsevier. Oxford, UK.