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

Recently one of my customer updated that they get an different issue with their ASP application. This application running on their Web server that uses MAPI to read the Contacts folder in the Public Folders from Exchange Server 2003 SP2 machine. The user can retrieve his email in outlook and browse the public folders as he is used to, but when this user want to use the ASP page that reads the public folder he fails. Customer receives the following error: bstrPublicRootID = objInfoStore.Fields.Item(&H66310102).Value

Here is a sample vbscript using which we can get SMTP servers instance names in a particular domain pragmatically via ADSI. 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 being demonstrated and the tools used to create and debug procedures. This sample

Determine version number of Exchange: To determine the version number, the build number, and the service pack level of a Microsoft Exchange Server computer, check the following properties of the server. If you have Exchange Server 4.0, Exchange Server 5.0, or Exchange Server 5.5 then you can, follow these steps: Start the Microsoft Exchange Administrator program. In the left pane, expand the objects until you locate the server object, and then click the server object. On the File menu, click Properties

using System; using System.Net; using System.IO; using System.Text; using System.Xml;   namespace SampleCode { class GetFolders { static void Main( string [] args) { // Variables. System.Net.HttpWebRequest Request; System.Net.WebResponse Response; System.Net.CredentialCache MyCredentialCache; string strRootURI = "http://server/exchange/username/Inbox/" ; // Provide the valid URI string strUserName = "UserName" ; string strPassword = "Password" ; string strDomain

Outlook 2003 and Exchange Server 2003 goes into extended Support from 4/14/2009 Exchange Server 2003 goes into Extended Support on 4/14/2009. http://support.microsoft.com/lifecycle/?LN=en-us&p1=1773&x=11&y=9   Outlook 2003 goes into Extended Support on 4/14/2009. http://support.microsoft.com/lifecycle/?p1=2520 What is the difference between Mainstream Support, Extended Support, and online self-help support? Support provided Mainstream Support phase Extended Support phase Paid support

I have recently worked out a VBScript to list delegate of the Outlook Mailbox using CDO 1.2.1 via VBScript and thought of share it with you all, here is the sample code: 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 being demonstrated and the tools

We can enumerate the store event sink as given below: 'This command helps us to enumerate the list of registered store event sink's with the 'administrator user's inbox available in contoso.com C:\> cscript regevent.vbs enum "file://./backofficestorage/contoso.com/mbx/administrator/inbox" all .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin:

;) = 1000   Set RsAll = Comm.Execute   Dim dn While Not RSAll.EOF dn = "LDAP://" &

Per the support KB , Microsoft PSS has the support policy for customization of Outlook Web Access for Exchange that cover its versions like 5.5, 2000 & 2003. Per the article, we can get more information regarding the support policy for OWA customization for its various versions like, “…The Exchange 5.5 version of OWA is made up of Active Server Pages (ASPs). The Exchange 2000 and Exchange 2003 versions of OWA are composed of two main components: templates and controls. Templates are served from