> Officially, there is no such thing, because Exchange is "magic".
>
> And, everything that deals with Office 365 is completely undocumented,
> although you can probably figure them out if you want to.
>
> There is an (incomplete) list here:
>
> http://technet.microsoft.com/en-us/library/bb738157(v=exchg.150).aspx
Thanks for that article, there are enough 'Not applicable' fields that is not
going to
be a solution. At any rate, I think I may have stumbled on to the issue I was
trying
to work around (slow performance from a .net app).
Out of curiosity, what might be an elegant way to accomplish something like
this:
# This list is dynamic, changes every invocation.
$attributes = 'Name', 'DisplayName', 'Database', 'EmailAddresses'
Get-Mailbox -ResultSize unlimited |foreach-object {
foreach ($attr in $attributes)
{
# Check for type of $attr in $mailbox
# Push type specific object into temp array
# For each element of that array, send to a streamwriter...
}
}
The issue is, the consumer of this data wants the values from the list of
attributes
returned like what they see when they pipe the cmdlet through format-list.
When working with each mailbox through the pipeline, those individual data types
range in format in type. What magic does FL do that I want:)?
Thanks for the help Michael!
jlc
