diff --git a/docs/Diagnostics/HealthChecker/ExchangeComputerMembership.md b/docs/Diagnostics/HealthChecker/ExchangeComputerMembership.md
index 9e233c26bb..f5f5ac6ca9 100644
--- a/docs/Diagnostics/HealthChecker/ExchangeComputerMembership.md
+++ b/docs/Diagnostics/HealthChecker/ExchangeComputerMembership.md
@@ -10,6 +10,30 @@ If an issue is detected, the group will display with where the problem is locate
 
 If the script is run from a computer that doesn't have Active Directory PowerShell module installed on it, `Get-ADComputer` will fail with the exception `CommandNotFoundException`. The output will then display that you should run `Install-WindowsFeature RSat-AD-PowerShell` on the computer to get the module installed. This is how you get this feature to then start reporting correctly.
 
+If you see an output of:
+
+    Exchange Server Membership: Failed
+            Unable to determine Local System Membership as the results were blank.
+
+This can have multiple meanings.
+
+1. Ambiguous: The command Get-LocalGroupMember failed to run successfully.
+2. Literal: That there is a group membership issue.
+
+Confirm which one of the two is the problem by reviewing local group membership. The `Administrators` group should have members which include: `Domain Admins`, `Exchange Trusted Subsystem`, and `Organization Management`.
+
+If you see an output of:
+
+    Exchange Server Membership: Failed
+            Unable to determine AD Group Membership as the results were blank.
+
+This can have multiple meanings.
+
+1. Ambiguous: The command Get-ADPrincipalGroupMembership failed to run successfully.
+2. Literal: That there is a group membership issue.
+
+Confirm which one of the two is the problem by reviewing what groups the Server is a member of. The server should be a member of `Exchange Trusted Subsystem`, and `Exchange Servers`.
+
 **Included in HTML Report?**
 
 Yes