{"id":549,"date":"2014-10-11T00:01:00","date_gmt":"2014-10-11T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2014\/10\/11\/weekend-scripter-use-powershell-to-calculate-and-display-percentages\/"},"modified":"2014-10-11T00:01:00","modified_gmt":"2014-10-11T00:01:00","slug":"weekend-scripter-use-powershell-to-calculate-and-display-percentages","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/weekend-scripter-use-powershell-to-calculate-and-display-percentages\/","title":{"rendered":"Weekend Scripter: Use PowerShell to Calculate and Display Percentages"},"content":{"rendered":"

Summary<\/b>: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to calculate and display percentages.<\/span><\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. This morning, I am sipping a cup of red berry tea. It is tangy and refreshing. I will admit that I cheated. I used our machine. Boom! 90 seconds later it was done. I guess I could actually do that in my sleep.<\/p>\n

Of course, I do not make tea in my sleep, but I do sometimes write Windows PowerShell script while I am dozing. When this happens, I need to get to work quickly—before I forget what I was thinking about.<\/p>\n

In Windows 8.1, Windows 8, Windows Server 2012 R2, and Windows Server 2012, there is a function named Get-Volume<\/b>. It provides a decent default output, and I use it quite a lot actually.<\/p>\n

Note <\/b> This function requires that the Windows PowerShell console or the Windows PowerShell ISE is opened with Administrator rights (or it generates an error message). But the message does not say that you do not have permission or rights. Instead it says, “Access to a CIM resource was not available to the client.” To figure out that it is a permission denied scenario, I need to look a bit further in the error message, where I will see the following: “+ CategoryInfo  : PermissionDenied:”<\/p>\n

Here is the standard output from the Get-Volume<\/b> function:<\/p>\n

PS C:\\> get-volume<\/p>\n

DriveLetter  FileSystemLabel  FileSystem DriveType  HealthStatus  SizeRemaining  Size<\/p>\n

———–     ————      ———-    ———       ————       ————      —-<\/p>\n

     C             SSD                     NTFS        Fixed       Healthy        72.65 GB    148.53 GB<\/p>\n

     E            HybridTer…          NTFS         Fixed      Healthy        560.81 GB   931.39 GB<\/p>\n

                    Recovery             NTFS        Fixed       Healthy        22.96 MB      300 MB<\/p>\n

I like the drive letter, label, size, and size remaining.  I already know the drives are fixed, and I am glad that they do not have any social diseases and are therefore healthy. But what I want to know is the percentage of utilization. I really cannot do a whole lot with the statistic "150 GB," but if I see that it is 85% utilized, I know that maybe I am starting to have an issue.<\/p>\n

I can obtain this same information by using Windows PowerShell 2.0 (or even Windows PowerShell 4.0 on Windows 7) by directly querying the WMI class. Here is an example:<\/p>\n

Get-CimInstance win32_volume | Select DriveLetter, Label, FileSystem, DriveTYpe, FreeSpace, Capacity<\/p>\n

Following is the output from this command. I would need to do a bit more work to display the output in gigabytes and in megabytes. I wrote a function a long time ago that I would use to display the output in the appropriately sized units.<\/p>\n

DriveLetter : C:<\/p>\n

Label       : SSD<\/p>\n

FileSystem  : NTFS<\/p>\n

DriveTYpe   : 3<\/p>\n

FreeSpace   : 78011699200<\/p>\n

Capacity    : 159486308352<\/p>\n

 <\/p>\n

DriveLetter : E:<\/p>\n

Label       : HybridTerrabyte<\/p>\n

FileSystem  : NTFS<\/p>\n

DriveTYpe   : 3<\/p>\n

FreeSpace   : 602152972288<\/p>\n

Capacity    : 1000068870144<\/p>\n

 <\/p>\n

DriveLetter :<\/p>\n

Label       : Recovery<\/p>\n

FileSystem  : NTFS<\/p>\n

DriveTYpe   : 3<\/p>\n

FreeSpace   : 24080384<\/p>\n

Capacity    : 314568704<\/p>\n

Getting the percentage volume utilization<\/h2>\n

In the past, I would always make the calculation, and then format the output. Following, is an example of doing that. (This is a one-line command that I broke at the pipe character.)<\/p>\n

PS C:\\> get-volume |<\/p>\n

select driveletter, FilesystemLabel, @{L='pct used';E={"{0:N2}" -f (($_.sizeremaining\/$_.size)*100)}}<\/p>\n

 <\/p>\n

                  driveletter FilesystemLabel      pct used<\/p>\n

                  ———–     —————      ——–<\/p>\n

                            C SSD                           48.91<\/p>\n

                            E HybridTerrabyte               60.23<\/p>\n

                              Recovery                      7.66<\/p>\n

That works, but it is actually quite a bit of work, and it is not all that easy to understand. I am using conditional formatting, and I am specifying that I want a number with two decimal places. It is pretty easy to get this wrong.<\/p>\n

I was thinking about this last night, and I realized there is a much easier way to accomplish the same task. It also gives me quite a bit of control over the process. I am going to create a new instance of the System.Globalization.CultureInfo<\/a> class, and specify en-us<\/b> culture. I store the returned object in the $nfi<\/b> variable. Here is that line:<\/p>\n

$nfi = New-Object System.Globalization.CultureInfo -ArgumentList "en-us",$false<\/p>\n

Now I decide that I want to define the number of digits used for percentages to be four decimal places. (For more information, see NumberFormatInfo.PercentDecimalDigits Property<\/a>.) This is a straightforward value assignment, as shown here:<\/p>\n

$nfi.NumberFormat.PercentDecimalDigits = 4<\/p>\n

Now that I have done that, I am going to use the ToString<\/b> method from the numbers and specify that I want percentage number formatting (see The Percent ("P") Format Specifier<\/a>). I also specify my customized CultureInfo<\/b> object with the custom number format for decimal places for percentages. Here is the command (again, it is a single line that is broken at the pipe character):<\/p>\n

get-volume |<\/p>\n

select driveletter, FilesystemLabel, @{L='pct used';E={($_.sizeremaining\/$_.size).ToString("P", $nfi)}}<\/p>\n

The command the associated output are shown here:<\/p>\n

\"Image<\/a><\/p>\n

This is actually easier than it looks. For example, if I do not want to customize the way my percentages display, I can use the default. There is already an instance the CultureInfo<\/b> class at work in the Windows PowerShell console. I can examine it by using the Get-Culture<\/b> cmdlet, as shown here:<\/p>\n

PS C:\\> $c = Get-Culture<\/p>\n

PS C:\\> $c.NumberFormat.PercentDecimalDigits<\/p>\n

2<\/p>\n

By not specifying a custom number format, I can use these defaults. This is shown here:<\/p>\n

PS C:\\> get-volume |<\/p>\n

select driveletter, FilesystemLabel, @{L='pct used';E={($_.sizeremaining\/$_.size).ToString("P")}}<\/p>\n

 <\/p>\n

                  driveletter FilesystemLabel      pct used<\/p>\n

                  ———–      —————      ——–<\/p>\n

                            C SSD                           48.91 %<\/p>\n

                            E HybridTerrabyte               60.23 %<\/p>\n

                              Recovery                      7.66 %<\/p>\n

If I want to change the default behavor, for example, for the number of percentage decimal places, I simply write a new value, as shown here:<\/p>\n

PS C:\\> $c = Get-Culture<\/p>\n

PS C:\\> $c.NumberFormat.PercentDecimalDigits = 4<\/p>\n

PS C:\\> get-volume | select driveletter, FilesystemLabel, @{L='pct used';E={($_.sizeremain<\/p>\n

ing\/$_.size).ToString("P")}}<\/p>\n

 <\/p>\n

                  driveletter FilesystemLabel       pct used<\/p>\n

                  ———–     —————       ——–<\/p>\n

                            C SSD                           48.9057 %<\/p>\n

                            E HybridTerrabyte               60.2304 %<\/p>\n

                              Recovery                      7.6550 %<\/p>\n

This behavior will exist until I close the Windows PowerShell console. If I want a permanent solution, I add the command to my Windows PowerShell profile.<\/p>\n

I hope you have an awesome day, and I will see you tomorrow.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b> <\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to calculate and display percentages. Microsoft Scripting Guy, Ed Wilson, is here. This morning, I am sipping a cup of red berry tea. It is tangy and refreshing. I will admit that I cheated. I used our machine. Boom! 90 seconds later it was […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[51,3,4,61,45],"class_list":["post-549","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-scripting-guy","tag-scripting-techniques","tag-weekend-scripter","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to calculate and display percentages. Microsoft Scripting Guy, Ed Wilson, is here. This morning, I am sipping a cup of red berry tea. It is tangy and refreshing. I will admit that I cheated. I used our machine. Boom! 90 seconds later it was […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/549","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=549"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/549\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=549"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=549"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=549"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}