###BeginCaseStudy###
Testlet 1
Topic 5, Proseware, Inc
Overview
General Overview
Proseware, Inc., is an international manufacturing company that has 3,000 users. Proseware has a sales
department, a marketing department, a research department, and a human resources department.
Proseware recently purchased a small competitor named Contoso, Ltd.
Physical Locations
Proseware has two offices. The offices are located in New York and London. The offices connect to each other
by using a WAN link. Each office connects directly to the Internet.
Contoso has one office in Chicago.
Existing Environment
Active Directory Environment
The network of Proseware contains an Active Directory forest named proseware.com. The forest contains a
single domain and two sites named London and New York. Each site contains two domain controllers that run
Windows Server 2008 R2. The domain controllers in the New York site are named DC1 and DC2. The domain
controllers in the London site are named DC3 and DC4.
All FSMO roles are hosted on DC3 and DC4.
The network of Contoso contains an Active Directory forest named contoso.com. The forest contains five
domain controllers and one site.
Exchange Server Organization
Proseware has an Exchange Server 2013 organization that contains two database availability groups (DAGs)
named DAG-NYC and DAG-LON. The DAGs are configured as shown in the following table.

The certificate used for Exchange Server 2013 has a subject name of mail.proseware.com and a Subject
Alternative Name (SAN) of autodiscover.proseware.com.
Each mailbox database has three copies. All users connect to an active copy of the database on a server in
their respective office. Native data protection is implemented.
NTLM communication is used exclusively for Outlook Anywhere both internally and externally.Problem Statements
Proseware identifies the following issues:
Users report that sometimes, they fail to access the free/busy information of the other users. You also
discover that some users fail to retrieve Autodiscover settings.
Users in the London office report that during a 24-hour WAN outage, they could see only new users in the
global address list (GAL) from Outlook Web App.
The manager of the human resources department in the New York office cannot see new London office
users in the GAL until several hours after the help desk confirms that the users were created.
A hung MSExchangeOWAAppPool in Internet Information Services (IIS) on EX1 causes all of the database
copies to fail over. Despite having the same CopyQueueLength and ReplayQueueLength as the copies on
EX2, the copies on EX3, which have a higher activation preference, are activated, forcing user connections
over the WAN.
A custom application named Appl recently malfunctioned and sent hundreds of false positive email
notifications that had a subject of System Alert: Sales Database Reaching Capacity to all of the users in the
organization. While attempting to remove the email messages, an administrator ran the Search-Mailbox –
DeleteContent command and erroneously deleted valid email messages from the mailboxes of some
executives.
Requirements
Business Goal
Proseware identifies the following business goals:
Reduce the costs associated with using bandwidth on the WAN links.
Improve social media integration by using a Microsoft Outlook app that will be deployed to all of the users in
the sales department.
Planned Changes
Proseware plans to make the following changes:
Implement a lagged copy for the mailbox database of the executives.
Implement an RBAC-linked role group for the administrators at Contoso to manage the mailboxes of the
Proseware users.
Technical Requirements
Proseware identifies the following technical requirements:
End users must be notified after one hour if the email messages that they send are not delivered.
If mailbox database storage fails, the IT department must be able to recover old email messages that were
sent up to five days earlier to the mailboxes of the executives.
All new users hired at Contoso must have a user account in contoso.com and an Exchange Server mailbox
in proseware.com. All new user accounts in contoso.com must have a user principal name (UPN) that ends
with proseware.com.
Administrators at Contoso must be able to create and manage recipient objects in the Exchange Server
organization of Proseware by using their existing contoso.com administrator account. All Contoso recipient
objects must reside in an organizational unit (OU) named proseware.com
Security Requirements
The Chief Security Officer (CSO) introduces the following security requirements:
All Outlook users who connect from the Internet must use Basic authentication only.
All Outlook users who connect from the internal network must use NTLM authentication only.
SLA Requirements
Due to productivity losses during some recent maintenance windows, the Chief Information Officer (CIO)
introduces a new service level agreement (SLA) requiring that all servers entering or exiting a maintenance
window must be taken in and out of service properly.
The SLA contains the following requirements:
All mounted databases on the server undergoing maintenance must be activated on another server.
All message queues on the server undergoing maintenance must be empty before maintenance can begin.
The server undergoing maintenance must be prevented from becoming a Primary Active Manager (PAM).Databases copies on the server undergoing maintenance must not be activated while maintenance is
occurring.
###EndCaseStudy###

HOTSPOT
You need to recommend a solution to resolve the Autodiscover and the free/busy information issues.
Which command should you include in the recommendation? (To answer, configure the appropriate options in
the answer area.)
Hot Area:

Answer:

Explanation:
Free/busy information issues
Sharing free/busy (calendar availability) information between users located on-premises and in the Exchange
Online organization is one of the primary benefits of a hybrid deployment.
Users in both organizations can view each other’s calendars just as if they were located in the same physical
organization. This makes scheduling meetings and resources easy and efficient.
Several components in a hybrid deployment are required to enable the shared free/busy feature in a Microsoft
Exchange Server 2013 deployment:
NOT Set-AutodiscoverVirtualDirectory
Changing the Autodiscover virtual directory will not address the issues,
Use the Set-AutodiscoverVirtualDirectory cmdlet to configure settings on the Autodiscover virtual directory on a
server running Microsoft Exchange Server 2013. You can run this cmdlet on the local Client Access server or
from another Exchange 2013 server.
EXAMPLE 1
This example sets the authentication method to Digest authentication for the Autodiscover virtual directory.
Set-AutodiscoverVirtualDirectory -Identity ‘autodiscover(default Web Site)’ -WindowsAuthentication $false –
BasicAuthentication $false -DigestAuthentication $true
NOT Set-AvailabilityConfig
The Set-AvailabilityConfig cmdlet defines two accounts or security groups: a per-user free/busy proxy account
or group, and an organization-wide free/busy proxy account or group.
These accounts and groups are trusted by all availability services in the current organization for availability
proxy requests.
For cross-forest availability services to retrieve free/busy information in the current forest, they must be using
one of the specified accounts, belong to one of the specified security groups, or have a user name and
password for one of the specified accounts or security groups.
Set-ClientAccessServer
Use the Set-ClientAccessServer cmdlet to set properties on specified Client Access server objects.
EXAMPLE 1
This example sets two properties on the Client Access server CAS-01.
Set-ClientAccessServer -Identity “CAS-01” -AutoDiscoverServiceInternalUri https://cas01.contoso.com/
autodiscover/autodiscover.xml-AutoDiscoverSiteScope “Mail”
-AutodiscoverServiceInternalURI
The AutoDiscoverServiceInternalUri parameter specifies the internal URL of the Autodiscover service.
NOT -External
Parameter not related to Set-ClientAccessServer
Parameter not related to Set-AvailabilityConfig
Parameter not related to Set-AutodiscoverVirtualDirectory
NOT -Internal
Parameter not related to Set-ClientAccessServerParameter not related to Set-AvailabilityConfig
Parameter not related to Set-AutodiscoverVirtualDirectory
http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx