INTECH 3200: System Administration and Maintenance

Download as pdf or txt
Download as pdf or txt
You are on page 1of 20

INTECH 3200

SYSTEM ADMINISTRATION AND


MAINTENANCE
What is Sytem Administration?
branch of engineering
that concerns the operational
management of human-computer systems

refers to the management of one or more


hardware and software systems ensuring
that the systems are running efficiently and
effectively.

The task is performed by a system


administrator
able to know how to communicate patient at all times and knows able to solve difficult
with technical and how to handle pressure technical problems
non-technical users and has a customer service
attitude
know how to document know the risks of being a
activities in order to system administrator or
reproduce the results sysadmin
SYSADMIN TASK
ORGANIZATIONAL POLICIES
the sysadmin has to think
carefully about computer
security and whether or not to
allow access to certain users

Should users be allowed to install software?

Should users have complex passwords with certain requirements?

Should you be able to view non-work related websites like


Facebook?

If you hand out a company phone to an employee, should you set


a device password?
SYSADMIN TASK
IT INFRASTRUCTURE SERVICES
As an IT support specialist doing system administration, you'd be responsible for the IT
infrastructure services in your organization.

• getting network access


• secure connection to websites and other computers
• services must be updated routinely
• patched for security holes
SYSADMIN TASK
ROUTINE MAINTENANCE

when managing machines for a company, you don't just set it and forget it, you have to constantly
provide updates and maintenance so that they run the latest secure software.

to effectively update and manage hardware, you do something called batch update

This means that once every month or so, you update all your servers with the latest security
patches. You have to find time to take their services offline, perform the update, and verify that
the new update works with the service. You also don't have to perform an update every single time
a new software becomes available.

But, it's common practice to do batch updates for security updates and very critical system
updates
SYSADMIN TASK
VENDORS

Sysadmins must be sure to weigh their option before purchasing anything. They need to think
about hardware supply. Working with vendors or other businesses to buy hardware is a common
practice.

Setting up businesses accounts with vendors like Hewlett Packard, Dell, Apple, etc., is usually
beneficial since these companies can offer discounts to businesses.

So if a certain laptop model isn't used anymore, they need to think of a suitable backup that works
with their organization. Price is also something to keep in mind. They'll probably need formal
approval from their manager or another leader to establish this relationship with a vendor.
SYSADMIN TASK
USER AND HARDWARE PROVISIONING
sys admins have to be able to create new users and give them access to their company's
resources.

They also have to remove users from an IT infrastructure if users leave the company. It's not just
user accounts they have to worry about, sys admins are also responsible for user machines.

Sys admins also have to ensure that the hardware they are provisioning or setting up for users is
standardized in some way.

Not only do sys admins have to standardize settings on a machine, they have to figure out the
hardware lifecycle of a machine.

• When was it built?


• When was it first used?
• Did the organization buy it brand new or was it used?
• Who maintained it before?
• How many users have used it in the current organization?
• What happens to this machine if someone needs a new one?
MAIN STAGES OF
HARDWARE
LIFECYCLE

PROCUREMENT DEPLOYMENT MAINTENANCE RETIREMENT

This is the stage This is where This is the stage where In this final stage,
hardware is set up software is updated hardware becomes
where hardware is
and hardware issues unusable or no longer
purchased or re- so that the needed and it needs to
are fixed if and when
used for any employee they occur.
be properly removed
from the fleet.
employee. can do their job.
SYSADMIN TASK
TROUBLESHOOTING AND MANAGING ISSUES

when you're managing an entire IT infrastructure, you'll constantly have to


troubleshoot problems and find solutions for your IT needs. This will probably take
up most of your time as an IT support specialist.

There are two skills that are critical to arriving at a good solution for your users.

• The first is troubleshooting, asking questions, isolating the problem, following


the cookie crumbs, and reading logs are the best ways to figure out the issue.

• The second super important skill that we covered is customer service;


showing empathy, using the right tone of voice and dealing well with difficult
situations.
SYSADMIN TASK
RISK ASSESSTMENT

It's super important to make sure that your company's data is routinely backed up
somewhere. Preferably, far away from it's current location. Being responsible for
keeping data available isn't easy.
Security Management

ADDITIONAL ROLES OF
SYSADMIN
Monitor system usage and
performance and managing
resources (disk, memory , CPU)
System planning
• Scaling the system
• Assessing new technologies
• Anticipate and avoid problems Perform upgrades/patches, and test
devices and schedule downtime to
manage devices.
WITH GREAT POWER COMES GREAT RESPONSIBILITY

APPLYING
THE MOST IMPORTANT THING IS TO
AVOID USING ADMINISTRATOR
RIGHTS FOR TASKS THAT DON'T
REQUIRE THEM.

CHANGES
IN THE RESPECT THE PRIVACY OF OTHERS.

SYSTEM
BEING AN ADMINISTRATOR OF AN EMAIL
SERVER DOESN'T MEAN YOU SHOULD READ
SOMEONE ELSE'S EMAIL.
WITH GREAT POWER COMES GREAT RESPONSIBILITY

APPLYING
YOU SHOULDN'T USE YOUR
ADMINISTRATOR RIGHTS TO
BYPASS ANY RULES.

CHANGES
IN THE MISTAKES LIKE DELETING THE WRONG SET
OF FILES, REBOOTING THE WRONG

SYSTEM
MACHINE, OR BREAKING THE CONNECTION
THAT YOU'RE USING TO MANAGE A
REMOTE MACHINE CAN ALL HAPPEN IF
YOU'RE NOT CAREFUL.

REVERTING TO THE PREVIOUS STATE IS


CALLED A ROLLBACK.
ASSESSING THE RISK

APPLYING •We can assess the risk involved by considering how

CHANGES
important the services to the infrastructure and how
many users would be impacted if the service went
down.

IN THE •You can also use these criteria to establish priorities


for fixing a problem.

SYSTEM
FIXING THINGS THE RIGHT WAY

The problem could be in a user's computer, a server

APPLYING
in your own infrastructure, a piece of code running in
the cloud or somewhere in between.

CHANGES
When looking for a reproduction case, there are three
questions you'll need to answer.
• What steps did you take to get to this point?

IN THE
• What's the unexpected or bad result?
• And what's the expected result?

SYSTEM
Make sure you document all your steps and any findings.
Having this documentation may prove invaluable if you
ever have to deal with similar issues again.
THANKYOU

You might also like