Skip to main content

Version 4 of the Mailbox Size Gui and using Quotas in Mailbox Size Reports

Version 5 has now been posted that fixes issue with quotas please see this

Based on the feedback and requests I’ve received I’ve updated the Mailbox Size Gui to show the percent of Quota used by each user. While this was not hard to do it’s unfortunately not as simple as just pulling the information from the get-mailboxstatistics cmdlet. As I’ve shown in other posts before when you what to determine the Quota that applies to a user’s mailbox you need to check quota information in a number of locations. The first place you need to check is the users account to see whether then have the use store quotas defaults set to true of false. Within a Get-mailboxstatitics operation there is a property made available called UseDatabaseQuotaDefaults which can be used to do this. If this property returns false then the quota information will be set on the User's Mailbox itself (or more accurately the User object in Active Directory) so in this case you can use the Get-Mailbox cmdlet to retrieve the ProhibitSendReceiveQuota property on the user account. If the UseDatabaseQuotaDefaults is set to true the you need to find out which Mailstore the Mailbox is located on and then check the Mailstores quotas setting using the get-mailboxdatabase cmdlet. If you want to do this for a number of users you could pipleline it a few different ways the way I’ve chosen to do this in my Mailbox GUI script is to create 2 hashtables to store any MailStore and UserMailbox quotas and then during the get-mailboxstatisitics cmd use these Hashtables to determine the percent of Quota the user has actually used. Here’s a quick sample

$mstoresquotas = @{ }
get-mailboxdatabase -server servername | ForEach-Object{
if ($_.IsUnlimited -ne $true){


$usrquotas = @{ }
Get-Mailbox -server servername -ResultSize Unlimited | foreach-object{
if($_.ProhibitSendQuota -ne "unlimited"){

get-mailboxstatistics | ForEach-Object{
$quQuota = "unlimited"
if ($_.UseDatabaseQuotaDefaults -eq $false){
if ($usrquotas.ContainsKey($_.MailboxGUID)){
$quQuota = "{1:P0}" -f ($_.TotalItemSize.Value.ToMB()/$usrquotas[$_.MailboxGUID].Value.ToMB())
if ($mstoresquotas.ContainsKey($_.database)){
$quQuota = "{1:P0}" -f ($_.TotalItemSize.Value.ToMB()/$mstoresquotas[$_.database].Value.ToMB())}

What’s next when I get time I want to add a history feature so that every time you run the Gui it will record the result to an XML file so that the next time you run it in a week or months time it can then show you how much each mailbox has grown since. Also I’d like to come up with a cmd-line version that will output the result to a HTML Email with all the same functions. If anyone has any other idea’s they would like to see please let me know and I’ll see what I can do.

I’ve put a download of the new version here.

Popular posts from this blog

Export calendar Items to a CSV file using EWS and Powershell

Somebody asked about this last week and while I have a lot of EWS scripts that do access the Calendar I didn't have a simple example that just exported a list of the Calendar events with relevant information to a CSV file so here it is. I've talked on this one before in this howto  but when you query the calendar folder using EWS you need to use a CalendarView which will expand any recurring appointments in a calendar. There are some limits when you use a calendarview in that you can only return a maximum of 2 years of appointments at a time and paging will limit the max number of items to 1000 per call. So if you have a calendar with a very large number of appointments you need to break your query into small date time blocks. In this example script I'm just grabbing the next 7 days of appointments if you want to query a longer period you need to adjust the following lines (keeping in mind what I just mentioned) #Define Date to Query $StartDate = (Get-Date) $EndDate

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 '

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Graph is limited to a m
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.