DRAG DROP
###BeginCaseStudy###
Case Study: 3
Litware, Inc
Overview
Litware, Inc., is a manufacturing company located in North America.
The company has a main office and two branch offices. The main office is located in Chicago.
The branch offices are located in Baltimore and Los Angeles.
Existing Environment
Active Directory Environment
The network contains one Active Directory forest named litwareinc.com. Each office is
configured as an Active Directory site.
All domain controllers in the Los Angeles office run Windows Server 2008 R2. All domain
controllers in the Chicago office run Windows Server 2003 Service Pack 1 (SP1). All domain
controllers in the Baltimore office run Windows Server 2012.
All of the FSMO roles are located on a domain controller in the Baltimore office. All of the
domain controllers are configured as global catalog servers.
You have a distribution group for each department. The distribution groups contain all of
the users in each respective department.

Network Infrastructure
The servers in each office are configured as shown in the following table.

The Baltimore and Chicago offices have independent Internet connections. Internet
connectivity for the Los Angeles office is provided through Chicago.
Users frequently send large email messages to other users in the company. Recently, you
increased the maximum message size to 50 MB.
Planned Changes
The company plans to deploy a new Exchange Server 2013 infrastructure that will contain
two Clients Access servers and two Mailbox servers in the Chicago office. The servers will be
configured as shown in the following table.

All client connections to the Exchange Server organization will be routed through a
hardware load balancer. The name client.litwareinc.com will point to the virtual IP address
of the hardware load balancer.
Once the transition to Exchange Server 2013 in the Chicago office is complete, all mail flow
to and from the Internet will be managed centrally through that office by using a Send
connector that has the following configurations:
• Connector name: CH-to-Internet
• Address space: *
• Source servers: CH-EX2, CH-EX3
• Cost: 10
###EndCaseStudy###

You need to identify which external namespaces must be used for the Exchange servers in each
office. Which external namespaces should you identify for each office?
To answer, drag the appropriate namespace to the correct office in the answer area. Each
namespace may be used once, more than once, or not at all. Additionally, you may need to drag the
split bar between panes or scroll to view content.

Answer:

Explanation:

This scenario has the following advantages:
Only one or very few DNS records need to be managed.
Only one or very few certificates are required for your Exchange organization.
All users use the same URL to access Exchange server.
The disadvantage of this model is that most users will access their mailboxes using proxying, thus
accessing their data might be slower across latent WAN links.
To configure this namespace model, you need to configure the ExternalURL option of the Client
Access server(s) at one site, and make sure that the ExternalURL settings on all the other sites are
configured to $Null. This configuration ensures that the Client Access server does not redirect the
connection to the target Client Access server, but instead proxies it. Redirect means that the Client
Access server forwards the connection to the target Client Access server; proxy means that the
Client Access server contacts the target Client Access server and retrieves the data for the
connection.
Autodiscover.domainname
In order for Exchange 2007/2010/2013 and Outlook 2007/2010/2013 to function properly, you must
have a special DNS record set up for your domain name which points to the Intermediate
Autodiscover server.
You need to set up the Autodiscover record for your domain name to have the following features:
Outlook 2007/2010/2013 setup using Autodiscovery

Outlook 2011 for Mac and Entourage EWS setup using Autodiscovery
Free/Busy information in your calendar
Out of office autoresponse messages setup in Outlook.
Note: Without the Autodiscover record you can use Outlook Web Access to set up automatic replies.
Proper syncing of Offline Address Book
Folder Sharing with sending out the Sharing invitation. Read the Knowledge Base article on How Do I
Share
(Let Others See) My Outlook Folders? for more information.
Load Balancing (Hardware and Virtual Load Balancing)
You need to have an understanding of how the load balancer fits in your environment. Typically
clients will connect to it for web services, like OWA, and also through Outlook via MAPI, using a
Client Access Array as illustrated by this simplified diagram:
In addition to planning your environment, you’ll also need some other information for the load
balancer setup:
IP address for management
IP address for the virtual load balancer interface, in the same subnet
DNS and NTP server addresses
Client Access Server IP addresses
Network Access from the virtual load balancer interface to the following TCP ports on the Client
Access
Servers:
80 and 443 for HTTP/HTTPS
135, 139, 6001-6004,60000 and 60001 for RPC Client Access
Note that if you’re testing this in a perimeter network, you only need ports 80 and 443 open for
external access to Exchange servers.