01 · Symptoms
Start with what actually failed
Capture the behavior that triggered the investigation without assuming the cause too early.
Aki Inu Tech Case Library
See how the problem was actually worked.
Aki Inu Tech 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 CaseKT-000003 · VPN / File Access
VPN Connected but Internal Resource Still Failed
A public-safe investigation that treats tunnel success as one checkpoint, then follows the downstream destination, identity, resource path, and mapping evidence.
Read the CaseKT-000004 · SharePoint / OneDrive
SharePoint Worked in Browser but File Explorer Was Incomplete
A public-safe case showing how browser access isolated a conflicting OneDrive shortcut from the intended SharePoint library sync.
Read the CaseKT-000005 · File Server / Permissions
Folder Access Was Wrong Because NTFS Inheritance
A public-safe case showing how broad inherited NTFS access was isolated from the SMB share, replaced safely, and verified for both approved and unapproved users.
Read the CaseKT-000006 · Security First Response
Malicious Outlook Attachment Was Already Quarantined
A public-safe case separating true-positive classification and completed mitigation from the execution and residual-activity questions that still required verification.
Read the CaseKT-000007 · Workstation Decisions
Repeated Scanner Problems Exposed an Aging Workstation
A public-safe case showing how temporary improvement, persistent saturation, rapid recurrence, and repair history supported a replacement recommendation.
Read the CaseKT-000008 · Identity / Authentication
Different Systems Accepted Different Password States
A public-safe case showing how hosted and cloud identity boundaries were tested separately before credential state was normalized and verified.
Read the CaseKT-000009 · Microsoft 365 / Outlook
Exchange Delivered Mail While Outlook Appeared Delayed
A public-safe case showing how exact-time message trace cleared Exchange transport and moved the investigation downstream to the Outlook client path.
Read the CaseKT-000010 · Printers / MFP
Printer Test Page Worked but Application Printing Failed
A public-safe case showing why network response and a Windows test page proved only part of the path before the actual PDF application workflow was verified.
Read the CaseKT-000011 · Windows / Office
Office APPCRASH Survived Repair and Reinstall
A public-safe case showing how persistent crash evidence narrowed broad remediation to one compatible, known-good Office component and verified the real Outlook workflow.
Read the CaseKT-000012 · Infrastructure / Lifecycle
Aging Server Capacity Became Lifecycle Debt
A public-safe case showing how tactical pressure reduction exposed a longer-term capacity and modernization decision without claiming the transition was completed.
Read the CaseKT-000013 · Infrastructure / Server Triage
Event Logs Proved Unexpected Server Restarts
A public-safe case showing how event timing separated recurring unplanned shutdowns from maintenance without claiming the underlying power, hypervisor, or hardware cause.
Read the CaseKT-000014 · Application Lifecycle
Legacy Application Upgrade Required Database Validation and Sequencing
A public-safe case showing how data protection, vendor-guided sequencing, integrity checks, and real workflow testing turned an installer task into a controlled lifecycle change.
Read the CaseKT-000015 · Mail Flow & Security
Forwarded Mail Failed After Authentication Changed Across Security Layers
A public-safe case showing why original delivery and forwarded authentication must be compared at the security layer that actually rejects the message.
Read the CaseKT-000016 · Microsoft 365 Identity & Offboarding
Microsoft 365 Offboarding Required the Right Order
A public-safe case showing how access removal, business continuity, licensing, and separately controlled endpoint handling depended on deliberate sequencing.
Read the CaseKT-000017 · Identity / SharePoint Access
SharePoint Access Failed Because MFA State Was Broken
A public-safe case showing why correct SharePoint authorization did not prove the user's authentication and MFA path was healthy.
Read the CaseKT-000018 · Windows User Profile Recovery
Windows User Profile Was Rebuilt from the Correct SID Mapping
A public-safe case showing why the affected SID, LocalPath, and ProfileImagePath were proven before removing only the verified profile registration.
Read the CaseKT-000019 · Remote Session / Camera & Audio
Remote Camera Failure Was Isolated Layer by Layer
A public-safe case showing why local hardware, Windows, remote-session redirection, and the conferencing application were tested as separate layers.
Read the CaseKT-000020 · DNS & Infrastructure Troubleshooting
Public Website Failed Internally Because DNS Owned the Name
A public-safe case showing how inside-versus-outside comparison isolated internal DNS after filtering visibility and whitelisting did not explain the failure.
Read the CaseKT-000021 · Endpoint Security & Recovery
BitLocker Recovery Key Was Missing from One Console but Present in Entra ID
A public-safe case showing why device identity, authorization, approved escrow sources, protected delivery, and successful boot must all be verified.
Read the CaseKT-000022 · Endpoint Hardware Isolation
Dock and USB-C Instability Spanned Multiple Peripherals
A public-safe case showing how changing display, keyboard, and mouse failures shifted the investigation toward their shared hardware path without claiming one exact failed component.
Read the CaseKT-000023 · WAN / ISP / Remote Access
Intermittent Internet and RDP Drops Required Continuous Evidence
A public-safe case showing how continuous monitoring, LAN/WAN comparison, carrier escalation, and post-repair retesting separated changing network fault domains.
Read the CaseKT-000024 · Endpoint Management / Vendor Escalation
RMM Agent Failure Required Vendor Escalation on ARM Hardware
A public-safe case showing how healthy business workloads, installer logs, and vendor confirmation isolated one RMM compatibility defect without destabilizing the endpoint.
Read the CaseKT-000025 · Endpoint Repair & Data Custody
External Repair Required a Data-Custody Plan
A public-safe case showing how continuity, sync disconnection, cached-data verification, custody transfer, and controlled rebuild protected business data during external repair.
Read the CaseKT-000026 · Windows / Cloud Sync / Application Persistence
Cloud-Synced Content Recreated a Removed Utility
A public-safe case showing how a healthy printer, recurring prompt, synced content, and local residue identified the source that could recreate a removed component.
Read the CaseKT-000027 · Security Investigation / Microsoft 365
Security Symptoms Required Separate Evidence Paths
A public-safe case showing how mail, sharing, identity, and endpoint evidence were separated before correlation, targeted controls, and an explicitly unconfirmed compromise outcome.
Read the CaseKT-000028 · Microsoft 365 / SaaS Licensing
SaaS License Rollout Required Recipient and Billing Control
A public-safe case showing why recipient selection, in-app access, assigned seats, required seats, subscription quantity, and billing cleanup need separate proof.
Read the CaseKT-000029 · Workstation Reliability / Hardware Escalation
Repeated Full-System Freezes Justified Hardware Escalation
A public-safe case showing how recurrence across meeting applications after a clean re-image shifted the next test from repeated software work to qualified hardware escalation.
Read the CaseKT-000030 · Microsoft 365 / SharePoint / Security Architecture
Secure External Sharing Required a Risk-Model Decision
A public-safe case showing how business risk, identity, traceability, recipient workflow, policy, testing, and cleanup shaped a controlled external-sharing process.
Read the CaseKT-000031 · Microsoft 365 / Entra / Application Consent
Microsoft 365 Admin Consent Required a Controlled Approval Path
A public-safe case showing how app identity, requested scopes, tenant policy, administrator review, least-necessary approval, and testing controlled a third-party integration.
Read the CaseKT-000032 · Evidence Handling / Application Dependencies
Proprietary Surveillance Export Failed in Its Playback Chain
A public-safe case showing how source preservation, format identification, viewer and dependency evidence, and endpoint comparison isolated a proprietary playback chain.
Read the CaseKT-000033 · Windows / Endpoint Management / Configuration Residue
Legacy Management Residue Kept Microsoft Store Blocked
A public-safe case showing how effective-state evidence and one targeted configuration change reopened a required Microsoft Store workflow.
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.