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 are planning the upgrade to Exchange Server 2013.
You plan to perform the following tasks:
• Identify the number of email messages sent and received by the users in the current
Exchange Server organization.
• Identify how many IOPS are required to provide adequate access to mailboxes for all of the
users in the planned organization.
• Validate that all of the planned servers will meet the IOPS requirements of the planned
organization.
You need to identify which tool must be used to achieve each task.
Which tools should you identify?
To answer, drag the appropriate tool to the correct task in the answer area. Each tool 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:

Box 1: Microsoft Exchange Server Profile Analyzer
Box 2: Exchange Mailbox Server Role Requirements Calculator
Box 3: Microsoft Exchange Server JetStress 2010
Exchange Mailbox Server Role Requirements Calculator
Exchange 2010 Product
http://blogs.technet.com/b/exchange/archive/2009/11/09/3408737.aspx
(Exchange 2013 Server Role Requirements Calculator
Yes, this is no longer a Mailbox server role calculator; this calculator includes recommendations on
sizing Client Access servers too!)
After you have determined the design you would like to implement, you can follow the steps in the
Exchange 2010 Mailbox Server Role Design Example article within the Exchange 2010 Online Help to
calculate your solution’s CPU, memory, and storage requirements, or you can leverage the Exchange
2010 Mailbox Server Role Requirements Calculator.
The calculator is broken out into the following sections (worksheets):
Input
Role Requirements
Activation Scenarios
Distribution
LUN Requirements
Backup Requirements
Log Replication Requirements
Storage Design

Based on the above input factors the calculator will recommend the following architecture, broken
down into four sections:
Environment Configuration
Active Database Copy Configuration
Server Configuration
Log, Disk Space, and IO Requirements

Microsoft Exchange Server Deployment Assistant
The Exchange Server Deployment Assistant is a web-based tool that asks you a few questions about
your
current environment and then generates a custom step-by-step checklist that will help you deploy
Exchange.
The Exchange Server 2013 Deployment Assistant is available for the following scenarios. More
scenarios will
be added on a continuous basis.
On-premises deployments
New installation of Exchange Server 2013

Upgrade from Exchange 2010 to Exchange 2013
Upgrade from Exchange 2007 to Exchange 2013
Upgrade from mixed Exchange 2007 and Exchange 2010 to Exchange 2013
Hybrid deployments
(On-premises + Cloud)
Exchange 2013 on-premises with Exchange Online
Exchange 2010 on-premises with Exchange Online
Exchange 2007 on-premises with Exchange Online
Cloud-only deployments
Understand your options for migrating email to Exchange Online and Microsoft Office 365

Microsoft Exchange Server Jetstress 2010
Applies to: Exchange Server 2010 SP1, Exchange Server 2010
Jetstress 2010 works with the Microsoft Exchange Server 2010 database engine to simulate the
Exchange database and log disk input/output (I/O) load.
You can use Jetstress 2010 to verify the performance and stability of a disk subsystem prior to
putting an Exchange 2010 server into production. Jetstress helps verify disk performance by
simulating Exchange disk I/O load. Jetstress simulates the Exchange database and log file loads
produced by a specific number of users.
You use Performance Monitor, Event Viewer, and the Exchange Server Database Utilities
(Eseutil.exe) tool in conjunction with Jetstress to verify that your disk subsystem meets or exceeds
the performance criteria you establish. After successful completion of the Jetstress disk performance
and stress tests in a non-production environment, you will have verified that your Exchange 2010
disk subsystem is adequately sized (in terms of performance criteria you establish) for the user count
and user profiles you have established.
Important:

Jetstress testing should be performed before you install Exchange on the server.

Microsoft Exchange Server Profile Analyzer

The Microsoft Exchange Server Profile Analyzer tool lets administrators collect estimated statistical
information from a single mailbox store or across an Exchange Server organization.
You can use the collected data to perform the following operations:
Analyze the performance and health of a mailbox server.
Improve capacity planning models.
Improve testing methodologies and tools.
Improve future client and server products.
STEPS
1. Microsoft Exchange Server Profile Analyser Collects statistical information across an

Exchange Server organization
2. Exchange Mailbox Server Role Requirements Calculator Makes recommendations based on inputs
provided.
3. Microsoft Exchange Server Jetstress 2010 Jetstress 2010 works with the Microsoft
Exchange Server 2010 database engine to simulate the Exchange database and log disk input/output
(I/O) load.