Trainer Guide
A practical delivery guide so you can teach the workshop confidently instead of reading slides.
How to teach each section
| Phase | What you do |
|---|---|
| 1. Explain | Give the concept in 60–90 seconds. |
| 2. Demonstrate | Open the real Windows/Plesk tool. |
| 3. Ask | Give a symptom and ask what to check next. |
| 4. Challenge | Reveal another clue that changes the investigation direction. |
| 5. Reinforce | Repeat: evidence before action. |
Suggested trainer script
Opening:
“Today is not about memorizing every Windows Server feature. The goal is to develop a standard process for investigating a Windows server before escalation.”
“Today is not about memorizing every Windows Server feature. The goal is to develop a standard process for investigating a Windows server before escalation.”
During scenarios:
“What evidence do we have? What layer are we testing? What is the smallest safe next action?”
“What evidence do we have? What layer are we testing? What is the smallest safe next action?”
Closing:
“A good CloudOps engineer does not just fix the symptom. They identify the layer, collect evidence, make a safe change, verify the result and document it.”
“A good CloudOps engineer does not just fix the symptom. They identify the layer, collect evidence, make a safe change, verify the result and document it.”
Live demo order
Task Manager
→Resource Monitor
→Event Viewer
→Services
→Plesk
→IIS
→PowerShell
→Task Scheduler