Implementing an email discovery,
compliance, archiving, and retention (DCAR) solution is similar to remodeling a house. You need a “blueprint” (plan) that provides detailed
instructions for the “remodeling”
(design, components, and implementation steps of the DCAR solution).
You also need to be able to translate
the plan into reality—as a contractor
would on a remodeling job—within
the budget and schedule you've allotted for the project. Like a remodeling,
implementing a DCAR solution might
disrupt your current messaging
scheme somewhat, but in the end it
will make your job as an Exchange
administrator easier and add functionality to your messaging system.
Fortunately, Exchange provides some
built-in features—message journaling, backup and restore APIs, and message and transport security—that
provide a framework for building a
DCAR solution. We'll examine those
features as well as some related technologies in Exchange, such as event
sinks, protocol logs, and message
tracking, and explore how each fits
into a DCAR strategy. And in the Web exclusive sidebar “Third-Party Products in an Exchange DCAR Solution,”
we'll look at
some important DCAR functions that
you'll need to obtain through third-party products and what to consider
when choosing such products. . . .
Register
