Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2011-03-19
The ability to change the priority of a cmdlet extension agent
in Microsoft Exchange Server 2010 is useful when you want a certain
agent to be called by a cmdlet before another agent. This is
especially useful if you create a custom script that's run in the
Scripting Agent, and you want that script to take
precedence over a built-in agent. For more information about the
Scripting Agent, see Understanding the
|Changing the priority or replacing the functionality of a built-in agent is an advanced operation. Be sure that you completely understand the changes you're making.|
Looking for other management tasks related to managing cmdlet extension agents? Check out Managing Cmdlet Extension Agents.
Use the Shell to change the priority of a cmdlet extension agent
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Cmdlet extension agents" entry in the Exchange and Shell Infrastructure Permissions topic.
|You can't use the EMC to change the priority of a cmdlet extension agent.|
Agents are ordered from 0 to the maximum number of agents. The closer to zero the agent is, the higher the priority of the agent. Agents with a higher priority are called first. For more information about agent priorities, see Understanding Cmdlet Extension Agents.
This example changes the priority of a cmdlet extension
agent by using the Set-CmdletExtensionAgent cmdlet. In this
example, the priority of the
Scripting Agent is
changed to 3.
Set-CmdletExtensionAgent "Scripting Agent" -Priority 3
For detailed syntax and parameter information, see Set-CmdletExtensionAgent.