###BeginCaseStudy###
Case Study: 2
A Datum Overview
General Overview
A Datum Corporation is a pet supply company that has stores across North America.
A Datum has an Exchange Server 2007 organization. A. Datum plans to migrate to
Exchange Server 2013.
Physical Locations
A Datum has five locations. The locations are configured as shown in the following table.
Existing Environment
Network Infrastructure
All of the locations connect to the each other by using a WAN link. The New York, Toronto,
and Chicago locations connect directly to the Internet. All client computers run Windows 7
and Office 2010. All servers run Windows Server 2008.
Active Directory Environment
The network contains an Active Directory domain named adatum.local. Adatum.local is the
corporate domain based in the United States. The network contains a domain named
Canada.adatum.local. Canada.adatum.local is the domain for the stores in Canada. Each
location is configured as an Active Directory site. The forest functional level is Windows
Server 2008. The main office and both of the distribution centers each has two domain
controllers for their respective domain. All of the other locations have one domain controller
for their respective domain. All of the domain controllers are global catalog servers.
Exchange Infrastructure
The main office and the distribution centers each have three servers that have Exchange
Server 2007 installed. The servers have the following configurations:
• Two of the servers have cluster continuous replication (CCR) deployed
• One of the servers has the Client Access server role and the Hub Transport server role
installed
Each store contains a server that has Exchange Server 2007 installed. Each server has
mailboxes for active users and mailboxes for inactive users. Each server has approximately
50 mailboxes. Remote users access Outlook Web Access by using a namespace of
mail.adatum.com, which resolves to the Client Access server in the New York office.
Requirements
Planned Changes
The company plans to implement the following changes:
• Migrate all of the mailboxes in the main office and the distribution centers to
Exchange Server 2013.
• Integrate a new telephone system to the Exchange Server 2013 organization.
• Deploy a standalone certification authority (CA) that will be used to issue all of the
certificates for the messaging infrastructure.
Technical Requirements
The company identifies the following technical requirements:
• Hardware costs must be minimized whenever possible.
• The impact on end users if a site fails must be minimized.
• Voice mail traffic between the telephone system and the Exchange Server
environment must be encrypted.
• Each user must be able to access the internal resources and their mailbox by using a
single user account.
Compliance Requirements
After a security review, the company identifies the following compliance requirements for
the new Exchange Server environment:
• All administrative changes made to the mailboxes must be tracked.
• The legal department must be able to search for messages in all of the mailboxes.
• Users must be prevented from sending email during an upcoming statutory holiday.
• All store managers must be prevented from permanently deleting email messages
from their Inbox.
• All email messages must be archived for a minimum of five years to meet regulatory
requirements.
• Management occasionally sends the staff internal memos that contain confidential
information, such as sales figures. The memos must be protected so that unauthorized users
cannot read the memos and internal users cannot forward the memos to external recipients.
• The users in the research department must be able to send email to anyone in the
organization, but only the members of a group named Execs must be able to send email to the
research users. All other users must be notified that email sent to the research users will
remain undelivered.
###EndCaseStudy###
You need to recommend a solution to ensure that during the planned migrations, all
Autodiscover requests are processed by the Exchange Server 2013 Client Access servers.
What should you recommend?
A.
On the Exchange Server 2007 Client Access servers, modify the
AutodiscoverServiceInternalURI.
B.
On the Exchange Server 2007 Client Access servers, modify the ExternalURL value of
the Autodiscover virtual directory.
C.
On the Exchange Server 2013 Client Access servers, modify the ExternalURL value of
the Autodiscover virtual directory.
D.
on the Exchange Server 2013 Client Access servers, modify the
AutodiscoverServiceInternalURI.
C
I would actually think A is the answer.
Back in the Exchange 2010 days, if there is Exchange 2007 co-exist, what I found out in a production environment is that when Outlook queries SCP objects, the list of SCP objects are returned in a particular order.
Now I can’t remember exactly what determines the actual order of those SCP objects, but one thing I did notice is that the list doesn’t necessarily have the “later” version of Exchange CAS servers on the top.
When Outlook processes this list, it always processes from top to bottom, and it will always use the URL defined by the InternalURI parameter.
So the problem we had back then was Outlook would always pop up a certificate error and we found the certificate reported by Outlook contained Exchange 2007’s name (which is a legancy.contoso.com name) rather than Exchange 2010’s name (which is using mail.contoso.com name), and we used Set-ClientAccessServer and set the internal uri to $null to address the issue.
So I am think this is a similar one here.
A is right