Windows System Volume Size & Usage
Log In or Register to download the BES file, and more.

0 Votes

Versioning - This is the latest version.

1Windows System Volume Size & Usage10/18/2013 8:55:44 AM
2Windows System Volume Size & Usage10/21/2013 2:03:49 PM

Description

This Analysis was created to determine the existance, size, and free space of the Windows System Volume.  Normally this is a dedicated partition with no drive letter assigned.

Property Details

ID2994588
StatusBeta - Preliminary testing ready for more
TitleWindows System Volume Size & Usage
DomainSYST
Keywordspartition size, space, System Reserved Partition, Boot partition
Added by on 10/21/2013 2:03:49 PM
Last Modified by on 10/21/2013 2:03:49 PM
Counters 6183 Views / 54 Downloads
User Rating 1 star 2 star 3 star 4 star 5 star * Average over 0 ratings. ** Log In or Register to add your rating.

Properties

Volume Label
Period 1 day
 
  * Results in a true/false
Show indented relevance
((if exists string value of properties "Label" of it then string value of properties ("Label") of it else "<none>")) of (select objects ("Label,DriveLetter, Capacity,FreeSpace from Win32_Volume WHERE SystemVolume='True'") of WMI)
Drive Letter
Period 1 day
 
  * Results in a true/false
Show indented relevance
((if exists string value of properties "DriveLetter" of it then string value of properties ("DriveLetter") of it else "<none>")) of (select objects ("Label,DriveLetter, Capacity,FreeSpace from Win32_Volume WHERE SystemVolume='True'") of WMI)
Capacity
Period 1 day
 
  * Results in a true/false
Show indented relevance
((string value of property "Capacity" of it as integer / 1024 / 1024) as string & " MB") of (select objects ("Label,DriveLetter, Capacity,FreeSpace from Win32_Volume WHERE SystemVolume='True'") of WMI)
Free Space
Period 1 day
 
  * Results in a true/false
Show indented relevance
((string value of property "FreeSpace" of it as integer / 1024 / 1024) as string & " MB") of (select objects ("Label,DriveLetter, Capacity,FreeSpace from Win32_Volume WHERE SystemVolume='True'") of WMI)
Free %
Period 12 hours
 
  * Results in a true/false
Show indented relevance
((string value of property "FreeSpace" of it as floating point / string value of property "Capacity" of it as floating point * 100) as integer as string & " percent free") of (select objects ("Label,DriveLetter, Capacity,FreeSpace from Win32_Volume WHERE SystemVolume='True'") of WMI)

Relevance

isWindows (Relevance 1172)
Used in 1112 fixlets and 524 analyses   * Results in a true/false
Show indented relevance
windows of operating system
Used in 2 analyses   * Results in a true/false
Show indented relevance
version of operating system >= "6"

Sharing

Social Media:
Share this page on Yammer

Comments

Log In or Register to leave comments!
JasonWalker -
Updated the Analysis to handle System Partitions with no Label, and System Partitions that are larger than "integer value of property" can handle.
jgstew -
Only "C:" appears to have a label.
jgstew -
Actually, the issue may be that on my system I am booting Windows 8 using EFI. I have a 300MB "Recovery Partition" and a 100mb "EFI System Partition" and then the "C:" partition which is "Boot, Page File, Crash Dump, Primary Partition"
jgstew -
Yes, it is worse to put WMI inspectors in the analysis' relevance since it will be constantly evaluated, better to be handled by the results error handling code.
JasonWalker -
Question, if you can give a reading on this. Since WMI inspectors are expensive, am I worse off putting WMI inspectors into the relevance of the Analysis (which I believe would be constantly evaluated) versus handling multiple WMI inspectors in the Analysis Results (which in this case I've tuned down to periods of 1 day or 12 hours)?
JasonWalker -
Yes, I'm looking for a particular edge case. Using Microsoft Deployment Toolkit to refresh the machine, MDT placed the boot.wim file on that partition and left it there post-deployment. This resulted in a System Reserved Partition that was too full to create VSS Snapshots and caused subsequent System State backups to fail. I needed a way to identify System Reserved Partitions that were nearly full. Does your Windows 8 machine have a System Reserved Partition (it would be visible in DiskPart's 'LIST VOLUME' command)? If there is no System Reserved partition, I see how that would error out. Maybe the right thing is to change the relevance to only be relevant to systems that have this partition; or handle the errors in the analysis results. Normally I'd like to handle that in the results (to me it's worth knowing that a machine does not have a System Reserved Partition at all), but since the WMI inspectors are expensive I think this one might be better off ignoring the irrelevant machines.
jgstew -
Actually, I think the windows 8 issue has to do with "WHERE SystemVolume='True'" which seems to cause it to return no results. Taking that out will cause it return everything but the system partition.
jgstew -
I see, you are looking for the system reserved volume with no drive letter? I didn't realize that. I could not tell what was failing, just gave no results. It might have to do with my configuration.
JasonWalker -
I don't have any Windows 8 systems with which to test. Can you tell what is failing? I'm using the WMI inspectors because the built-in Inspector for the 'drives' object only returns values for volumes that have a drive letter assigned, and the System Reserved Partition by default does not have a drive letter. Are there any built-in inspectors that will examine a partition that has no drive letter assignment? I couldn't find any.
jgstew -
Also, these don't appear to work in the debugger in Windows 8.
jgstew -
I also have some windows specific hard drive properties here: http://bigfix.me/analysis/details/2994542
jgstew -
Some of these can be done using the built in BigFix Inspectors, which are faster and more universal than using WMI calls. See examples here: http://bigfix.me/analysis/details/2994572