DRAG DROP

###BeginCaseStudy###
Case Study: 4
A Datum Corporation Overview
A Datum Corporation is an airline catering company that has 8,000 users. A. Datum has
three main offices. The offices are located in Detroit, Chicago, and New York.
Existing Environment
Active Directory Environment
The network contains an Active Directory forest named adatum.com. The forest contains a
single domain. All domain controllers run Windows Server 2012.

Each main office contains two domain controllers. Each office is configured as an Active
Directory site.
The functional level of the forest is Windows Server 2012.
Network Infrastructure
The offices connect to each other by using a dedicated WAN link. Only the office in New
York and the office in Detroit connect directly to the Internet. Each office has a firewall.
The public DNS records for A. Datum are configured as shown in the following table.

The external interface for the firewall in the New York office is configured to use an IP
address of 131.107.1.200 and to pass inbound traffic on port 25 and port 443 to EX2.
The external interface for the firewall in the Detroit office is configured to use an IP address
of 131.107.2.200 and to pass inbound traffic on port 443 to EX4.
The Active Directory site is configured as shown in the Sites exhibit. (Click the Exhibit
button.)
Exchange Server Organization
A Datum has an Exchange Server 2013 organization that contains two servers. The servers
are configured as shown in the following table.

Each server contains 15 mailbox databases.
Users use the name mail.adatum.com to connect to their mailbox from the Internet. The
users use the FQDN of the servers to connect from the internal network.
AM of the users in the Detroit office have a mailbox hosted on EX2.
The default email address policy contains a single email address format of @adatum.com.
A separate Send connector exists for the Chicago office and the New York office. The local
servers in each office are the only source servers in each Send connector.
The New York office is configured as a hub site. Antimalware filtering is disabled on EX1 and
EX2.
Problem Statements
A Datum identifies the following issues:
• Users in the Detroit office report that sometimes, Microsoft Outlook takes a long
time to open.
• During a recent storage failure, administrators failed to restore the latest backup and
lost all of the email messages from the previous 48 hours.
• Users report that the email messages sent to some Internet domains are not
received. Users in the Chicago office report that some of their email messages generate a
non-delivery report (NDR).
• The help desk in the New York office reports that its most common Exchange-related
task is to restore email messages that were deleted by users more than 14 days ago. The
task requires time-consuming restore operations by the help desk.
Requirements
Business Requirements
A Datum wants to provide users with the ability to access their email from Internet Explorer
10, even when the users are disconnected from the network. This ability must only be
available if the users log on to Outlook Web Access by using the Private option.
Planned Changes
You plan to deploy three additional Exchange Server 2013 servers. The servers will be
configured as shown in the following table.

After the planned deployment, all of the mailboxes of the Detroit office users will be moved
to EX3. All of the Detroit office users will use the name detroitmail.adatum.com when they
connect from the Internet and the name ex4.adatum.com when they connect from the
internal network.
Technical Requirements
A Datum identifies the following technical requirements:
• All existing and future mailboxes must be limited to 5 GB of storage.
• Antimalware and anti-spam filtering must be enabled for the entire Exchange Server
organization.

• If storage for the mailbox database fails, administrators must be able to recover
email messages handled by transport services for to the last five days.
• Only the members of a group named Executives must be able to schedule meetings
in a room mailbox named Boardroom. Meeting requests must not be moderated.
• All of the servers in the New York office that have the Client Access server role
installed must be accessed by using a load balancing solution that can mark a server as
down ifa specific URL on the server is unavailable.
Mailbox Creation Requirements
A Datum identifies the following requirements for creating new mailboxes:
• All mailboxes must automatically have single item recovery enabled.
• All mailboxes must automatically have the Exchange ActiveSync feature disabled.
###EndCaseStudy###

You need to recommend a solution to meet the mailbox creation requirements. Which three actions
should you recommend performing in sequence? (To answer, move the appropriate three actions
from the list of actions to the answer area and arrange them in the correct order.)

Answer:

Explanation:

Edit the ScriptingAgentConfig.xml.sample file, and then rename the file as ScriptingAgentConfig.xml.
Copy the ScriptingAgentConfig.xml file to all of the Mailbox servers
Run the Enable-CmdletExtensionAgent “Scripting Agent” command
http://technet.microsoft.com/en-us/library/dd335054(v=exchg.150).aspx
Cmdlet Extension Agents
Cmdlet extension agents are components in Microsoft Exchange Server 2013 invoked by Exchange
2013 cmdlets when the cmdlets run. As the name implies, cmdlet extension agents extend the capabilities
of the cmdlets that invoke them by assisting in processing data or performing additional actions based on
the requirements of the cmdlet. Cmdlet extension agents are available on any server role.
Agents can modify, replace, or extend functionality of Exchange Management Shell cmdlets. An
agent can provide a value for a required parameter that isn’t provided on a command, override a
value provided by a user, perform other actions outside of the cmdlet workflow while a cmdlet runs,
and more.
You can use the Scripting agent cmdlet extension agent in Exchange 2013 to insert your own
scripting logic into the execution of Exchange cmdlets. Using the Scripting agent, you can add
conditions, override values, and set up reporting.
Every time an Exchange cmdlet is run, the cmdlet invokes the Scripting agent cmdlet extension
agent. When this agent is invoked, the cmdlet checks whether any scripts are configured to be
invoked by the cmdlet. If a script should be run for a cmdlet, the cmdlet tries to invoke any APIs
defined in the script.
The Scripting agent configuration file contains all the scripts that you want the Scripting agent to run.
Scripts in the configuration file are contained within XML tags that define the beginning and end of
the script and various input parameters required to pass data to the script. Scripts are written using
Windows PowerShell syntax. The configuration file is an XML file that uses the elements or attributes
in the following table.
Every Exchange 2013 server includes the file ScriptingAgentConfig.xml.sample in the <installation
path>\V15\Bin\CmdletExtensionAgents folder. This file must be renamed to
ScriptingAgentConfig.xml on every Exchange 2013 server if you enable the Scripting Agent cmdlet
extension agent. The sample configuration file contains sample scripts that you can use to help you
understand how to add scripts to the configuration file.
After you add a script to the configuration file, or if you make a change to the configuration file, you
must update the file on every Exchange 2013 server in your organization. This must be done to make
sure that each server contains an up-to-date version of the scripts that the Scripting Agent cmdlet
extension agent runs.
ScriptingAgentConfig.xml
Renamed from ScriptingAgentConfig.xml.sample on every Exchange 2013 server if you enable the
Scripting Agent cmdlet extension agent.
ScrptingAgentConfig.xml.sample
Every Exchange 2013 server includes the file ScriptingAgentConfig.xml.sample in the <installation
path>\V15
\Bin\CmdletExtensionAgents folder.
This file must be renamed to ScriptingAgentConfig.xml on every Exchange 2013 server if you enable
the Scripting Agent cmdlet extension agent.
The sample configuration file contains sample scripts that you can use to help you understand how
to add scripts to the configuration file.
Enable-CmdletExtensionAgent “Scripting Agent” command
Use the Enable-CmdletExtensionAgent cmdlet on a server running Microsoft Exchange Server 2013
to enable a cmdlet extension agent.
EXAMPLE 1 This example enables the Scripting Agent cmdlet extension agent. Before you enable the
Scripting Agent, you need to make sure that you’ve first deployed the ScriptingAgentConfig.xml
configuration file to all the servers in your organization. If you don’t deploy the configuration file first
and you enable the Scripting Agent, all non-Get cmdlets fail when they’re run.
Enable-CmdletExtensionAgent “Scripting Agent”

Run the Set-CmdletExtensionAgent “Scripting Agent” command
Use the Set-CmdletExtensionAgent cmdlet on a server running Microsoft Exchange Server 2013 to
modify a cmdlet extension agent.
EXAMPLE 1
This example changes the priority of the fictitious “Validation Agent” cmdlet extension agent to 9.
Set-CmdletExtensionAgent “Validation Agent” -Priority 9
STEPS
1. Edit the ScriptingAgentConfig,xml.sample file, and then rename the file as
ScriptingAgentConfig.xml
Need to add in your own appropriate scripts
2. Copy the ScriptingAgentConfig.xml file to all of the Mailbox Servers
The question refers to mailbox creation requirements but according to the above information After you add a script to the configuration file, or if you make a change to the configuration file, you
must update the file on every Exchange 2013 server in your organization. In the absence of further
information, accept updating the mailbox servers over the client access servers 3.EnableCmdletExtensionAgent “Scripting Agent” command Have to enable the cmdlet extension agent.