Maybe someone can shed some light on a bit of Powershell weirdness I've come across and can't explain.
This PS script returns a list of exchange databases, their sizes and the number of mailboxes in each one:
Get-MailboxDatabase | Select Server, StorageGroupName, Name, @{Name="Size (GB)";Expression={$objitem = (Get-MailboxDatabase $_.Identity); $path = "`\`\" + $objitem.server + "`\" + $objItem.EdbFilePath.DriveName.Remove(1).ToString() + "$"+ $objItem.EdbFilePath.PathName.Remove(0,2); $size = ((Get-ChildItem $path).length)/1048576KB; [math]::round($size, 2)}}, @{Name="Size (MB)";Expression={$objitem = (Get-MailboxDatabase $_.Identity); $path = "`\`\" + $objitem.server + "`\" + $objItem.EdbFilePath.DriveName.Remove(1).ToString() + "$"+ $objItem.EdbFilePath.PathName.Remove(0,2); $size = ((Get-ChildItem $path).length)/1024KB; [math]::round($size, 2)}}, @{Name="No. Of Mbx";expression={(Get-Mailbox -Database $_.Identity | Measure-Object).Count}} | Format-table –AutoSize
If I add a simple 'sort name' before the 'format-table' my resulting table contains blanks where the database sizes and number of mailboxes should appear (not zeros, blank empty space).... but only in some rows, not all rows. Some rows contain numbers!
If I put the '|sort name| ' after the initial 'get-mailboxdatabase' it works fine.
Whats even weirder is if I do the following:
- Execute the above command
- Add the sort before format-table
- Execute the new command
- Execute the initial command again
What I see is different amounts in each of the three cases - all of which are incorrect. Yet 1 and 3 are the same command and the only difference with 2 is a sort. 1 and 3 should, at a minimum, return the same results. I get blanks where I should have MBs
If I add the sort after the get-mailboxdatabase, it always returns identical results (as it should).
Can anyone suggest an explanation as to what may be going on?
If its of any help in reading the expression, I've reformatted it here to make it a bit more readable:
Get-MailboxDatabase | Select Server, StorageGroupName, Name,
@{Name="Size (GB)";Expression={
$objitem = (Get-MailboxDatabase $_.Identity); $path = "`\`\"
+ $objitem.server + "`\"
+ $objItem.EdbFilePath.DriveName.Remove(1).ToString() + "$"
+ $objItem.EdbFilePath.PathName.Remove(0,2);
$size = ((Get-ChildItem $path).length)/1048576KB; [math]::round($size, 2)
}},
@{Name="Size (MB)";Expression={
$objitem = (Get-MailboxDatabase $_.Identity);
$path = "`\`\"
+ $objitem.server + "`\"
+ $objItem.EdbFilePath.DriveName.Remove(1).ToString() + "$"
+ $objItem.EdbFilePath.PathName.Remove(0,2);
$size = ((Get-ChildItem $path).length)/1024KB; [math]::round($size, 2)
}},
@{Name="No. Of Mbx";expression={
(Get-Mailbox -Database $_.Identity | Measure-Object).Count
}}
| Format-table –AutoSize
I'm sort of thinking aloud here, but maybe this is related to this known issue with PowerShell 2.0 which has been resolved in PowerShell 3.0 CTP2. I know you don't explicitly call
Add-Member
, but theSelect
statement with a calculated field sort of accomplishes the same thing. It seems like they could be related. I ran some tests to compare PS 2.0 and 3.0 and 3.0CTP2 never once failed on your query. PowerShell 2.0 gave me different output every time.If you can't install PS 3.0 yet, I've rewritten part of your script, but it doesn't have all of the columns that your original does. I'll let you tweak it to perfection. You'll just need to use
Add-Member
to add more properties.Keep in mind that if you install PS 3.0, you can still launch version 2.0 if you add the
-version 2.0
parameter after thepowershell.exe
call.