P-TECH IT
All P-TECH sites online· 9:15 PM Eastern, open the status page

Lesson 19: Operational Procedures: Documentation, Change, Backup, Safety, Scripting and Remote Access

CompTIA A+ Core 2 (220-1202) · Objectives 220-1202 4.1, 220-1202 4.2, 220-1202 4.3, 220-1202 4.4, 220-1202 4.5, 220-1202 4.8, 220-1202 4.9 · Download .docx

Objectives

Key terms

Ticketing system
Software that records, tracks, prioritizes, and documents support requests from submission to resolution.
Change management
Formal process for requesting, evaluating, approving, scheduling, implementing, and documenting changes to IT systems to reduce disruption.
Full backup
Backup that copies all selected data every time, giving the fastest restore but taking the most time and storage.
ESD
Electrostatic Discharge; a sudden flow of static electricity between objects that can damage computer components, even below the level a person can feel.
SDS
Safety Data Sheet, formerly MSDS; a manufacturer document describing a product's hazards, safe handling, first aid, and disposal requirements.
Script
Text file of commands executed by an interpreter rather than compiled, used to automate repetitive administrative tasks.
RDP
Remote Desktop Protocol; Microsoft's protocol for remotely controlling a Windows desktop over TCP and UDP port 3389.
Ticket category
Classification of a support request by type, such as hardware, software, network, or account, used to route it to the right team.
Rollback plan
Documented steps for undoing a change and restoring the previous working state if the change fails.
Incremental backup
Backup that copies only data changed since the last backup of any type; restoring needs the last full plus every later incremental.
ESD strap
Wrist band connected to ground that safely drains static charge from a technician's body while working inside equipment.
Proper battery disposal
Recycling batteries, especially lithium-ion and lead-acid, through approved programs instead of trash because they can leak toxins or catch fire.
.bat
Windows batch file containing Command Prompt commands that run in sequence when the file is executed.
VNC
Virtual Network Computing; a cross-platform remote desktop system that shares the screen using the RFB protocol, typically on TCP port 5900.
Ticket severity
Rating of how serious and urgent an issue is, based on its impact and how many users are affected, which sets the response order.

The concept

220-1202 4.1 — Use documentation and support systems: ticketing, knowledge bases, asset management, SLAs and incident reports. ticket required fields: The ticket identifies the user (A. Knight), a category (Hardware), a priority (Medium), a status, and a description, but nothing identifies the device itself. ticket progress notes: Clear, dated progress notes record each action and its outcome, so whoever picks up the ticket does not repeat failed fixes or lose context. CompTIA's ticketing objective stresses clear, concise written communication across the issue description, progress notes, and the final resolution. ticket escalation levels: Escalation levels exist so that issues exceeding a tier's skills or authority move to the group that can resolve them, with the ticket history intact. The technician should escalate to the network team, document what was found so far, and keep the user informed of the handoff. CMDB purpose: A configuration management database (CMDB) stores configuration items (CIs) such as devices, software, and services, along with their settings and the relationships between them. Because it maps dependencies, technicians and change boards can use it to estimate the impact of a change on other systems. warranty in asset records: Asset records follow each device through the procurement life cycle (purchase, deployment, maintenance, and disposal), including its warranty terms. Checking the warranty expiration date and coverage type tells the technician whether to file a manufacturer claim instead of buying a part. SOP custom installation: A standard operating procedure (SOP) gives step-by-step instructions that every technician follows, so the outcome is repeatable. CompTIA specifically lists a software package custom installation procedure as a type of SOP.

220-1202 4.2 — Apply change management: requests, risk analysis, change boards, rollback plans and user acceptance. rollback plan: A rollback (backout) plan documents exactly how to undo a change and return systems to their last known good state if the change fails. Change boards require it before approval because even well-tested changes can fail in production. sandbox testing: Sandbox testing applies the change in an isolated environment that mimics production, so conflicts and bugs surface without affecting real users or data. Sandbox results inform the change board's decision and help refine the rollback plan. emergency change type: An emergency change addresses an urgent issue, such as an actively exploited vulnerability, that cannot wait for the normal approval cycle. It uses an expedited approval path, such as an emergency change board or a designated approver, and it is still documented and reviewed afterward. change freeze: A change freeze is a period during which non-emergency changes are prohibited, usually around business-critical events such as grading deadlines, fiscal year-end, or major launches. It reduces the chance that a change causes an outage when the organization can least tolerate one. change request impact and risk: The board's two concerns map directly to two request-form fields. The affected systems/impact section shows which services and users depend on DHCP and would be disrupted, and the risk analysis estimates the likelihood and severity of failure and assigns a risk level such as low, medium, or high. peer review: Peer review is a qualified colleague examining a proposed change, its steps, and any code before approval to catch mistakes the author missed. It improves quality and spreads knowledge across the team.

220-1202 4.3 — Implement workstation backup and recovery: full, incremental, differential, rotation schemes and the 3-2-1 rule. synthetic full backup: A synthetic full backup is assembled on the backup server or storage by merging the most recent full backup with later incrementals, producing a new full backup without reading every file from the protected computer again. This shortens the backup window and reduces load on the source system and network, while still giving the simple restore of a single full backup. differential backup size: A differential backup copies everything that changed since the last full backup. From Sunday's full through Thursday, four days of changes accumulate: Monday + Tuesday + Wednesday + Thursday = 4 × 20 GB = 80 GB. incremental restore sets: Restoring from incrementals requires the last full backup plus every incremental taken since, applied in order. The latest full is Saturday's, and incrementals ran Sunday, Monday, Tuesday, and Wednesday nights, so the restore needs 1 + 4 = 5 sets. restore to alternate location: Restoring to an alternative location, such as a different folder or file name, recovers the older version without touching the current file, so the user keeps both. An in-place (overwrite) restore replaces the current file with the backup copy, which is appropriate only when the current version is unwanted. backup testing frequency: A backup is proven good only when data is actually restored from it. Regular test restores at a defined frequency, such as monthly file-level tests and periodic full-system tests, verify that media are readable, that jobs capture the right data, and that staff know the procedure. 3-2-1 backup rule: The 3-2-1 rule calls for three copies of the data (the original plus two backups), on two different types of media, with one copy off-site. The office already has two copies on two media (internal SSD and USB drive), so it needs a third copy stored off-site, such as cloud storage or a drive kept at another location.

220-1202 4.4 — Use common safety procedures: ESD protection, electrical safety, lifting and fire safety. ESD wrist strap: An ESD wrist strap connected to a ground point, such as the unpainted metal chassis, keeps the technician's body at the same potential as the computer, so static charge drains away safely instead of discharging through the RAM. Damage can occur at voltages far below what a person can feel. cable management: Proper cable management routes cables away from foot traffic, along walls, through raceways, or under rated cord protectors, so they are not trip hazards and cannot be pulled loose or damaged. Trip hazards cause both injuries and damaged equipment. proper lifting technique: Proper lifting technique uses the strong leg muscles instead of the back: bend at the knees, keep the back straight, hold the load close to the body, and lift smoothly without twisting. For heavy or awkward loads, a team lift or a cart reduces the risk further. electrical fire extinguisher class: In the U.S. classification system, Class C covers energized electrical equipment. goggles and air filter mask: Blowing out dust with compressed air throws fine particles into the air. Safety goggles protect the eyes from flying debris, and an air filter mask keeps the technician from inhaling the fine dust. equipment grounding: The grounding prong provides a low-resistance path for fault current, so if a live conductor touches the metal case, the current trips the breaker instead of passing through a person. Without it, the case can become energized.

220-1202 4.5 — Summarize environmental controls and impacts: temperature, humidity, power protection and proper disposal. safety data sheet: A safety data sheet (SDS), formerly called a material safety data sheet (MSDS), is provided by the manufacturer of a hazardous product and lists its hazards, first aid, handling and storage, spill cleanup, protective equipment, and disposal considerations. OSHA's Hazard Communication Standard requires employers to keep SDSs readily accessible to employees. battery and toner disposal: Lithium-ion batteries can catch fire if crushed or punctured and contain materials that should not go to landfills, so they belong with a certified battery or e-waste recycler, with terminals taped and swollen packs isolated. Toner cartridges should go back through a manufacturer or vendor recycling program, or be disposed of as the SDS and local regulations direct. toner spill cleanup: Toner particles are fine enough to pass through ordinary vacuum filters and be blown back into the air, and a cloud of fine toner dust can even ignite. A toner vacuum, which has a fine-particle filter and a static-safe design, captures the particles safely. temperature, humidity, ventilation: Very low humidity lets static charge build up and increases ESD risk, so humidity should be raised into a moderate range of roughly 40–60% (very high humidity risks condensation). The high temperature points to poor airflow: equipment placed against a wall cannot exhaust its heat, so moving the rack to allow clearance and improving ventilation or cooling addresses the heat. UPS for brownouts and blackouts: An uninterruptible power supply (UPS) contains a battery that supplies power instantly when utility voltage sags (brownout) or fails (blackout), keeping equipment running for minutes. Many UPS units also signal the server over USB or the network to shut down cleanly before the battery runs out. disposal of devices and assets: Proper disposal of devices and assets has two parts: protect the data, then handle the hardware responsibly. Drives are sanitized (for example, purged or destroyed according to NIST SP 800-88) and documented, and the equipment goes to a certified electronics recycler, because electronics can contain lead, mercury, and other hazardous materials.

220-1202 4.8 — Explain scripting basics: file types, use cases and risks of scripts. .ps1 script files: The .ps1 extension identifies a PowerShell script. PowerShell is an object-based shell and scripting language included with Windows and also available for macOS and Linux. .sh script files: Scripts for Bash and similar Unix shells conventionally use the .sh extension and begin with a shebang line such as #!/bin/bash. They run natively on Linux and macOS and are commonly scheduled with cron for tasks such as log rotation and backups. remapping network drives: Remapping network drives is a classic scripting use case: a logon script, such as a batch file using net use or a PowerShell script using New-PSDrive, runs for each user at sign-in and maps H: to the new server path. Scripting the change fixes every computer consistently instead of having technicians remap drives by hand. resource mishandling crashes: Scripts that mishandle resources, such as holding thousands of open file handles and ever-growing data in memory inside a loop, can exhaust what the operating system can provide, causing slowdowns and browser or system crashes. In Python, opening files with the with statement closes each one automatically, and processing each file and then discarding its data keeps memory use flat. untrusted script risks: Scripts from untrusted sources can unintentionally introduce malware or inadvertently change system settings, and running them with administrator rights magnifies the damage. The technician should read and understand the code, verify its source, and test it in an isolated sandbox or virtual machine before any deployment. .bat batch files: A .bat (batch) file contains Command Prompt commands that cmd.exe runs in order. Batch files are the oldest Windows scripting format and work on every Windows version without extra software.

220-1202 4.9 — Use remote access technologies: RDP, SSH, VPN, VNC, RMM tools and their security considerations. WinRM remote management: Windows Remote Management (WinRM) is Microsoft's implementation of the WS-Management protocol and underlies PowerShell remoting (for example, Invoke-Command), letting administrators run commands on many machines without a GUI session. It listens on TCP 5985 (HTTP) and 5986 (HTTPS). SSH replacing Telnet: SSH (Secure Shell, TCP port 22) provides an encrypted remote command-line session that protects credentials and commands in transit, whereas Telnet sends everything in cleartext. SSH can be hardened further with key-based authentication, disabling direct root login, and limiting which hosts may connect. securing RDP with VPN: RDP (TCP 3389) exposed directly to the internet is a common target for password-guessing and exploit attacks. Requiring users to connect to a VPN first, so RDP is reachable only through the encrypted tunnel, removes the exposed service, and MFA on the VPN adds further protection. remote monitoring and management: Remote monitoring and management (RMM) platforms install an agent on each endpoint that reports health and inventory to a central console, which can then alert, patch, run scripts, and open remote sessions across many customers. Because one compromised RMM account can reach every managed device, RMM access needs MFA, least privilege, and auditing. SPICE for VM consoles: SPICE (Simple Protocol for Independent Computing Environments) is an open remote display protocol built for virtualized desktops, commonly used with KVM/QEMU, and it supports USB redirection, audio, and clipboard sharing. SPICE connections should be encrypted with TLS and restricted to authorized administrators, because console access bypasses the guest operating system's own network controls. VNC desktop sharing: Virtual Network Computing (VNC) uses the Remote Frame Buffer (RFB) protocol to share a graphical desktop across platforms, with servers and viewers available for Windows, macOS, and Linux. It typically listens on TCP 5900.

Worked examples

Example 1: Before planning a summer device refresh, a district needs a list of every laptop with its model, purchase year, building, and assigned room. Which asset management document provides this? Answer: Inventory list. An inventory list records each asset and its key attributes, such as model, age, location, and asset tag. Planners can sort and count it to see how many devices are due for replacement and where they are.
Example 2: Before approving a firmware update for the district's core firewall, the change board asks how the team will return the device to its previous working state if the update fails. Which part of the change documentation answers this question? Answer: Rollback plan. A rollback (backout) plan documents exactly how to undo a change and return systems to their last known good state if the change fails. Change boards require it before approval because even well-tested changes can fail in production. It usually depends on the backup plan, such as a saved copy of the current firmware and an exported configuration taken before the change.
Example 3: Refer to the exhibit. A file server receives a 500 GB full backup on Sunday. Each day Monday through Saturday, about 20 GB of different files change, and no file changes twice. Using the full + differential strategy, approximately how much data does Thursday's backup copy? Answer: 80 GB. A differential backup copies everything that changed since the last full backup. From Sunday's full through Thursday, four days of changes accumulate: Monday + Tuesday + Wednesday + Thursday = 4 × 20 GB = 80 GB. Differentials grow each day until the next full backup, which is the trade-off for needing only two sets to restore.

Common mistakes

Self-check

Try each one before you look. A miss here costs nothing and tells you exactly what to reread.

1. A technician opens the help desk ticket shown in the exhibit to begin work. Based on ticketing best practices, which essential information is missing and should be added before troubleshooting starts?
2. A change request to upgrade the core switches this weekend lists the purpose, risk, and rollback steps. The change board sends it back, asking who will carry out the work and who is accountable if problems arise. What must be added?
3. A sync error corrupted every file in a user's project folder. He wants the folder returned to exactly where it was, with the damaged copies replaced by last night's good versions, and does not need to keep the damaged files. Which recovery method fits?
4. A projector's power cable runs across a classroom walkway from a wall outlet to the teacher's desk, and a student recently tripped on it. What should the technician do?
5. A district is retiring 300 old desktops whose hard drives hold student records. What is the proper disposal process?

Canvas is the official record. This companion enhances the PGCC curriculum; it does not replace it. Last name and class year only. Students with a 504 plan or IEP: your accommodations apply.

← Lesson 18: Mobile, Browser and PC SecurityLesson 20: Policy, Privacy, Professionalism and AI →

↑ Back to top