Skip to main content

Combining multiple Exchange Management Shell powershell cmdlets and maintaining the Pipeline

This post continues on a little bit from last weeks update of the mailbox size GUI where I combined three Exchange powershell cmdlets get-mailbox,get-mailboxstatistics and get-mailboxdatabase to get the percentage of quota used for a users mailbox. When I did this although I used the Pipeline I didn’t really maintain it because I didn’t really need to I had my own custom methods for displaying the data I was querying. But one of the most useful things about Powershell is when using the pipeline normally you have a lot of built in functionality as to how you can format and export the results of whatever command you are running for instance Export-Csv format-table etc.

Someone asked the question this week

We need to get the user's list from POWER SHELL sorting by database , ProhibitsendrecieveQuota, mailboxsize & lastlogontime ( those who have not been logged on their mails for 60 days).

I hope there should be merged these two comlets "get-mailbox "and "get-mailboxstatistics".

Out put format should be as follows:

Alias, Databasename, ProhibitsendrecieveQuota, lastlogontime

Peter MailDB 100 MB 30/11/2007 “

While I might go about this another way such as writing another little gui or mod the mailbox size report it’s a useful problem to confront for people who are getting more and more comfortable with Pipelining in Exchange Management Shell but maybe not really sure how you could go about combining two or three cmdlets like I have and still get the normal output features.

The answer is relatively easy all you need to do is create your own custom collection and then write the result of your combined cmdlet queries to your custom collection and then at the end of the pipeline you can then use the normal export-csv or format-table cmds. For example here’s a script that solves the question asked and allows both outputting the result to a screen and exporting to a csv.

$mbcombCollection = @()
Get-Mailbox -ResultSize Unlimited | foreach-object{
$mbstatis = get-mailboxstatistics $_.identity
$mbcomb = "" | select Alias,Databasename,ProhibitsendrecieveQuota,lastlogontime
$pequote = "unlimited"
$dbarry = $_.Database.ToString().split("\")
if ($_.UseDatabaseQuotaDefaults -eq $true){
$dbsetting = get-Mailboxdatabase $_.database
if ($dbsetting.ProhibitSendReceiveQuota -ne "unlimited"){
$pequote = $dbsetting.ProhibitSendReceiveQuota.Value.ToMB()
}
}
else {
if ($_.ProhibitSendReceiveQuota -ne "unlimited"){
$pequote = $_.ProhibitSendReceiveQuota.Value.ToMB()
}}
$mbcomb.Alias = $_.Alias
$mbcomb.Databasename = $dbarry[2]
$mbcomb.ProhibitsendrecieveQuota = 299
$mbcomb.lastlogontime = $mbstatis.LastLogonTime
$mbcombCollection += $mbcomb
}


$mbcombCollection
$mbcombCollection | Export-Csv C:\LogonStats.csv

This is a simple example if you have a large number of users for example this would be a little slow it would be better just to make one get-mailbox request and one get-mailboxstatitics request store the results in two hash tables then merge the result of the hash tables which is what I did with the mailbox size gui. But the above method is much easier for people to understand so it’s probably a better example in that regard.

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 https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filename.txt 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 ' https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filena

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 https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . 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.