The Win32_VolumeUserQuota association class relates per user quotas to quota-enabled volumes. A system administrator can configure Windows to prevent disk space use that is more than a user's quota, and then log an event when a user exceeds the specified disk space limit. A system administrator can also log an event when a user exceeds a specified disk space warning level. A disk quota cannot be set for an administrator account. Windows XP and earlier: This class is not available.
Methods
Win32_VolumeUserQuota has no methods.
Properties
Win32_VolumeUserQuota returns 6 properties:
'Account','DiskSpaceUsed','Limit','Status','Volume','WarningLimit'
Unless explicitly marked as writeable, all properties are read-only. Read all properties for all instances:
Get-CimInstance -ClassName Win32_VolumeUserQuota -Property *
Most WMI classes return one or more instances.
When
Get-CimInstance
returns no result, then apparently no instances of class Win32_VolumeUserQuota exist. This is normal behavior.Either the class is not implemented on your system (may be deprecated or due to missing drivers, i.e. CIM_VideoControllerResolution), or there are simply no physical representations of this class currently available (i.e. Win32_TapeDrive).
Account
Reference to the volume.
Get-CimInstance -ClassName Win32_VolumeUserQuota | Select-Object -Property Account, Volume
DiskSpaceUsed
Number of bytes that a user or group is using.
For more information about using uint64 values in scripts, see Scripting in WMI.
Get-CimInstance -ClassName Win32_VolumeUserQuota | Select-Object -Property Account, Volume, DiskSpaceUsed
Limit
Limit set for this user or group in bytes.
For more information about using uint64 values in scripts, see Scripting in WMI.
Get-CimInstance -ClassName Win32_VolumeUserQuota | Select-Object -Property Account, Volume, Limit
Status
Current status of an object. Various operational and nonoperational statuses can be defined. Available values:
$values = 'Degraded','Error','Lost Comm','No Contact','NonRecover','OK','Pred Fail','Service','Starting','Stopping','Stressed','Unknown'
Status returns a numeric value. To translate it into a meaningful text, use any of the following approaches:
Use a PowerShell Hashtable
$Status_map = @{
OK = '0'
Warning = '1'
Exceeded = '2'
}
Use a switch statement
switch([int]$value)
{
OK {'0'}
Warning {'1'}
Exceeded {'2'}
default {"$value"}
}
Use Enum structure
Enum EnumStatus
{
_0 = OK
_1 = Warning
_2 = Exceeded
}
Examples
Use $Status_map in a calculated property for Select-Object
<#
this example uses a hashtable to translate raw numeric values for
property "Status" to friendly text
Note: to use other properties than "Status", look up the appropriate
translation hashtable for the property you would like to use instead.
#>
#region define hashtable to translate raw values to friendly text
# Please note: this hashtable is specific for property "Status"
# to translate other properties, use their translation table instead
$Status_map = @{
OK = '0'
Warning = '1'
Exceeded = '2'
}
#endregion define hashtable
#region define calculated property (to be used with Select-Object)
<#
a calculated property is defined by a hashtable with keys "Name" and "Expression"
"Name" defines the name of the property (in this example, it is "Status", but you can rename it to anything else)
"Expression" defines a scriptblock that calculates the content of this property
in this example, the scriptblock uses the hashtable defined earlier to translate each numeric
value to its friendly text counterpart:
#>
$Status = @{
Name = 'Status'
Expression = {
# property is an array, so process all values
$value = $_.Status
$Status_map[[int]$value]
}
}
#endregion define calculated property
# retrieve the instances, and output the properties "Caption" and "Status". The latter
# is defined by the hashtable in $Status:
Get-CimInstance -Class Win32_VolumeUserQuota | Select-Object -Property Caption, $Status
# ...or dump content of property Status:
$friendlyValues = Get-CimInstance -Class Win32_VolumeUserQuota |
Select-Object -Property $Status |
Select-Object -ExpandProperty Status
# output values
$friendlyValues
# output values as comma separated list
$friendlyValues -join ', '
# output values as bullet list
$friendlyValues | ForEach-Object { "- $_" }
Use $Status_map to directly translate raw values from an instance
<#
this example uses a hashtable to manually translate raw numeric values
for property "Win32_VolumeUserQuota" to friendly text. This approach is ideal when
there is just one instance to work with.
Note: to use other properties than "Win32_VolumeUserQuota", look up the appropriate
translation hashtable for the property you would like to use instead.
#>
#region define hashtable to translate raw values to friendly text
# Please note: this hashtable is specific for property "Win32_VolumeUserQuota"
# to translate other properties, use their translation table instead
$Status_map = @{
OK = '0'
Warning = '1'
Exceeded = '2'
}
#endregion define hashtable
# get one instance:
$instance = Get-CimInstance -Class Win32_VolumeUserQuota | Select-Object -First 1
<#
IMPORTANT: this example processes only one instance to illustrate
the number-to-text translation. To process all instances, replace
"Select-Object -First 1" with a "Foreach-Object" loop, and use
the iterator variable $_ instead of $instance
#>
# query the property
$rawValue = $instance.Status
# translate raw value to friendly text:
$friendlyName = $Status_map[[int]$rawValue]
# output value
$friendlyName
Use a switch statement inside a calculated property for Select-Object
<#
this example uses a switch clause to translate raw numeric
values for property "Status" to friendly text. The switch
clause is embedded into a calculated property so there is
no need to refer to external variables for translation.
Note: to use other properties than "Status", look up the appropriate
translation switch clause for the property you would like to use instead.
#>
#region define calculated property (to be used with Select-Object)
<#
a calculated property is defined by a hashtable with keys "Name" and "Expression"
"Name" defines the name of the property (in this example, it is "Status", but you can rename it to anything else)
"Expression" defines a scriptblock that calculates the content of this property
in this example, the scriptblock uses the hashtable defined earlier to translate each numeric
value to its friendly text counterpart:
#>
$Status = @{
Name = 'Status'
Expression = {
# property is an array, so process all values
$value = $_.Status
switch([int]$value)
{
OK {'0'}
Warning {'1'}
Exceeded {'2'}
default {"$value"}
}
}
}
#endregion define calculated property
# retrieve all instances...
Get-CimInstance -ClassName Win32_VolumeUserQuota |
# ...and output properties "Caption" and "Status". The latter is defined
# by the hashtable in $Status:
Select-Object -Property Caption, $Status
Use the Enum from above to auto-translate the code values
<#
this example translates raw values by means of type conversion
the friendly names are defined as enumeration using the
keyword "enum" (PowerShell 5 or better)
The raw value(s) are translated to friendly text by
simply converting them into the enum type.
Note: to use other properties than "Win32_VolumeUserQuota", look up the appropriate
enum definition for the property you would like to use instead.
#>
#region define enum with value-to-text translation:
Enum EnumStatus
{
_0 = OK
_1 = Warning
_2 = Exceeded
}
#endregion define enum
# get one instance:
$instance = Get-CimInstance -Class Win32_VolumeUserQuota | Select-Object -First 1
<#
IMPORTANT: this example processes only one instance to focus on
the number-to-text type conversion.
To process all instances, replace "Select-Object -First 1"
with a "Foreach-Object" loop, and use the iterator variable
$_ instead of $instance
#>
# query the property:
$rawValue = $instance.Status
#region using strict type conversion
<#
Note: strict type conversion fails if the raw value is
not defined by the enum. So if the list of allowable values
was extended and the enum does not match the value,
an exception is thrown
#>
# convert the property to the enum **Status**
[EnumStatus]$rawValue
# get a comma-separated string:
[EnumStatus]$rawValue -join ','
#endregion
#region using operator "-as"
<#
Note: the operator "-as" accepts values not defined
by the enum and returns $null instead of throwing
an exception
#>
$rawValue -as [EnumStatus]
#endregion
Enums must cover all possible values. If Status returns a value that is not defined in the enum, an exception occurs. The exception reports the value that was missing in the enum. To fix, add the missing value to the enum.
Volume
Reference to a volume.
Get-CimInstance -ClassName Win32_VolumeUserQuota | Select-Object -Property Account, Volume
WarningLimit
Number of bytes a user or group can use before receiving a warning.
For more information about using uint64 values in scripts, see Scripting in WMI.
Get-CimInstance -ClassName Win32_VolumeUserQuota | Select-Object -Property Account, Volume, WarningLimit
Examples
List all instances of Win32_VolumeUserQuota
Get-CimInstance -ClassName Win32_VolumeUserQuota
Learn more about Get-CimInstance
and the deprecated Get-WmiObject
.
View all properties
Get-CimInstance -ClassName Win32_VolumeUserQuota -Property *
View key properties only
Get-CimInstance -ClassName Win32_VolumeUserQuota -KeyOnly
Selecting Properties
To select only some properties, pipe the results to Select-Object -Property a,b,c
with a comma-separated list of the properties you require. Wildcards are permitted.
Get-CimInstance
always returns all properties but only retrieves the ones that you specify. All other properties are empty but still present. That’s why you need to pipe the results into Select-Object
if you want to limit the visible properties, i.e. for reporting.
Selecting Properties
The code below lists all available properties. Remove the ones you do not need:
$properties = 'Account',
'DiskSpaceUsed',
'Limit',
'Status',
'Volume',
'WarningLimit'
Get-CimInstance -ClassName Win32_VolumeUserQuota | Select-Object -Property $properties
Limiting Network Bandwidth
If you work remotely, it makes sense to limit network bandwidth by filtering the properties on the server side, too:
Get-CimInstance -Class Win32_VolumeUserQuota -Property $property |
Select-Object -Property $property
Selecting Instances
To select some instances, use Get-CimInstance and a WMI Query. The wildcard character in WMI Queries is % (and not “*”).
The parameter -Filter runs a simple query.
Listing all instances where the property Caption starts with “A”
Get-CimInstance -Class Win32_VolumeUserQuota -Filter 'Caption LIKE "a%"'
Using a WQL Query
The parameter -Query uses a query similar to SQL and combines the parameters -Filter and -Property. This returns all instances where the property Caption starts with “A”, and returns the properties specified:
Get-CimInstance -Query "SELECT Account, WarningLimit, Volume, DiskSpaceUsed FROM Win32_VolumeUserQuota WHERE Caption LIKE 'a%'"
Any property you did not specify is still present but empty. You might need to use
Select-Object
to remove all unwanted properties:Get-CimInstance -Query "SELECT Account, WarningLimit, Volume, DiskSpaceUsed FROM Win32_VolumeUserQuota WHERE Caption LIKE 'a%'" | Select-Object -Property Account, WarningLimit, Volume, DiskSpaceUsed
Accessing Remote Computers
To access remote systems, you need to have proper permissions. User the parameter -ComputerName to access one or more remote systems.
Authenticating as Current User
# one or more computer names or IP addresses:
$list = 'server1', 'server2'
# authenticate with your current identity:
$result = Get-CimInstance -ClassName Win32_VolumeUserQuota -ComputerName $list
$result
Authenticating as Different User
Use a CIMSession object to authenticate with a new identity:
# one or more computer names or IP addresses:
$list = 'server1', 'server2'
# authenticate with a different identity:
$cred = Get-Credential -Message 'Authenticate to retrieve WMI information:'
$session = New-CimSession -ComputerName $list -Credential $cred
$result = Get-CimInstance Win32_VolumeUserQuota -CimSession $session
# remove the session after use (if you do not plan to re-use it later)
Remove-CimSession -CimSession $session
$result
Learn more about accessing remote computers.
Requirements
To use Win32_VolumeUserQuota, the following requirements apply:
PowerShell
Get-CimInstance
was introduced with PowerShell Version 3.0, which in turn was introduced on clients with Windows 8 and on servers with Windows Server 2012.
If necessary, update Windows PowerShell to Windows PowerShell 5.1, or install PowerShell 7 side-by-side.
Operating System
Win32_VolumeUserQuota was introduced on clients with None supported and on servers with Windows Server 2003.
Namespace
Win32_VolumeUserQuota lives in the Namespace Root/CIMV2. This is the default namespace. There is no need to use the -Namespace parameter in Get-CimInstance
.
Implementation
Win32_VolumeUserQuota is implemented in Vdswmi.dll and defined in Vds.mof. Both files are located in the folder C:\Windows\system32\wbem
:
explorer $env:windir\system32\wbem
notepad $env:windir\system32\wbem\Vds.mof