Le Café Central de
Deva             


                    ... Deva blogs!!



  • Le Café Central de DeVa

    Monitoring event sink # 25 - Recipients modified mail (using event sink) sent from PICKUP folder and lands in the DROP folder ?

    • 1 Comments

    Recipients modified email messages (using event sink) sent from PICKUP folder and lands in the DROP folder ?

    The Pickup folder processes outgoing messages that are created as text files and then copied to the Pickup folder. When Request for Comments (RFC) 822 messages that are correctly formatted are copied to the Pickup folder, the SMTP service initiates delivery. In this replay method, the X-Sender envelope field and the X-Receiver envelope field are written to the e-mail message when the SMTP service puts the e-mail message into the Drop folder.

    Note
    The SMTP service puts the e-mail message into the Drop folder for local delivery on a computer where Exchange is not installed.

    In this scenario, the Pickup operation honors the envelope fields that are written to the e-mail message

    In detail

    This is because, we will have an default domain entry in the SMTP mail area of IIS. This is the process that handles all mail that comes into your SMTP system that is not otherwise specified. This mail would be delivered based on the settings you make in the properties area of that default setting. This includes the name of the server that the mail claims to be from.

    In addition to this default entry, you can also create an Alias Domain for any other domains you might own. Each one can have its own name. So where your default might say mail is coming from Mydomain.com, you can set up alias domains for domain.com and minedomain.com. Once you have those aliases set up, each alias then sends its mail to the DROP folder associated with that alias. The mail will sit there in the DROP folder, waiting for further processing. It assumes that another system is going to poll that DROP folder and do something with the mail.

    If you end up with mail messages in your DROP folder because you created an alias domain by accident, simply delete that alias and then stop and restart the mail server. Now drag all the messages from the DROP area back into the PICKUP area. They will process through the default queue, following your normal rules and get out to your recipients.

    .

  • Le Café Central de DeVa

    Test and troubleshooting tools for various Exchange technologies

    • 0 Comments
    I tried to compose the test and troubleshooting tools for various exchange technologies. This initial list upto Exchange Server 2003. 
     

    Technology

     

    Tools for test and troubleshooting tools

    Active Directory Services Interfaces (ADSI)

     

    All standard test and debugging tools, as well as other Microsoft and third-party test and debugging tools, can be used.

     

    Collaboration Data Objects for Windows 2000 (CDOSYS)

     

    No special debugging tools are needed to debug applications that use CDOSYS.

     

    CDOSYS SMTP/NNTP Event Sinks

     

    No special debugging tools are needed to debug applications that use CDOSYS. For particularly difficult protocol-interaction issues, a network monitoring utility may prove helpful, but is typically not required.

     

    Collaboration Data Objects for Exchange 2000 Server (CDOEX)

     

    No special debugging tools are needed to debug applications that use CDOEX.

     

    Collaboration Data Objects for Exchange Management (CDOEXM)

     

    No special debugging tools are needed to debug applications that use CDOEXM.

     

    Collaboration Data Objects for Exchange Workflow (CDOWF)

     

    No special debugging tools are needed to debug applications that use CDOWF. Custom applications might be created to analyze the process audit logs created during process execution. If you are using the Workflow Designer for Exchange 2000 Server, enable Just-In-Time (JIT) script debugging. JIT starts the Microsoft Script Debugger when the error occurs. The debugger starts on the server, so you need to have access to the server.

     

    Exchange OLE DB Provider (ExOLEDB)

     

    No special debugging tools are needed to debug applications that use ExOLEDB.

     

    Exchange Store Event Sinks

     

    No special debugging tools are needed to debug applications that use Exchange store event sinks.

     

    Exchange Web Forms

     

    No special debugging tools are needed to debug applications that use Exchange Web forms. Note, however, that because the forms execute on the computer running Microsoft Exchange Server 2003, debugging may require the developer have access to the Exchange server. Always use caution when allowing anyone direct access to the Exchange server.

     

    HTTP/Web Distributed Authoring and Versioning (WebDAV)

     

    No special debugging tools are required to debug applications that use WebDAV. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful. The NETMON.EXE tool can be very useful in debugging WebDAV protocol interactions. Because WebDAV queries are sometimes sensitive to minor syntactical differences, a WebDAV query tool can also be helpful.

     

    WebDAV Notifications

     

    No special debugging tools are needed to debug applications that use WebDAV Notifications. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful, but is typically not required.

     

    Incremental Change Synchronization (ICS)

     

    No special debugging tools are needed to debug applications that use ICS.

     

    Lightweight Directory Access Protocol (LDAP)

     

    No special debugging tools are needed to debug applications that use LDAP. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful, but is typically not required.

     

    Messaging Application Programming Interface (MAPI)

     

    No special debugging tools are needed to debug applications that use MAPI.

     

    Outlook Object Model (OOM)

     

    No special debugging tools are needed to use OOM.

     

    Outlook Web Access

     

    No tools are available for debugging calls to Microsoft Outlook® Web Access, because the internal architecture is not available for debugging, and the URL calls required to access Outlook Web Access programmatically are not documented or supported.

     

    Exchange Rules

     

    No special debugging tools are needed to debug applications that use Exchange rules. Client-side rules require Outlook for proper testing.

     

    SMTP Event Sinks

     

    No special debugging tools are needed to debug applications that use SMTP event sinks. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful, but is typically not required.

     

    Windows Management Instrumentation providers for Exchange (WMI)

     

    No special tools are required to debug applications that use WMI.

     

    Exchange Backup & Restore API

     

    No special tools are required to debug applications that use the Exchange Backup and Restore API.

     

    Exchange writer for the Windows Volume Shadow Copy Service

     

    No special tools are required to debug applications that use the Windows Volume Shadow Copy Service.

     

  • Le Café Central de DeVa

    CDOSYS + Quoted-printable

    • 0 Comments

     

    Code snippet
     
     
    'private void cmdSend_Click(object sender, System.EventArgs e)
     
    {
     
    try
     
    {
     
    CDO.Message oMsg = new CDO.MessageClass();
     
    CDO.Configuration oConfig = new CDO.ConfigurationClass();
     
    ADODB.Fields oFields = oConfig.Fields;
     
    StringBuilder MailString = new StringBuilder();
     
    int x = 1000;
     
    // Set up configuration to send to remote SMTP server
     
    oFields["http://schemas.microsoft.com/cdo/configuration/sendusing"].Value = CDO.CdoSendUsing.cdoSendUsingPort;
     
    oFields["http://schemas.microsoft.com/cdo/configuration/smtpserver"].Value = txtSMTPServer.Text;
     
    oFields["http://schemas.microsoft.com/cdo/configuration/smtpserverport"].Value = 25;
     
    oFields.Update();
     
    // Apply the configuration object to the message object
     
    oMsg.Configuration = oConfig;
     
    // Make the root bodypart "quoted-printable"
     
    oMsg.BodyPart.ContentTransferEncoding = "quoted-printable";
     
    // Set up the message
     
    oMsg.From = txtFrom.Text;
     
    oMsg.To = txtTo.Text;
     
    oMsg.Subject = txtSubject.Text;
     
    MailString.Append("<table>");
     
    while (x > 0) 
     
    {
     
    MailString.Append("<tr><td>this is a test, </td></tr>");
     
    x--;
     
    }
     
    MailString.Append("</table>");
     
    oMsg.HTMLBody = MailString.ToString();
     
    oMsg.Send();
     
    txtOutput.Text = "Message Sent!";
     
    MailString = null;
     
    oFields = null;
     
    oConfig = null;
     
    oMsg = null;
     
    }
     
    catch(Exception MyException)
     
    {
     
    txtOutput.Text = MyException.Message;
     
    }
     
    }
  • Le Café Central de DeVa

    Gotcha : PowerShell questions

    • 1 Comments

    I composed couple of Windows PowerShell questions:

    Can you create your own PowerShell object?

    We can write a Cmdlet, but we have to do that with a .NET Framework language such as C# or VB.NET.

    Can we create a.BAT file using PowerShell?

    No. But we can create PowerShell scripts, which have a .PS1 file extension

    Can we run a .VBS file natively run in PowerShell?

    No, we can't.

    Can we work PowerShell against remote systems? If so how?

    PS 1.0 will not work against remote systems. However, we can call WMI or .NET Framework and use them to run against remote machines.

    How can we sign a script?

    Same as signing any code

    Can you run more than one copy of PowerShell at the same time?

    Yes.

    Will I need to know PowerShell to administer Exchange 2007?

    Yes we can manage Exchange from the command prompt or by using scripts. Also we can still do it by using the GUI-based management of Exchange without knowing PowerShell.

    How do you find all the namespaces available in PowerShell?

    Get-PSProvider will list all the PowerShell providers and Get-PSDrive will list all the drives currently mapped to the namespaces surfaced by those providers.

  • Le Café Central de DeVa

    API's that are not included in Exchange Server 2007 ?

    • 0 Comments

    When you migrated from Microsoft Exchange 2000 & 2003, where they provide several API's that are not included in Microsoft Exchange Server 2007. Please find the following API's that are not included in the Exchange Server 2007 environment & the recommended technologies to migrate to.

    APIs that are not included in Exchange 2007

    API

    Status in Exchange 2007

    Replacement Technology

    CDOEX

    De-emphasized but still supported.

    Exchange Web Services

    CDOEXM

    Not included in Exchange 2007.

    Microsoft Windows PowerShell and Exchange 2007 commands

    CDOWF

    Not included in Exchange 2007.

    Windows Workflow Foundation (WWF) and Microsoft BizTalk Server 2006

    EXOLEDB

    De-emphasized but still supported.

    Exchange Web Services

    MAPI

    De-emphasized but still supported.

    Exchange Web Services

    Public Folders

    De-emphasized but still supported.

    Exchange Web Services

    Store Events

    De-emphasized but still supported.

    Exchange Web Services

    WebDAV

    De-emphasized but still supported.

    Exchange Web Services

    Web Forms

    Not included in Exchange 2007.

    ASP.NET

    WMI Providers

    Not included in Exchange 2007.

    Windows PowerShell and Exchange Server 2007 commands.

     

  • Le Café Central de DeVa

    Monitoring event sink # 24 - Store event sink is not working as expected in Exchange Server 2007

    • 0 Comments

    When i am working with my customer with regards to Exchange store event sink, he reported it's not working as expected. There is no issues in the Event viewer and no error it thrown. We tried with Microsoft Exchange Server 2007 environment, the store event sink does not run as expected.

    Note: The event is triggered, but the registered script is not executed or no file is created.

    This issue occurs because of some changes in Active Template Library (ATL) 8.0.

    To resolve this problem in Exchange Server 2007 Service Pack 1, install Update Rollup 1 for Exchange Server 2007 Service Pack 1. For more information and resolution of this issue, please go through the following KB article.

  • Le Café Central de DeVa

    Nutshell : MSXML is not supported in .Net applications

    • 0 Comments

    I started working from Visual Basic 6, where i had used XML Parser (MS XML) to fetch the data's using WebDAV. But the same logic won't apply for you when you do with .Net applications.

    So, where we need to use MSXML and .Net Framework classes's for XML?

    • Microsoft XML Core Services (MSXML) : As i updated you earlier you can easily use MSXML in Visual Studio 6.0 applications as DOM and SAX Parser with support for XSLT and XPath.
    • .NET Framework Classes for XML : But when you're planning to implement the XML, then you need to make use of System.XML, the .Net framework classes for XML instead of MSXML.
      • Because the System.Xml namespace provides standards-based support for processing XML.
      • System.xml is not just the managed version of MSXML;
      • its functionality may overlap that of the MSXML COM library, and it also contains a rich object model and hierarchy.

    FYI: You can go through this below given article, which gives overall view and design goals of XML in the .Net Framework.

    Design Goals for XML in the .NET Framework
    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpcondesigngoalsforxmlframeworkinnet.asp

    No Official support. Do you know why it so?

    Officially Microsoft does not support the use of MSXML (Microsoft’s COM-based XML parser) in .NET applications.

    This is because MSXML uses threading models and garbage-collection mechanisms that are not compatible with the .NET Framework. Using MSXML in .NET applications through COM interoperability can result in unexpected problems that are difficult to debug.

    Please note that Microsoft does not recommend or support directly instantiating and using MSXML objects in .NET code, nor does Microsoft recommend or support marshalling MSXML interface pointers across the interop boundary

    So what is the workaround or best practice needs to be done?

    Support for implementing standards-based XML functionality in .NET applications is built into the .NET Framework. The .NET Framework classes in the System.xml namespaces should be used to implement standards-based XML functionality in .NET applications.

    Code snippets: FYI: I have enclosed couple of code snippets for your reference.

    Earlier we might have created a web request to a web server like this using MSXML,

       1:  Dim oXMLHttpRequest As New MSXML2.XMLHTTP
       2:  ' Provide the respective values
       3:  oXMLHttpRequest.open "GET", "http://[servername]/[virtualdirectory]/[filename.xml]", False, "", ""
       4:  oXMLHttpRequest.send
       5:  Debug.Print (oXMLHttpRequest.responseText)


    When you create the .Net applications, you need to do the same by using .Net framework classes like,

       1:      using System;
       2:      using System.Xml;
       3:      using System.Net;
       4:      
       5:      public class Sample    
       6:      {
       7:          public static void Main()        
       8:          {
       9:              // Provide the respective values
      10:              HttpWebRequest request = (HttpWebRequest)WebRequest.Create("http://[ServerName]/[virtualdir]/[filename.xml]");
      11:   
      12:              // Provide the Username and password.
      13:              request.Credentials = new NetworkCredential("[username]", "[password]");
      14:   
      15:              // It downloads the XML file from the specified server.
      16:              HttpWebResponse response = (HttpWebResponse)request.GetResponse();
      17:              
      18:              // Then it loads the XmlDocument.
      19:              XmlDocument doc = new XmlDocument();            
      20:              doc.Load(response.GetResponseStream());
      21:              doc.Save(Console.Out);
      22:   
      23:              // Finally don't forgot to release the resources of the response.
      24:              response.Close();
      25:          }
      26:      }
     
     
  • Le Café Central de DeVa

    Tutorial : Organizational Forms Library - Series # 2

    • 0 Comments

    Can we create it programmatically?

    To create it programmatically using MAPI, we need to make use of CreateFolder(), the MAPI function. It is necessary to have very special privileges (obtained by opening the store with an EntryID created using IExchangeManageStore::CreateStoreEntryID()) to get it to work.

    Please refer the following KB to create Org. forms library programmatically.


    How to create Org. Forms Library in Exchange Server 2003 ?

    To create a new Organizational Form in Exchange Server 2003, please follow the steps given below:

    1. Start Exchange System Manager.

    2. Expand the Organization object. Expand your Administrative Group.

    3. Expand Folders. Right-click Public Folders.

    4. Click View System Folders.

    5. In the list of folders present in the right-hand pane, click the EFORMS Registry folder.

    6. Right-click the EFORMS Registry folder, then click New. Click Organizational Form.

    7. Enter a name for your Organizational Form, and then click OK.

    8. Repeat these steps for multiple forms to create the library.

    Note:
    1)
    How to create copies of organizational forms library?

    In Exchange Server 2003, to create copies of the Organizational Forms Library on other servers, click the Replication tab, and then type the name of server that you want to contain the copy of the Organizational Forms Library.

    2) How to set the storage limits for an organizational forms library?

    To set storage limits for an Organizational Forms Library, click the Limits tab. To create a description of an Organizational Forms Library, click the Details tab. To set permissions for each user, click the Permissions tab.


    How to create Org. Forms Library in Exchange Server 2007 ?

    Per the KB, you need to follow the following method to create an Organizational Forms Library as it got changed in Exchange 2007.

    To create an Organizational Forms Library in Exchange 2007, follow these steps.

    1. Create a new public folder.

    a. Click Start, point to All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell.

    b. Run the following command at the Exchange Management Shell prompt:
    New-PublicFolder -Path "\NON_IPM_SUBTREE\EFORMS REGISTRY" -Name "My Organizational Forms Library"

    Note: You can use the Exchange management shell on any version of Exchange 2007 to create a folder. However, in Exchange 2007 SP1, you can also create the EFORMS REGISTRY folder by following these steps:

                a. Go to Toolbox in Exchange Management Console. Double-click Public Folder Management Console.

                b. In the left pane, click System Public Folders.

                c. in the Action pane, click New Public Folder. Type EFORMS REGISTRY as the folder name, and then click NEW.

                d. After the folder is created, click Finish to exit the wizard.

    2. Add the PR_EFORMS_LOCALE_ID.

    a. Use an account that belongs to the Exchange Administrators Group to log on to a client computer that is running Microsoft Office Outlook 2003 or a later version of Microsoft Outlook.

    b. Start the Microsoft Exchange Server MAPI Editor (Mfcmapi.exe) from the MFCMAPI folder.

    c. Create a MAPI profile if it is necessary.

    d. On the Session menu, click Logon and Display Store Table.  Select MDB menu, click Open Public Folder Store, and then click OK.

    e. Expand Public Root, expand NON_IPM_SUBTREE, and then expand EFORMS REGISTRY.

    f. Click the public folder that you created in step 1. For example, click My Organizational Forms Library.

    g. Click the PR_URL_NAME property. On the Property Pane menu, click Modify Extra Properties. Click Add, and then click Select Property Tag.

    h. Click PR_EFORMS_LOCALE_ID in the list, and then click OK. Click OK two times. A red mark is displayed next to the newly created PR_EFORMS_LOCALE_ID property.

    i. Double-click PR_EFORMS_LOCALE_ID. In the Unsigned Decimal box, type the desired locale ID, and then click OK. For example, type 1033 for English, type 1040 for Italian, or type a different ID for a different locale.
    Note: To determine the locale ID for other locales, visit the following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/aa579489.aspx (http://msdn2.microsoft.com/en-us/library/aa579489.aspx)

    j. Exit MAPI Editor.

    3. Configure limits and permissions for the Organizational Forms Library folder. Note: You can use suitable cmdlets in the Exchange Management Shell to set limits and permissions for the Organizational Forms Library folder.

    a. To set storage limits, use the following cmdlet: Set-PublicFolder

    b. To set permissions for each user, use the following cmdlets: Add-PublicFolderClientPermission, Add-PublicFolderAdministrativePermissions

  • Le Café Central de DeVa

    Tutorial : Organizational Forms Library - Series # 1

    • 0 Comments

    What are the various types of Outlook form libraries available?

    There are three types of Outlook form libraries are available, they are (i) Organizational Forms Libraries (2) Personal Form Libraries (3) Folder Libraries.

    What is an Organizational Forms Library?

    • An organization's forms library is a repository for forms (templates that help users to enter and view information)  that are accessed by all users in a company.
    • In simple terms, an organizational forms library is a special type of public folder that is listed only with system folders.

    Some of the examples are, a standard supply request form can be stored in an organizational forms library or a form used to report vacation time etc.

    Why to use Organizational Forms Library?

    If we publish the forms at Organizational forms library it will used throughout the enterprise-wide. Org. forms library acts as the centralized library or repository. Saving to this library provides a quick and easy way to distribute and update forms.

    How to use the forms enterprise-wise or throughout the organization?

    • You must publish a form to this library if you want to make the form available to everyone in your organization.
    • You can publish a form to the Organizational Forms Library when you want to use the same custom form in more than one folder.
    • This library is frequently used for e-mail message forms because they are typically not based on a specific folder.
    • When you publish a form, you can maintain only a single published form.
    • Everyone in the organization can access the forms that are published to this library as long as the administrator grants the users permissions to the library.

    Where these libraries stored in Exchange?

    Exchange stores these libraries in the EFORMS REGISTRY system folder.

    Note: In Exchange Server 2003, you can only create organizational forms libraries in the system folders subtree of the Public Folders tree. Even if you have created new public folder hierarchies to work with the organizational forms libraries, only the Public Folders tree supports the EFORMS REGISTRY system folder.

    What are the permissions required to view or use this?

    Org. forms library is stored on the Microsoft Exchange Server-based computer. The administrator must give you permissions to publish to the Organizational Forms Library. This permission is typically given to only some individuals or a department that manages the Exchange server-based computer

    Note: You can't publish forms to the Organizational Forms library unless the systems administrator grants you permission.

    Multi-languages support for Organizational Forms Library?

    • Organizational Forms libraries provides supports for multi-languages.
    • When you create an organizational forms library, you assign a language to it. You can have only one organizational forms library for each language.
    • When you use the Forms Administrator to create Organizational Forms Libraries, you must consider the different languages that clients use to access those libraries.
  • Le Café Central de DeVa

    Microsoft Learning’s limited time offer – Second shot can save 25% more

    • 0 Comments

    Second Shot now offers two incentives to get certified!

    Today, Second Shot provides the benefit of a free retake if you fail a Microsoft Certification exam.

    From October 15 – December 31, 2008, you will also be rewarded for passing the exam!

    If you pass, you can now use the Second Shot offer to enjoy 25% off a different exam!

     


    The Offer – 3-easy steps :

    1. Register for Second Shot offer and sit for the exam by December 31, 2008!

    2. If you fail the exam you will receive a free retake exam that can be utilized until June 30, 2008

    3. If you Pass, you will get 25% off a second exam.  You have until February 28, 2009 to utilize the discounted exam.  

     

    Note: If you pass the first exam but fail your 25% off second exam, you will not get a free retake on your second exam.


    For more details, please visit http://www.microsoft.com/learning/mcp/offers/secondshot/default.mspx

  • Le Café Central de DeVa

    Microsoft Product Lifecycle : Visual Basic, Exchange Server and Outlook (various versions)

    • 0 Comments

     

     

    Microsoft Product Lifecycle for various versions of Visual Basic

     

    Products Released

     

    General Availability Date

     

    Mainstream Support Retired

     

    Extended Support Retired

     

    Service Pack Retired

     

    Notes

     

    Visual Basic .NET 2002 Standard Edition

     

    4/15/2002

     

    7/10/2007

     

    7/14/2009

     

       

    Visual Basic .NET 2003 Standard Edition

     

    7/10/2003

     

    10/14/2008

     

    10/8/2013

     

       

    Visual Basic 2005 Express Edition

     

    1/14/2006

     

    4/12/2011

     

    4/12/2016

     

       

    Visual Basic 2008 Express Edition

     

    2/19/2008

     

    Review Note

     

    Review Note

     

     

    Mainstream support will end two years after the next version of this product is released. Extended support will end five years after mainstream support ends.

     

    Visual Basic 6.0 Enterprise Edition

     

    1/27/1999

     

    3/31/2005

     

    4/8/2008

     

       

    Visual Basic 6.0 Standard Edition

     

    1/27/1999

     

    3/31/2005

     

    4/8/2008

     

       


    Microsoft Product Lifecycle for various versions of Exchange Server

     

    Products Released

     

    General Availability Date

     

    Mainstream Support Retired

     

    Extended Support Retired

     

    Service Pack Retired

     

    Notes

     

    Exchange Server 2000 Service Pack 3

     

    7/18/2002

     

    Review Note

     

    Review Note

     

     

    Support ends 12 months after the next service pack releases or at the end of the product's support lifecycle, whichever comes first. For more information, please see the service pack policy at http://support.microsoft.com/lifecycle/#ServicePackSupport .

     

    Exchange Server 2003 Service Pack 2

     

    10/19/2005

     

    Review Note

     

    Review Note

     

     

    Support ends 12 months after the next service pack releases or at the end of the product's support lifecycle, whichever comes first. For more information, please see the service pack policy at http://support.microsoft.com/lifecycle/#ServicePackSupport .

     

    Exchange Server 2007 Service Pack 1

     

    11/29/2007

     

    Review Note

     

    Review Note

     

     

    Support ends 12 months after the next service pack releases or at the end of the product's support lifecycle, whichever comes first. For more information, please see the service pack policy at http://support.microsoft.com/lifecycle/#ServicePackSupport .

     

    Exchange Server 4.0 Standard Edition

     

    6/11/1996

     

    6/30/2003

     

    Not Applicable

     

       

    Exchange Server 5.0 Enterprise Edition

     

    5/23/1997

     

    12/31/2003

     

    1/10/2006

     

     

    Support for the Exchange 5.0 Outlook Web Access (OWA) client and Internet Information Server (IIS) 3.0 ended on March 31, 2000. (IIS 3.0 is a required component of Exchange 5.0 OWA.) We strongly recommend that customers who are running Exchange 5.0 OWA, upgrade to Internet Information Server 4.0 or later and Exchange 5.5 OWA.

     

    Exchange Server 5.0 Standard Edition

     

    5/23/1997

     

    12/31/2003

     

    1/10/2006

     

       

    Exchange Server 5.5 Enterprise Edition

     

    2/3/1998

     

    12/31/2003

     

    1/10/2006

     

       

    Exchange Server 5.5 Standard Edition

     

    2/3/1998

     

    12/31/2003

     

    1/10/2006

     

       

    Forefront Security for Exchange Server

     

    3/8/2007

     

    4/10/2012

     

    4/11/2017

     

       

    Exchange Server 4.0 Service Pack 1

     

    5/1/1996

     

    Not Applicable

     

    Not Applicable

     

    12/31/1996

     

     

    Exchange Server 4.0 Service Pack 2

     

    7/19/1996

     

    Not Applicable

     

    Not Applicable

     

    1/29/1997

     

     

    Exchange Server 4.0 Service Pack 3

     

    10/29/1996

     

    Not Applicable

     

    Not Applicable

     

    6/28/1997

     

     

    Exchange Server 5.0 Service Pack 1

     

    6/18/1997

     

    Not Applicable

     

    Not Applicable

     

    5/10/1998

     

     

    Exchange Server 4.0 Service Pack 4

     

    3/28/1997

     

    Not Applicable

     

    Not Applicable

     

    8/5/1998

     

     

    Exchange Server 5.5 Service Pack 1

     

    8/5/1998

     

    Not Applicable

     

    Not Applicable

     

    3/23/1999

     

     

    Exchange Server 5.5 Service Pack 2

     

    12/23/1998

     

    Not Applicable

     

    Not Applicable

     

    12/9/1999

     

     

    Exchange Server 5.5 Service Pack 3

     

    9/9/1999

     

    Not Applicable

     

    Not Applicable

     

    1/1/2001

     

     

    Exchange Server 2000 Service Pack 1

     

    6/21/2001

     

    Not Applicable

     

    Not Applicable

     

    2/28/2002

     

     

    Exchange Server 4.0 Service Pack 5

     

    5/5/1998

     

    Not Applicable

     

    Not Applicable

     

    6/30/2003

     

     

    Exchange Server 2003 Enterprise Edition

     

    9/28/2003

     

    4/14/2009

     

    4/8/2014

     

    5/25/2005

     

     

    Exchange Server 2003 Standard Edition

     

    9/28/2003

     

    4/14/2009

     

    4/8/2014

     

    5/25/2005

     

     

    Exchange Server 5.0 Service Pack 2

     

    2/10/1998

     

    Not Applicable

     

    Not Applicable

     

    12/31/2005

     

     

    Exchange Server 5.5 Service Pack 4

     

    11/1/2000

     

    Not Applicable

     

    Not Applicable

     

    12/31/2005

     

     

    Exchange Server 2003 Service Pack 1

     

    5/25/2004

     

    Not Applicable

     

    Not Applicable

     

    1/8/2008

     

     

    Exchange Server 2007 Enterprise Edition

     

    3/8/2007

     

    4/10/2012

     

    4/11/2017

     

    1/13/2009

     

     

    Exchange Server 2007 Standard Edition

     

    3/8/2007

     

    4/10/2012

     

    4/11/2017

     

    1/13/2009

     

     

     

    Microsoft Product Lifecycle for various versions of Outlook

     

    Products Released

     

    General Availability Date

     

    Mainstream Support Retired

     

    Extended Support Retired

     

    Service Pack Retired

     

    Notes

     

    Outlook 97 Standard Edition

     

    1/16/1997

     

    12/31/2001

     

    2/28/2002

     

       

    Outlook Express 4.0 for Macintosh

     

    1/6/1998

     

    6/30/2003

     

    Not Applicable

     

       

    Outlook Express 4.0

     

    4/21/1998

     

    3/31/2003

     

    Not Applicable

     

       

    Outlook 98 Standard Edition

     

    6/21/1998

     

    1/16/2004

     

    1/16/2004

     

       

    Outlook Express 4.5 for Macintosh

     

    1/5/1999

     

    6/30/2003

     

    Not Applicable

     

       

    Outlook 2000 Standard Edition

     

    6/27/1999

     

    6/30/2004

     

    7/14/2009

     

       

    Outlook Express 5.0 Macintosh Edition

     

    10/19/1999

     

    6/30/2003

     

    Not Applicable

     

       

    Outlook 2002 Standard Edition

     

    5/31/2001

     

    7/11/2006

     

    7/12/2011

     

       

    Outlook Express 6.0

     

    8/27/2001

     

    Review Note

     

    Review Note

     

     

    Please review the Internet Explorer 6 information that is on the Select a Product for Lifecycle Information site at http://support.microsoft.com/gp/lifeselect or the Support Lifecycle Index site at http://support.microsoft.com/gp/lifeselectindex.

     

    Outlook 2003

     

    11/20/2003

     

    4/14/2009

     

    4/8/2014

     

       

    Outlook 2007

     

    1/27/2007

     

    4/10/2012

     

    4/11/2017

     

       

    Outlook 2007 with Business Contact Manager

     

    1/27/2007

     

    4/10/2012

     

    Not Applicable

     

       

    Outlook 2007 with Interconnect

     

    1/27/2007

     

    4/10/2012

     

    4/11/2017

     

       

     

  • Le Café Central de DeVa

    Microsoft Windows : I'm a PC, aren't you?

    • 1 Comments

    Many people started murmuring what is this new stuff, "I'm a PC"? what is this all about.

    Even i got the following excerpts:

    "... if you're a PC, you belong to one of the world's most diverse communities, connecting across countries, cultures and technologies. Explore this PC Gallery and see what individuality looks like on your screen. You can also record and upload yourself, becoming part of this site and appearing in online ads across the world wide web.

    Where you connect to a global community of more than a billion people and nothing comes between you and a world of ideas and opportunities. With Windows on your mobile phone, PC, or the Web, walls begin to disappear—at home, at the office, and anywhere in between. You can balance work and life as well as fun and functionality. And with a wide range of software, services, and devices to choose from, your technology can be as unique as you are. That's Windows. Life without walls..."

    Later I found that Microsoft launched the next phase of a long-term Windows marketing effort, with the tagline “Life Without Walls.” Key to the new initiative are TV and online spots called “I’m a PC”, which feature both real people celebrating their connection to the community of one billion Windows users worldwide. Windows users can join the community by uploading their own “I’m a PC” videos on windows.com and some user videos will be show on digital billboards in New York’s Time Square.

    The “Life Without Walls” theme was introduced via a set of print and out of home ads which show how multiple Windows devices connect seamlessly, across PCs, phones, TVs and other devices. See the Image Gallery for sample print ads.

  • Le Café Central de DeVa

    Monitoring event sink # 23 - OnsyncSave global Events causing notifications

    • 0 Comments

    One of my customer who has reported that on Exchange Server 2000 his Store event sink (onSyncSave) for global events causing the notifications for the couple of empty flags. When we analyzed his event sink, he registered it as,

    regevent add onsyncsave sink.sink.1 "file://./backoficestorage/%userdnsdomain%/MBX/SystemMailbox{GUID}/StoreEvents/GlobalEvents/<reg>"

    This issue happens whenever he created a new user and immediately he try to send the message in the user mailbox. When he tries to create OnSyncSave global event bindings in the Global Events folder for the store. For this they receive extra OnSyncSave folder event notifications, that are generated with empty bstrURLItem and EVT_ERROR | EVT_IS_COLLECTION bit set in lflags

    Per the KB article this happens due to following: when a new user mailbox is created, the store automatically creates many subfolders such as Inbox, Outbox, and so on. The store delays such creation until the first item is created in the user's mailbox. Thus, when a new message is created in a new mailbox, extra OnSyncSave folder event notifications related to mailbox creation are generated.

  • Le Café Central de DeVa

    Available public : List of exported Outlook APIs - definitions, data structures, functions & interfaces

    • 0 Comments

    As described in the MSDN article, Microsoft Office Outlook exports the following definitions, data structures, functions, and interfaces that were originally designed for internal use but are now exposed for public consumption.

    Definitions: Constants for Exported Outlook APIs

    Data structures: CONTAB_ENTRYID, RTF_WCSINFO, RTF_WCSRETINFO, TZDEFINITION, TZREG, TZRULE

    Functions: GetDefCachedMode, GetDefCachedModeDownloadPubFoldFavs, HrCreateApptRebaser, HrGetAutoDiscoverXML, MAPICrashRecovery, RebaseTaskComplete, RebaseTaskProgress, WrapCompressedRTFStreamEx

    Interfaces: IOlkApptRebaser

  • Le Café Central de DeVa

    Out of Scope : How To Programmatically Cause the Creation of a User's Profile - Windows ?

    • 1 Comments

    Hi, this is a new series called “Out of scope”, where i am trying to add non-Messaging Dev technologies. This won’t be supported by me nor by my team, just added based on my programming interest. So, “Out of Scope” tag is meant for general audience.

    Many a times i thought how to programmatically cause a user's profile to be created without requiring an interactive logon? First of all, whether this will be possible in the Windows?

    Please go through the following article. The remainder of this article demonstrates how to work with the User Profile structures and functions on Windows NT 4.0. For complete information on these structures and functions, refer to the Platform SDK documentation in the latest release of the MSDN Library.

    By default, a new user's profile is not created until the user logs on to the computer interactively. An interactive logon occurs when a user logs on to the computer by pressing CTRL+ALT+DEL to gain access through the WinLogon dialog box.

    It is possible to programmatically cause a user's profile to be created without requiring an interactive logon by calling the LoadUserProfile() API. In Windows 2000 and Windows XP, this function is exposed within the Platform SDK header files and documented in the MSDN Library. On Windows NT 4.0, the LoadUserProfile() API is not exposed, but it can still be called by dynamically loading the Userenv.dll library and obtaining a pointer to the function.

    Calling LoadUserProfile() on Windows NT 4.0

    This article has a code snippet which demonstrates how to programmatically create a new user account, force a profile to be created for the new user, and retrieve the new profile directory.

  • Le Café Central de DeVa

    Tutorial : Free/Busy data - Series # 1

    • 2 Comments

    Publishing Free/Busy data:

    Free/busy data is published information that contains a user's personal availability data based on the user's schedule. Microsoft Exchange Server uses the information extensively when users schedule meetings.

    • Exchange Server 2003 stores free/busy information in a dedicated public folder that is named SCHEDULE+ FREE BUSY. This folder contains a separate subfolder for each administrative group in your Exchange organization. When a user publishes free/busy data, Exchange Server 2003 posts the information in a message in the appropriate free/busy subfolder. The free/busy folders are system folders and function in a manner that is similar to offline address book folders.
    • Exchange Server 2007 uses the availability service.

    Free/Busy data & different versions of Outlook and Exchange Server :

    • The process of publishing free/busy data from the user's client application to the appropriate free/busy folder depends in part on the client that the user has.
    • Outlook and other MAPI-based clients function somewhat differently in this respect from Web-based clients such as Microsoft Office Outlook Web Access for Exchange Server 2003 and Microsoft Outlook Mobile Access.
    • The Availability service for Microsoft Exchange Server 2007 provides calendar information for your users. This information is known as free/busy information.

    How Outlook publishes free/busy data?

    By default, Outlook publishes the free/busy data for a user one time every 15 minutes, and again when Outlook shuts down. When publishing, Outlook updates the entire free/busy message instead of just adding changes to the existing message. The message includes free/busy data that ranges from the current month to two months in the future.

    How to customize with Outlook?

    Outlook users can customize the free/busy settings, including the following:

      • Publishing interval, which can be as short as one minute.
      • Number of months in the future to publish, which can be as long as 36 months.

    Outlook 2007 with different Exchange Servers:

    As we know that Microsoft Office Outlook 2007 works well with a variety of e-mail servers, and you can take advantage of an even richer feature set by using Outlook with the latest version of Microsoft Exchange Server. Some features of Office Outlook 2007 require or work better with Microsoft Exchange Server 2003 or later.

    • Free/Busy information is always up-to-date for users with Exchange 2007 Availability service. But it’s not the case with Exchange 2003.
    • Tentative calendar booking is managed on the Exchange Server. Users do not need to run Outlook for others to see their Free/Busy status. This feature is only available in Exchange Server 2007, not with Exchange Server 2003.

    MadFB, Autodiscover & Outlook clients:

    • The Autodiscover service provides information for the Availability service by locating and providing the external and internal URLs for the Outlook 2007 client.
    • If your Microsoft Office Outlook 2007 users cannot view calendar information for other Outlook 2007 users in your Exchange 2007 environment, the problem may involve a failure in either the Autodiscover service or the Availability service.
    • Microsoft Entourage for the Macintosh also relies on this MadFB(MSExchangeFBPublish) process to publish free/busy data.
    • Outlook Web Access and Outlook Mobile Access do not publish free/busy data directly to the public folder store.
    • Instead, they rely on a free/busy publishing agent that is named MadFB (also known as MSExchangeFBPublish), which runs as part of the Microsoft Exchange System Attendant service (MSExchangeSA).
    • MadFB has two functions.
      • It publishes free/busy messages for Outlook Web Access and Outlook Mobile Access
      • It deletes duplicate free/busy messages

    Note: Because most of the processing is handled by the Exchange servers instead of the client, using Outlook Web Access and Outlook Mobile Access can provide performance and reliability advantages over Outlook.

    There are various other issues happens with respect to Free/Busy data when we do with programming as well as with the Outlook clients. I tried to catch up some of them and summarize for your view….

    1. Troubleshooting the Free/Busy information for Outlook 2007 by reading this technet article or you can check it through the error codes available. Some of them are,

    • 0x80072EE7 – ERROR_INTERNET_NAME_NOT_RESOLVED - This error is usually caused by a missing host record for the Autodiscover service in the Domain Naming service.
    • 0X80072F17 – ERROR_INTERNET_SEC_CERT_ERRORS - This error is usually caused by an incorrect certificate configuration on the Exchange 2007 computer that has the Client Access server role installed.
    • 0X80072EFD – ERROR_INTERNET_CANNOT_CONNECT - This error is usually caused by issues that are related to Domain Naming service.
    • 0X800C820A – E_AC_NO_SUPPORTED_SCHEMES - This error is usually caused by incorrect security settings in Outlook 2007.

    2. If you use Exchange Server 2007, you can determine whether the Availability service is not functioning properly or not:
    (i) using Event log (ii) using Test-OutlookWebServices cmdlet
    .

    Using Event log:

    When we try to review the application event log on the Exchange 2007 Client Access server and check for events that are generated by the Availability service. There are common events that are associated with the availability service as described. Some of them are,

  • 4001 The Availability service could not discover an Availability service in the remote forest   If you see this event, verify that the Autodiscover service in the remote forest is functioning correctly.
  • 4003 PublicFolderRequestFailed   This event usually indicates a failure to look up free/busy information for legacy mailboxes. Typically, this information comes from public folders. This error might be caused if the public folders are configured incorrectly or if the Availability service has not been configured to look up public folders for the legacy mailboxes. The description of this event will usually include the URL to the target public folder and one of the following HTTP errors:
    • 401   If you see this HTTP error, Integrated Windows authentication is probably disabled on the /public virtual directory.
    • 403   If you see this HTTP error, the Client Access server may be offline or it does not contain a replica. This might occur if Secure Sockets Layer (SSL) is not enabled on the /public virtual directory.
    • 404   This HTTP error can occur if the /public virtual directory could not be found.
  • 4005 Could not find information in Active Directory to allow cross-forest requests   If you see this event, you must configure the Availability service across forests.
  • 4011 Cross-forestRequestFailed   This usually indicates a failure to locate an AvailabilityAddressSpace object that is required to proxy the Availability service request to a different forest.
  • In this case, we will see how to find and troubleshoot the issue using the Event log. A 4003 event indicates a failure to look up free/busy information for legacy mailboxes. Typically, this information comes from public folders. The following is an example of a 4003 event.

    Event ID : 4003

    Raw Event ID : 4003

    Category : Availability Service

    Source : MSExchange Availability

    Type : Error

    Message : Process 4664[w3wp.exe:/LM/W3SVC/1/ROOT/EWS-1-128114978363374212]: Microsoft.Exchange.InfoWorker.Common.Availability.PublicFolderRequest failed. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.PublicFolderRequestProcessingException

    This may be due to Exchange 2007 users are unable to see the free/busy information for users whose mailboxes reside on the Exchange 2003 server. The free/busy information displays as hash marks for these users in the Outlook Scheduling Assistant page.

    Using Test-OutlookWebServices cmdlet:

    When you try to test through cmdlet test the service using, 
                            Test-OutlookWebServices -id:user1@contoso.com -TargetAddress: user2@contoso.com

    • The Test-OutlookWebServices cmdlet uses a specified e-mail address to verify that the Outlook provider is configured correctly.
    • The optional MonitoringLogFile parameter indicates whether the results are written to the log file for Microsoft Operations Manager (MOM).
    • Using the Test-OutlookWebServices cmdlet to verify the Autodiscover service settings for Microsoft Outlook on a computer that is running Microsoft Exchange Server 2007 that has the Client Access server role installed.
    • This will provide the error details about the Availability service.

    For example, as specified in the following article and code example verifies the service information that is returned to the Outlook 2007 client from the Autodiscover service for a user who is named monika@contoso.com. The code example verifies information for the following services:

    • Availability service
    • Outlook Anywhere
    • Offline Address Book
    • Unified Messaging
    test-OutlookWebServices -identity:monika@contoso.com

    This code example tests for a connection to each service. This example also submits a request to the Availability service for the user monika@contoso.com to determine whether the user's free/busy information is being returned correctly from the Client Access server to the Outlook 2007 client.

    3. Free/Busy Options Not Unique to Each Profile:

    On a computer that contains multiple profiles, the Free/Busy options will be the same for every profile. This information is defined in the KB article. The Free/Busy information is stored on a per-user basis rather than a per-profile basis. If the user who is logged on to the computer defines multiple profiles, each profile will contain the same Free/Busy information.

    To set the calendar Free/Busy information, follow these steps:

    1. On the Tools menu, click Options.

    2. On the Preferences tab, click Calendar Options.

    3. Click Free/Busy Options. In the Free/Busy Options dialog box you can set the following items:

    • How many months of Free/Busy information to publish.

    • How frequently the information should be updated.

    • Whether the information should be published on the Internet.

    • The Internet URL address for storing and searching for the information.

    4. Conditions that affect the display of Free/Busy time in Outlook:

    After you make an appointment in your active Calendar in Microsoft Outlook, other people may not immediately see that time as busy. This condition may also occur when someone attempts to invite you to a meeting.

    There are three possible causes for this behavior:

    • By default, Outlook updates your Free/Busy time every 15 minutes. If the update is not complete, others will not see your appointment as busy time.

    • Outlook publishes your Free/Busy time for only the next two months. If your appointment is beyond the published limit, others will not see your appointment as busy time.

    • If the appointment Show Time As property is set to Free, others will not see your appointment as busy time.

    The unavailability of Free/Busy information appears as black hatched lines in the Attendee Availability dialog box.

    Resolution:

    • If the cause is how often Outlook updates Free/Busy time, follow these steps as described in the support KB.
    • If the cause is how far ahead Outlook publishes Free/Busy time, follow these steps as described in the support KB
    • If the cause is that the Appointment Show Time As property is not set to Free, follow these steps as described in the support KB

    5. Legacy free/busy information no longer appears for appointments that are booked against a mailbox in Exchange Server 2007:

    In a Microsoft Exchange Server 2007 environment, you configure a room mailbox to have the AllBookInPolicy attribute set to "false." When you do this, the legacy free/busy information no longer appears for the appointments that are booked against the mailbox. For example, when you examine the free/busy information by using the Scheduling Assistant, the room mailbox shows a status of No Information.

    This issue occurs because the default permission is changed to "None" when the AllBookInPolicy attribute is set to "false." This situation prevents the Exchange System Attendant from publishing the legacy free/busy information. By default, when any mailbox is created, the free/busy permissions are set as follows:

    Default: Read: Free/Busy time
    Anonymous: None

    This condition is also true for resource mailboxes.

    To go through the following article to resolve this problem in Exchange Server 2007 Service Pack 1.

    6. Resolving problems in Outlook for delegated Exchange Server 2003 mailbox users :

    As stated above, we need to perform this procedure if delegated users are receiving error messages such as "Unable to open the free/busy message" when they try to modify the mailbox owner's calendar.

    1. Request that all delegate users and the mailbox owner shut down Outlook.

    2. Request that the mailbox owner start Outlook with the /cleanfreebusy switch. The mailbox owner can do this from the command prompt by typing: outlook/cleanfreebusy

      Outlook will re-create the LocalFreeBusy message and synchronize the other mailbox folders to use it.

    3. Resume using Outlook. Delegates should now be able to use the mailbox as expected.

    7. Cleaning Mailbox stores using MadFB:

    As stated above, and in the over time, the free/busy folders may accumulate duplicate free/busy messages. In addition, Outlook and the free/busy folders may become unsynchronized, especially for mailboxes that have multiple delegate users. This section provides information about how Exchange Server 2003 automatically maintains free/busy data according to a configurable schedule, and about how you can repair synchronization problems.

    The cleanup process includes:

    • Deleting duplicate free/busy data messages.
      These are messages with an appended –x in the URL, where x is the number of the duplicate message. For each set of duplicates, MadFB keeps the oldest message and deletes the rest.
    • Repairing the URLs of free/busy messages.
      The URL of a free/busy message must be in canonical format, ending with subject(based on legacyExchangeDN).EML.
      Messages that are duplicates of existing free/busy messages have non-canonical URLs because of the appended -x. Messages that have been upgraded or replicated from Microsoft Exchange Server version 5.5 have URLs that contain GUIDs. These messages are also considered non-canonical.

    8. Calendar support in an Exchange and Non-exchange environment:

    As stated in the following article regarding the calendar support in an Exchange and Non-exchange environment (for ex. using the Microsoft Exchange Connector for Lotus Notes and the Microsoft Exchange Connector for Novell GroupWise) perform several functions to support calendaring capabilities between the foreign system and Exchange Server 2003:

    • Replicate directory information so that both Exchange users and foreign system users have access to calendaring data.
    • Convert meeting request items from Exchange format to the foreign format and from the foreign format to the Exchange format.
    • Detect Exchange Server 2003 free/busy requests and look up the appropriate free/busy data in the foreign system. This free/busy lookup is bidirectional.
  • Le Café Central de DeVa

    Outlook Programming Series # 14 : How to - Create a Rule to Move Specific E-mails to a Folder programmatically ?

    • 0 Comments

    The code sample uses the RuleAction and RuleCondition objects to specify a rule that moves messages from a specific sender to a specific folder, unless the message contains certain terms in the subject. Note that the code sample assumes that there already exists a folder named "Outlook" under the Inbox.

    Code snippet:

       1:  Sub CreateRule()
       2:      Dim colRules As Outlook.Rules
       3:      Dim oRule As Outlook.Rule
       4:      Dim colRuleActions As Outlook.RuleActions
       5:      Dim oMoveRuleAction As Outlook.MoveOrCopyRuleAction
       6:      Dim oFromCondition As Outlook.ToOrFromRuleCondition
       7:      Dim oExceptSubject As Outlook.TextRuleCondition
       8:      Dim oInbox As Outlook.Folder
       9:      Dim oMoveTarget As Outlook.Folder
      10:   
      11:      'Specify target folder for rule move action
      12:      Set oInbox = Application.Session.GetDefaultFolder(olFolderInbox)
      13:      'Assume that target folder already exists
      14:      Set oMoveTarget = oInbox.Folders("Outlook")
      15:      
      16:      'Get Rules from Session.DefaultStore object
      17:      Set colRules = Application.Session.DefaultStore.GetRules()
      18:      
      19:      'Create the rule by adding a Receive Rule to Rules collection
      20:      Set oRule = colRules.Create("Sample_rule", olRuleReceive)
      21:   
      22:      'Specify the condition in a ToOrFromRuleCondition object
      23:      'Condition is if the message is from "<alias>"
      24:      Set oFromCondition = oRule.Conditions.From
      25:      With oFromCondition
      26:          .Enabled = True
      27:          .Recipients.Add ("<alias>")
      28:          .Recipients.ResolveAll
      29:      End With
      30:   
      31:      'Specify the action in a MoveOrCopyRuleAction object
      32:      'Action is to move the message to the target folder
      33:      Set oMoveRuleAction = oRule.Actions.MoveToFolder
      34:      With oMoveRuleAction
      35:          .Enabled = True
      36:          .Folder = oMoveTarget
      37:      End With
      38:   
      39:      'Specify the exception condition for the subject in a TextRuleCondition object
      40:      'Exception condition is if the subject contains "spam" or "text"
      41:      Set oExceptSubject = _
      42:          oRule.Exceptions.Subject
      43:      With oExceptSubject
      44:          .Enabled = True
      45:          .Text = Array("spam", "text")
      46:      End With
      47:   
      48:      'Update the server and display progress dialog
      49:      colRules.Save
      50:  End Sub
     
    Reference: For more detailed information, please go through this article.
  • Le Café Central de DeVa

    Outlook Programming Series # 13 : Programmatic equivalent for Outlook UI's Send/Receive

    • 1 Comments

    Whenever we work with Outlook 2007 UI, we click either "Send/Receive button" or press "F9" to send and receive emails. In couple of our cases we use to do programmatically you can make use of Outlook Object Model's (OOM) SendAndReceive method. You need to know that calling the SendAndReceive method is synchronous only.

    Syntax: expression.SendAndReceive(showProgressDialog)

    Here, showProgressDialog - Indicates whether the Outlook Send/Receive Progress dialog box should be displayed, regardless of user settings

    Note:

    • SendAndReceive provides the programmatic equivalent to the Send/Receive All command that is available when you click Tools and then Send/Receive.
    • If you do not need to synchronize all objects, you can use the SyncObjects collection object to select specific objects. For more information, see NameSpace.SyncObjects.
    • All accounts defined in the current profile are used in Send/Receive All.
    • If an online connection is required to perform the Send/Receive All, then the connection is made according to user preferences.

    Using with Outlook Object Model & Visual Basic 6:

    Use NameSpace.SendAndReceive Method. Initiates immediate delivery of all undelivered messages submitted in the current session, and immediate receipt of mail for all accounts in the current profile.

    Using in .Net environment & Outlook interop:

    Use NameSpaceClass.SendAndReceive Method (Microsoft.Office.Interop.Outlook). The types and members of the Microsoft.Office.Interop.Outlook namespace provide support for interoperability between the COM object model of Microsoft Office Outlook 2007 and managed applications that automate Outlook.

    This is a .NET class or a member of a .NET class created when processing a COM coclass that is required by managed code for interoperability with the corresponding COM object. Use this class only when you have to access an earlier event in this class that has been subsequently extended in a later version of Outlook. Otherwise, use the .NET interface derived from the COM coclass.

    Code snippet (used in the add-in):

    C#

       1:  public virtual void _NameSpace.SendAndReceive (
       2:      [InAttribute] bool showProgressDialog
       3:  )

    then we need to use the SyncObject,

       1:  //trap the SyncObject.SyncStart Event 
       2:    this.Application.Session.SyncObjects[1].SyncStart += new Microsoft.Office.Interop.Outlook.SyncObjectEvents_SyncStartEventHandler(ThisAddIn_SyncStart);
       3:   
       4:  //finally don't forget to trap the SyncObject.SyncEnd Event 
       5:  this.Application.Session.SyncObjects[1].SyncEnd += new Microsoft.Office.Interop.Outlook.SyncObjectEvents_SyncEndEventHandler(ThisAddIn_SyncEnd);
       6:   

    Visual Basic:

       1:  Dim instance As NameSpaceClass
       2:  Dim showProgressDialog As Boolean
       3:   
       4:  CType(instance, _NameSpace).SendAndReceive(showProgressDialog)


    Reference(s):

    http://msdn.microsoft.com/en-us/library/microsoft.office.interop.outlook.namespaceclass.sendandreceive.aspx
    http://msdn.microsoft.com/en-us/library/microsoft.office.interop.outlook.syncobjectevents_event_members.aspx

  • Le Café Central de DeVa

    Outlook 2007 / MS CRM : Access denied error - [0x80070005-0x80070005-0x000508]

    • 0 Comments

    Whenever we send any email from the Outlook client (Outlook 2007) & MS CRM the email bounces back undeliverable with the following message:

    This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator. Error is [0x80070005-0x80070005-0x000508].

    The above error code is "Windows General Access Denied" message.

    When we investigated and found that,

    • It's due to "permissions issue" in the "Exchange Organization object" in "Active Directory". In our scenario the error thrown to the Outlook Client, when it tries to attempt to access MessageID from Exchange and failing.
  • Le Café Central de DeVa

    Error Codes : Windows Mail and Windows Live Mail error codes

    • 0 Comments

    I came across this KB article which contains a list of error codes that may occur in Windows Mail or in Windows Live Mail. The list contains the following categories:

    • Error code  • Error type • Description

    The list of error codes may be returned in Windows Mail or in Windows Live Mail if a failure occurs when you send mail or when you receive mail. The list contains, General errors, Winsock errors, SMTP (Simple Mail Transfer Protocol) errors, HTTPmail errors, NNTP (Network news Transport Protocol) errors, Remote access errors, IMAP (Internet Message Access Protocol) errors,

  • Le Café Central de DeVa

    Outlook Errors : General Errors - Part # 2

    • 0 Comments

    Receive error when you press F9 to send and receive e-mail in Outlook 2007 & Cached Exchange Mode:

    You use Cached Exchange Mode in Microsoft Office Outlook 2007. Additionally, you use the DownloadOAB registry value to prevent the automatic download of the offline address book (OAB). When you press F9 to send and receive e-mail messages in all Outlook accounts, Outlook unexpectedly tries to download the OAB. Additionally, you receive the following error message:

    TASK 'Microsoft Exchange Server' reported error (0x8004010F) : The operation failed. An object could not be found.

    To resolve this problem, apply hotfix 939596. Additionally, you must turn off the option to download the offline address book before you press F9.

    Reference: For more details refer this KB article and how to obtain the hotfix to resolve the issue.

    Error message when you try to synchronize Outlook to a Windows Live Hotmail account: "Error with Send/Receive"

    You use the Microsoft Office Outlook Connector to synchronize Microsoft Office Outlook to a Windows Live Hotmail account. If the synchronization fails after several attempts, the synchronization process stops. Additionally, you receive the following error message:

    Error in Mail. Error with Send/Receive. http://g.live.com/1OLC12URL/SyncLimit

    This issue occurs if the Windows Live Hotmail account cannot currently be synchronized. To avoid saturating the synchronization limit for the account, the Outlook Connector preemptively stops the synchronization process.

    Reference: For more details refer this KB article to find the workaround to resolve the issue.

  • Le Café Central de DeVa

    Outlook Errors : Send and receive e-mail errors - Part # 1

    • 1 Comments

    Outlook Send and receive e-mail errors:

    When you try to send and receive e-mail, you may receive an error message that is similar to one of the following:

    No connection could be made because the target machine actively refused it.

    The server could not be found. (Account:account name, POPserver:'mail', Error Number: 0x800ccc0d)

    Task 'server name - Sending and Receiving' reported error (0x800ccc0f): 'The connection to the server was interrupted. If this problem continues, contact the server administrator or Internet service provider (ISP). The server responded: ? K'

    Your server has unexpectedly terminated the connection. Possible causes of this include server problems, network problems, or a long period of inactivity. Account. account name, Server: 'server name', Protocol: POP3, Server Response: '+OK', Port: 110, Secure(SSL): No, Error Number: 0x800ccc0f

    Task 'SMTP server name - Sending and Receiving' reported error (0x80042109): 'Outlook is unable to connect to your outgoing (SMTP) e-mail server. If you continue to receive this message, contact the server administrator or Internet service provider (ISP).'

    The operation timed out waiting for a response from the receiving (POP) server 0x8004210a

    A time-out occurred while communicating with the server 0x800ccc19

    You may also receive an error message that includes one or more of the following error codes:

    0x800ccc15

    • 0x80042108

    • 0x800ccc0e

    • 0x8004210b

    • 0x800ccc0b

    • 0x800ccc79

    • 0x800ccc67

    • 0x80040900

    • 0x800ccc81

    These error messages may occur if Microsoft Outlook or if Microsoft Outlook Express cannot establish a connection with your e-mail server. These error messages are frequently caused by one of the following:

    • You are not connected to the Internet or a network

    • Incorrect account settings

    • Your user profile in Outlook is damaged

    • An e-mail item on your POP3 server is damaged

    • Incorrect configuration of your AV software

    • Outlook Express has been removed from the computer or the installation is damaged

    • Incorrect configuration of personal firewall software

    The most common causes of these error messages are problems with Internet connectivity and incorrectly configured account settings in Outlook or Outlook Express.

    Please find the following article which talks about the following possible resolution methods available for the various Outlook or Outlook Express and its versions.

  • Le Café Central de DeVa

    How to access a particular mailbox using Microsoft Exchange web services ?

    • 0 Comments

    In this article, we will see how we can access a particular mailbox using Microsoft Exchange web services ?

    The DistinguishedFolderId element identifies Microsoft Exchange Server 2007 folders that can be referenced by name. The DistinguishedFolderId class has an optional Mailbox property on it that allows you to indicate which mailbox you are accessing.

       1:  <DistinguishedFolderId Id="" ChangeKey="">
       2:     <Mailbox/>
       3:  </DistinguishedFolderId>

    Note: A DistinguishedFolderId resolves to a FolderId. The schema that describes this element is located in the EWS virtual directory of the computer that is running Microsoft Exchange Server 2007 that has the Client Access server role installed.

  • Le Café Central de DeVa

    Screencast: Outlook Context Menus and Creating a Meeting from an Email

    • 0 Comments

    Please view this wonderful Screencast from channel9, which easily we can able to create our own menu option to the context menu in Outlook.

    Per jwiese "...would you like to add your own menu option to the context menu in Outlook?  How about turning an email into a new meeting request without having to type in all the attendees or the body and subject?  Well, in this Screencast I'll show you how to add to the context menu and generate a meeting request that includes the email's recipients, subject and body in the meeting details..."

  • Le Café Central de DeVa

    Exchange Server 2007 &amp; Domain Security

    • 1 Comments

    Exchange 2007 includes a new feature set that is named "Domain Security." Domain Security refers to the set of functionality in Exchange 2007 and Outlook 2007 that provides a relatively low-cost alternative to S/MIME or other message-level security solutions.

    The purpose of the Domain Security feature set is to provide administrators a way to manage secured message paths over the Internet with business partners. After these secured message paths are configured, messages that have successfully traveled over the secured path from an authenticated sender are displayed to users as "Domain Secured" in the Outlook and Outlook Web Access interface.

    Domain Security uses Transport Layer Security (TLS) with mutual authentication to provide session-based authentication and encryption. TLS with mutual authentication differs from TLS as it is usually implemented. Typically, when TLS is implemented, the client verifies that the connection securely connects to the intended server by validating the server’s certificate. This is received as part of TLS negotiation. In this scenario, the client authenticates the server before the client transmits data. However, the server doesn't authenticate the session with the client.

    With mutual TLS authentication, each server verifies the connection with the other server by validating a certificate that is provided by that other server. In this scenario, where messages are received from external domains over verified connections in an Exchange 2007 environment, Outlook 2007 will display a "Domain Secured" icon.

    For more information about how to plan for and deploy Domain Security in your organization, see White Paper: Domain Security in Exchange 2007

    Reference(s):
    http://technet.microsoft.com/en-us/library/bb691338(EXCHG.80).aspx
    http://technet.microsoft.com/en-us/library/bb124392(EXCHG.80).aspx

  • Page 1 of 2 (35 items) 12