4.0 Operational Procedures

• Tickets should identify the user, device, symptoms, impact, contact method, location, category, severity, status, owner, actions, and resolution.
• Good notes allow another technician to continue without starting over.
• Categories route the work; severity reflects business impact and urgency.
• Escalate when the current level lacks the skill, access, tools, permissions, or vendor relationship needed.

Information Systems

• Asset management tracks device ownership, location, warranty, lifecycle, licensing, configuration, and history.
• A CMDB connects assets, services, users, applications, and configuration items.
• Accurate records support troubleshooting, audits, procurement, warranty claims, security, and lifecycle planning.

Procedures and Knowledge

• Use incident reports, SOPs, installation procedures, upgrade records, onboarding/offboarding checklists, SLAs, and knowledge base articles.
• Knowledge articles should include symptoms, environment, steps, verification, owner, and date.
• Search with exact error messages, device models, service names, and keywords that match the symptom.

Communication

• Issue descriptions should be clear and factual.
• Progress notes show what was tried, what happened, and what happens next.
• Resolution notes explain the fix, not just say "done."

• A change request defines purpose, scope, type, owner, affected systems, timeline, maintenance window, change freeze conflicts, and communication plan.
• Risk planning includes impact analysis, risk level, backup plan, rollback plan, sandbox testing, and approvals.
• Peer review catches errors before implementation.
• End-user acceptance matters when the change affects workflow.

Change Types

• Standard changes are low-risk, preapproved, and repeatable.
• Normal changes follow planning, review, approval, implementation, and verification.
• Emergency changes address urgent issues but still require documentation after stabilization.
• Unauthorized changes create risk because they bypass review and accountability.

Implementation

• Back up before risky changes and know how to roll back.
• Implement during the approved window and communicate status.
• Verify the original goal, monitor for side effects, update documentation, and close the change record.

Exam Clues

• Approval, maintenance window, rollback, affected systems, impact, and peer review point to change management.
• When something goes wrong after a change, check the change record and rollback plan.

• Backup plans should match recovery time, recovery point, storage limits, and risk.
• Full backups copy all selected data. Incremental backups copy changes since the last backup. Differential backups copy changes since the last full backup.
• Synthetic full backups combine backup sets into a new full backup without rereading the source.
• Test restores regularly; untested backups are assumptions.

Storage and Rotation

• Use onsite backups for quick restores and offsite/cloud backups for site-level events.
• The 3-2-1 rule means three copies, two media types, and one offsite copy.
• Grandfather-father-son rotation keeps daily, weekly, and monthly restore points.
• Protect backups from ransomware, theft, corruption, and accidental deletion.

Recovery Choices

• Restore in place when returning data to the original location is safe.
• Restore to alternate location when comparing, preserving evidence, or avoiding overwrite risk.
• Image recovery restores system state; file recovery restores selected data.
• Verify restored data and document what was recovered.

Risk and Privacy

• Backups may contain sensitive data and must follow retention, encryption, and access-control policies.
• Do not restore infected, corrupted, or unauthorized data over clean copies.

• Use ESD straps, ESD mats, antistatic bags, and proper component handling to protect electronics.
• Disconnect power before servicing equipment unless a documented procedure requires live testing.
• Respect high-voltage devices such as power supplies, CRTs, printers, and UPS units.
• Use lockout/tagout or site-specific procedures when required.

Personal Safety

• Use proper lifting technique and ask for help with heavy equipment.
• Wear goggles, gloves, masks, or other PPE when the environment requires it.
• Keep walkways clear and manage cables to avoid trips, blocked airflow, and accidental disconnection.
• Know fire extinguisher locations and the correct class for the fire type.

Equipment Safety

• Handle components by edges and avoid touching contacts.
• Store components in antistatic packaging.
• Do not open sealed high-voltage components unless trained and authorized.
• Follow manufacturer and site procedures for printers, batteries, and power equipment.

Professional Judgment

• Safety rules vary by workplace, customer site, local regulation, and equipment type.
• When the task is unsafe or outside your role, stop and escalate.

• Temperature, humidity, airflow, dust, power quality, and equipment placement affect stability and lifespan.
• High heat can cause shutdowns, throttling, failed components, and shortened battery life.
• Low humidity increases static risk; high humidity can cause corrosion or condensation.
• Dust blocks airflow and traps heat.

Materials and Disposal

• MSDS/SDS documentation explains safe handling, storage, cleanup, and disposal.
• Batteries, toner, ink, chemicals, and electronic waste may require special disposal or recycling.
• Follow local regulations and organization policy.

Power Protection

• Surge suppressors help protect against voltage spikes.
• UPS units provide temporary battery power and controlled shutdown time.
• Brownouts, blackouts, surges, and unstable power can damage systems or corrupt data.

Cleaning and Placement

• Use compressed air carefully and in short bursts; do not overspin fans.
• Use approved vacuums for toner or electronics when required.
• Keep vents clear and avoid placing equipment near heat, moisture, or heavy dust.

• Prohibited content or activity may require escalation, management notification, incident reporting, and evidence preservation.
• Do not investigate beyond your role when policy, law, or chain of custody applies.
• Chain of custody documents who handled evidence, when, where, and why.
• Order of volatility helps prioritize evidence collection when authorized.

Privacy and Data

• Protect PII, PHI, payment card data, government IDs, customer records, employee data, and confidential business information.
• Follow NDA, MNDA, retention, disposal, classification, and least-privilege requirements.
• Do not discuss customer or employee data casually.

Licensing

• Licensing terms may include EULA, DRM, valid license, open-source terms, personal versus corporate use, and perpetual or subscription licensing.
• License violations can create legal and audit risk.
• Use approved sources and record license assignment where required.

Acceptable Use and Compliance

• AUPs define allowed and prohibited technology use.
• Compliance may require splash screens, consent banners, documented policies, and user acknowledgment.
• Escalate suspected violations through approved channels.

• Present yourself professionally for the environment and follow dress code and workplace expectations.
• Use clear, respectful language and avoid unnecessary jargon.
• Listen actively, avoid interrupting, and restate the issue to confirm understanding.
• Be culturally sensitive and use appropriate titles, names, and communication styles.

Time and Focus

• Arrive on time or notify the customer if delayed.
• Stay focused during work hours and avoid personal calls, texting, social media, and unrelated conversations.
• Respect the user's time while still performing thorough work.

Difficult Interactions

• Stay calm, professional, and solution-focused.
• Do not argue, get defensive, make assumptions, or judge the customer.
• Use open-ended questions, take concerns seriously, and narrow the scope of the problem.

Expectations and Confidentiality

• Explain the plan, timeline, options, documentation, and follow-up steps.
• Document services provided and check back when appropriate.
• Keep customer data private and discuss sensitive information only with those who need to know.

• Scripting languages automate repetitive tasks and run a series of commands.
• Common file types include .bat, .ps1, .vbs, .sh, .js, and .py.
• PowerShell is a major Windows scripting and command-line tool that uses cmdlets and .ps1 scripts.
• Different languages fit different operating systems, tasks, and environments.

Why Scripts Are Used

• Scripts can automate restarts, remap network drives, install applications, run backups, gather system information, and initiate updates.
• Automation improves consistency, saves time, reduces manual errors, and supports work across many systems.
• Scheduled scripts can run during off-hours or at startup/logon.

Risks

• Scripts can install software, download files, change settings, modify registry keys, consume resources, restart systems, or affect many computers quickly.
• Small mistakes can cause broad impact.
• Unknown scripts can deliver malware or make unauthorized changes.

Safe Habits

• Use trusted sources and review code before running it.
• Test in a lab, VM, test device, or small group first.
• Use least privilege, back up before risky changes, track what changes, verify results, and document the outcome.

• RDP provides full graphical Windows remote desktop access and uses TCP port 3389 by default.
• VNC provides cross-platform graphical remote access through the RFB protocol.
• VPN creates an encrypted tunnel to private network resources; VPN concentrators manage connections.
• SSH provides encrypted command-line access and uses TCP port 22 by default.

Management and VM Tools

• RMM platforms monitor, patch, inventory, alert, and remotely manage many devices from a central dashboard.
• SPICE provides remote display access for virtual machines.
• WinRM lets administrators run commands and scripts on remote Windows systems and receive output.
• Third-party tools include screen sharing, video conferencing, file transfer, endpoint management, and client-to-site VPN software.

Security Controls

• Use strong authentication, MFA where available, least privilege, encryption, patching, monitoring, and logging.
• Restrict exposure with VPNs, gateways, firewalls, ACLs, trusted IP ranges, and approved tools.
• Close sessions and remove temporary access when work is complete.

Exam Traps

• Do not choose RDP for every scenario.
• Do not use Telnet when SSH is required.
• Do not treat VPN as safe if credentials, MFA, access scope, or concentrator patching are weak.
• Remember that RMM is a high-value target because it can reach many systems.

• Appropriate AI uses include data analysis, automation support, specialized decision support, translation, proofreading, summaries, and communication support.
• AI should support professional judgment, not replace accountability.
• Review AI output before using it in tickets, user communication, documentation, code, security reports, or decisions.

Inappropriate Use

• Do not use AI for fraud, impersonation, deepfakes, fake identities, plagiarism, hidden authorship, or unethical shortcuts.
• Follow disclosure, citation, acceptable use, and workplace policy.
• Preserve evidence and escalate suspected AI-assisted deception when required.

Limitations

• AI is limited by training data, model design, prompts, assumptions, and connected sources.
• Bias can appear in data or algorithms.
• Hallucinations are confident but incorrect or unsupported outputs.
• Polished writing is not proof of accuracy.

Public vs. Private AI

• Public AI is broadly available and useful for general, non-sensitive tasks.
• Private or enterprise AI is approved or controlled by an organization and may use internal data.
• Do not paste customer data, credentials, certificates, logs, source code, security findings, or regulated data into public AI unless policy explicitly allows it.
• Verify important output and protect output that contains sensitive or inaccurate information.