obj 4 Flashcards
ticketing systems
the best way to manage support requests
usually, a responsibility of the help desk
there are many different ticketing systems
managing a support ticket
information gathering
applying context
clear and concise communication
user information
you can’t address a person’s problem unless you know who has the issue
usually integrated into a name service
may be added automatically
always confirm the contact information
device and description
device information
description
the description determines the next step
asset management
a record of every asset
associate a support ticket with a device make and model
financial records, audits, depreciation
add an asset tag
categorization and escalation
categories
severity
escalation levels
resolving the issue
progress notes
problem resolution
incident reports
security policy
documentation must be available
incidents are ongoing
reports and documentations
compliance
meeting the standards of laws, polices, and regulations
a healthy catalog of rules
procurement life cycle
the purchasing process
start with a request from the user
negotiate with suppliers
purchase, invoice, and payment
acceptable user policies (AUP)
what is acceptable use of company assets?
covers many topics
used by an organization to limit legal liability
asset database
a central asset tracking system
assigned users
warranty
licensing
splash screens
a message, logo, or graphic shown during startup or login
can be informational
may be required for legal or administrative purposes
network topology diagram
describes the network layout
standard operating procedures
organization have different business objectives
operation procedures
software installation and upgrades
documentation is key
onboarding
bring a new person into the organization
IT agreements need to be signed
create accounts
provide required IT hardware
offboarding
end user termination checklist
this process should be predefined
what happens to the hardware?
what happens to the data?
account information is usually deactivated
knowledge base and articles
external sources (manufacturer knowledge base, internet communities)
internal documentation (institutional knowledge, usually part of helpdesk software)
find the solution by searching through archives
change management
how to make a change
one of the most common risks in the enterprise
often overlooked or ignored
have clear policies
sometimes extremely difficult to implement
rollback plan
the change will work perfectly and nothing will ever go bad “totally not satire”
you should always have a way to revert your changes
this isn’t as easy as it sounds
always have backups
sandbox testing
isolated testing environment
use before making a change to production
confirm the rollback plan
responsible staff members
a team effort
IT team
business customer
organization sponsor
change management process
a formal process for managing change
Complete the request forms
Determine the purpose of the change
Identify the scope of the change
Schedule a date and time of the change
Determine affected systems and the impact
Analyze the risk associated with the change
Get approval from the change control board
Get end-user acceptance after the change is complete
change request forms
a formal process always seems to include a bit of paperwork
nothing gets missed
usually a transparent process