COURSE CONTENT
Start with the lessons
YOUR NEXT STEP
Keep building your skills
No directly related CogniSkill book is mapped to this course yet. Continue with the free learning, or compare the publishing catalogue by your next goal.
Explore books by topic and goal →Would this book help you?
Proposed topic: PowerShell for Service Desk Automation — Practical Workbook. This is an interest check; the book is not yet available.
Anonymous interest only. This does not subscribe you to email or reserve a copy.COURSE OVERVIEW
What you will learn
What you will make
Design a read-only triage report that records evidence and refuses to equate ping failure with device failure.
What you need
PowerShell Foundations; use a writable practice folder.
Save as Triage.ps1 in PowerShell 7. All observations are simulated. Do not replace them with production probes until you have separately tested and approved the collector.
How to work through it
- Understand the mechanism and predict the result.
- Run or trace the fixture and preserve the evidence.
- Change the inputs, expose a failure and explain the repair.
- Complete a project and answer the retrieval questions.
Scope
A focused practical workshop, not a complete beginner-to-expert programme. Allow time for the exercises and project; the pace depends on your prior experience. Related CogniSkill books are optional next steps. No purchase is required.
Applied capability and learning route
Design a safe service-desk report that separates collection errors from actionable findings.
Follow the lessons in order: establish the model, trace the supplied evidence, attempt the case, compare the worked solution, and complete the changed-condition project. The target is intermediate reasoning within this stated scope, not mastery of the entire profession or product. If a prerequisite is unfamiliar, pause and use the linked foundational teaching before attempting the project.
All teaching, explained answers and core synthetic practice are free. Some operational labs require separately available software, a licensed test tenant or an authorized lab; offline completion does not claim hands-on product proficiency.
How to complete this course
Study the worked examples, attempt the exercises before opening solutions, and submit your own project notes. Completion records are self-reported; practical competence requires the stated verification.
What you will learn
- Normalize sample tickets
- Validate required fields
- Export a focused support report
- Design a safe service-desk report that separates collection errors from actionable findings.
Before you start
- PowerShell Foundations; use a writable practice folder.
Practice environment
- Use the lesson’s fictional data or local lab. Cloud configuration is not required for the core tabletop exercises; follow the stated software prerequisites for executable labs.
Tested versions
- See worked example verification notes; optional tenant features require current provider checks.
Technical review: 2026-10-07
Technical referencePractical project
Extend the result with a Contradiction flag, CheckedAtUTC and NextOwner. Add four test cases covering application success with ping failure, DNS failure, incomplete application testing and contradictory DNS/application evidence. Produce a ticket-ready report without adding any remediation command.
Applied transfer project: Write a read-only collector using mocked inputs first. Add a structured output file and a summary that reconciles all four hosts. Then design—but do not execute—a separate remediation stage that accepts only approved H2-like records, logs each decision and checks the postcondition. Include a stale-record test in which the service starts between collection and remediation. Explain how rechecking state prevents acting on an obsolete assumption.
Check your project
- Input/output counts reconcile
- Unknown priorities visible
- Output location explicit
- Only synthetic tickets used
- Applied laboratory rubric: five dimensions, 0–2 each; target 8/10 with no zero in main result or safety. Native quiz score is separate.
Use these criteria for self-review. Completing a lesson records your progress; it does not verify code correctness.
Practice files
APPLY THE SKILL
Your practical project
Extend the result with a Contradiction flag, CheckedAtUTC and NextOwner. Add four test cases covering application success with ping failure, DNS failure, incomplete application testing and contradictory DNS/application evidence. Produce a ticket-ready report without adding any remediation command. Applied transfer project: Write a read-only collector using mocked inputs first. Add a structured output file and a summary that reconciles all four hosts. Then design—but do not execute—a separate remediation stage that accepts only approved H2-like records, logs each decision and checks the postcondition. Include a stale-record test in which the service starts between collection and remediation. Explain how rechecking state prevents acting on an obsolete assumption.
Evidence to keep
- Input/output counts reconcile
- Unknown priorities visible
- Output location explicit
- Only synthetic tickets used
- Applied laboratory rubric: five dimensions, 0–2 each; target 8/10 with no zero in main result or safety. Native quiz score is separate.
Use fictional practice data. Keep your inputs, outputs and explanation of the result. Lesson completion records your progress; it does not verify your project.
PRACTICE MATERIALS
Course downloads
Save the materials before starting your lab. Read source files before running them.
CHECK YOUR KNOWLEDGE