DRAG DROP
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.)
Select and Place:
Explanation/Reference:
Explanation:
Cmdlet Extension Agents: Exchange 2013 Help
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>V15BinCmdletExtensionAgents 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
BinCmdletExtensionAgents 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.Enable- CmdletExtensionAgent “Scripting Agent” command Have to enable the cmdlet extension agent.