CompTIA A+ Exam  >  CompTIA A+ Notes  >   Core 2  >  Cheatsheet: IT Support Best Practices

Cheatsheet: IT Support Best Practices

1. Communication Skills and Professionalism

1.1 Professional Communication Techniques

TechniqueDescription
Active ListeningAllow customer to complete explanations without interruption; take notes; repeat back key points for confirmation
Use Proper LanguageAvoid jargon, acronyms, and slang; use terms customer can understand; speak clearly and professionally
Maintain Positive AttitudeProject confidence and competence; remain calm and patient; avoid arguing with customers
Set and Meet ExpectationsProvide realistic timelines; communicate status updates; offer alternatives when unable to meet requests
Clarify Customer StatementsAsk open-ended questions; restate issues to confirm understanding; avoid assumptions

1.2 Dealing with Difficult Customers

  • Do not argue or become defensive
  • Avoid dismissing or minimizing customer concerns
  • Do not be judgmental of customer's technical knowledge
  • Listen actively and acknowledge their frustration
  • Remain calm and professional regardless of customer behavior
  • Escalate to supervisor when situation cannot be resolved directly

1.3 Cultural Sensitivity

  • Be aware of cultural differences in communication styles
  • Respect personal space and physical boundaries
  • Use appropriate titles and forms of address
  • Be mindful of language barriers; speak clearly and confirm understanding

2. Troubleshooting Methodology

2.1 Six-Step Troubleshooting Process

StepActions
1. Identify the ProblemGather information from user; identify symptoms; inquire about recent changes; determine if anything has changed; duplicate the problem if possible; approach multiple problems individually
2. Establish a TheoryQuestion the obvious; consider multiple approaches; start with simple explanations; research knowledge bases
3. Test the TheoryConfirm the theory; if theory is not confirmed, establish new theory or escalate
4. Establish Plan of ActionIdentify required resources; obtain approval if needed; create implementation plan; consider corporate policies
5. Verify Full FunctionalityVerify system operation; implement preventive measures; confirm with customer that issue is resolved
6. Document FindingsRecord problem description; document solution; update knowledge base; note lessons learned

2.2 Information Gathering Techniques

  • Ask open-ended questions: "What were you doing when the problem occurred?"
  • Gather details about error messages or symptoms
  • Identify environmental or infrastructure changes
  • Review system logs and event viewer entries
  • Attempt to reproduce the issue
  • Isolate problems when multiple issues exist

3. Safety Procedures

3.1 Electrical Safety

HazardSafety Measures
Electrical ShockDisconnect power before servicing; use ESD strap properly grounded; avoid working on live circuits; keep liquids away from equipment
Power SurgesUse surge protectors; install UPS for critical systems; verify proper grounding
Trip HazardsUse cable management; secure cables with ties or raceways; mark cable pathways

3.2 Physical Safety

  • Lift heavy objects with proper technique: bend knees, keep back straight, lift with legs
  • Use assistance or mechanical aids for objects over 50 pounds
  • Wear safety equipment: safety glasses when working with compressed air, gloves when handling sharp components
  • Remove jewelry and secure loose clothing when working inside equipment
  • Keep work area clean and organized to prevent accidents

3.3 Environmental Controls

ControlPurpose and Guidelines
MSDS/SDSMaterial Safety Data Sheet/Safety Data Sheet provides handling, storage, and emergency procedures for chemicals; must be accessible for all hazardous materials
Temperature ControlMaintain 68-77°F (20-25°C) for equipment rooms; ensure adequate ventilation; monitor humidity levels 45-55%
VentilationEnsure proper airflow around equipment; maintain clear air intake and exhaust paths; use adequate HVAC systems

3.4 Fire Safety

  • Class C fire extinguisher for electrical fires
  • Class ABC extinguisher for general purpose use
  • Never use water on electrical fires
  • Know evacuation routes and assembly points
  • Pull alarm and evacuate before attempting to fight large fires

4. Environmental Protection and Disposal

4.1 Proper Disposal Methods

ItemDisposal Method
BatteriesNever dispose in regular trash; recycle at designated collection sites; lithium and alkaline batteries require special handling
Toner CartridgesReturn to manufacturer or use recycling programs; do not incinerate; avoid exposing to heat
CRT MonitorsContains lead and other toxic materials; requires certified e-waste recycling facility; never landfill
Cell Phones/TabletsErase all data before disposal; use manufacturer take-back programs or certified e-waste recyclers
Hard DrivesShred, degauss, or physically destroy before disposal; use certified e-waste facility for final disposal
Chemical SolventsFollow MSDS disposal instructions; use hazardous waste collection services; never pour down drains

4.2 Environmental Compliance

  • Follow local, state, and federal regulations for hazardous waste
  • Maintain compliance with EPA and OSHA guidelines
  • Use authorized disposal vendors for regulated materials
  • Document disposal for audit and compliance purposes

5. Privacy, Licensing, and Policy

5.1 Data Privacy

PrincipleImplementation
User PrivacyDo not browse user files without permission; close private windows/applications when accessing system; respect confidentiality
Data HandlingFollow company policies for sensitive data; use encryption when required; secure data during repairs
Personal InformationProtect PII (Personally Identifiable Information); follow privacy regulations; obtain consent before accessing personal data

5.2 Software Licensing

  • Personal License: Single user, single device installation
  • Enterprise License: Organization-wide deployment with volume pricing
  • Open Source License: Free to use with specific terms (GPL, MIT, Apache)
  • Verify license compliance during software installations
  • Maintain license documentation and proof of purchase
  • Never install unlicensed or pirated software
  • Track license counts to ensure compliance with agreements

5.3 Digital Rights Management (DRM)

  • Protects copyrighted digital media from unauthorized use
  • Enforces restrictions on copying, sharing, and playback
  • Respect DRM protections; do not attempt to circumvent
  • Verify legitimate access rights before assisting users

5.4 Corporate Policies

Policy TypeKey Elements
Acceptable Use Policy (AUP)Defines appropriate use of company IT resources; specifies prohibited activities; outlines consequences for violations
Password PolicyMinimum length requirements; complexity requirements; expiration periods; prohibition of password sharing
Data ClassificationPublic, Internal, Confidential, Restricted categories; handling requirements for each level
BYOD PolicyRequirements for personal devices accessing corporate resources; security controls; data separation

6. Incident Response

6.1 Incident Types

IncidentResponse Actions
Security BreachIsolate affected systems; report to security team immediately; preserve evidence; do not power off systems; document all actions
Malware InfectionDisconnect from network; identify infected systems; quarantine affected devices; run antimalware scans; report to security team
Unauthorized AccessLock account immediately; change credentials; review access logs; report to management and security team
Data Loss/LeakContain the leak; notify data protection officer; document scope; follow breach notification procedures

6.2 Chain of Custody

  • Document who collected evidence, when, and where
  • Maintain detailed logs of evidence handling
  • Use tamper-evident bags or containers for physical evidence
  • Track all transfers of evidence between parties
  • Preserve original state; work from copies when possible
  • Never turn off system involved in security incident without consulting security team

6.3 First Response Actions

  • Identify and verify the incident
  • Report to appropriate personnel (security team, supervisor, management)
  • Contain the incident to prevent further damage
  • Preserve evidence and document observations
  • Follow escalation procedures defined by organization
  • Do not attempt unauthorized investigation or remediation

7. Change Management

7.1 Change Management Process

StepDescription
Request FormDocument proposed change, justification, impact assessment, and required resources
Approval ProcessSubmit to Change Advisory Board (CAB) or management; obtain sign-off before proceeding
Purpose of ChangeClearly define objectives and expected outcomes; align with business needs
Scope DefinitionIdentify affected systems, users, and services; determine boundaries of change
Risk AnalysisAssess potential impacts; identify mitigation strategies; plan rollback procedures
Implementation PlanSchedule change window; coordinate with stakeholders; prepare step-by-step procedures
End-User AcceptanceObtain user confirmation that change meets requirements; validate functionality

7.2 Change Documentation

  • Maintenance windows: scheduled downtime for updates and changes
  • Standard operating procedures: documented steps for common changes
  • Rollback plan: procedures to reverse change if problems occur
  • Notification to affected users: communicate timing, impact, and expected duration
  • Post-implementation review: document results, issues, and lessons learned

7.3 Types of Changes

  • Standard Change: pre-approved, low-risk, routine changes with documented procedures
  • Normal Change: requires CAB review and approval; follows full change process
  • Emergency Change: expedited approval for urgent fixes; post-implementation review required

8. Backup and Recovery

8.1 Backup Types

TypeDescription
Full BackupComplete copy of all selected data; archive bit cleared; longest backup time; fastest restore
Incremental BackupBacks up only data changed since last backup (full or incremental); archive bit cleared; fastest backup; slower restore (requires full + all incrementals)
Differential BackupBacks up data changed since last full backup; archive bit not cleared; moderate backup time; faster restore than incremental (requires full + last differential)

8.2 Backup Best Practices

  • 3-2-1 Rule: 3 copies of data, 2 different media types, 1 offsite copy
  • Test restores regularly to verify backup integrity
  • Schedule backups during off-peak hours
  • Encrypt backup data for security
  • Maintain backup logs and verify completion
  • Store offsite backups in secure location
  • Define retention periods based on compliance and business requirements

8.3 Disaster Recovery

ConceptDefinition
RTO (Recovery Time Objective)Maximum acceptable time to restore service after disruption
RPO (Recovery Point Objective)Maximum acceptable data loss measured in time; determines backup frequency
Cold SiteBackup facility with power and cooling but no equipment; longest recovery time; lowest cost
Warm SiteBackup facility with some equipment and connectivity; moderate recovery time and cost
Hot SiteFully equipped backup facility ready for immediate failover; fastest recovery; highest cost

9. Regulated Data and Compliance

9.1 Data Protection Regulations

RegulationScope and Requirements
PCI DSSPayment Card Industry Data Security Standard; protects credit card data; requires encryption, access controls, and regular security testing
GDPRGeneral Data Protection Regulation; EU regulation for personal data; requires consent, data minimization, right to deletion, breach notification
HIPAAHealth Insurance Portability and Accountability Act; protects healthcare information; requires encryption, access controls, audit logs, and training

9.2 Handling Regulated Data

  • Classify data according to sensitivity and regulatory requirements
  • Implement appropriate access controls and encryption
  • Maintain audit trails for data access and modifications
  • Follow data retention and destruction policies
  • Report breaches according to regulatory timelines
  • Limit data collection to necessary information only
  • Train staff on compliance requirements and handling procedures

10. Remote Access and Support

10.1 Remote Support Tools

Tool TypeUse Cases
RDP (Remote Desktop Protocol)Windows remote access; port 3389; full desktop control; requires authentication
VNC (Virtual Network Computing)Cross-platform remote desktop; port 5900; screen sharing and control
SSH (Secure Shell)Secure command-line access; port 22; encrypted terminal sessions for Linux/Unix systems
Screen Sharing SoftwareWeb-based or application-based remote control; often requires user permission to initiate

10.2 Remote Access Security

  • Use strong authentication (multi-factor when available)
  • Encrypt all remote sessions
  • Verify user identity before initiating support
  • Limit remote access to necessary personnel
  • Log all remote access sessions
  • Disconnect sessions when support is complete
  • Use VPN for accessing internal resources remotely
  • Disable remote access features when not in use

10.3 Remote Support Best Practices

  • Obtain verbal or written permission before accessing system
  • Explain actions being performed to user
  • Respect user privacy; avoid viewing personal files
  • Document all actions taken during session
  • Verify issue resolution before ending session
  • Ensure user knows how to prevent future occurrences

11. Ticketing and Documentation

11.1 Ticketing System Elements

ElementPurpose
User InformationName, contact details, department, location of person reporting issue
Device InformationAsset tag, model, serial number, hostname of affected equipment
DescriptionDetailed problem statement, symptoms, error messages, when issue started
CategoriesHardware, software, network, security classification for routing and reporting
Severity/PriorityImpact level and urgency; determines response time requirements
StatusOpen, In Progress, Pending, Resolved, Closed tracking
AssignmentTechnician or team responsible for resolution

11.2 Documentation Requirements

  • Problem description: clear statement of issue reported by user
  • Troubleshooting steps: all actions taken to diagnose and resolve
  • Solution implemented: specific fix or workaround applied
  • Parts used: replacement components with part numbers
  • Time spent: accurate recording for billing and metrics
  • Follow-up actions: any pending tasks or monitoring required
  • User confirmation: acknowledgment that issue is resolved

11.3 Knowledge Base Management

  • Document common problems and solutions for future reference
  • Include step-by-step procedures for recurring issues
  • Update articles when new solutions are discovered
  • Use clear, searchable titles and keywords
  • Categorize articles for easy navigation
  • Review and verify accuracy periodically

12. Asset Management and Inventory

12.1 Asset Tracking

ElementDetails Recorded
Asset TagsUnique identifier affixed to equipment; barcode or RFID for scanning
Inventory ListsDatabase of all IT assets including hardware, software licenses, peripherals
Asset InformationManufacturer, model, serial number, purchase date, warranty expiration, assigned user, location
Lifecycle TrackingProcurement, deployment, maintenance, retirement stages

12.2 Procurement and Deployment

  • Follow purchasing procedures and approval workflows
  • Verify compatibility with existing infrastructure
  • Document vendor information and support contacts
  • Record warranty and support agreement details
  • Assign asset tags upon receipt
  • Add to inventory database before deployment
  • Configure and image devices according to standards
  • Document deployment date and assigned user

12.3 End-of-Life Procedures

  • Identify equipment for retirement based on age, support status, or failure
  • Back up all data before decommissioning
  • Sanitize or destroy storage devices to protect data
  • Remove from inventory and asset management system
  • Dispose through proper channels (recycling, donation, certified destruction)
  • Document disposal method and date
  • Update license counts if software licenses can be reassigned

13. Prohibited Content and Activities

13.1 Prohibited Content

  • Illegal materials: pirated software, copyrighted media, hacking tools
  • Inappropriate material: adult content, offensive images, hate speech
  • Malicious software: viruses, trojans, spyware, ransomware
  • Unlicensed software: applications without proper licensing
  • Personal business materials: files related to outside employment or business ventures

13.2 Prohibited Activities

  • Unauthorized access: accessing systems, data, or accounts without permission
  • Password sharing: providing credentials to others or using shared accounts
  • Unauthorized software installation: installing applications without approval
  • Personal use: excessive personal email, shopping, social media, gaming on company time
  • Network abuse: consuming excessive bandwidth, running personal servers
  • Data exfiltration: copying confidential data to personal devices or external services
  • Circumventing security: disabling antivirus, bypassing content filters, avoiding monitoring

13.3 Enforcement and Consequences

  • Monitor compliance with acceptable use policies
  • Report violations to appropriate management or security personnel
  • Document incidents for disciplinary action or legal proceedings
  • Consequences may include warnings, suspension of access, termination, or legal action
  • Technicians must report violations discovered during support activities

14. Physical Security

14.1 Access Controls

Control TypeImplementation
Badge SystemsID cards with magnetic stripe or RFID for entry; track who enters and exits; revoke access immediately upon termination
Biometric LocksFingerprint, retina, or facial recognition; unique authentication; prevent credential sharing
Security GuardsMonitor entry points; verify identification; challenge unknown individuals
MantrapsDouble-door entry requiring first door to close before second opens; prevents tailgating
Door LocksKey locks, cipher locks, or electronic locks on server rooms and restricted areas

14.2 Equipment Security

  • Cable locks: secure laptops and portable equipment to desks
  • Server locks: locked racks and cages in data centers
  • USB locks: physical blocks to prevent unauthorized USB device use
  • Laptop alarms: motion sensors that trigger when device is moved
  • Secure disposal: use locked bins for paper and media requiring secure destruction

14.3 Environmental Monitoring

  • Security cameras: monitor entry points and equipment areas; record for incident investigation
  • Motion sensors: detect unauthorized access during off-hours
  • Lighting: adequate illumination in parking areas and building perimeter
  • Alarm systems: intrusion detection with alerts to security personnel
  • Visitor logs: record all non-employee access including name, time, purpose, escort

14.4 Clean Desk Policy

  • Secure sensitive documents when not in use
  • Lock workstations when leaving desk
  • Store media and removable drives in locked drawers
  • Shred confidential papers before disposal
  • Clear whiteboards containing sensitive information

15. Mobile Device Management

15.1 Mobile Device Policies

Policy ElementRequirements
EnrollmentRegister device with MDM system; install management profile; accept policy terms
Security SettingsEnforce password/PIN; require encryption; enable remote wipe capability
App ManagementApprove allowed applications; block unauthorized apps; push corporate app updates
Container/PartitionSeparate corporate and personal data; enforce policies only on corporate partition
Lost/Stolen ResponseReport immediately; remote lock; remote wipe if necessary; deactivate corporate access

15.2 BYOD (Bring Your Own Device)

  • User agreement: acknowledge acceptance of corporate policies on personal device
  • Security baseline: minimum OS version, encryption, password requirements
  • Data separation: corporate data isolated from personal apps and files
  • Limited access: may restrict access to sensitive systems or data
  • Compliance monitoring: MDM verifies device meets security requirements
  • Offboarding: corporate data wiped upon separation; personal data retained

15.3 Mobile Security Features

  • Passcode lock: require complex password or biometric authentication
  • Full device encryption: protect data at rest
  • Remote lock: disable device remotely if lost or stolen
  • Remote wipe: erase all data remotely to prevent data breach
  • Locator services: GPS tracking to find lost devices
  • App whitelisting/blacklisting: control which applications can be installed
  • VPN requirement: mandate encrypted connection for corporate access
The document Cheatsheet: IT Support Best Practices is a part of the CompTIA A+ Course CompTIA A+ Core 2.
All you need of CompTIA A+ at this link: CompTIA A+
Explore Courses for CompTIA A+ exam
Get EduRev Notes directly in your Google search
Related Searches
ppt, Sample Paper, practice quizzes, Important questions, MCQs, Exam, Free, mock tests for examination, Semester Notes, video lectures, Previous Year Questions with Solutions, Cheatsheet: IT Support Best Practices, shortcuts and tricks, Viva Questions, Objective type Questions, past year papers, Extra Questions, Cheatsheet: IT Support Best Practices, Cheatsheet: IT Support Best Practices, Summary, pdf , study material;