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?
Sent Items file://./backofficestorage/example.com/MBX/UserAlias/Sent%20Items
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.
- When multiple public folder databases that are located on separate servers support a single public folder tree, Microsoft Exchange uses public folder replication to keep the databases synchronized.
- Public folder content exists only in Exchange stores that are configured to have a replica of a specific folder.
- Content and hierarchy information are replicated separately.
- Each public folder database retains a copy of the hierarchy, which includes lists of the other public folder databases that retain content replicas of each folder.
- Content replicas exist only on the public folder databases that you specify
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.
- For example, the namespaces urn:schemas:httpmail: and urn:schemas:mailheader: both contain properties named From.
- By prefacing the name of a property with the correct namespace, you can avoid collisions between properties with similar names.
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.