Exchange throttling is your friend… well, more like a police officer.

Here is one way to think of Exchange throttling: Exchange is the freeway. Applications accessing Exchange are the drivers on the freeway. Exchange Throttling is the COP who is there to enforce the rules if you don’t behave. The Exchange Administrator of the servers is the governing power which establishes the throttling limits (laws) which…

0

About: Exchange APIs to backup and restore data

Summary: There limited supported ways to backup and restore data with Exchange programmatically.  Backup Supported APIs can backup the data and restore properly.  Some developers try using APIs which were not meant for backup up and restoring data in order to gain certain functionality – such approaches usually lead to dead ends such as not being…

0

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 was introduced with Exchange 2007 as a replacement of CDOEXM and WMI which were used for Exchange administration.   Exchange 2007 did…

0

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 Remote Powershell Sample Explained…http://blogs.msdn.com/dvespa/archive/2009/10/22/remote-powershell-sample-explained.aspx Programmatic Access via Remote PowerShell in Exchange Server 2010http://msexchangeteam.com/archive/2009/11/02/453016.aspx Connect Remote Exchange Management Shell to an Exchange Serverhttp://technet.microsoft.com/en-us/library/dd297932.aspx Install Windows Management…

0

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 you need these files with the minimal installation, then use the Exchange installer to install them –…

2

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 Management Shell Commands with Managed Code…

1

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 it work with…

17

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.  However, the client MUST…

1

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 gives a…

3

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 get at with WebDAV…

3