Applies to: Exchange Server 2010
Topic Last Modified: 2011-03-19
When you disable a cmdlet extension agent in Microsoft Exchange Server 2010, the agent is disabled on every server running Exchange 2010 in the organization. When an agent is disabled, it's not made available to cmdlets. Cmdlets can no longer use the agent to perform additional operations.
.gif) Caution: |
|---|
|
Before you disable an agent, be sure that you're aware of how the agent works and what impact disabling the agent will have on your organization.
|
Looking for other management tasks related to managing cmdlet extension agents? Check out Managing Cmdlet Extension Agents.
Use the Shell to disable 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.
.gif) Note: |
|---|
|
You can't use the EMC to disable a cmdlet extension agent.
|
To disable a cmdlet extension agent, use the Disable-CmdletExtensionAgent cmdlet. Specify the name of the agent you want to disable when you run the cmdlet. This example disables the Scripting Agent.
Disable-CmdletExtensionAgent "Scripting Agent"
For detailed syntax and parameter information, see Disable-CmdletExtensionAgent.
Other Tasks
After you disable a cmdlet extension agent, you may also want to: