In Exchange 2007 if you wanted to enable HTTP for Exchange Web Services all you had to do was go into Internet Information Services (IIS) and uncheck the box 'Require secure channel (SSL)' on the EWS virtual directory. In Exchange 2010 RTM this is no longer possible. IIS still gives you this option; however it does not give you the behavior you are expecting. If you uncheck this box and attempt to make a request using HTTP you receive a HTTP 404 Resource Not Found. Exchange 2010 Web Services are

In Outlook, custom forms are typically published to a forms library so that only one copy of a form is stored on your computer. Individual items contain a Message Class field that indicates which form to use to display the data that is contained in the item. When you publish custom forms to a forms library, Microsoft Exchange Server-based computers and Outlook use considerably less resources and bandwidth because the form itself does not need to be stored within each individual item. Considerations

We just announced a new release of the MAPI Download that’s pretty much mandatory if you want to work with Exchange 2010. You’ll also need to get and apply Rollup 1 (RU1) for Exchange 2010 . Details about the MAPI Download: The first version of the MAPI download which is compatible with Exchange 2010 is 6.5.8147 If you already have a version of the MAPI Download installed, you must unininstall it before installing the new version. The installer does not upgrade, nor does it warn you if you try to

http://www.microsoft.com/downloads/details.aspx?FamilyID=371add31-d7a0-4c8b-8325-a6fced2d05e6&displaylang=en Along with a new version of the MAPI download: http://www.microsoft.com/downloads/details.aspx?familyid=e17e7f31-079a-43a9-bff2-0a110307611e&displaylang=en Once the new MAPI download has been installed you should no longer have to disable MAPI Encryption on the Client Access Server Read more about it here: http://msexchangeteam.com/archive/2009/12/09/453486.aspx

Earlier i got a chance to play around creating recurring tasks. I followed the article from MSDN and it worked like charm for me. public TaskType CreateRecurringTask() { // Create the task item and set property values. TaskType task = new TaskType(); task.Subject = "Recurring Task" ; task.Body = new BodyType(); task.Body.BodyType1 = BodyTypeType.Text; task.Body.Value = "Occurs every week" ; task.StartDate = DateTime.Now; task.StartDateSpecified = true ;   // Create the regeneration

From time to time, I get asked to explain where CDO publishes Free Busy information in the Public Folder store, so I figured I’d put this article together. The basic process CDO uses for updating FB information is outlined in the More Information section of KB 278954 . We’re concerned with the part of the process summarized as “queued up to be sent to the site’s Free/Busy public folder.” The first thing CDO does is to open the Public Folder store and read a couple properties off of it, PR_FREE_BUSY_FOR_LOCAL_SITE_ENTRYID

Matt’s very excited about the release of EWSEditor . This tool does for EWS what MFCMAPI does for MAPI. With this tool, Matt does what I did with MFCMAPI and what I recommend to anyone trying to learn a new API: the best way to learn an API is to write tools that use it. As you work with EWSEditor, you may notice a few things which are similar to MFCMAPI. This is no coincidence. EWS and MAPI, both designed primarily to interact with an Exchange server, share much of the same object hierarchy, which

As Paul Thurrott notes, we just announced that we’re documenting the PST file structure . I haven’t decided yet if I’ll be writing a standalone parser/viewer/validator, but I’m sure I’ll be adding some interesting stuff to MFCMAPI . I’ll let you know when I know more. digg_url = "http://blogs.msdn.com/stephen_griffin/archive/2009/10/26/inside-the-pst.aspx";digg_title = "Inside the PST";digg_bgcolor = "#FFFFFF";digg_skin = "compact"; digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin

This is a continuation of my previous post . I wanted to take a moment and discuss the intent of the sample, how to get it working, and some caveats when you attempt to take the sample and turn it into production ready code. Purpose The purpose of the sample is to demonstrate how to use Remote Powershell from several different clients and then call an Exchange 2010 cmdlet. Components There are several components that make up the sample, the RemoteExchangePS proxy DLL, the managed client and the native

I have seen this question posed a lot so I decided that I would post a quick code sample here and the complete sample on my samples site. In my sample I created a managed client and a native client which both call into a managed DLL that runs the Get-ExchangeServer cmdlet using Remote Powershell. Here is the method that actually does the work if you don't want to download the entire sample: private const string SHELL_URI = " http://schemas.microsoft.com/powershell/Microsoft.Exchange "; public void