Skip to main content

Export Your Performance Monitor Data to Excel

Updated: 2016MAY04

To clarify when this functionality is available, you can only save the view when you are viewing a Data Collection Set.  The "live" data cannot be saved in this way.

Performance Monitor in Windows Server give us the ability to see when our servers are having some issues.  Analyzing that data into something meaningful can be a problem.  You can export your data to Excel so you can better see what your performance data represents. 
First collect your data.
image
Right click the graph and select Save Data As.
Change the Save as type to Text file (comma delimited)(*.csv).
Give the file a name and save it where you want to store it.
Now open that file on a client with Excel installed on it.  By using excel, you will be able to present the data in a more meaningful format.

Comments

Saurabh Sinha said…
Thanks for this post jason, This helped me to analyse my data well
Saurabh,

Don't forget to look into PowerShell to help you analyze your data.

Jason
Anonymous said…
This would've added a lot more value to the internet if you explained how to create a graph from the output data, its not hard to double-click a CSV file.
Hey Anonymous,

Take a look at Technet or Bing/Google how to use Performance Monitor. Instructions on how to create this information is widely available.

Take care,
Jason
Unknown said…
"Save Data As" is disabled. How to enable it?
The "Save data As" works only with Data Collection Sets, which is one of the features of Performance Monitor. I will update the blog to reflect this. You cannot do it with the live view, but only recorded data.

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...