Desktop Support Technician [Must have SCCM & Active Directory] - Columbia SC/onsite

We need to produce HTML fragment with sections: About the role? The posting includes job description, responsibilities, required skills, preferred skills, required education/certifications, interview process, reporting structure. Also location, duration, possibility for extension, fully onsite, work week schedule. We need to include sections only if there is real specific content. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content. We have: Job Description (could be About the role). Responsibilities (Daily Responsibilities, Monthly Responsibilities). Required Skills (maybe Skills). Preferred Skills (maybe also Skills). Required Education/Certifications (Qualifications). Interview Process (maybe About the role or separate). Reporting Structure (maybe About the role). Location, duration, possibility for extension, fully onsite, work week schedule (Schedule). No? Actually schedule is Monday-Friday 8am-5pm with one-hour lunch break). That's schedule info. Also physical exertion (force). That could be part of Requirements? Not exactly. Could be part of Qualifications? Might be considered Requirements. But we should not create sections with filler. We need to include only sections with real content. We have location: Columbia SC/onsite. Duration: 12 months, possibility for extension: Yes. Fully onsite. Work week schedule: Monday-Friday 8am-5pm with one-hour lunch break. So we can have a Schedule section with that info. We have Pay? Not mentioned. So we should NOT create Pay section. Benefits? Not mentioned. So no Benefits. We have Requirements? Could combine required skills, education, physical exertion? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to use "Requirements" for required skills and education, maybe also physical exertion. "Skills" for required and preferred skills? But we might double. Better to separate: "Skills" for required and preferred skills. "Qualifications" for education/certifications. "Responsibilities" for duties. "About the role" for overview (job description, location, duration, onsite, schedule maybe). But schedule is its own section. We must not repeat job title as heading. So no heading for Desktop Support Technician. We must not put Job ID/requisition numbers as headings (none present). We must output only HTML fragment, no /, no markdown fences. We need to preserve all substantive information. So we need to include details: location, duration, possibility for extension, fully onsite, work week schedule, job description paragraphs, responsibilities (daily and monthly), required skills, preferred skills, required education/certifications, interview process, reporting structure, physical exertion (force). Also mention SCCM & Active Directory requirement (must have SCCM & Active Directory). That is in title but also in description? It says "[Must have SCCM & Active Directory]" in title. Should we include that as part of Skills? Yes. We need to ensure we don't invent or summarize away detail. Keep specifics. Let's craft sections:

About the role

Location: Columbia, SC (onsite). Duration: 12 months contract with possibility for extension. Position is fully onsite at the South Carolina Department of Transportation (SCDOT) Headquarters building. Work schedule: Monday–Friday, 8 am–5 pm with a one‑hour lunch break (40 hours per week). The role reports to management in Desktop Support at SCDOT Headquarters.

But we also have Reporting Structure separate maybe. Could include in About the role. Better to keep Reporting Structure separate? The instruction says prefer a few substantive sections over many thin ones. So we can combine reporting structure into About the role. We also need to include physical exertion details: "Requires the exertion of 50 pounds of force occasionally. Requires the exertion of 20 pounds of force frequently." Where to put? Could be in About the role or Requirements. Probably Requirements. We'll have sections: - About the role (overview, location, duration, onsite, schedule, reporting structure) - Responsibilities (daily and monthly) - Skills (required and preferred) - Qualifications (education/certifications) - Requirements (maybe physical exertion and required experience? But we already have Skills for experience. Could combine experience in Skills. Requirements maybe for physical exertion and mandatory SCCM & Active Directory? But those are skills. Hmm. We could have: Skills (required and preferred), Qualifications (education/certifications), Responsibilities, About the role (including location, duration, schedule, reporting). Physical exertion could be placed in About the role or a separate "Requirements" section. Since we have no explicit "Requirements" heading in the list but it's allowed. We'll add a Requirements section for physical exertion and maybe mention must have SCCM & Active Directory (though that's skill). But we can keep it in Skills. Let's decide: Sections: - About the role - Responsibilities - Skills - Qualifications - Requirements (physical exertion) Check if any content missing: Interview process. Could be part of About the role or a separate section. Could add a small section "Interview Process". But we prefer few sections. Could incorporate interview process into About the role as a note. But the instruction: "Prefer a few substantive sections over many thin ones." So we can combine interview process into About the role. Now ensure we don't create sections with filler like "commensurate with experience". We have real content. Now produce HTML:

About the role

The South Carolina Department of Transportation (SCDOT) is seeking an applicant to assist under general supervision of the IT Manager II for Desktop Support, Regional Technician I for Headquarters and District 1, or Endpoint Technician I. The role provides technical assistance, manages laptop, tablet, and workstation builds, and assists with deployments for departmental personnel in the setup, installation, maintenance and proper usage of desktops, laptops, tablets, printers, scanners, monitors, application software, local area network, and associated equipment for the Headquarters building under the management of Information Technology Services (ITS).

Location: Columbia, SC (onsite). Duration: 12 months contract with possibility for extension. Position is fully onsite at the SCDOT Headquarters building. Work schedule: Monday–Friday, 8 am–5 pm with a one‑hour lunch break (40 hours per week). Reports to management in Desktop Support at SCDOT Headquarters.

Now Responsibilities:

Responsibilities

• Build desktops, laptops, and tablets using Microsoft Endpoint Configuration Manager.
• Ensure the BitLocker encryption key is successfully stored in Active Directory and InTune.
• Ensure the Microsoft Endpoint Configuration Manager Client is installed on each desktop, laptop, and tablet during the build process.
• Ensure each desktop, laptop, and tablet stays connected to the NTS Network for at least 2.5 hours after build completes.
• Ensure that all software listed on the build sheet is installed on each desktop, laptop, and tablet built.
• Document each desktop, laptop, tablet, docking station, 27” monitor, printer, scanner, and any other tracked asset assigned to an end-user in the designated IT Services asset management system per the Desktop Support Asset Management procedure manual.
• Diagnose and resolve problems reported by users on endpoint hardware and/or software.
• Record work performed in the Help Desk ticket system.
• Perform routine maintenance and repair on equipment or contact vendor support for equipment repair.
• Assist with removal and disposal of obsolete equipment using the electronic TID and Request to Dispose of Accountable Equipment, salvaging any usable parts.
• Perform other related duties as required.
• Monthly: Ensure that all SCDOT Commission backup tablets are connected by patch cable to the NTS Network to receive Patch Tuesday patches (tablets powered on via power cord, connected second Friday of each month, remain connected until 12 pm the following Wednesday; login using local account before shutdown).
• Monthly: Power on all iPads using the appropriate power cable and charging brick for the same duration as the SCDOT Commission tablets; login not required.
• . We'll keep all as
• inside
  . For monthly responsibilities we can still be
  • . Now Skills:

    Skills

    • Required: 4+ years of experience in desktop and networked systems support; extensive knowledge of desktops, laptops, tablets, printers, and scanners.
    • Required: 4+ years of experience in computer deployments, operation, and repair.
    • Required: 4+ years of experience with hardware and software installation.
    • Required: 4+ years of experience with Microsoft Endpoint Configuration Manager (SCCM).
    • Required: Experience with Active Directory or InTune (preferred but also mentioned as must have SCCM & Active Directory).
    • Preferred: Experience working with a help desk ticketing system.
    • Preferred: Experience with the NTS Network.
    But we duplicated Active Directory; we can combine. Now Qualifications:

    Qualifications

    • High school diploma required.
    • Associate or bachelor’s degree in a related field preferred; may be substituted for required work experience.
    Now Requirements (physical exertion):

    Requirements

    • Must be able to exert 50 pounds of force occasionally.
    • Must be able to exert 20 pounds of force frequently.
    We should also mention that the role requires onsite presence 40 hours/week, but we already have schedule. Check if any content missed: The job description repeated sentences; we captured essence. The requirement to "Confirming the installation is successful by ensuring the BitLocker Key is stored in Active Directory and InTune, and that the Microsoft Endpoint Configuration Manager Client is installed." Already covered. The requirement to "Ensure that desktops, laptops, and tablets fully check in 2.5 hours after the MECM Task Sequence completes." Covered. The requirement to "Assist with deployment of endpoints and associated devices that make up an end-user setup in the Headquarters building." Covered in responsibilities (build and deploy). The requirement to "Applicants will be required to be onsite for 40 hours a week within the SCDOT Headquarters building to provide IT Support for IT Services Desktop Support Staff." Covered in schedule. The requirement to "Work week is Monday – Friday (8am – 5pm with a one-hour lunch break)." Covered. The requirement to "Requires the exertion of 50 pounds of force occasionally. Requires the exertion of 20 pounds of force frequently." Covered. The requirement to "Interview Process 1st round video A second interview may be requested (onsite)". We omitted. Should include somewhere. Could add a short paragraph in About the role or a separate small section. Since we prefer few sections, we can add a sentence in About the role: "Interview process: first‑round video interview; a second on‑site interview may be requested." Let's edit About the role paragraph to include that. Also we missed "Reporting Structure Reports to: Management in Desktop Support at SCDOT Headquarters Building." Already included. Now ensure we didn't miss any specifics: "Manages building laptops, tablets, and workstations using Microsoft Endpoint Configuration Manager (MECM)." Covered. "Confirming the installation is successful by ensuring the BitLocker Key is stored in Active Directory and InTune, and that the Microsoft Endpoint Configuration Manager Client is installed." Covered. "Ensure that deskt