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.
Labels:

Popular posts from this blog

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 Gr...
Read more

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more

EWS-FAI Module for browsing and updating Exchange Folder Associated Items from PowerShell

Folder Associated Items are hidden Items in Exchange Mailbox folders that are commonly used to hold configuration settings for various Mailbox Clients and services that use Mailboxes. Some common examples of FAI's are Categories,OWA Signatures and WorkHours there is some more detailed documentation in the https://msdn.microsoft.com/en-us/library/cc463899(v=exchg.80).aspx protocol document. In EWS these configuration items can be accessed via the UserConfiguration operation https://msdn.microsoft.com/en-us/library/office/dd899439(v=exchg.150).aspx which will give you access to either the RoamingDictionary, XMLStream or BinaryStream data properties that holds the configuration depending on what type of FAI data is being stored. I've written a number of scripts over the years that target particular FAI's (eg this one that reads the workhours  http://gsexdev.blogspot.com.au/2015/11/finding-timezone-being-used-in-mailbox.html is a good example ) but I didn't have a gene...
Read more
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.