In today’s world, email is an indispensable communications tool that almost no organization can do without. Whether it is an email thread between employees, a complaint from a customer, a product launch announcement, or a confidential email, corporate email is a business record which needs to be protected. Not only are these emails the lifeblood of the organization but at some point they could be requested for legal or compliance reasons. In some cases, organizations have to retain email for a number of years placing additional burdens on their email infrastructure. This is why a growing number of organizations are investing in an email archiving solution – saving a copy of every email without affecting the message storage on the email server.

Continue at Curu.ca

With Exchange 2010 Service Pack 1, you may find that performing a search via Outlook Web App (OWA) results in an error message, “The action couldn’t be completed. Try again later.” Additionally, Outlook clients operating in Online Mode can no longer search for attachments or embedded emails.

When this issue occurs, you will see the following events in the application log:

Log Name: Application
Source: MSExchangeIS Mailbox Store
Event ID: 9877
Task Category: Content Indexing
Level: Error
Keywords: Classic
Description:
Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.Mailbox Database: Mailbox Database 1 Error Code: 0x80043629

Log Name: Application
Source: MSExchangeIS Mailbox Store
Event ID: 9842
Task Category: Content Indexing
Level: Error
Keywords: Classic
Description:
Function CISearch::EcGetRowsetAndAccessor detected that content indexing was disabled for database '' because of error '0x80041820' from MSSearch.

Cmdlet extension agents are new components in Exchange 2010 that are called by Exchange 2010 cmdlets, when they are run. It is used to extend the functionality of Exchange 2010 cmdlets by running a script or set of code after the Exchange cmdlet has run. For example, you can run a set of configurations after a new mailbox has been created, basically calling the scripting agent to run a code after the New-Mailbox cmdlet completes. Scripting agent is one of the seven cmdlet extension agents available in Exchange 2010 and is the one that is disabled by default.

Let's say that you are in charge of a large Exchange organization that is distributed across multiple locations. You have administrators on your messaging team that are located in multiple cities, and they will be delegated tasks like managing recipients and creating mailbox databases. You need to implement a naming convention for mailbox databases, and you want to ensure that databases are only created using a predefined naming scheme, such as SEA-DB-01, or PHX-DB-01. This is a great use case for the scripting agent validation API.