01 · Symptoms
Start with what actually failed
Capture the behavior that triggered the investigation without assuming the cause too early.
KrippyTech Case Library
See how the problem was actually worked.
KrippyTech cases preserve the investigation behind technical problems: the symptoms, evidence, decisions, resolution, and verification. Tutorials teach the reusable method. Cases show that method under real troubleshooting pressure.
From ticket noise to useful evidence
A good case is not a victory lap after the fix. It records the reasoning that made the fix defensible and reusable.
02 · Evidence
Inspect the systems that can prove it
Permissions, configuration, logs, traces, identity, networking, health signals, and user context narrow the problem.
03 · Resolution
Change the cause, not the symptom
The useful part is knowing why the selected change addressed the evidence better than the alternatives.
04 · Verification
Prove the original failure is gone
Re-test the original scenario and document what confirmed the issue was actually resolved.
Current published case
The public library stays intentionally small while each record is reviewed for technical accuracy, reusable value, and public-safe context.
KT-000001 · Microsoft 365
Shared Mailbox Not Showing in Outlook
An investigation of a mailbox that did not appear in Outlook after access had already been assigned.
Read the CaseKT-000002 · Exchange Online
Exchange Online Archive Not Reducing Primary Mailbox
An investigation that separates correct archive configuration from proof of active MRM processing.
Read the CaseRelated tutorial
Use the repeatable troubleshooting flow
The paired tutorial turns the reusable checks from the case into a direct troubleshooting method.
Open the TutorialPublic-safe by design
Problem first, customer never
Cases are rewritten around the technical problem so customer names, ticket exports, credentials, logs, and identifying details stay out of the public record.
The tutorial gives you the method. The case gives you the judgment.
Start with Tutorials when you need a repeatable path. Use Cases when you want to see how evidence, uncertainty, and verification shaped the troubleshooting decision.