← Back to BlogTemplates

Essential IT Admin SOP Templates for 2026: Master Password Resets, System Setup, and Troubleshooting with AI Efficiency

ProcessReel TeamApril 27, 202628 min read5,586 words

Essential IT Admin SOP Templates for 2026: Master Password Resets, System Setup, and Troubleshooting with AI Efficiency

In 2026, the landscape of IT administration is more complex and demanding than ever. Digital transformation initiatives, hybrid work environments, and an ever-evolving threat landscape place immense pressure on IT teams. From managing a myriad of applications and devices to safeguarding sensitive data, IT administrators are the unsung heroes keeping organizations operational. Yet, without clear, consistent procedures, even the most skilled teams can struggle with efficiency, consistency, and scalability. This is where well-defined Standard Operating Procedures (SOPs) become not just beneficial, but absolutely critical.

Imagine a world where every IT support specialist, regardless of their tenure, handles a password reset with the same security protocols and efficiency. Envision new systems being deployed with zero configuration drift, consistently adhering to security baselines. Picture troubleshooting complex network issues with a structured, step-by-step approach that significantly reduces resolution times and unnecessary escalations. This isn't a fantasy; it's the reality achievable through comprehensive IT Admin SOP templates.

The absence of robust SOPs in IT administration often leads to a cascade of problems: inconsistent service delivery, heightened security risks due to varied approaches, slower onboarding for new IT personnel, increased Mean Time To Resolution (MTTR) for critical issues, and ultimately, a frustrated user base. Furthermore, knowledge becomes siloed, residing only in the minds of a few senior administrators, creating a single point of failure and hindering the team's collective growth.

This article will delve into three high-impact IT Admin SOP templates – Secure Password Reset, New System Setup, and Basic System Troubleshooting – providing actionable steps and illustrating their profound impact on operational excellence. More importantly, we'll explore how modern AI tools like ProcessReel are transforming the creation and maintenance of these essential documents, converting complex screen recordings with narration into professional, publish-ready SOPs with unprecedented ease.

The Indispensable Role of SOPs in Modern IT Administration

SOPs are the backbone of any efficient operation, and in IT, their importance is amplified by the dynamic nature of technology and the critical impact of IT failures. They provide a standardized framework for performing routine tasks, ensuring predictability, quality, and compliance across all IT functions.

Consider the common challenges faced by IT departments in organizations employing 200-500 staff:

The Tangible Benefits of Robust IT SOPs

Implementing comprehensive SOPs delivers measurable improvements:

  1. Ensured Consistency and Quality: Every task is performed uniformly, maintaining high standards and predictable outcomes. For instance, a standardized "new laptop setup" ensures all devices meet the same security and software baseline.
  2. Increased Efficiency and Productivity: By codifying the most efficient way to perform tasks, SOPs eliminate guesswork, reduce redundant steps, and allow IT staff to complete operations faster. A well-documented password reset procedure can cut average resolution time by 60%.
  3. Reduced Training Time and Costs: New hires can rapidly come up to speed by following detailed, step-by-step guides, freeing up senior IT personnel for more complex projects. This significantly reduces the overhead associated with knowledge transfer.
  4. Improved Knowledge Retention and Transfer: SOPs act as a living knowledge base, preventing the loss of critical information when personnel change. They democratize operational expertise across the team.
  5. Enhanced Security and Compliance: Documented procedures ensure that security policies are consistently applied and auditable trails exist for critical operations, simplifying compliance checks and reducing the risk of security breaches.
  6. Lower Error Rates: Clear instructions minimize human error, leading to fewer incidents, less rework, and a more stable IT environment.
  7. Faster Problem Resolution: With structured troubleshooting guides, IT staff can diagnose and resolve issues more quickly, minimizing disruption for end-users and business operations.

Organizations often underestimate the cumulative cost of undocumented processes. A recent study indicated that poor documentation practices could cost large enterprises hundreds of thousands of dollars annually in lost productivity and increased support overhead. By investing in comprehensive IT Admin SOP templates, IT departments are not just creating documents; they are investing in the long-term resilience, efficiency, and security of the entire organization.

Core IT Admin SOP Templates: Pillars of Operational Excellence

To illustrate the practical application and impact of well-structured SOPs, we'll examine three foundational IT admin procedures. These represent common, high-frequency tasks that, when standardized, yield significant returns in terms of efficiency, security, and staff productivity.

IT Admin SOP Template 1: Secure Password Reset Procedure

The password reset request is one of the most frequent interactions between end-users and the IT help desk. While seemingly simple, an insecure or inconsistent password reset process can pose significant security risks, lead to compliance violations, and cause immense frustration for users and IT staff alike.

Importance: A standardized password reset SOP ensures that user identities are rigorously verified, security protocols are consistently applied, and temporary credentials are communicated securely. This minimizes the risk of unauthorized access, reduces the potential for social engineering attacks, and streamlines a common, often time-consuming, support request. From a compliance perspective, robust password management procedures are critical for frameworks like HIPAA, GDPR, and PCI DSS.

Challenges Without a Clear SOP:

Real-World Impact and Metrics (for an organization with 300 employees, ~100 password resets/month):

Without a clear SOP, an average password reset might take a Tier 1 help desk technician 15 minutes, factoring in identity verification, navigating different systems (e.g., Active Directory, various SaaS apps), and communicating the new password. With a well-defined SOP, this time can be reduced to 5 minutes, primarily through a consistent verification script and streamlined system access.

Detailed Steps: Secure Password Reset Procedure (Example using Microsoft Active Directory/Azure AD)

This procedure outlines the steps for resetting a user's password securely and efficiently.

  1. Receive Password Reset Request:
    • Method: Via IT service desk ticketing system (e.g., Jira Service Management, Zendesk Support), phone call, or approved communication channel.
    • Initial Action: Create or update an incident ticket, noting the user's name, affected system/account, and time of request.
  2. Verify User Identity:
    • Primary Method (Internal Staff):
      1. Ask for the user's employee ID, full name, and last 4 digits of their social security number (or another pre-defined secure identifier).
      2. Cross-reference with HR system or employee directory.
      3. If unsure, use a pre-defined security question (e.g., "What was the name of your first pet as recorded in your HR profile?") or require multi-factor authentication (MFA) approval if the user has access to their registered device.
    • Primary Method (External Contractors/Vendors):
      1. Verify against a sponsor/manager who can confirm their identity directly.
      2. Use pre-registered security questions.
      3. Require MFA approval if possible.
    • Crucial Note: Never accept identity verification solely based on information easily found in public records or social media. If identity cannot be definitively verified, escalate to a Tier 2 administrator or decline the request until further proof is provided.
  3. Access User Account in Directory Service:
    • For On-Premise AD:
      1. Open "Active Directory Users and Computers" (dsa.msc).
      2. Navigate to the appropriate Organizational Unit (OU) for the user.
      3. Locate the user's account, right-click, and select "Reset Password..."
    • For Azure AD (Microsoft 365/Cloud Accounts):
      1. Log in to the Azure portal (portal.azure.com) with appropriate administrative credentials.
      2. Navigate to "Azure Active Directory" > "Users" > "All users."
      3. Search for the user's account, click on their profile, then select "Reset password" from the top menu.
  4. Initiate Password Reset:
    • Set Temporary Password:
      • Generate a strong, complex temporary password using a secure password generator (e.g., built-in tool, LastPass, 1Password).
      • Important: Ensure "User must change password at next logon" is checked (for AD) or selected (for Azure AD). This forces the user to create their own unique, secure password immediately.
    • Do Not Use: Simple, easily guessable passwords like "password123" or the user's name.
  5. Securely Communicate Temporary Password:
    • Preferred Method 1 (Out-of-Band): Send the temporary password via a pre-registered, alternate communication channel (e.g., personal email address, personal phone via SMS, or directly communicate verbally if the user is physically present and verified). Never send it to the locked-out email address.
    • Preferred Method 2 (MFA-gated): If the user can receive MFA prompts, send the temporary password to their verified mobile device via SMS or an authenticated app notification after they confirm their identity via MFA.
    • Avoid: Emailing the temporary password to their primary work email address if that account is compromised or inaccessible.
  6. Instruct User on Next Steps:
    • Clearly inform the user that the provided password is temporary and must be changed upon their first successful login.
    • Provide instructions for accessing the system and changing the password (e.g., "Go to portal.office.com, enter the temporary password, and you'll be prompted to create a new one").
    • Advise them on password best practices (minimum length, complexity requirements, avoiding reuse).
  7. Document the Incident and Resolution:
    • Update the IT service desk ticket with details:
      • Date and time of reset.
      • Method of identity verification used.
      • Temporary password communication method.
      • Confirmation that "User must change password at next logon" was enabled.
      • Resolution notes.
    • Close the ticket once confirmed the user has successfully logged in and changed their password.
    • Audit Trail: Ensure all actions are logged within the directory service for auditing purposes.

How ProcessReel Simplifies This: A critical challenge with documenting password reset procedures is capturing the exact steps, especially across multiple systems. ProcessReel excels here. An IT administrator can simply record themselves performing a password reset in Active Directory and then in Azure AD, narrating each click, verification step, and security consideration. ProcessReel automatically converts these screen recordings into a detailed, step-by-step SOP with screenshots, text descriptions, and even highlights of where to click. This ensures every new help desk technician learns the exact secure procedure, minimizing inconsistencies and security risks.

IT Admin SOP Template 2: New System Setup and Configuration

Every organization regularly adds new hardware and software to its environment. This could range from onboarding new employee workstations to deploying new servers or configuring SaaS applications. A standardized system setup SOP is crucial for ensuring consistency, security, and efficiency in these deployments.

Importance: This SOP ensures that all new systems are provisioned to organizational standards, meeting security baselines, software requirements, and network configurations. It prevents "configuration drift" – where systems diverge from the intended standard – and guarantees a predictable, secure, and ready-to-use environment for end-users or specific business functions. It's particularly vital for rapid and consistent onboarding of new employees.

Challenges Without a Clear SOP:

Real-World Impact and Metrics (for an organization onboarding 15 new employees/month):

Without an SOP, a comprehensive new employee workstation setup (OS install, software, security, network, peripherals) could take 4 hours per machine. With a detailed SOP, this can be reduced to 2 hours, through clear steps, pre-built images, and a consistent workflow.

Detailed Steps: New Employee Workstation Setup and Configuration (Example: Windows 11 Enterprise)

This procedure outlines the steps for setting up a new Windows 11 workstation for a new employee.

  1. Preparation and Hardware Staging:
    • Inventory Check: Verify all components (laptop, monitor, keyboard, mouse, power adapters) are present and undamaged.
    • Record Asset: Log the device's serial number, asset tag, and model into the asset management system (e.g., ServiceNow CMDB, Snipe-IT). Affix the asset tag securely.
    • Initial Power-On Diagnostics: Power on the device, check for any hardware POST errors, and confirm basic functionality (display, keyboard, trackpad).
  2. Operating System Installation and Base Configuration:
    • Image Deployment: Deploy the standard Windows 11 Enterprise image via PXE boot, USB, or Microsoft Intune Autopilot.
      • Note: If using Autopilot, ensure the device is registered in Intune.
    • Initial Setup:
      1. Select correct language, region, and keyboard layout.
      2. Connect to the corporate Wi-Fi or wired network.
      3. Name the device according to organizational standards (e.g., DEPT-LASTNAME-W11-001).
    • Local Admin Account (if required, temporary): Create a temporary local administrator account with a strong, complex password, to be disabled or removed post-configuration.
  3. Domain Join / Mobile Device Management (MDM) Enrollment:
    • For On-Premise Active Directory:
      1. Navigate to System Properties > Computer Name tab > Change... > Domain.
      2. Enter the corporate domain name (e.g., corp.example.com).
      3. Provide domain administrator credentials when prompted.
      4. Reboot the workstation.
    • For Azure AD / Intune (Recommended for Cloud-First):
      1. During OOBE (Out-Of-Box Experience), select "Set up for work or school account."
      2. Enter the employee's corporate email address and credentials.
      3. The device will automatically enroll in Intune and join Azure AD.
  4. Standard Software Installation:
    • Automated Deployment (Preferred):
      1. Verify software deployment policies are applied via Group Policy (GPO), Microsoft Intune, or a third-party RMM tool (e.g., ConnectWise Automate, NinjaOne).
      2. Initiate or verify installation of:
        • Microsoft 365 Apps (Word, Excel, Outlook, Teams)
        • Endpoint Protection (Antivirus/EDR - e.g., Microsoft Defender for Endpoint, CrowdStrike)
        • VPN Client (e.g., Cisco AnyConnect, GlobalProtect)
        • Web Browsers (Chrome, Edge)
        • Productivity Tools (e.g., Adobe Reader, Slack, Zoom client)
    • Manual Installation (if necessary): For specialized software not automated, follow specific vendor installation guides. Ensure licenses are properly activated.
  5. Security Configuration:
    • Operating System Updates: Run Windows Update to ensure all critical and security updates are installed. Reboot as required.
    • Firewall Configuration: Verify Windows Defender Firewall is enabled and configured according to corporate policy (e.g., blocking unauthorized incoming connections).
    • Endpoint Protection Check: Confirm Antivirus/EDR agent is running, definitions are updated, and reporting to the central console.
    • BitLocker Encryption: Ensure BitLocker Drive Encryption is enabled for the OS drive and recovery keys are securely backed up to AD or Azure AD.
    • Local Account Management: Disable or remove any temporary local administrator accounts. Verify standard user accounts have appropriate permissions.
  6. Network Configuration:
    • IP Settings: Verify the device receives IP addresses via DHCP or configure static IP if required for specific roles.
    • Proxy Settings: Configure web proxy settings if the organization uses one.
    • DNS Resolution: Test internal and external DNS resolution.
  7. Peripheral Setup and Testing:
    • Monitor Configuration: Connect monitors, adjust resolution and display settings.
    • Printer Drivers: Install drivers for standard network printers or local printers. Test print functionality.
    • Webcam/Microphone: Test audio and video functionality.
  8. Initial User Login and Verification:
    • Log in as New Employee: Log in with the new employee's corporate credentials to create their user profile.
    • Profile Configuration: Verify desktop settings, document folders, and basic application functionality.
    • Test Key Applications: Open and briefly test email client, web browser, and any critical business applications.
  9. Final Documentation and Handover:
    • Update Asset Management: Confirm all asset details, assigned user, and current location are accurate.
    • Service Desk Ticket: Update and close the related IT service desk ticket.
    • Physical Handover: Securely provide the device to the employee, ensuring they know how to log in and where to seek support.

How ProcessReel Simplifies This: A multi-step procedure like system setup, especially for new IT staff, can be overwhelming. ProcessReel is uniquely suited for this. An experienced systems administrator can simply record themselves going through a complete workstation setup, from powering on the device (or initiating Autopilot) to installing software and verifying settings. The narration captures the 'why' behind each step, while ProcessReel automatically generates clear, visual documentation with sequential screenshots. This transforms a complex, potentially error-prone process into an easy-to-follow guide, significantly accelerating technician readiness and ensuring consistent, secure deployments. Operations Manager's 2026 Playbook: Essential Strategies for Effective Process Documentation highlights how crucial detailed, accessible documentation like this is for operational success.

IT Admin SOP Template 3: Basic System Troubleshooting (e.g., Network Connectivity)

Troubleshooting is a core function of IT administration. However, without a structured approach, it can quickly devolve into trial-and-error, wasting valuable time and resources, and leading to unnecessary escalations. A basic troubleshooting SOP empowers Tier 1 support to resolve common issues independently and provides a consistent diagnostic path for more complex problems.

Importance: This SOP standardizes the diagnostic process for common IT issues, reducing Mean Time To Resolution (MTTR), decreasing the number of unnecessary escalations to higher-tier support, and improving overall user satisfaction. It enables IT staff to methodically approach problems, ruling out common culprits before escalating, making support more efficient and effective.

Challenges Without a Clear SOP:

Real-World Impact and Metrics (for an organization with 300 employees, ~50 network connectivity tickets/month):

Without an SOP, an average "no internet" troubleshooting ticket might take 30 minutes, involving disparate checks and potentially premature escalation. With a structured SOP, this can be reduced to 15 minutes, with many issues resolved at Tier 1.

Detailed Steps: Basic Network Connectivity Troubleshooting (Example: "No Internet Access" on a Workstation)

This procedure outlines the steps for diagnosing a user's report of "no internet access."

  1. Gather Initial Information from User:
    • Create/Update Ticket: Log the issue in the IT service desk system.
    • Scope: Is it only this user, or are others affected? Is it specific applications, or all internet access?
    • Recent Changes: Have there been any recent changes to the workstation, network, or applications?
    • Exact Error Message: What error message are they seeing (e.g., "DNS_PROBE_FINISHED_NXDOMAIN", "No Internet Connection")?
    • Connectivity Test: Can they access internal network resources (e.g., file shares, internal intranet)?
  2. Perform Basic Physical and System Checks:
    • Physical Connection (Wired):
      1. Verify Ethernet cable is securely plugged into both the workstation and the wall/dock.
      2. Check for link lights on the network port (usually amber/green).
    • Wi-Fi Connection (Wireless):
      1. Verify Wi-Fi is enabled on the workstation.
      2. Confirm connection to the correct SSID (e.g., Corp_WiFi).
      3. Check for strong signal strength.
      4. Verify airplane mode is OFF.
    • Reboot Devices: Instruct the user to reboot their workstation. If possible, have them reboot their network adapter (right-click, disable, then enable in Network Connections). For home users, suggest rebooting their router/modem.
  3. Verify IP Configuration:
    • Open Command Prompt: Type cmd in the Windows search bar and press Enter.
    • Check IP Address: Type ipconfig /all and press Enter.
      1. Verify an IP address is assigned (not 169.254.x.x which indicates APIPA).
      2. Note the Default Gateway and DNS Servers.
      3. Confirm the network adapter is listed and enabled.
    • Renew IP Address: If IP is invalid or missing:
      1. Type ipconfig /release and press Enter.
      2. Type ipconfig /renew and press Enter.
      3. Re-run ipconfig /all to verify new settings.
  4. Test Network Connectivity:
    • Ping Default Gateway: ping <Default_Gateway_IP> (e.g., ping 192.168.1.1).
      • Result: Success indicates local network connectivity. Failure suggests a physical or local network issue.
    • Ping DNS Servers: ping <Primary_DNS_Server_IP> (e.g., ping 8.8.8.8 for Google DNS).
      • Result: Success indicates DNS servers are reachable. Failure points to a DNS or broader network issue.
    • Ping External Website by IP: ping 1.1.1.1 (Cloudflare DNS).
      • Result: Success indicates internet access, but potentially a DNS resolution issue.
    • Ping External Website by Name: ping google.com.
      • Result: Success indicates full internet and DNS functionality. Failure suggests DNS resolution issues.
    • Flush DNS Cache: If ping google.com fails but ping 1.1.1.1 succeeds:
      1. Type ipconfig /flushdns and press Enter.
      2. Try ping google.com again.
  5. Check Browser and Proxy Settings:
    • Try Different Browser: If one browser fails, try another (e.g., Edge vs. Chrome).
    • Proxy Settings: Check browser proxy settings (e.g., in Chrome: Settings > System > Open your computer's proxy settings). Ensure they match corporate policy or are set to "Automatically detect settings" if no proxy is used.
  6. Review System Event Logs:
    • Open Event Viewer: Type eventvwr in Windows search.
    • Focus: Check "Windows Logs" > "System" for errors related to network adapters, DHCP, or DNS around the time the issue started.
  7. Test on Different Network (if applicable):
    • If the user is remote, ask them to test with a mobile hotspot or another network to isolate if the issue is with their home network or the workstation.
  8. Document Findings and Escalate:
    • If the issue persists after all steps, document all findings, including ipconfig /all output, ping results, and event log entries.
    • Escalate the ticket to Tier 2 Network Support, providing a clear summary of troubleshooting steps already performed and observed symptoms. This avoids redundant checks.

How ProcessReel Simplifies This: For troubleshooting, ProcessReel allows an experienced IT admin to record themselves systematically diagnosing a common network issue. They can narrate their thought process, explain why they are running specific commands (ipconfig, ping), and highlight what to look for in the output. This visual, narrated guide becomes an invaluable resource for junior technicians. It's not just a list of steps; it's a demonstration of diagnostic thinking. ProcessReel captures command line interactions, system dialogues, and browser behaviors, turning a complex, often abstract, diagnostic flow into a concrete, easy-to-follow SOP. This directly addresses the need for efficient knowledge transfer in IT operations, as explored in The Operations Manager Guide to Process Documentation: Driving Efficiency and Growth in 2026.

Building Your IT Admin SOP Library with ProcessReel

The concept of IT Admin SOP templates is not new, but the traditional methods of creating and maintaining them have always been a bottleneck. Imagine:

This manual, time-consuming process often means that SOPs are outdated almost as soon as they are published, leading to low adoption rates and a perpetually incomplete knowledge base.

ProcessReel changes this paradigm.

ProcessReel is an AI tool designed specifically to convert screen recordings with narration into professional, publish-ready Standard Operating Procedures. For IT administrators, this capability is nothing short of transformative.

Here's how ProcessReel revolutionizes SOP creation for IT teams:

  1. Effortless Capture: An IT expert simply records their screen while performing a task – be it a password reset, a system setup, or a troubleshooting sequence. Crucially, they narrate their actions and rationale as they go.
  2. AI-Powered Conversion: ProcessReel's intelligent algorithms analyze the screen recording and narration. It automatically detects individual steps, captures precise screenshots for each action, extracts relevant text from the screen, and transcribes the narration into clear, concise step-by-step instructions.
  3. Professional Output: The result is a fully formatted SOP document, complete with titles, numbered steps, clear screenshots, and descriptive text. These are not raw video transcripts; they are polished, ready-to-use guides that can be shared internally or stored in a central knowledge base.
  4. Easy Updates: When a process changes, updating an SOP is as simple as re-recording the affected segment or making quick edits within ProcessReel's intuitive editor, eliminating the need to start from scratch.

Consider the complexity of documenting a full system setup. A single recording with ProcessReel can replace days of manual documentation effort. This significantly reduces the overhead associated with creating and maintaining critical IT documentation, making it feasible to build a comprehensive, up-to-date IT Admin SOP library. For a deeper look into the mechanics of this conversion, refer to Revolutionize Your Workflows: How ProcessReel Converts a 5-Minute Screen Recording with Narration into Professional Documentation.

Future-Proofing Your IT Operations with Dynamic SOPs

In 2026, IT environments are not static. New technologies emerge, security threats evolve, and organizational needs shift constantly. Your IT Admin SOPs cannot be static documents collecting digital dust; they must be living, breathing guides that adapt with your operations.

ProcessReel inherently supports this dynamic approach. By making the creation and updating of SOPs incredibly efficient, it encourages a culture of continuous documentation. This means:

Investing in tools like ProcessReel is not merely about automating documentation; it's about building a foundation for a more resilient, efficient, and future-ready IT department. It frees up valuable IT administrator time from mundane documentation tasks, allowing them to focus on innovation, security enhancements, and strategic projects that truly move the business forward.

Frequently Asked Questions (FAQ)

Q1: How often should IT SOPs be updated?

A1: IT SOPs should be reviewed and updated regularly, not just annually. Best practice suggests a formal review cycle of at least once every six months, but more frequently if:

Q2: Who should be responsible for creating and maintaining IT SOPs?

A2: The responsibility should be a collaborative effort, but with clear ownership.

Q3: Can SOPs replace formal training for IT staff?

A3: No, SOPs are a critical component of training but do not replace it entirely. Formal training provides:

Q4: What's the biggest barrier to effective SOP implementation in IT?

A4: The most significant barrier is often the time and effort required for creation and ongoing maintenance. Traditional documentation methods are incredibly tedious, leading to:

Q5: How does ProcessReel handle sensitive information in SOPs created from screen recordings?

A5: ProcessReel offers features to manage sensitive information effectively:

Conclusion

In the dynamic world of 2026 IT administration, the need for clear, consistent, and current Standard Operating Procedures is paramount. Whether it's securely resetting a password, flawlessly deploying a new system, or methodically troubleshooting a network issue, well-defined IT Admin SOP templates are the bedrock of operational excellence. They enhance efficiency, bolster security, streamline training, and fundamentally improve the overall resilience of your IT department.

The traditional challenges of creating and maintaining these essential documents are no longer an excuse. AI tools like ProcessReel are revolutionizing process documentation, allowing IT experts to transform their actions and knowledge into professional, actionable SOPs with remarkable speed and accuracy. By capturing screen recordings with narration and letting AI do the heavy lifting, ProcessReel ensures your IT Admin SOP library is always up-to-date, comprehensive, and truly useful. Invest in robust SOPs today, and empower your IT team for tomorrow's challenges.

Try ProcessReel free — 3 recordings/month, no credit card required.

Ready to automate your SOPs?

ProcessReel turns screen recordings into professional documentation with AI. Works with Loom, OBS, QuickTime, and any screen recorder.