//====================================================================================================== // CdoexmMailboxUtil - // Exchange Mailbox and user account creation sample. // // This sample demonstrates the following: // Creating a user account in AD // Mail Enable an existing user. // List information on an existing user. // Note: This code is provided as a sample only, so you need to test and take responsibility // of the code and any of its possible actions before usage. Being a sample,

If your living in a pre Exchange 2007 Powershell worlds and want to mail enable or disable public folders, you may come to the point where you will be needing to write some CDOEX and CDOEXM code to do what you want. Below is a C# sample console application which will allow you to mail enable, mail disable and view mail settings on a public folder. //====================================================================================================== // ExchangePfUtil - // Exchange Public Folder

Ever copied a DLL from one system to another and registered it using RegSvr32.exe? or in other words ever created a DLL hell situation? Its easy and dirty at the same time to copy-paste DLL between systems and register them using regsvr32.exe Often you copy-paste, register DLL from temporary folders or may be desktop and then later delete the DLL or move to other folder without unregistering/re-registering it. Stop right there!!! You are creating a problem for yourself. Every time you register a

CDOEX is a superset of CDOSYS; this means that CDOEX contains all of the functionality of CDOSYS, plus additional functionality for use with Microsoft Exchange Server 2000. When CDOEX is installed on a computer, it takes over the functionality that was previously provided by CDOSYS. Any program that makes calls to CDOSYS will now call CDOEX instead. When CDOEX is installed (by installing Microsoft Exchange Server 2000, Microsoft Office XP, or other programs), the CDO for Windows 2000 reference is

My customer has CDOEX based legacy application which pulls the calendar and appointment items. Later they had merged their Exchange Server 2003 SP2 along with Exchange Server 2007 SP1 – mixed mode environment. He had an unique issue, whenever he tries to access couple of appointments created in Exchange Server 2007 environment, his CDOEX application throws the error : 8004011B: Unknown Error which means MAPI_E_CORRUPT_DATA. When we started troubleshooting we found that those appointments were created

The following sample is a simple VBScript code sample that that uses CDOEX and ADO to iterate through multiple mailboxes and dumps out the contact data to a text file. This code must be run on the Exchange server. To use this sample, paste the following code in a new text file, and then name the file DumpContacts.vbs: 'This script must be run on an Exchange Server. 'USAGE: cscript DumpContacts.vbs DOMAIN Datafile(FullPath) Dim obArgs Dim cArgs Set obArgs = WScript.Arguments cArgs = obArgs.Count Main

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

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

Not getting all the properties you would expect from an WebDAV ALLPROPS or from an Event sink? Well, it could be that the Exchange schema is broken. The Problem: If you find that your application is no longer retrieving a full list of properties, it may be due to a broken Exchange Web Store Schema. Cause: This is a state where the schema is broken, and can happen due to a variety of causes; such as failed extension of the schema from an application installation or incorrect schema modification of

Please find the VBScript code-snippet to get or extract the messages that are contained in the other objects like Message or IBodyPart.   1: ' Please provide the value for sVal 2: Function getMsg(sVal As IBodyPart) As Message 3: Dim Msg 4: Set Msg = CreateObject( "CDO.Message" ) 5: Dim getVal 6: Set getVal = Msg.DataSource 7: getVal.OpenObject sVal, "IBodyPart" 8: Set getMsg = Msg 9: End Function .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: