Let’s compare the same request (opening the InboxRules pane in ECP) without this setting enabled and with it enabled: We can also export the table’s content by pressing the Copy button in the top left corner and copy all data into Notepad, Word, Excel, etc., which makes it easier to sort and analyze all counters:īut, there is more we can do with this console! In the section there is also another interesting feature:īy setting the LogPerformanceData to true, IIS will log all counters we see in the console for each request made to ECP.
This value measures the performance of the client UI code.Īlthough most of these are too technical to be used by most administrators, there are many useful counters that will help troubleshoot a possible performance issue, such as Client Request Time, Server Request Time, LDAP Latency, Authentication or Client Network Time for example. UI Response (ms) – time spent by the browser to process the response received. Here is the list of all of them with a brief description: There are many counters available with this console, mostly are self-explanatory. If we go straight to the console once we log in to ECP, we will only have the following URLs:īut once we go back to ECP and start “moving around”, we will see information regarding more and more URLs as we can see from the screenshot above. Once we click on Performance Console, the console itself will open in a new window: However, after enabling the console we will also have the Performance Console link: If we log in to the ECP before this change and click on the drop-down to the right of the help icon, we will only see the Help, Help Bubble and Copyright links:
Exchange 2010 best practices analyzer update#
Save the file, run the usual IISRESET /NOFORCE to update IIS and we are good to go! In there we will find the following key:Īs the comment explains, all we have to do to enable the console is update the value of the ShowPerformanceConsole key from false to true. Open the file with Notepad and look for the section, right in the first few lines. In this case, we are only interested in the one for ECP, which is located (by default) in: %SystemDrive%\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\web.config Outlook Web App and ECP both have a web.config file that is used to configure some settings specific to ASP.NET. To enable it, we have to manually edit the web.config file on the Client Access Server we want to troubleshoot or analyze. We can use it to check how long it takes to authenticate a user, how many PowerShell cmdlets have been invoked and even how long the server took to process requests. This console, which is not visible by default, provides numerous counters regarding the performance of the ECP. We analyze how the CPU, memory and disk are performing through PerfMon, we look at the Event Logs, Exchange Best Practices Analyzer, we use Performance Troubleshooter, etc… But now there is another tool that might be useful in certain scenarios: the Exchange Control Panel Performance Console.
Exchange 2010 best practices analyzer Pc#
Although most of the time this is due to the user’s PC or the network itself, sometimes there might be actually a performance issue with one or more Exchange servers. Every Exchange Administrator has had at least one user complaining that Outlook or Outlook Web App was running slow.
0 kommentar(er)
