Enabling the Exchange 2010 ECP Performance Console

If you’ve been testing or even running Exchange 2010 in production, you will most certainly be aware of the Exchange Control Panel – which is now not only the user’s Options panel but provides access to a number of Administrative tools, such as basic user management and reporting/mailbox searches.

However one feature contained in the ECP but isn’t visible immediately is the ECP Performance Console.

The ECP Performance Console is ECP-specific in that it provides a whole wealth of information about how your Exchange Control Panel is performing – from how long client requests are taking, RPC latency down to what’s happening on the Powershell side. Although it is totally ECP specific the information can help you diagnose areas in which your client access server isn’t performing as it should and verifying improvements are working as they should.

The fields available in the ECP Performance console are as follows:

Request URL
Client Request Time (ms)
Server Request Time (ms)
RBAC Session
RBAC Session Latency (ms)
RPC Requests
RPC Latency (ms)
LDAP Requests
LDAP Latency (ms)
Serialization Time (ms)
Runspace Latency (ms)
Runspace Activations
Runspace Active Time (ms)
Windows PowerShell Invoke Count
Windows PowerShell Invoke Time (ms)
Cmdlets Instantiated
Cmdlet Time (ms)
Cmdlets Invoked
BeginProcessing Time (ms)
ProcessRecord Count
Process Record Time (ms)
EndProcessing Time (ms)
Authentication (ms)
Authorization (ms)
Resolve Cache (ms)
Map Request (ms)
Acquire State (ms)
Execute Handler (ms)
Release State (ms)
Update Cache (ms)
Log Request (ms)
Client Network Time (ms)
UI Response (ms)

To enable the ECP Performance Console, edit the ECP root directory’s web.config file on each Client Access server you wish to use this on. This is located at the following location:

C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\web.config

Look int he file for the following section:

<!-- Set ShowPerformanceConsole to "true" to show ECP's Perf Console: -->
    <add key="ShowPerformanceConsole" value="false" />

Change the value for ShowPerformanceConsole to false to true as described in the preceding comment, and save the file.

Once you’ve made the change, run the customary iisreset /noforce to reset IIS then as normal login at your ECP URL (i.e. https://mail.contoso.com/ecp) and after login, click the drop-down to the right of the help icon:


You should see Performance Console now listed. Click it and voila – it should appear.


If you want to export the data –  simply press the Copy button in the top left corner. The data can then be pasted into Excel.

Hope you find this useful, at some point!


12 thoughts on “Enabling the Exchange 2010 ECP Performance Console

  1. Pingback: Встроенная консоль мониторинга производительности в Exchange 2010 « Тишина

  2. Great find, Steve!

    I have a standard build/configuration script for each exchange role, so I can knock them out in a standardized way very quickly. I’ve added this to my script:

    $ecpConfig = [xml](Get-Content -Path “C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\web.config”)
    foreach($item in $ecpConfig.configuration.appSettings.add) {
    if($item.Key -eq “ShowPerformanceConsole”) { $item.value = “true” }
    $ecpConfig.Save(“C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\web.config”)

  3. Pingback: Enabling the Exchange 2010 ECP Performance Console : BPMi

    • Hi Mike,

      I found it by looking around the web.config files for ECP. I started playing around with them trying to enable new-mailbox cmdlets (as they appear to be there in the on-premise version, just disabled) and stumbled across this. Searched around and couldn’t find any mention of it anywhere on the web, which I thought was strange and worth a blog post!


    • Hey Mike,

      Do you know how to get the New Mailbox UI to appear in the ECP ?

      We use a separate group of people for Mailbox creation and I would rather not give them access to the EMC.

      • It’s in the Web.Config but no combination of changes to the web.config or RBAC makes it work.

        Apparently it’s not coming back in SP1 either. It’s solely there for Exchange Online and Outlook Live.

Comments are closed.