Which commands should you run?

DRAG DROP
###BeginCaseStudy###
Case Study: 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###

You need to identify which commands must be run to perform the maintenance window tasks.
Which commands should you run? (To answer, drag the appropriate commands to the correct tasks.
Each command may be used once, more than once, or not at all. You may need to drag the split bar
between panes or scroll to view content.)

Answer:

Explanation:

Start-DatabaseAvailabilityGroup
Use the Start-DatabaseAvailabilityGroup cmdlet to reincorporate one or more previously failed
members of a database availability group (DAG).
EXAMPLE 1
This example starts the Mailbox server MBX2 in the DAG DAG1.
Start-DatabaseAvailabilityGroup -Identity DAG1 -MailboxServer MBX2
Stop-DatabaseAvailabilityGroup
Use the Stop-DatabaseAvailabilityGroup cmdlet to mark a member of a database availability group
(DAG) as failed, or to mark all DAG members in a specific Active Directory site as failed.
EXAMPLE 1
This example stops the Mailbox server MBX2 in the DAG DAG1.
Stop-DatabaseAvailabilityGroup -Identity DAG1 -MailboxServer MBX2
The Stop-DatabaseAvailabilityGroup cmdlet is used during a datacenter switchover. This cmdlet is
used to mark one or members of the DAG as failed (also known as stopped).The Stop

DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a
DatacenterActivationMode value of DagOnly.
Suspend-ClusterNode <ServerName>
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from
being and becoming the PAM.
Primary Active Manager (PAM)
Microsoft Exchange Server 2013 includes a component called Active Manager that manages the high
availability platform that includes the database availability group (DAG) and mailbox database
copies. Active Manager runs inside the Microsoft Exchange Replication service
(MSExchangeRepl.exe) on all Mailbox servers. On Mailbox servers that aren’t members of a DAG,
there is a single Active Manager role: Standalone Active Manager. On servers that are members of a
DAG, there are two Active Manager roles: Primary Active Manager (PAM) and Standby Active
Manager (SAM). PAM is the Active Manager role in a DAG that decides which copies will be active
and passive. PAM is responsible for getting topology change notifications and reacting to server
failures. The DAG member that holds the PAM role is always the member that currently owns the
cluster quorum resource (default cluster group). If the server that owns the cluster quorum resource
fails, the PAM role automatically moves to a surviving server that takes ownership of the cluster
quorum resource. In addition, if you need to take the server that hosts the cluster quorum resource
offline for maintenance or an upgrade, you must first move the PAM to another server in the DAG.
The PAM controls all movement of the active designations between a database’s copies. (Only one
copy can be active at any specified time, and that copy may be mounted or dismounted.) The PAM
also performs the functions of the SAM role on the local system (detecting local database and local
Information Store failures).
Set-MailboxServer <ServerName> – DatabaseCopyAutoActivationPolicy Blocked
Performing maintenance on DAG members
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the
server from hosting active database copies.
Set-MailboxServer <ServerName> – DatabaseCopyActivationDisabledAndMoveNow $True
Failover the databases that are hosted on the Mailbox server by using this command:
In computing, failover is switching to a redundant or standby computer server, system, hardware
component or network upon the failure or abnormal termination of the previously active
application,[1] server, system, hardware component, or network. Failover and switchover are
essentially the same operation, except that failover is automatic and usually operates without
warning, while switchover requires human intervention.
At server level, failover automation usually uses a “heartbeat” cable that connects two servers. As
long as a regular “pulse” or “heartbeat” continues between the main server and the second server,
the second server will not initiate its systems. There may also be a third “spare parts” server that has
running spare components for “hot” switching to prevent downtime. The second server takes over
the work of the first as soon as it detects an alteration in the “heartbeat” of the first machine. Some
systems have the ability to send a notification of failover.
Set-MailboxServer <ServerName> -Component Hub Transport -State Draining -Requester
Maintenance
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining Requester
Maintenance to begin the process of draining the transport queues.
Draining the transport queue refers to emptying the transport queue.

Set-ServerComponentState <ServerName> – Component ServerWideOffline – State Inactive
Requester Maintenance
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Inactive –
Requester Maintenance to place the server into maintenance mode.
STEPS
1. All mounted databases on the server undergoing maintenance must be activated on another
servver.
Set-MailboxServer <ServerName> – DatabaseCopyActivationDisabledAndMoveNow $True
The question is asking you to failover the databases
2. All message queue on the server undergoing maintenance must be empty before maintenance
can begin
Set-MailboxServer <ServerName> -Component Hub Transport -State Draining -Requester
Maintenance
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining Requester
Maintenance to begin the process of draining the transport queues.
Draining the transport queue refers to emptying the transport queue.
3. The server undergoing maitenance must be prevented from becoming a PAM.
Suspend-ClusterNode <ServerName>
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from
being and becoming the PAM.
Primary Active Manager (PAM)
4. Database copies on the server undergoing maintenance must not be activated while maintenance
is occurring.
Set-MailboxServer <ServerName> – DatabaseCopyAutoActivationPolicy Blocked
Performing maintenance on DAG members
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the
server from hosting active database copies.
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Performing maintenance on DAG members
Before performing any type of software or hardware maintenance on a DAG member, you should
first place the DAG member into maintenance mode. This involves moving all active databases off
the server and blocking active databases from moving to the server. It also ensures that all critical
DAG support functionality that may be on the server (for example, the Primary Active Manager
(PAM) role) is moved to another server and blocked from moving back to the server. Specifically, you
should perform the following tasks:
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining Requester
Maintenance to begin the process of draining the transport queues.
Run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Draining Requestor
Maintenance to begin the process of draining all Unified Messaging calls.
Run Redirect-Message -Server <ServerName> -Target <MailboxServerFQDN> to redirect messages
pending delivery in the local queues to the Mailbox server specified by the Target parameter.
Run Suspend-ClusterNode <ServerName> to pause the cluster node, which prevents the node from
being and becoming the PAM.

Run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $True to
move all active databases currently hosted on the DAG member to other DAG members.
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked to prevent the
server from hosting active database copies.
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Inactive –
Requester Maintenance to place the server into maintenance mode.
To verify that a server is ready for maintenance, perform the following tasks:
Run Get-ServerComponentState <ServerName> | ft Component,State -Autosize to verify the server
has been placed into maintenance mode
Run Get-MailboxServer <ServerName> | ft DatabaseCopy* -Autosize to verify the server is not
hosting any active database copies.
Run Get-ClusterNode <ServerName> | fl to verify that the node is paused.
Run Get-Queue to verify that all transport queues have been drained.
After the maintenance is complete and the DAG member is ready to return to service, you can take
the DAG member out of maintenance mode and put it back into production by performing the
following tasks:
Run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Active –
Requester Maintenance to designate that the server is out of maintenance mode.
Run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Active –Requestor
Maintenance to allow the server to accept Unified Messaging calls.
Run Resume-ClusterNode <ServerName> to resume the node in the cluster, which enables full
cluster functionality for the server.
Run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $False to
allow databases to become active on the server.
Run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Unrestricted to remove
the automatic activation blocks.
Run Set-ServerComponentState <ServerName> -Component HubTransport -State Active –Requester
Maintenance to resume the transport queues and allow the server to accept and process messages.