One of the challenges many Exchange administrators will face is determining how to generate useful reports that...
will assist them in accomplishing their operational tasks. Sometimes, the difficulty is finding the appropriate cmdlet to run. Other times, the difficulty is in finding the correct combination of cmdlets to run to produce the specific reports you need. In the most frustrating cases, you try to do something you were able to do in previous versions of Exchange, but you can't find a way to do it in the current version of Exchange.
Microsoft has provided a number of cmdlets specifically geared toward mailbox reporting. The cmdlet that exposes the StorageLimitStatus of mailboxes is the Get-MailboxStatistics cmdlet. However, due to an architectural change in the Exchange information store, this information is no longer available. The end result is that the value is null in an Exchange 2013 mailbox because the information is no longer cached on the server's databases. This could affect how a mailbox quota warning appears.
Microsoft suggests two workarounds for this quota-warning issue. First, it's possible to use the Exchange Admin Console and view the mailbox usage information in the properties of a specific recipient. It's also possible to use certain cmdlets to display the mailbox quota and mailbox size values.
Single mailbox example:
Get-MailboxStatistics Annie | Format-Table *quota*,*size -AutoSize –Wrap
Multiple mailboxes on a database example:
Get-MailboxStatistics -Database DB01 | Format-Table displayname,*quota*,*size -AutoSize -Wrap
You'll still need to compare the values to determine if the mailboxes have exceeded their quota and if they have received quota warning notifications. For additional information, Microsoft offers a Knowledge Base article about the empty StorageLimitsStatus field when you run the Get-MailboxStatistics cmdlet in Exchange 2013. It gives details about what causes the empty field and the workaround steps you can take in your Exchange Server 2013 environment to verify your mailboxes' quota status.
About the author:
Richard Luckett is a consultant and instructor specializing in messaging and unified communications. He's been a certified professional with Microsoft since 1996 and has 20 years of experience in the public and private sectors. He's a Microsoft Certified Trainer with more than 15 years of training experience with the Microsoft product line and received the Exchange MVP award in 2006, 2007 and 2008. He's also an expert in deploying and integrating Exchange Server and Lync Server. He leads the Microsoft training and consulting practice at LITSG.
Dig Deeper on Exchange Server setup and troubleshooting
Related Q&A from Richard Luckett
Some folders in a mailbox on Exchange Server 2013 are not showing up on the folder list in the OWA virtual directory but do appear in other views. Continue Reading
We have a Client Access Server and Mailbox Server on Exchange 2013 and we want to install an Edge Transport role on another machine. I joined the ... Continue Reading
How can I enable Outlook Anywhere to allow internal use for all users and external use for only some users in Exchange 2013? Continue Reading