Lecture 01 Introduction to SA

Santelmo
15 Aug 202121:52

Summary

TLDRThis video introduces the role of a systems administrator (SA), who ensures the smooth operation of computing systems. It covers SA tasks like user and hardware management, software installation, security, and troubleshooting. The script emphasizes the importance of patience, tenacity, and strong organizational skills for SAs. It also discusses the challenges, such as dealing with user frustration and long hours, and highlights the value of documentation and the Systems Administrators Guild. The video concludes with insights on SA training, certifications, and key principles like policy, predictability, and scalability.

Takeaways

  • 👨‍💻 Systems Administration (SA) involves managing computing systems to ensure they run smoothly and efficiently for users.
  • 👥 SA tasks include user management, hardware and software management, security management, system monitoring, and troubleshooting.
  • 🛠️ SA professionals are expected to perform backups, maintain documentation, and manage licenses.
  • 💡 Automation and planning are crucial for system scalability, assessing new technologies, and avoiding potential problems.
  • 🔑 Essential qualities for an SA include patience, tenacity, strong organizational skills, logical reasoning, and ethical behavior.
  • 🌟 Benefits of being an SA include job variety, challenges, employability, and the opportunity for continuous learning.
  • 😕 Downsides may include occasional user frustration, long working hours, and the expectation to solve every problem.
  • 🤝 The Systems Administrators Guild (SAGE) is a professional body that promotes the visibility and recognition of SA as a profession.
  • 📚 SAGE provides resources like job descriptions and guidelines to help SA professionals at various levels.
  • 🏆 Certifications and trainings, such as those from Microsoft, Red Hat, and LPI, can be beneficial for SA professionals to enhance their skills.
  • 🛡️ Key principles in SA include policy foundation, predictability, scalability, and the principle of minimum privilege.

Q & A

  • What is the role of a systems administrator?

    -A systems administrator, also known as an SA, is a professional responsible for ensuring that computing systems work effectively. They manage, maintain, and troubleshoot systems to ensure they run smoothly and efficiently, facilitating user productivity.

  • What are some key tasks of a systems administrator?

    -Key tasks of a systems administrator include user management, hardware and software management, maintaining resources like disks, memory, and CPU, security management, system monitoring and troubleshooting, documentation, and providing help desk support.

  • Why is automation important in systems administration?

    -Automation is crucial for systems administrators as it helps to streamline repetitive tasks, increase efficiency, reduce human error, and free up time for more complex problem-solving and strategic planning.

  • What are some personal qualities that are beneficial for a systems administrator to possess?

    -Systems administrators should have patience, tenacity, strong organizational skills, well-developed logic, reasoning, and critical thinking skills, and ethical behavior. These qualities help them handle the challenges and responsibilities of their role effectively.

  • What does the Systems Administrators Guild (SAGE) do?

    -SAGE is a professional body for practicing systems administrators, established to increase the visibility and recognition of systems administration as a profession. It provides resources, guidelines, and a community for systems administrators worldwide.

  • What are the different levels of systems administration as per the Systems Administrators Guild?

    -The Systems Administrators Guild categorizes systems administration into four levels: Level 1 (Novice), Level 2 (Junior), Level 3 (Intermediate), and Level 4 (Senior). Each level represents increasing experience, education, and responsibilities.

  • What are some certifications that can be helpful for a systems administrator?

    -Certifications such as those from Microsoft, Red Hat, Novell, Linux Professional Institute (LPI), CompTIA, and O'Reilly School of Technology can be beneficial for systems administrators, providing specialized knowledge and industry recognition.

  • Why is ethical behavior important for a systems administrator?

    -Ethical behavior is important for systems administrators to ensure honesty, fairness, and equity in their professional and academic relationships. It also helps in maintaining the privacy and rights of individuals and groups within the organization.

  • What is the significance of the 'mantra' for a systems administrator?

    -The mantra for a systems administrator, 'The computer environment does not exist solely for the amusement of the systems administrator,' serves as a reminder to prioritize the needs of the users and the organization over personal interests or amusement.

  • How does a systems administrator manage the life cycle of a computer system?

    -A systems administrator manages the life cycle of a computer system by moving it through states such as new, build, clean, configured, unknown, debug, rebuild, and retire. Each state represents a phase in the system's life, from initial setup to eventual decommissioning.

Outlines

00:00

💻 Introduction to Systems Administration

This paragraph introduces the concept of systems administration, defining it as the management of computing systems to ensure they operate effectively and efficiently. It highlights the role of a systems administrator (SA), who is responsible for user and hardware management, software installation, security, system monitoring, and troubleshooting. The SA also handles documentation, user support, and automation. The paragraph outlines the tasks of an SA, which include adding or removing users and hardware, configuring and maintaining systems, managing resources like disks and CPU, and ensuring system security. It also touches on the need for SAs to have patience, tenacity, organizational skills, logical reasoning, and ethical behavior.

05:00

🔧 The Roles and Challenges of a Systems Administrator

Paragraph 2 delves into the benefits and challenges of being a systems administrator. It mentions the variety and challenges that come with the role, making it a fulfilling career. It also notes the high employability of SAs and the importance of independent learning and organized work habits. The downsides include potential frustrations with users, management, and tech support, as well as the expectation to have immediate solutions to problems. The paragraph also discusses the 'ugly' side of the job, where SAs may go unnoticed when things run smoothly but are heavily relied upon during crises. It emphasizes the importance of documentation, which helps in system reconstruction, decision-making narratives, and maintaining service quality.

10:04

📜 The Systems Administrators Guild and Ethical Standards

This paragraph introduces the Systems Administrators Guild (SAG), established in 1992, which serves as a professional body for systems administrators worldwide. It discusses the guild's goal of increasing the visibility and recognition of systems administration as a profession. The SAG has published a series of handbooks, including job descriptions for SAs at various levels. The paragraph also presents the SAG's creed, which includes a commitment to high ethical and professional standards, personal integrity, and adherence to laws and policies. It outlines the ethical responsibilities of SAs, emphasizing the importance of education, social responsibility, and the well-known adage 'with great power comes great responsibility.'

15:05

🛠 Systems Administration Levels and Certifications

Paragraph 4 discusses the different levels of systems administration, ranging from novice to senior, each with increasing responsibilities and experience. It mentions that new hires are expected to operate at the guild's level one. The paragraph also covers the various certifications and trainings available for systems administrators, such as those from Microsoft, Red Hat, Novell, LPI, CompTIA, and O'Reilly School of Technology. It stresses the value of certain principles in systems administration, including policy as the foundation, predictability, scalability, minimum privilege, and community considerations.

20:06

🔄 Systems Administration Processes and Lifecycle

The final paragraph outlines the processes and lifecycle of systems administration, including the states of machines and the transitions between them. It describes the stages from a new machine to a retired one, with states such as build, clean, configured, unknown, and off. The paragraph explains the transitions, such as initialization, update, entropy, debug, rebuild, and retirement. It also touches on the importance of understanding these states and transitions for effective systems administration.

Mindmap

Keywords

💡Systems Administration

Systems Administration refers to the management of an organization's computer systems and networks. It involves ensuring that systems run smoothly, efficiently, and securely. In the video, it is the central theme, with the systems administrator (SA) being described as someone who takes care of the systems others are using. The video discusses various tasks of an SA, emphasizing the importance of balancing system performance with user needs.

💡User Management

User Management is a key task for systems administrators, which involves adding and removing users from systems. This is crucial for maintaining security and ensuring that only authorized individuals have access to the system. The video mentions user management as one of the primary responsibilities of an SA, highlighting the need for efficient user handling to support system security and functionality.

💡Hardware Management

Hardware Management encompasses the tasks of adding, removing, configuring, and maintaining hardware and software. This is essential for the physical components of a system to function correctly and to ensure they are compatible with the software. The video script mentions that systems administrators are responsible for hardware management, which is critical for the overall performance and reliability of the systems they manage.

💡Security Management

Security Management is about securing the entire computing environment, which includes protecting systems from unauthorized access, data breaches, and other security threats. The video emphasizes the importance of security management in systems administration, as it is a vital aspect of ensuring the integrity and confidentiality of the systems and data.

💡System Monitoring and Troubleshooting

System Monitoring and Troubleshooting involve monitoring system usage and performance, detecting and correcting problems, and optimizing system performance. This is a critical aspect of systems administration, as it helps to maintain the efficiency and reliability of systems. The video script describes this as a key task for SAs, who must be vigilant in identifying and resolving issues to prevent system downtime.

💡Documentation

Documentation in systems administration refers to the practice of recording system configurations, policies, procedures, and changes. It is essential for maintaining a clear record of system states and decisions, which can be useful for troubleshooting and future reference. The video script highlights the importance of documentation, suggesting that it helps to recreate systems and provides a narrative for decisions made.

💡Automation

Automation in systems administration is the process of using scripts and tools to perform routine tasks automatically. This can increase efficiency and reduce the potential for human error. The video mentions automation as a way for SAs to handle complex tasks and maintain system efficiency by automating as many tasks as possible.

💡Ethical Behavior

Ethical Behavior in the context of systems administration involves adhering to principles of honesty, fairness, and equity in professional and academic relationships. It also includes respecting the rights and dignity of individuals within the organization. The video script discusses the importance of ethical behavior for SAs, emphasizing that it is a cornerstone of professional conduct and responsible system management.

💡Systems Administrators Guild (SAGE)

The Systems Administrators Guild (SAGE) is a professional organization for systems administrators, established to increase the visibility and recognition of systems administration as a profession. The video script mentions SAGE as a resource for SAs, providing guidelines, training, and a community for professionals in the field.

💡Certifications

Certifications in systems administration are professional qualifications that demonstrate an individual's expertise and knowledge in specific areas of systems management. The video script lists various certifications such as those from Microsoft, Red Hat, and LPI, which can be helpful for SAs to validate their skills and advance in their careers.

💡Policy

Policy in systems administration refers to the rules, regulations, and procedures that guide the operation and management of systems. It serves as the foundation for decision-making and resource allocation within an organization. The video script discusses policy as a key principle for systems administration, emphasizing its role in maintaining order and predictability within the system.

Highlights

Introduction to systems administration and the role of a systems administrator (SA).

SA responsibilities include user management, hardware and software management, and security.

The importance of system monitoring, troubleshooting, and optimization for performance.

Documentation and help desk support as key tasks for a SA.

Automation and planning policies as part of a SA's job.

The necessity of patience and tenacity for a successful SA.

Strong organizational skills as a requirement for effective systems administration.

The significance of logical reasoning and critical thinking in problem-solving for SAs.

Ethical behavior in systems administration, including respect for user privacy and rights.

Benefits of being a SA, such as job variety, challenges, and employability.

Challenges faced by SAs, including long hours and the expectation to solve all problems.

The 'ugly' side of systems administration, where the job's importance is often overlooked.

Strategies for dealing with problems and stress in systems administration.

The role of documentation in systems administration for maintaining system integrity.

The Systems Administrators Guild (SAGE) and its resources for professional development.

SAGE's code of ethics and its importance for professional conduct.

The importance of certifications and training for SAs for career advancement.

Principles of systems administration, including policy, predictability, and scalability.

The concept of minimum privilege and its role in system security.

The significance of communities and uniformity in systems administration.

Resource mapping as a strategy for effective systems management.

The five-state submachine model for understanding systems administration processes.

Transcripts

play00:04

hi hello there welcome to introduction

play00:07

to systems administration

play00:11

what is a systems administration

play00:14

when you say systems administration

play00:17

there should be a systems administrator

play00:20

aka sa for short

play00:23

someone who takes good care of the

play00:24

systems others are using

play00:27

the professional responsible for making

play00:30

computing systems work

play00:32

effectively

play00:33

so one can be an essay at home

play00:36

or at work

play00:38

they are responsible

play00:40

for balancing systems running smoothly

play00:42

and efficiently with the users able to

play00:45

work in an easy and efficient manner

play00:49

if you own and maintain a computer

play00:51

then you are a systems administrator for

play00:54

that computer

play00:58

what are the system administration tasks

play01:02

first would be user management

play01:05

add and remove users from the systems

play01:10

hardware management

play01:12

add and remove hardware and software

play01:15

configure and maintain hardware and

play01:17

software

play01:18

maintain resources like disks

play01:21

memory and cpu

play01:24

and

play01:25

sa should be able to retire a hardware

play01:30

software management

play01:31

install software

play01:33

or reinstall software

play01:37

security management meaning the sa have

play01:40

to secure the entire environment

play01:44

system monitoring and troubleshooting

play01:47

perform backup and restore operations

play01:51

monitor system usage and performance

play01:54

detect and correct problems

play01:57

and optimize system performance

play02:01

next would be documentation and help

play02:03

desk

play02:04

so general user support is answering

play02:07

users questions

play02:09

and maintain documentation and

play02:11

licenses

play02:14

sa should be able to perform backup also

play02:18

next would be automation

play02:21

planning policies and auditing

play02:23

this includes system planning

play02:25

scaling the system

play02:27

assessing new technologies

play02:29

anticipate and avoid problems

play02:32

also under automation and planning

play02:35

the sa write programs to automate as

play02:39

many tasks as possible

play02:42

determine and enforce usage policy

play02:45

educate users

play02:47

role model a liarson between user needs

play02:51

and the budgetary

play02:53

resource and technology limitations

play02:56

and

play02:57

sa should negotiate with

play02:59

vendors

play03:04

systems administration requirement

play03:06

the first one would be patience

play03:09

the first person that you need to have

play03:11

patients with when you are administering

play03:13

a system is yourself

play03:16

systems administration is hard and

play03:18

sometimes

play03:20

you will have bugs or difficult problems

play03:22

to overcome

play03:24

if it's always easy

play03:26

then you aren't challenging yourself

play03:29

and you aren't growing as a system

play03:31

administrator

play03:34

next would be tenacity

play03:37

most people will tell you that tenacity

play03:40

is a great quality to have

play03:42

especially if you're trying something

play03:44

challenging

play03:45

that takes a while to complete

play03:49

next would be

play03:50

strong organizational skills

play03:54

organizational skills are the abilities

play03:56

that let you stay focused on different

play03:58

tasks

play03:59

and

play04:00

use your time energy

play04:03

strength

play04:04

mental capacity

play04:06

physical space and others

play04:08

to effectively and efficiently in order

play04:10

to achieve the desired outcome

play04:15

next would be well-developed logic

play04:18

reasoning

play04:19

and critical thinking skills

play04:21

so try to anticipate the outcome for

play04:23

your decisions

play04:26

the ability to read and comprehend

play04:28

technical information

play04:30

also ethical behavior

play04:33

ethical behavior is characterized by

play04:35

honesty

play04:36

fairness

play04:38

and equity in interpersonal

play04:40

professional and academic relationships

play04:44

and in research and scholarly activities

play04:46

also

play04:47

so ethical behavior respects the dignity

play04:50

diversity and rights of individuals and

play04:54

group of people within the organization

play04:59

okay

play05:00

so what are the good about

play05:02

being a systems administrator

play05:05

so good ideas for systems that means

play05:08

lots of variety

play05:10

okay challenging

play05:12

fulfilling

play05:14

and face well

play05:16

also

play05:17

it's very employable

play05:19

so learn

play05:20

to learn independently

play05:22

okay develop systematic and organized

play05:25

work habits

play05:26

find balance between reality problems

play05:29

happen take note and utopia

play05:33

next would be the bad

play05:35

okay bad ideas for systems admin

play05:38

annoying at times

play05:41

to the users

play05:43

management

play05:44

vendor tech support

play05:46

expect a single right answer to every

play05:49

problem

play05:50

okay

play05:51

so

play05:52

get stuck due to frustration

play05:55

okay so long hours of

play05:58

work

play05:59

and this may not be your only job

play06:02

so expect the manual internet co-worker

play06:06

to be able to accurately and completely

play06:09

answer every question

play06:11

okay so these are the bad ideas for the

play06:13

systems admin

play06:15

now let's take a look at the ugly side

play06:19

most people don't understand the job

play06:22

okay so understand that you're not alone

play06:27

when things go well

play06:29

go unnoticed

play06:32

okay

play06:33

they don't do anything be like a game

play06:36

player like a webster uh surfers

play06:41

it's important to document everything

play06:44

okay

play06:45

so don't panic

play06:47

see the problem as a challenge

play06:50

not a deal breaker

play06:52

okay so fake it till you make it if you

play06:55

have encounter problem

play06:57

then admit it if you don't know

play07:00

you can also find an ally

play07:03

ask specific questions

play07:05

and then check in with others

play07:07

okay so these are just some of the

play07:09

strategies

play07:10

for what you can do

play07:13

if it's happening to you at work

play07:19

next

play07:21

when there is a problem

play07:23

well

play07:25

everyone is looking for you

play07:28

okay that's highly stressful

play07:31

some blame

play07:32

you

play07:33

for that problem

play07:35

and may graduate to miracle worker

play07:38

status once problem is fixed

play07:41

okay

play07:42

now for the documentation

play07:45

documentation help ensure

play07:47

consent and expectations

play07:50

okay so it enables you to recreate

play07:53

system

play07:55

it helps to tell the narrative for

play07:57

decisions made

play07:59

and how yourself or the client responded

play08:02

to different situations

play08:04

in the same manner

play08:06

it is important to record information

play08:08

that can help support the proper

play08:10

treatment plan and the reasoning for

play08:13

such services

play08:14

now the contents include

play08:16

configuration information

play08:19

policies and procedures

play08:21

useful commands and resources

play08:24

daily lag of modifications

play08:27

okay you could also have wikis

play08:30

and a request ticket system

play08:35

systems admin guild or the search

play08:39

okay so this is the systems

play08:41

administrators guild

play08:43

it was established in 1992 out of usenix

play08:47

license conferences

play08:49

large installation

play08:51

systems administrators

play08:53

so for almost a decade

play08:55

such has served the needs of systems

play08:57

administrators around the world

play09:00

so this is a professional body for

play09:02

practicing systems administration

play09:05

so one of the such main goals is the

play09:08

increase of visibility and recognition

play09:10

of systems administration

play09:12

as a profession

play09:14

so such is made up of sa organizations

play09:17

from all over the world

play09:20

okay so if you want to know more about

play09:22

this sags

play09:24

you could go ahead and check them online

play09:26

via http www.such.org

play09:31

so to this end

play09:32

such has published a series of short

play09:35

topics handbooks all of them are

play09:37

excellent

play09:38

so a good one to start with is a job

play09:41

descriptions for systems administrators

play09:44

so this work provides detailed job

play09:46

descriptions

play09:47

for systems administration's position

play09:50

in various levels so as such

play09:53

it is very useful for evaluating both

play09:55

your skills

play09:57

and your present position in light of

play09:59

general practices

play10:04

let's talk about the such guidelines

play10:06

so they have creed

play10:08

god of essex

play10:09

and mantra

play10:12

let's go to it

play10:13

let's start with such grid

play10:16

okay so the sunscreen states that we

play10:20

as professional systems administrators

play10:23

do hereby commit ourselves to the

play10:25

highest standards of ethical and

play10:27

professional contact and

play10:29

agree to be guided by this code of

play10:31

ethics and encourage every system

play10:34

administrator to do the same

play10:36

code of ethics

play10:39

first would be professionalism

play10:42

must display professionalism in the

play10:44

performance of duties at all times

play10:47

contact with clients and colleagues must

play10:50

be kept to the highest standards of

play10:51

professional behavior

play10:54

next would be personal integrity

play10:57

integrity must be beyond reproach

play11:01

privacy do not unnecessarily infringe

play11:05

on the rights of others

play11:07

maintain an exemplary work ethic

play11:11

laws and policies would be next

play11:14

you also have communication

play11:17

system integrity

play11:19

education

play11:21

responsibility to computing community

play11:24

social responsibility

play11:26

and

play11:27

ethical responsibility

play11:33

so according to edmund burke the greater

play11:36

the power

play11:37

the more dangerous the abuse

play11:40

okay so from the spider-man you still

play11:42

remember that with great power comes

play11:45

great responsibility

play11:50

how about the mantra mantra of a systems

play11:53

administrator

play11:55

the computer environment does not exist

play11:57

solely for the amusement of the systems

play12:00

administrator

play12:01

okay so mantra is a mystical words of

play12:04

our sounds used to facilitate

play12:07

a meditative conscious state

play12:13

next

play12:14

what are new

play12:16

to systems administrators training

play12:18

okay

play12:20

so new hires are expected to be

play12:22

operating at systems administrators

play12:25

guild level one

play12:27

okay so that is level one is novice

play12:31

junior level two

play12:33

level three is intermediate

play12:35

and then level four is senior so higher

play12:39

such levels have more experience more

play12:42

education

play12:43

more responsibilities and then maybe

play12:45

they are managers

play12:50

so for the systems administrator levels

play12:53

okay so you will each be responsible for

play12:55

running one of the following small or

play12:57

complex sites

play12:59

so when you say small small uniform site

play13:02

less than 50 computers

play13:04

all running the same operating system

play13:07

and 20 or

play13:09

fewer users

play13:11

that is small

play13:13

now for complex site that would be up to

play13:15

100 systems

play13:17

running more than two different

play13:19

operating systems and up to 100 users

play13:23

you even have the large complex site so

play13:26

that is greater than 100 computers

play13:28

potentially running more than one

play13:30

operating system and

play13:32

more than 100 or more users

play13:38

now what are the certifications

play13:39

available and trainings available for

play13:42

systems admin

play13:44

so certifications are not required for

play13:46

your current position but may be helpful

play13:50

especially the first two

play13:52

okay

play13:53

so microsoft so i know a specific

play13:55

approach

play13:56

to systems administration

play13:59

and then you also have red hat having

play14:01

the same thing

play14:03

next would be

play14:04

novell

play14:06

okay

play14:08

so linux professional institute or the

play14:10

lpi

play14:12

comptia

play14:14

o'reilly school of technology

play14:18

principles of systems administration

play14:21

so our organization strongly believes in

play14:24

the value of the following principles

play14:27

first

play14:28

policy is the foundation

play14:30

policy is a law

play14:32

regulation

play14:33

procedure

play14:34

administrative

play14:36

action

play14:37

incentive

play14:39

or voluntary

play14:41

practice of governments and other

play14:44

institutions

play14:45

so policy decisions are frequently

play14:47

reflected in resource allocations

play14:51

okay health can be influenced by

play14:52

policies in many different sectors

play14:55

all right

play14:56

next would be predictability this is the

play14:59

goal

play15:00

predictability is the degree to which a

play15:02

correct prediction or forecast of system

play15:05

state

play15:06

can be made either qualitatively or

play15:09

quantitatively

play15:12

next would be scalability

play15:14

this is often important

play15:16

so scalability is the measure of systems

play15:18

ability to increase or decrease in

play15:20

performance

play15:21

and cost in response to changes in

play15:23

application and systems

play15:25

processing demands

play15:27

enterprises that are growing rapidly

play15:29

should pay special attention to

play15:30

scalability

play15:32

when evaluating hardware and software

play15:36

next

play15:37

minimum privilege restriction of

play15:40

unnecessary privilege protects a system

play15:42

from accidental and malicious damage

play15:45

okay so that comes with the corollary

play15:48

don't work

play15:50

as administrator

play15:52

root

play15:52

okay so something like 95 percent of all

play15:55

businesses today

play15:57

okay

play15:58

uses their computers

play16:01

running as administrator root on their

play16:03

computer at all time

play16:05

i upload the businesses

play16:07

who have successfully removed elevated

play16:09

privileges from non-admin employees

play16:12

although it isn't easy to do

play16:15

making this one security change can

play16:17

significantly reduce the risk of

play16:19

malicious exploit

play16:21

okay so the most common issue is that

play16:24

end users want to install and remove

play16:27

their own software and configure their

play16:30

own settings

play16:32

so developers often need to debug

play16:34

programs and load and unload device

play16:37

drivers

play16:40

right

play16:41

next would be

play16:42

communities so each member needs to

play16:45

consider

play16:46

ramifications of actions

play16:51

sixth would be uniformity so increases

play16:54

predictability

play16:56

it may decrease costs

play16:58

variety

play17:00

so used as needed for risk management

play17:03

and flexibility

play17:04

it may increase costs

play17:08

delegation aka specialization so develop

play17:11

experts

play17:13

who can do tasks more efficiently

play17:16

and more costly effective

play17:18

and

play17:20

resource map

play17:21

so mapping our hardware and software

play17:23

resources increases the predictability

play17:26

and removes ambiguity of the complete

play17:29

system

play17:30

okay it displays parts of the system

play17:33

and their inter relationships so

play17:36

contingencies can be made

play17:39

for expected problem areas

play17:43

some crude

play17:44

model what is a sample model so the

play17:47

basic components of our organization

play17:50

and the system administrators

play17:52

responsibilities can be summarized as

play17:55

some good

play17:56

okay

play17:57

first

play17:58

software users

play18:01

machines

play18:03

that's for some

play18:05

create

play18:06

read

play18:07

update

play18:09

delete that's for root

play18:12

so when you say systems admin

play18:15

it's a sum root

play18:21

average pipe state of machine so being

play18:23

assistance admin

play18:25

you should know

play18:26

this five state submachine

play18:28

okay so the first one would be

play18:31

new

play18:32

when you say new it's a new machine

play18:34

okay

play18:36

so build

play18:37

this is moving between states okay so

play18:39

when say build

play18:41

that is during the build process the

play18:43

operating system is installed on the

play18:45

machine

play18:47

okay

play18:48

next would be clean

play18:50

what is clean a computer with the os

play18:52

installed but not configured

play18:55

to work in the environment

play18:57

you also have configured

play19:00

configured a computer that is configured

play19:02

correctly according to the requirements

play19:04

of the computing environment

play19:07

next state is

play19:08

unknown a computer that has been

play19:11

misconfigured or

play19:13

gotten out of the or perhaps been

play19:16

borrowed by an intern and returned with

play19:19

stains on it okay so that's unknown

play19:22

and then off is or

play19:26

surplus

play19:27

okay now let's go over moving between

play19:30

states we are done already with build

play19:34

okay

play19:35

let's go to initialize what is

play19:37

initialize this is the state

play19:40

or the movement from clean to configured

play19:42

when you say initialize

play19:44

often directly after or part off

play19:48

build the process

play19:50

this will typically include things like

play19:52

network configuration

play19:54

naming

play19:55

and may include os patches and other

play19:57

changes

play19:59

okay

play20:00

the next one would be update

play20:02

okay

play20:03

so update at some point after the

play20:05

initialization the computer will

play20:07

probably have to be modified in order to

play20:10

bring the machine into conformance

play20:13

with the current requirements in most

play20:15

cases

play20:17

this will happen continually

play20:19

for the lifetime of the computer

play20:22

right

play20:23

next from configured to unknown you've

play20:25

got entropy there

play20:27

okay so entropy refers to the gradual

play20:30

process of change

play20:32

that results in a computer

play20:34

that has an unknown state

play20:38

the causes for this are numerous they

play20:41

include for example undisciplined

play20:43

changes made to the machine

play20:46

major changes in the environment

play20:48

or unexplained problems

play20:51

okay

play20:52

next would be debug debug is from

play20:54

unknown to configured

play20:56

so this refers to the process of

play20:57

debugging an unknown machine and getting

play21:00

it back

play21:01

into specification

play21:04

right next would be rebuild so from

play21:07

unknown to clean

play21:09

okay so rebuild

play21:10

in some cases

play21:12

a machine will need to be rebuilt

play21:14

either because of some kind of problem

play21:17

or for a large scale change

play21:20

okay

play21:21

and the last one would be retired okay

play21:23

retire

play21:24

from unknown to off

play21:26

retire this is the process of turning

play21:28

the machine off in some sites

play21:31

there is an official process for this

play21:34

matters

play21:36

it merely involves turning the computer

play21:38

off or forgetting it exists

play21:42

right so that's the end of this video

play21:44

have a great day see you on the next

play21:46

video

Rate This

5.0 / 5 (0 votes)

Связанные теги
Systems AdministrationIT ManagementUser ManagementHardware MaintenanceSoftware SecurityTroubleshootingDocumentationAutomationEthics in ITSA TrainingCertifications
Вам нужно краткое изложение на английском?