Microsoft Teams has three different types of logs, which get stored on different locations. Web Logs Consists of most Teams client activi...

Just recently someone asked me if there was a way to determine which email client (Outlook, OWA or ActiveSync) was used to send a particula...

Excessive database and/or transaction log growth is, unfortunately, not an uncommon problem in Exchange deployments. On top of being hard t...

When searching the Admin Audit Log using the Search-AdminAuditLog cmdlet, you might find some useful information missing: Search-AdminAud...

If you navigate to the Exchange’s ProbeResult Crimson Channel under ActiveMonitoring, you will likely find the following error event logged...

Loose Truncation is a new feature that was introduced in Exchange 2013 Service Pack 1. Its purpose is to prevent possible disk space issue...

Having a list of all Exchange cmdlets we ran is always useful. Besides the usual methods of getting these from the PowerShell window histor...

The Exchange 2010 Management Center included PowerShell cmdlet logging functionality, something that was removed in Exchange 2013. The good...

New to Exchange 2013, the Get-MessageTrackingReport cmdlet is used to return data for a specific message tracking report.   This cmdle...

In Exchange 2013, native, built-in monitoring and recovery actions are included in a feature called Managed Availability , which is made up...

By default, you have to use PerfMon counters to see how often throttling is occurring for RPC connections. However, there is a way to have...

I have been using Log Parser for some years now and sometimes it is a life saver! It is easy to use and makes parsing logs so simple. Howe...

Here is a problem I faced today: when trying to move all the tracking logs for 3 CAS boxes from the C to the D drive I used the command: G...