Troubleshooting Low Disk Space on Exchange Server 2019 / SE

 

---

📝 Troubleshooting Low Disk Space on Exchange Server 2019 / SE(Complete Real Case Study)

📌 Problem Statement

An Exchange Server 2019 running on Windows Server 2019 had a 75 GB C: drive, with only ~11 GB free space remaining, creating a high risk of:

• Mail flow disruption
• Exchange service issues
• Server instability

---

🔍 Initial Investigation

We first checked the Exchange logging folder size:

Command Used: (Get-ChildItem "C:\Program Files\Microsoft\Exchange Server\V15\Logging" -Recurse | Measure-Object Length -Sum).Sum / 1GB

✅ Output:

6.08960135094821 GB

👉 The Exchange Logging folder alone was consuming ~6 GB

---

✅ Solution Step 1: Clean Old Exchange Logs

To safely free space, logs older than 7 days were removed.

Command Used: Get-ChildItem "C:\Program Files\Microsoft\Exchange Server\V15\Logging" -Recurse -File | Where-Object {$_.LastWriteTime -lt (Get-Date).AddDays(-7)} | Remove-Item -Force

---

📊 Result After Cleanup

Rechecked folder size:

Command Used: (Get-ChildItem "C:\Program Files\Microsoft\Exchange Server\V15\Logging" -Recurse | Measure-Object Length -Sum).Sum / 1GB

✅ Output:

3.30880791042 GB

---

🎯 Impact

Before Cleanup	After Cleanup	Space Recovered
6.09 GB	3.30 GB	✅ ~2.8 GB freed

👉 Nearly 50% of the log space was recovered safely

---

🔍 Further Analysis: Windows Component Store (WinSxS)

Next, we analyzed hidden system usage:

Command Used: Dism /Online /Cleanup-Image /AnalyzeComponentStore

✅ Findings:

• Component Store Size: ~12.2 GB
• Reclaimable Packages: ✅ Yes
• Cleanup Recommended: ✅ Yes

---

✅ Solution Step 2: Clean Component Store

Command Used: Dism /Online /Cleanup-Image /StartComponentCleanup

👉 This removes:

• Old Windows updates
• Superseded components
• Unused system files

---

⚠️ Note on DISM Execution

During execution, the process appeared stuck at:

[===========================99.0%========================= ]

✅ This is normal
✅ The system continues cleanup in the background
✅ It may take 10–30 minutes

---

✅ ✅ DISM Completion Confirmation

After completion:

[===========================99.0%========================= ]
[==========================100.0%==========================]
The operation completed successfully.

✅ What This Confirms:

• Cleanup completed successfully ✅
• Old system components removed ✅
• Disk space reclaimed ✅
• System stability maintained ✅

---

✅ Additional Observation

• IIS Logs → Only MBs ✅
• Transport Logs → Only MBs ✅

👉 These were not major contributors to disk usage

---

✅ Final Step: Extending C: Drive (Permanent Fix)

Even after cleanup, it was decided to increase disk size for long-term stability.

---

✅ Step 3: Extend Disk from Virtual Machine

The VM disk size was increased:

• From 75 GB → 100 GB

This was done using VM settings (VMware/Hyper-V).

---

✅ Step 4: Extend C: Drive in Windows

After disk expansion, the unallocated space was added to C:.

Method Used:

• Open: diskmgmt.msc
• Right-click C: drive
• Select Extend Volume
• Add full available space

---

✅ Final Result

• Total Disk Size → 100 GB
• Free Space → ~45 GB available ✅

---

🎯 Overall Outcome

✅ ~2.8 GB freed from Exchange logs
✅ Additional cleanup via DISM
✅ Disk expanded by 25 GB
✅ Total free space increased significantly
✅ Exchange server stabilized

---

✅ Best Practices Learned

🔹 1. Monitor Exchange Logging Regularly

Logs can grow rapidly and consume space.

---

🔹 2. Perform Periodic Cleanup

Use PowerShell to remove old logs safely.

---

🔹 3. Maintain Safe Free Space

👉 Always keep 20–30 GB free on Exchange servers

---

🔹 4. Use Disk Expansion as Long-Term Solution

When cleanup isn’t enough, extending disk is the safest option.

---

🔹 5. Avoid Risky Actions

• Do NOT manually move Exchange system folders
• Always use recommended procedures

---

🔮 Recommended Future Actions

✅ Automate weekly log cleanup
✅ Move logs to secondary drive (E:)
✅ Monitor disk usage regularly

---

📌 Conclusion

Low disk space in Exchange servers is typically caused by:

• Logging growth
• Windows component store accumulation

By:

✔ Cleaning old Exchange logs
✔ Running DISM cleanup
✔ Extending disk capacity

👉 The issue was resolved safely without downtime or service impact

---

✅ Final Status

👉 Server is now stable with:
~45 GB free space on C: drive ✅

---

👏 Summary

This case demonstrates a safe, structured, and production-ready approach to resolving disk space issues in Exchange environments.