###BeginCaseStudy###
Case Study: 1
Contoso Ltd
Company Overview
Contoso, Ltd. is a wholesale travel agency.
Physical Locations
The company has offices in New York and Seattle. Each office has a call center. All IT staff
and help desk staff are located in the New York office.
Existing Environment
Contoso has a single domain named contoso.com. An Active Directory site exists for each
office. The sites connect to each other by using a high-speed WAN link. The WAN link has
an average utilization rate of 90 percent during business hours. The domain contains three
domain controllers. The domain controllers are configured as shown in the following table.
The network has an Exchange Server 2010 Service Pack 1 (SPl) organization that contains
four servers. The servers are configured as shown in the following table.
Each mailbox database is 400 GB.
All of the servers have the following hardware configurations:
• 64 GB of RAM
• One dual quad-core Intel Xeon processor
• Two l-gigabit per second Ethernet network adapters
• One RAID 10 disk array that has 12 300-GB, 15,000-RPM SAS disks for data
• one RAID 1 disk array that has two 73-GB, 10,000-RPM SAS disks for program files
• One RAID 1 disk array that has two 73-GB, 10,000-RPM SAS disks for the operating system
Requirements
Business Goals
Contoso has the following general requirements that must be considered for all technology
deployments:
• Minimize costs whenever possible.
• Minimize administrative effort whenever possible.
• Minimize traffic on the WAN link between the offices.
Planned Changes
Contoso acquires a company named Margie’s Travel. Margie’s Travel has 3,000 employees.
Margie’s Travel has the following email infrastructure:
• A call center, where 200 employees work
• UNIX-based email hosts that users access by using POP3 and SMTP
• Three departments that use the SMTP domains of margiestravel.com,
east.margiestravel.com, and blueyonderairlinesxam. Users are assigned only one email
address that uses the SMTP domain of their department
You plan to deploy a new Exchange Server 2010 SP1 organization to Margie’s Travel. The
new email infrastructure must meet the following implementation requirements:
• All employees must have access to their mailbox if a single server fails.
• Call center employees must use windows Internet Explorer 8 to access their mailbox.
• The administration of the Margie’s Travel Exchange organization must be performed by a
dedicated team.
• Call center employees must be prevented from accessing the calendar or journal features of
Outlook Web App.
• All employees who do not work in the call center must have access to all of the Outlook
web App features.
• All email messages sent to recipients outside of Margie’s Travel must have a return address
in the [email protected] format.
The new email infrastructure for Margie’s Travel must meet the following security
requirements:
• Contoso administrators must be prevented from viewing or modifying the settings of the
mailboxes of Margie’s Travel users.
• All inbound and outbound Internet email to and from the Margie’s Travel domains must be
routed through the Hub Transport servers of Contoso.
• All email messages that contain confidential customer information must be encrypted
automatically while in transit and the recipients of the messages must be prevented from
forwarding them to other users.
Compliance Requirements
Contoso must meet the following compliance requirements:
• Each email message sent by an attorney from the Contoso legal department must be
approved by the manager of the legal department.
• Attorneys must be able to classify email messages as “attorney-client privileged”.
• All messages classified as “attorney-client privileged” must contain a legal disclaimer
automatically.
User Requirements
All users who have a portable computer use Microsoft Outlook 2010 when they work online
and offline. When the users work offline, they must be able to read existing email messages
and create new email messages. Users who have a large mailbox must minimize the amount
of hard disk space used by the mailbox on their portable computer.
###EndCaseStudy###
You need to recommend changes to the Exchange organization of Contoso. The solution must meet
the compliance requirements and the business goals of Contoso. What should you include in the
recommendation? (Choose all that apply.)
A.
journal rules
B.
message classification templates
C.
Hub Transport rules
D.
Edge Transport rules
E.
Secure MIME
F.
moderated recipients
Explanation:
Message classifications are a Microsoft Exchange Server 2010 and Microsoft Office Outlook 2007
feature intended to help organizations comply with their e-mail policies and regulatory
responsibilities. When a message is classified, the message contains specific metadata that describes
the intended use or audience of the message. Outlook 2007 or Microsoft Office Outlook Web App
may act on this metadata by displaying a user-friendly description of the classification to senders and
receivers of a classified message. In Exchange 2010, the Microsoft Exchange Transport service may
act on the metadata if there’s a transport rule that meets specific criteria that you have configured.
The following list provides a brief description of some of the message classification fields that you
can set:
Display name:
This property specifies the display name for the message classification instance. The display name
appears in the Permission menu in Outlook 2007 and Outlook Web App and is used by Outlook and
Outlook Web App users to select the appropriate message classification before a message is sent.
The display name is also displayed in the recipient description that appears in the InfoBar in an
Outlook message. The parameter name for this property is DisplayName.
Sender description:
This property explains to the sender what the message classification is intended to achieve. The text
that you enter for this field is used by Outlook and Outlook Web App users to select the appropriate
message classification before a message is sent. The parameter name for this property is
SenderDescription.
Recipient description:
This property explains to the recipient what the message classification was intended to achieve. The
text that you enter for this field is viewed by Outlook and Outlook Web App users when they receive
a message that has this message classification. The parameter name for this property is
RecipientDescription.
Locale:
This field specifies a culture code to create a locale-specific version of the message classification. For
more information about the locale field, see “Localizing Message Classification Instances for
Different Languages and Locales” later in this topic. The parameter name for this property is Locale.After Outlook 2007 is enabled to accept the default message classifications, users can apply message
classification to messages that they send. Senders see the sender description in the InfoBar in
Outlook 2007.
By using the Exchange Management Shell, you can customize the sender description for each
message classification and locale.
Note:
Outlook Web App requires no special configuration to display or use message classifications.
Three message classifications are enabled in Exchange 2010 by default:
Attachment Removed This classification notifies recipients when attachments have been removed
from the message.
Originator Requested Alternate Recipient Mail This classification notifies recipients that the message
has been redirected from delivery to the original addressed recipient.
Partner Mail This classification notifies recipients that the message was encrypted and delivered
through a secure connector.
When you configure a recipient for moderation, all messages sent to that recipient are subject to
approval by the designated moderators. For more information about how Exchange 2010 handles
recipient moderation, see Understanding Moderated Transport.
Automatic Protection Using Transport Protection Rules
Messages containing business critical information or PII can be identified by using a combination of
transport rule conditions, including regular expressions to identify text patterns such as social
security numbers.
Organizations require different levels of protection for sensitive information. Some information may
be restricted to employees, contractors, or partners; while other information may be restricted only
to full-time employees.
The desired level of protection can be applied to messages by applying an appropriate rights policy
template.
For example, users may mark messages or e-mail attachments as Company Confidential. As
illustrated in the following figure, you can create a transport protection rule to inspect message
content for the words “Company Confidential”, and automatically IRM-protect the message.
Create a transport protection rule
For more information about creating transport rules to enforce rights protection, see Create a
Transport Protection Rule.
