In Exchange 12 (“E12”), we have focused our public API story on:
Web Services for accessing information stored on the server
Managed Agents for processing mail flowing through the serve...
Updated Jul 01, 2019
Version 2.0
Blog Post
Re: Joe's comment: http://blogs.technet.com/exchange/archive/2005/09/15/410941.aspx#411245
http://blogs.technet.com/exchange/archive/2005/09/15/410941.aspx#411245
Great to hear the feedback on WMI providers, please let us know what other areas have been problematic. On your other questions:
#4: There are two items to discuss here. One is the ability to do cross-forest operations like moving mailboxes. For this we will provide cmdlets that accept credentials other than the current logon, enabling the scenario where you are working in Forest 1 but
need to move data to Forest 2. For the second case, which is the ability to manage a remote machine, we do support remote operations and in some cases specifically providing the DC you want to operate on.
#5: Actually the monad way to do it is to get all the data back and select only what you need. For example: $stats = get-mailboxstatistics "domainuser"; $stats.LastLogonTime. Or you can do get-mailboxstatistics | select-object LastLogonTime. Either method
will work.
#6: Yes your assumption is correct for the example given. You can actually pass in multiple things for that identity argument: GUID, DN, or a friendly string. All are acceptable.
Thanks, ~vivek