Few of our customer reported that if they are getting HTTP 404 Error reported; when they tries to use EWS HTTP service endpoint for their application for Exchange Server 2010 . However, the same application work fine with EWS HTTP service endpoint with Exchange Server 2007. In Exchange 2010 RTM if we go into Internet Information Services (IIS) and uncheck the box 'Require secure channel (SSL)' on the EWS virtual directory. And then we attempt to make a request using HTTP using EWS service endpoint

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

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

Exchange Server 2007 SP2 Update Rollup 1 is available to download @ Download the Exchange2007-KB971534-EN package now . Update Rollup 1 for Exchange Server 2007 Service Pack 2 (SP2) resolves issues that were found in Exchange Server 2007 SP2 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP2 customers. For the details related to the issue fixed by it refer to Description of Update Rollup 1 for Exchange Server 2007 Service Pack 2 .   If

If you are developing using Exchange Web Services Managed API then now you can download @ Microsoft Exchange Web Services (EWS) Managed API 1.0 The Microsoft Exchange Web Services (EWS) Managed API 1.0 provides a managed interface for developing client applications that use Exchange Web Services. The EWS Managed API simplifies the implementation of applications that communicate with Microsoft Exchange Server 2007 Service Pack 1 (SP1) and later versions of Microsoft Exchange. Built on the Exchange

We can perform GetItem Exchange Web Service call to get Extended MAPI Properties refer my previous post How to get Extended MAPI Properties in the GetItem Exchange Web Service call? and can also perform FindItem based on the Extended MAPI Properties. In the sample code given below we would use CleanGlobalObjectId to perform FindItem for Calendar Items: NOTE: Following programming examples is for illustration only, without warranty either expressed or implied, including, but not limited to, the implied

We can get/set Extended MAPI Properties using Exchange Web Services for Exchange Server 2007/2010. Here is sample code snippet to get value for CleanGlobalObjectID via GetItem call of Exchange Web Services: NOTE: Following programming examples is for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This sample code assumes that you are familiar with the programming language

As we know by default the Display Name of Exchange Mailboxes(Exchange Server 2007 SP2) is in the format of “Firstname Lastname”. I want to change this for the couple of existing mailboxes to “Lastname, Firstname” for one my customer – he preferred non-development stuff!! I tried to do the same using the Exchange Management Shell, which fits for my requirement: > Get-Mailbox “User Name” | Get-User | ?{ $_.Lastname -ne $null } | %{ $dispName=$_.LastName + “, ” + $_.FirstName ; set-mailbox $_.SamAccountName

My experience with BitLocker: I use Windows BitLocker Drive Encryption (BitLocker) in my Windows Server Vista, 2008 & new Win 7 boxes. As i am trying this for a while, i thought to apply it with Exchange Server 2007 SP2 also; also wanted to see, whether i can make Exchange Server more stronger? How i tried? Step 1: I tried creating my new installation of Windows Server 2008 machine with SP updates Step 2: Tried creating the BitLocker Step 3: Tried creating the Exchange Server 2007 SP2 Let me

Tried finding the list of information about ports, authentication and encryption by Exchange Server 2007? Your search ends here. Please refer the TechNet article . You can find the list of information about ports, authentication, and encryption for all data paths used by Microsoft Exchange Server 2007. The Notes sections following each table clarify or define non-standard authentication or encryption methods.