The Complete IT Support L1/L2 Troubleshooting Playbook: Windows CLI, Active Directory & Network Diagnostics

Working in Level 1 and Level 2 IT Support, Help Desk, or Service Desk Operations requires more than basic computer literacy. You are the frontline defender ensuring employee workstations, domain authentication, network connectivity, and corporate applications remain operational.

This comprehensive playbook covers the industry-standard CompTIA A+ 6-step troubleshooting methodology, essential Windows CMD/PowerShell diagnostics, Active Directory user management workflows, and step-by-step solutions for real-world enterprise tickets.

1. The CompTIA 6-Step Troubleshooting Framework

Hiring managers and enterprise ITIL organizations expect candidates to follow a structured diagnostic progression rather than guessing solutions randomly:

1. Identify the Problem: Gather details from the user, question environmental changes, observe symptoms, and check event logs.
2. Establish a Theory of Probable Cause: Question the obvious (e.g., unplugged cable, CAPS LOCK on password) and consider multiple factors.
3. Test the Theory to Determine Cause: If confirmed, proceed to the action plan. If disproven, establish a new theory or escalate.
4. Establish a Plan of Action: Formulate steps to resolve the issue while identifying potential side effects.
5. Verify Full System Functionality: Confirm with the end user that their workflow is restored and implement preventive measures.
6. Document Findings, Actions, and Outcomes: Log comprehensive notes in the ticketing system (ServiceNow, Jira Service Desk, Zendesk).

2. Essential Windows Command Line & PowerShell Diagnostic Toolkit

A top-tier IT Support technician resolves problems faster using the command line rather than clicking through deep GUI menus:

# 1. Inspect IP address, subnet mask, default gateway, and DHCP lease
C:\> ipconfig /all

# 2. Release and renew dynamic IP from DHCP server
C:\> ipconfig /release
C:\> ipconfig /renew

# 3. Flush DNS resolver cache (solves website resolution mismatch)
C:\> ipconfig /flushdns

# 4. Test DNS server resolution for specific domain names
C:\> nslookup mail.company.com

# 5. Trace Layer 3 packet hops to identify where a network drops
C:\> tracert 8.8.8.8

# 6. Force immediate Group Policy update from Domain Controller
C:\> gpupdate /force

# 7. Scan and repair corrupted Windows system files
C:\> sfc /scannow

3. Active Directory (AD DS) Operations

Active Directory Domain Services is the centralized identity management database used by 90%+ of global enterprises. As an L1 Support engineer, your primary AD responsibilities include:

• Account Lockouts & Password Resets: Unchecking "Account is locked out" in AD Users and Computers (ADUC) and generating compliant temporary passwords.
• Managing Security Groups: Adding users to departmental security groups (e.g., SG-Marketing-RW) to grant shared drive permissions.
• Organizational Units (OUs): Placing computer accounts into the correct OU so departmental Group Policy Objects (GPOs) apply cleanly.

# PowerShell: Quick Active Directory User Inspection
PS C:\> Get-ADUser -Identity jsmith -Properties LockedOut, PasswordExpired, MemberOf

# PowerShell: Unlock a user account immediately
PS C:\> Unlock-ADAccount -Identity jsmith

4. Real-World Ticket Resolution Playbooks

Summary & Interview Readiness

Technical troubleshooting is 50% technical knowledge and 50% customer service composure. Always validate user frustrations with empathy, communicate updates clearly inside ticketing systems, and never close a ticket without confirmed user satisfaction.