Dan's WebDAV 101
This blog covers Messaging API development for Exchange and Outlook. My name is Daniel Bagley, I'm on the Messaging Developer Team.
Translate This Page
Translate this page
exchange managed API
exchange web services
Forms based authentication
outlook object model
Browse by Tags
Dan's WebDAV 101
Tagged Content List
About: Exchange PowerShell Automation
API Type: Exchange Administration API Interface: .NET Framework Class Libraries Business Logic: Managing mailboxes, storage groups, and databases. Language Support: Any .NET language. Direct Property Access: N/A Product Versions: Exchange 2007 and later. Summary: Exchange PowerShell...
18 May 2015
With Exchange 2010, use Remote Powershell
With Exchange 2010, you should be using Remote Powershell. Below are some articles to help get you started. How to call Exchange 2010 cmdlet's using Remote Powershell in code http://blogs.msdn.com/dvespa/archive/2009/10/22/how-to-call-exchange-2010-cmdlet-s-using-remote-powershell-in-code.aspx ...
10 Dec 2009
Don't redistribute product DLLs unless you know its safe and legal to do so.
Redistribution of files in the “ C:\Program Files\Microsoft\Exchange Server ” folder and sub-folders is not advised/supported. Yes, this does include the “C:\Program Files\Microsoft\Exchange Server\Public” folder also. These files are installed when the Exchange 2007 (or later) tools are installed. If...
2 Apr 2009
Links on Common PowerShell Automation Questions
I've put together a list of articles which cover common questions on Exchange PowerShell Automation. These links cover issues from starting out to common problems. I hope they help. Please let me know if there are others you see as important. Starting articles on automation: Using Exchange...
26 Sep 2008
Howto: Calling Exchange Powershell from an impersonated thread.
There are not many examples on doing doing impersonation for Exchange Powershell and non of the ones I see currently cover a few of the important gotccha’s. So, I put this together and wish to share. Impersonation and Exchange PowerShell: In order to do impersonation on a thread and have...
25 Sep 2008
Call Dispose on client when calling COM+ objects.
Dispose MUST be called from the client and not from the serviced component... There is a requirement for clients of COM+ Serviced Components to call dispose on the component. If you do not do this, it will not shut down. When you inherit from servicedcomponent, you also inherit from IDisposable...
29 May 2008
Handling results of calling Powershell - Multivalued and string arrays.
When calling PowerShell from managed code, you need to be aware of what is being returned and to not process properties returned always as strings. When you get information you were not expecting or no info returned from the call, you should look at TypeNameOfValue and see what is returned - this often...
8 Feb 2008
How to access or change OWA settings for Exchange 2007/2003/2000?
There is no supported way of changing OWA settings using WebDAV for Exchange 2007. Under Exchange 2000 and 2003, there were properties on the mailbox root which could be changed via code. However OWA 2007 is a much different animal. Under Exchange 2000 and 2003, there are properties which you could...
31 Jan 2008
HOWTO: csharp - powershell - call get-clusteredmailboxserverstatus with managed code.
// HOWTO: csharp - powershell - call get-clusteredmailboxserverstatus with managed code. // Sample which calls get-clusteredmailboxserverstatus and returns a list of nodes. //TODO: //#1 - Create a C# winform application and add a button. //#2 - Add namespace reference statements (using statements): ...
29 Nov 2007
HOWTO: csharp - Exchange powershell - call get-StorageGroupCopyStatus with managed code.
This sample is good for both calling and for using with calling other commandlets and seeing what is returend - ie it breaks-down the return results in general. See, most examples I've found so far show only how to get exact properties and not just dump out specific ones. You should be aware of what...
29 Nov 2007
Page 1 of 1 (10 items)
© 2015 Microsoft Corporation.
Privacy & Cookies