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

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

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

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:

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

With continuation of my previous article … now you can get support for Virtualized Exchange environment with the release of Microsoft Windows Server 2008 with Hyper-V and Microsoft Hyper-V Server 2008, a virtualized Exchange 2007 SP1 server is no longer restricted to the realm of the lab; it can be deployed in a production environment and receive full support from Microsoft. This past August, Microsoft published our support policies and recommendations for virtualizing Exchange , but many people

As you know Collaboration Data Objects for Exchange Management or CDOEXM is used to create applications that manage Exchange servers, databases, public folders, and user mailboxes. It provides the fundamental Component Object Model (COM) classes and interfaces that are used to manage the Exchange store. From Exchange 2007 onwards… From Exchange Server 2007 onwards you can’t use the CDOEXM functionalities, because Exchange Server 2007 doesn’t include CDOEXM i.e., CDOEXM does not ship in and is not

What is CDO for Workflow? CDO for Workflow (CDOWF) is built-in functionality provided with Microsoft Exchange 2000 Server. By using CDOWF, which is driven by the Exchange store event architecture, you can design workflow applications without having to write the fundamental code that accesses, modifies, and controls data. CDOWF includes a workflow engine, modeling tools, and an event sink. Applications that use CDOWF are stored on the Exchange server. Direct access to that server, however, is not

If you work with Outlook Web Access (OWA) along with Exchange Server 2000 or/and Exchange Server 2003 or/and Exchange Server 2007, then please find the wonderful technet article , which i read frequently and distribute it with my customers. This article explains how Microsoft Outlook Web Access works in Exchange organizations that include computers that are running one or more versions of Microsoft Exchange that were released earlier than Microsoft Exchange Server 2007. These earlier versions can