Le Café Central de Deva
let.us.share.develop.more... Deva blogs!!
I changed the way of blogging. Re-designed the site & started using the latest Windows Live Writer 2011!! Additionally added Microsoft Translator gadget available @ top of page, so that you can change the page in your preferred language!!
Please find the following Microsoft Clinic for Exchange Server 2007 available for free - limited period, so make use of this!!
Course Name: Clinic 5091: Introduction to Microsoft Exchange Server 2007 Unified MessagingURL: https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=75413Estimated Time: 2 hrsAvailable Offline: Yes
In this online clinic, you are introduced to the new Unified Messaging features and functionalities in Exchange Server 2007. In addition, you learn how telephony and Unified Messaging can be integrated in Exchange Server 2007. This online clinic is composed of a rich multimedia experience. It is intended for IT Professionals, who are interested in telephony or Unified Messaging.
You can also monitor the Event sinks by using Performance Counters.
Each event appears as an instance of one of the following counters:
The following table describes these events.
The support guidelines for client-side messaging development
This is one of the finest article describes "what is supported" and "what is not supported" when you develop custom solutions that integrate with Microsoft-based messaging products or Microsoft technologies. This article also contains most of the key information to be aware of when you develop with Microsoft products and Microsoft technologies.
However, this article does not cover all scenarios.
Some of them were,
Please find the article
Hi Exchange and Outlook developers!!
I found this wonderful article, which describes a change in how Microsoft Office Outlook 2003 Service Pack 2 (SP2) and later service packs, Microsoft Exchange Server 2003 Service Pack 2 (SP2), and later versions of Exchange Server and of Outlook handle meetings. This new design addresses disappearing-meeting scenarios that were introduced by Outlook 2003 in cached mode.
The new design does not have a visible effect on end-users. However, the new design can affect custom solutions that integrate with the calendar features in Outlook. This article describes the new design so that developers of custom solutions can update those solutions if it is required
It's for all Microsoft developers, enthusists!!
Windows Server 2008 Release Candidate helps IT professionals to increase the flexibility and reliability of their server infrastructure while offering developers a more robust web and applications platform for building connected applications and services.
To download the RC1 Enterprise 64 bit only with the Hyper-V Beta, go to
Other Windows Server 2008 Resources:
Free Windows Server 2008 e-book offer and Microsoft Press newsletter
This e-book includes excerpts from two recent publications from Microsoft Press:
Introducing Windows Server 2008 by Mitch Tulloch with the Microsoft Windows Server Team (ISBN: 9780735624214)This e-book covers Windows Server virtualization, managing Windows Server 2008, Active Directory, Terminal Services, and failover clustering.
Microsoft Windows PowerShell Step by Step by Ed Wilson (ISBN: 9780735623958)This e-book includes an overview of Windows PowerShell, using Windows PowerShell cmdlets, and leveraging PowerShell providers.
Additional chapters from Introducing Windows Server 2008 will be added periodically, so be sure to come back and read more from expert Mitch Tulloch and the Windows Server team. Register to get the free e-book offer, and sign up for the Microsoft Press Book Connection newsletter.
Collection 5934: Introducing Windows Server 2008—free for a limited time!This online learning collection of clinics introduces the new features and functionality in Windows Server 2008. The clinics cover server virtualization, security and policy management, branch office management, centralized application access, and server management. You can take the entire collection of clinics, or just the clinics that interest you.
Clinic 5935: Introducing Server Virtualization in Windows Server 2008
Clinic 5936: Introducing Security and Policy Management in Windows Server 2008
Clinic 5937: Introducing Branch Office Management in Windows Server 2008
Clinic 5938: Introducing Centralized Application Access in Windows Server 2008
Clinic 5939: Introducing Server Management in Windows Server 2008
Collection 6041: Upgrading Your Windows Server 2003 MCSE Technical Skills to Windows Server 2008
Get a head start on Windows Server 2008. Now is the time to upgrade your technical skills on Windows Server 2008 with Microsoft E-Learning Collection 6041, including access to virtual labs. Special limited time offer! Sign up for this collection now and get free registration for three upgrade collections on Networking, Active Directory, and Application Platform Services as they become available.
Course 6042: Installing and Managing Windows Server 2008 (Beta)
Course 6043: Implementing Active Directory Domain Services in Windows Server 2008 (Beta)
Course 6044: Implementing Active Directory Identities and Access in Windows Server 2008 (Beta)
Course 6045: Managing Internet Information Services 7.0 and Windows Media Server in Windows Server 2008 (Beta)
Course 6046: Implementing Network Infrastructure Services in Windows Server 2008 (Beta)
Course 6047: Implementing Network Access Protection in Windows Server 2008 (Beta)
Course 6048: Implementing Terminal Services in Windows Server 2008 (Beta)
Course 6049: Implementing a Storage Infrastructure in Windows Server 2008 (Beta)
Course 6050: Implementing Security in Windows Server 2008 (Beta)
Course 6051: Implementing High Availability and Virtualization in Windows Server 2008 (Beta)
Classroom training is designed to help you transition your skills and build expertise on Windows Server 2008 with world-class learning content. In this section, you will find both first-look courses as well as skills-transitioning courses.
First-look courses and hands-on labs
These 90-minute clinics and accompanying hands-on labs target specific scenarios on Windows Server 2008 to help you prepare for Windows Server 2008 certification.
Course 6400: First Look: Getting Started with Centralized Application Access in Windows Server 2008
Course 6401: First Look: Getting Started with Centralized Application Access in Windows Server 2008 Hands-On Lab
Course 6402: First Look: Getting Started with Branch Office Management in Windows Server 2008
Course 6403: First Look: Getting Started with Branch Office Management in Windows Server 2008 Hands-On Lab
Course 6404: First Look: Getting Started with High Availability in Windows Server 2008
Course 6405: First Look: Getting Started with High Availability in Windows Server 2008 Hands-On Lab
Course 6406: First Look: Getting Started with Security and Policy Control in Windows Server 2008
Course 6407: First Look: Getting Started with Security and Policy Control in Windows Server 2008 Hands-On Lab
Course 6408: First Look: Getting Started with Server Management in Windows Server 2008
Course 6409: First Look: Getting Started with Server Management in Windows Server 2008 Hands-On Lab
Course 6410: First Look: Getting Started with Server Virtualization in Windows Server 2008
Course 6411: First Look: Getting Started with Server Virtualization in Windows Server 2008 Hands-On Lab
Course 6412: First Look: Getting Started with Web and Applications Platform Technologies in Windows Server 2008
Course 6413: First Look: Getting Started with Web and Applications Platform Technologies in Windows Server 2008 Hands-On Lab
Skills transitioning courses
These three-day classroom sessions are designed to help Microsoft Certified Systems Administrators (MCSAs) and Microsoft Certified Systems Engineers (MCSEs) transition their skills from Windows Server 2003 to Windows Server 2008.
Course 6415: Updating Your Network Infrastructure Technology Skills to Windows Server 2008
Course 6416: Updating Your Active Directory Technology Skills to Windows Server 2008
Course 6417: Updating Your Application Platform Technology Skills to Windows Server 2008
Course 6418: Deploying Windows Server 2008
If you are interested in building a Learning Plan for 2008, here is the place.
Modifying Exchange Transport Agent
For administer transport agents, we must use the Set-TransportAgent cmdlet (Exchange Management Shell). For its details syntax and parameters, please refer here.
The following example shows how the priority of a sample agent for Exchange agent would be modified. You can use the Exchange Management Shell to modify the priority of an existing transport agent by using,
Set-TransportAgent "Sample Agent for Exchange" -Priority 2
To run the Set-TransportAgent cmdlet, the account you use must be delegated to: Exchange Server Administrator role and local Administrators group for the target server.
1) What do you meant by "MAPI table"?
2) How the values are stored and can be used in MAPI table?
3) In which way usage of MAPI tables are useful?
Take this case directly a client cannot access an attachment's PR_ATTACH_METHOD property by calling IMAPIProp::GetProps; it must always retrieve the attachment table of the message to which it is attached. PR_ATTACH_METHOD is a required column in all attachment tables.
One of my customer asked this question, "what is the Difference between Mailbox store & Public folder store objects in Active Directory & Exchange System Manager ?".
Yep, not only him, many of us want to know the same?
I found this wonderful article, which discusses the top support issues for the Microsoft Exchange 2000 & 2003 Server information stores.
This article lists references to Microsoft Knowledge Base articles that describe the issues that may occur when you use the Microsoft Exchange information stores. Additionally, this article lists references to Microsoft Knowledge Base articles that discuss how to troubleshoot issues that you may experience.This article does not provide a complete list of all the support issues for the Exchange information stores, but certainly it will be a eye opener or will fit into 'generic starter' soup!!
1) In general, by where Exchange Store event interfaces are implemented?
Exchange Store event interfaces are implemented in EXOLEDB.DLL and EXEVTSNK.TLB.
2) What're the unsupported Exchange store event interfaces?
When we program with Exchange store, certain event interfaces are not supported. It is recommended that they not be used in applications:
Here are some questions that are frequently asked by my customers whenever they try to access/enumerate Exchange Store:
1) Can you name some of the known URL's of users mailbox folders?
Calendar file://./backofficestorage/example.com/MBX/UserAlias/Calendar Contacts file://./backofficestorage/example.com/MBX/UserAlias/Contacts Drafts file://./backofficestorage/example.com/MBX/UserAlias/Drafts Inbox file://./backofficestorage/example.com/MBX/UserAlias/Inbox Journal file://./backofficestorage/example.com/MBX/UserAlias/Journal Notes file://./backofficestorage/example.com/MBX/UserAlias/Notes Outbox file://./backofficestorage/example.com/MBX/UserAlias/Outbox Sent Items file://./backofficestorage/example.com/MBX/UserAlias/Sent%20Items Tasks file://./backofficestorage/example.com/MBX/USerAlias/Tasks
2) What do you meant by "Public folder replication"?
Public folder replication is the process by which public folder content and the public folder hierarchy is replicated across multiple servers for efficiency and fault tolerance purposes.
3) What do you mean by "Exchange Store Schema"?
Exchange store schema consists of properties that define all resources in the store, including e-mail messages, appointments, folders, and contacts. It includes numerous predefined properties you can use in your applications.
4) Can we extend the "Exchange Store Schema"?
Yes, you can also extend the Exchange store schema by defining your own custom properties.
5) What is so called "Namespace" in "Exchange Store Schema"?
A namespace provides a unique name for every property in the Exchange store schema.
6) What is "DAV:Namespace"?
This namespaces defines properties for the WebDAV. It includes properties for general data access (such as DAV:href). Also it can be used for determining hierarchical information such as DAV:isfolder.
Exchange Server - Frequently Asked Questions
When we do Exchange programming with client and server versions of the Exchange Server Providers, MAPI32, EMSMDB, EMSABP and MSPST32 almost or always causes confusion. In this article, we'll discuss about the common terminologies:
MAPI will generally mean MAPI32.dll, or the APIs contained. It's an API, implemented largely in MAPI32.dll (Messaging Application Programming Interface, 32 bit build). By using this, developers implement a series of Providers. Providers come in three major types, Transport Providers, Message Store Providers, and Address Book Providers. Providers are DLLs that implement a specific pseudo COM API, such as IMessageStore, and the underlying required interfaces, such as IMAPIProp.
An empty profile gives a MAPI application no data access, so MAPI applications add Providers (also called Services) to the profile. A common thing for MAPI applications to do is add services for EMSMDB and EMSABP to a profile, granting the ability to access data from Exchange Server. Providers do all of the actual work in MAPI. When you submit a message, although the call might pass through MAPI32, it is EMSMDB (or your provider) that does the actual work for sending. When saving a message, it is not MAPI32 that saved the message; it's the message store provider (usually EMSMDB for Exchange Server). When you resolve a recipient, it is not MAPI32 that searches for the user in the address book. It is the Address Book Provider, implementing the IAddrBook interface (probably EMSABP).
Collaboration Data Objects (CDO) refers to CDO.DLL, not CDONTS, CDOSRV, CDOSYS, CDOEX, EXCDO, or CDOEXM. CDO and Outlook are both MAPI applications, meaning that they use MAPI APIs to access their data and, therefore, the underlying providers. CDO and Outlook share a common set of Properties that, when taken together, define different classes of messages and different functionality. This works similar to the schema in a database; however, MAPI32 does not implement the storage. The Message Store Provider does. In the case of Exchange Server, this provider is EMSMDB, and Exchange Server is mostly agnostic about the semantics of the data that applications choose to store. Exchange Server 5.5 has almost no knowledge of individual named property meanings. Exchange 2000 Server and Exchange Server 2003 are considerably more aware of the significance of particular named properties on different message classes, in particular, calendar items. This logic is implemented in EXOLEDB and EXCDO. In general, it is up to users of a particular set of properties to agree on what those properties mean and how they are manipulated.
CDO implements an API to manipulate sets of properties together to accomplish tasks, such as scheduling a meeting. Outlook also implements APIs to manipulate sets of properties, and does presentation of that data to the end user. If CDO and Outlook don't agree on what particular properties mean, or on the mechanisms used to control processing logic (for instance, when an appointment has been updated), potential for problems interoperating between Outlook and CDO exist. Although Outlook continues to be updated and expanded with every version, CDO.dll is more or less static at the same level of functionality it has possessed for years. Newer libraries for manipulating calendar data, such as CDOEX, are considerably more up to date.
EMSMDB refers to the Exchange transport provider, EMSMDB32. One example of a provider is EMSMDB2, the "Electronic Messaging System Microsoft Data Base, 32 bit build" provider. EMSMDB implements both a transport and a message store and, as such, is a dual provider.The transport is the ability to submit messages to Exchange Server; the message store is the ability to read (and possible write) messages to an Exchange store process.
EMSABP refers to the Exchange address book provider, EMSABP32. The other common provider involved with Exchange Server is EMSABP, which is an Address Book Provider (Electronic Messaging System Address Book Provider, 32 bit build). EMSABP implements IAddrBook and allows access to the Exchange global address list through Name Service Provider Interface (NSPI).
1) In Exchange Store, how to get all properties for a particular item?
To get all the properties for a particular item, bind to it directly by using various technologies like Activex Data Objects, Collaboration Data Objects, OLE DB, or through WebDAV.
2) So, can i get all properties for all items using SELECT * ?
This is one of the frequently asked questions from our customers whenever they try to access any of the Exchange Store. But we can't get all properties for all items. Because each item in the folder could have different properties in it.
3) So, what will we get when we make use of SELECT * ?
When running the SELECT * statement on a folder, we can get only the list of properties. These properties are defined by the schema for the folder.
4) What're the properties that cannot be searched?
The following properties cannot be searched because their values are only calculated when used and are not stored in the Exchange store.
DAV:getetag, DAV:href, DAV:lockdiscovery, DAV:parentname, DAV:resourcetype, DAV:searchrequesthttp://schemas.microsoft.com/exchange/content-hrefhttp://schemas.microsoft.com/exchange/ntsecuritydescriptorhttp://schemas.microsoft.com/exchange/oof-statehttp://schemas.microsoft.com/exchange/publicfolderemailaddresshttp://schemas.microsoft.com/repl/repl-uidhttp://schemas.microsoft.com/repl/resourcetagurn:schemas:contacts:proxyaddresses urn:schemas:httpmail:htmldescriptionurn:schemas:httpmail:subjecturn:schemas:mailheader:subjecturn:schemas-microsoft-com:exch-data:baseschemaurn:schemas-microsoft-com:exch-data:schema-collection-refAll properties that contain URL values, such as DAV:href, are calculated and UTF-8 encoded. Even this list is not comprehensive and is subject to change.
5) What're the SQL grammar, functions and functionality are not supported?
AVG, CONVERT (use CAST), COUNT, CREATE VIEW, DATASOURCE, DELETE, DROP INDEX, INSERT, JOINS, MAX, MIN, Revision ID header (ignored), Scope aliases, SELECT DISTINCT, SET, Scope revision numbers, SHAPE, SUM, UNKNOWN, UPDATE, Wildcard expressions (use CONTAINS, FREETEXT, and LIKE)
This list is not comprehensive and is subject to change.
6) When i try to search or index certain properties, it throws errors or getting no results?
In Exchange store calculates some of the properties but does not store those values/entires. But some of these properties are cached, however, and can be searched or indexed.
7) What is the property needs to set to access hidden items from MAPI Clients?
To hide items that are accessible to MAPI clients (like Outlook), you must set the http://schemas.microsoft.com/mapi/proptag/x67aa000b property to true when the item is created.
Note: If the flag is not set when the item is first created, you cannot hide it later from MAPI clients.
Please find the Outlook 2007 PIA documentation available @ online
Run the following command in Exchange Management shell,
Find the small article which talks about how to configure the pickup directory in Exchange Server 2007.
Exchange Server 2007 & configuring Pickup directory:
Its' quite interesting to configure the pickup directory in Exchange Server 2007 environment. As we know that the Pickup directory is used by administrators for mail flow testing, or by applications that must create and submit their own messages. If we copy the correctly formatted e-mail message files to the Pickup directory are submitted for delivery.
Some points to remember:
By default, the Pickup directory is located at C:\Program Files\Microsoft\Exchange Server\TransportRoles\Pickup. The directory must be local to the Exchange 2007 computer.
By default, the Pickup directory exists on every Exchange 2007 computer that has the Hub Transport server role or the Edge Transport server role installed.
To configure the Pickup directory location, we can make use of "Set-TransportServer" cmdlet. This cmdlet lets you configure any transport configuration parameter on a Microsoft Exchange Server 2007 Hub Transport or Edge transport server.
The Set-TransportServer cmdlet manipulates the following groups of parameters:
Note: The Set-TransportServer cmdlet does not require the Identity parameter to be specified when you run the command. When you use the Set-TransportServer command, you can set any number of parameters at the same time.
Configuring the Pickup Directory Location:
To set the Pickup directory to C:\Pickup Directory on an Exchange 2007 computer named Exchangesvr, run the following command:
Note: Setting the value of the PickupDirectoryPath parameter to $null disables the Pickup directory. The directory that is specified by the PickupDirectoryPath parameter and the ReplayDirectoryPath parameter can't be the same.
Still issues or not successful to configure Pickup directory location, you can create the new Pickup directory and apply the correct permissions to it before you use the PickupDirectoryPath parameter with the Set-TransportServer cmdlet.
Issue with TNEF:
The use of TNEF is commonly affected by settings in Outlook that are referred to as "Microsoft Outlook Rich Text Format." Rich Text Format and TNEF are not exactly the same, but they are closely related.A TNEF-encoded message contains a plain text version of the message, and a binary attachment that "packages" various other parts of the original message. In most cases, the binary attachment will be named Winmail.dat, and may include:
The formatted text version of the message (font information, colors, and such)
OLE objects (embedded pictures, embedded Office documents, and such)
Special Outlook features (custom forms, voting buttons, meeting requests, and such)
Regular file attachments that were added to the original message
In addition to the information listed above, the path to your personal folders file (PST) file and your logon name are embedded in the winmail.dat file. Although this data is not explicitly exposed to the recipient, if the recipient opens the winmail.dat file for editing in a binary or text editor, he can see the path and logon name. Note that no password information is revealed. To ensure that the path to your PST file or your logon name is not included in the winmail.dat attachment, use the steps in this article to send mail that does not include winmail.dat.Some Outlook features require TNEF encoding to be understood correctly by an Internet e-mail recipient who also uses Outlook. For example, when you send a message with voting buttons to a recipient over the Internet, if TNEF is not enabled for that recipient, the voting buttons will not be received. Alternatively, for sending messages with regular file attachments, TNEF is not needed. If you are sending e-mail with file attachments to a recipient who does not use Outlook or the Exchange Client, you should manually choose to use a mail format that does not require TNEF (such as plain text). By not sending TNEF messages, the recipient will be able to view and save the attachments as expected.
Issues when Send & Receiving mails:
When a message containing TNEF information is received by a mail client that does not understand TNEF, there are three common results:
The plain text version of the message is received and it contains an attachment named Winmail.dat. The Winmail.dat attachment does not contain any useful information when opened since it is in the special TNEF format.
The plain text version of the message is received and it contains an attachment with a generic name such as ATT00008.dat or ATT00005.eml. In this case the client is unable to recognize the TNEF part of the message, and is unable to recognize the Winmail.dat file name, so it creates a file name to hold the TNEF information.
The plain text version of the message is received and the client ignores the Winmail.dat attachment. This is the behavior found in Microsoft Outlook Express. Outlook Express does not understand TNEF, but it does know to ignore TNEF information. The result is a plain text message.
In addition to the receiving client, it is not uncommon for a mail server to strip out TNEF information from mail messages as it delivers them. If a server option to remove TNEF is turned on, clients will always receive a plain text version of the message. Microsoft Exchange Server is an example of a mail server application that has the option to remove TNEF from messages.
Internet Standards - Message Encoding:
The Internet standards for encoding messages such as Multipart Internet Mail Extensions (MIME) and UUENCODE are used independently of TNEF. TNEF can exist in a MIME-encoded message as a MIME body part of type "application/ms-tnef," or in a UUENCODED message as an attachment named Winmail.dat.When a TNEF message is sent using MIME, an entry similar to the following is added to the message:
------ =_NextPart_000_01BA6275.348C1000 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IisSAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAENgAQAAgAAAAEAAQ ABBJAGAEgBAAABAAAADAAAAAMAADACAAAACwAPDgAAAAACAf8PAQAAAHQAAAAAAAAAtTvC [. . .]
Alternatively, if a TNEF message is sent using UUENCODE, information similar to the following is added to the bottom of the message:
begin 600 WINMAIL.DAT M>)\^(C<.`0:0" `$```````!``$``0>0!@`(````Y 0```````#H``$%@ ,` M#@```,L'" `$``<`)P`O``4`0 $!"8 !`"$````S,S5$,C,W,#%"0T-#13$ [. . .]
In either case, the TNEF encoding is sent to the recipient and must be understood by the receiving client to correctly display the encapsulated information.
For more information, please read this article
TNEF & Winmail.dat
Exchange Server 2003 uses transport neutral encapsulation format (TNEF) to convert MAPI messages to RFC 822 format. TNEF appears on a message as a MIME attachment of type application/ms-tnef. The attachment is called Winmail.dat. It contains the full message content and any attached files. Only MAPI clients, such as Outlook, are able to decode the Winmail.dat attachment. Non-MAPI clients are unable to decode TNEF and might show Winmail.dat as a typical, but useless file.
Note: Recipients with mailboxes on an Exchange server, who use Internet clients to access their messages, are not considered non-MAPI recipients. This is because the Exchange store that hosts the mailboxes can produce the necessary RFC 822 content in non-MAPI format when users download MAPI messages from their Inboxes using a POP3 or an IMAP4 client. There are several possible Exchange-to-Exchange transfer scenarios that require MAPI to RFC 822 conversion:
Note: Within a routing group, Exchange Server 2003 always uses S/TNEF, because in all remote delivery cases, the message is guaranteed to take either an SMTP hop directly to a server running Exchange 2000 Server or Exchange Server 2003 or go to the Exchange MTA. Exchange 2000 Server and Exchange Server 2003 support binary MIME. On the other hand, if the message is passed to the Exchange MTA for delivery to a server running Exchange Server 5.5 through RPCs, message conversion is not required, because the RFC 822 format is not used.
Note: Non-MAPI recipients typically prefer to receive a message in plain text or HTML without TNEF, because their clients cannot decode the Winmail.dat file that includes the message and all attachments. TNEF encapsulation prevents non-MAPI clients from accessing attachments. Non-Microsoft tools, such as EPOC WMDecode for Windows, might be able to extract attachments from Winmail.dat files.
You can control the TNEF format behavior for sending messages by adding the following registry key. The number nn represents the virtual server instance for this machine.
HKey_Local_Machine\Software\Microsoft\Exchange\StoreDriver\Exchange\ nn \EnableTnef
A value of 0x0 disables TNEF, and messages are generated without using TNEF. A value of 0x1 will generate a message using legacy TNEF when S/TNEF would ordinarily be generated. A value of 0x2 has no effect, as that is the default behavior.
I have found this wonderful piece of code(Visual Basic 6.0), used to create mailbox store.
'//////////////////////////////////////////////////////////////////////////////////'// Name: CreateNewMailboxStoreDB'// Purpose: To create a new Mailbox Store (MDB) with a given name'// Input: strMDBName = contains the name of the new MDB to be created'// blnMount = True if the new MDB will be mounted after creation or False if the new MDB will not be mounted'// strComputerName = contains the name of the Exchange 2000 server'// strSGName (Optional) = contains the name of the storage group to create the new MDB in; if it is empty then the new MDB will be created in the'// default Storage Group'// strMDBUrl (Optional ByRef) = contains the URL to the new MDB created;'//'//////////////////////////////////////////////////////////////////////////////////
Public Sub CreateNewMailboxStoreDB(ByVal strMDBName As String, ByVal strComputerName As String, Optional ByVal blnMount As Boolean, _ Optional ByVal strSGName As String, Optional ByRef strMDBUrl As String)
Dim iServer As New CDOEXM.ExchangeServer Dim iMDB As New CDOEXM.MailboxStoreDB Dim arrStGroup() As Variant Dim i As Integer Dim strTemp As String
' Set the name of the MailboxStoreDB iMDB.Name = strMDBName
' Bind to the Exchange Server iServer.DataSource.Open strComputerName
' Start to build the URL to the MailboxStoreDB - first part strTemp = "LDAP://" & iServer.DirectoryServer & "/" & "cn=" & strMDBName & ","
' Set variant array to the ExchangeServer.StorageGroups arrStGroup = iServer.StorageGroups
' Look in the StorageGroups array if the StorageGroup with strSGName exists If strSGName = "" Then ' Finish to build the URL to the MailboxStoreDB - add last part strMDBUrl = strTemp & iServer.StorageGroups(0) Else For i = 0 To UBound(arrStGroup) If InStr(1, UCase(arrStGroup(i)), UCase(strSGName)) <> 0 Then strMDBUrl = arrStGroup(i) End If Next If strMDBUrl <> "" Then ' Finish to build the URL to the MailboxStoreDB - add last part strMDBUrl = strTemp & strMDBUrl End If End If
' Save the New MailboxStoreDB iMDB.DataSource.SaveTo strMDBUrl
' Mount the MailboxStoreDB if blnMount is True If blnMount = True Then iMDB.Mount End If
' Cleanup Set iServer = Nothing Set iMDB = Nothing
Microsoft have done changes in Exchange Server 2003 SP2. It includes new DLLs for several key APIs, and includes some key changes in behavior. While Exchange Server 2003 SP2 does not include any changes to the objects, classes, and interfaces, it does introduce key differences in how some of the APIs work.
The following API libraries that ship with Exchange Server 2003 or with Microsoft Outlook 2003 have been updated in Exchange Server 2003 SP2:
Important: These changes only affect the libraries that ship with Exchange Server 2003. The libraries that ship with Microsoft Windows XP, Microsoft Windows 2000 Server, Microsoft Windows Server 2003, and Microsoft Exchange 2000 Server are not affected by these changes.
For more information, please find the detailed article available
Do you know?
MS Exchange 2000 Server application development-related technologies and features were changed in MS Exchange Server 2003. Some technologies were enhanced, while others were removed, or are not supported in specific scenarios.
Exchange 2000 Technologies not Included with Exchange 2003:
More information is available at this following article, please click here
Exchange Management Shell: