Introduction

Low disk space is a common operational problem in Windows environments. Workstations and servers can gradually consume storage because of Windows updates, application data, temporary files, user profiles, logs, cached content and other files.

In a small environment, an administrator can manually open This PC on each computer and inspect the available storage. In a domain environment containing dozens or hundreds of computers, that approach quickly becomes inefficient.

A better approach is to query domain computers remotely and retrieve their disk information from a centralized administration workstation.

Windows PowerShell provides the Get-CimInstance cmdlet, while the Win32_LogicalDisk class exposes information such as drive letter, capacity and free space. Microsoft specifically documents Win32_LogicalDisk for retrieving available disk space. :chatgpt-content-reference{index=”1″}

Why Check Disk Space Remotely?

Centralized disk-space checking is particularly useful for organizations managing multiple Windows clients.

How Remote Disk-Space Checking Works

The process can be viewed as a simple management workflow:

Requirements

Before checking disk space remotely, make sure the environment satisfies the following requirements:

• Windows Server 2025 domain environment or compatible Windows administration workstation.
• Active Directory Domain Services.
• Domain-joined target computers.
• Network connectivity between the administrator computer and target clients.
• Appropriate permissions for remote management.
• PowerShell available on the administration computer.
• Remote CIM/WMI communication available according to your environment’s firewall and security configuration.

Step 1: Open the Windows Administration Tools

Step 2: Check Disk Space on One Remote Domain Computer

Suppose the computer name is:

Open PowerShell on the administration computer and run:

Get-CimInstance -ClassName Win32_LogicalDisk `
-ComputerName CLIENT-PC01 `
-Filter "DriveType=3"

The command queries the remote computer and returns fixed local disks.

Typical properties include:

• DeviceID — drive letter such as C:
• VolumeName — volume label.
• Size — total capacity in bytes.
• FreeSpace — available capacity in bytes.

Step 3: Display Disk Space in GB

Raw WMI/CIM values are returned in bytes, which can be difficult to read. PowerShell can convert the values into gigabytes.

Get-CimInstance -ClassName Win32_LogicalDisk `
-ComputerName CLIENT-PC01 `
-Filter "DriveType=3" |
Select-Object DeviceID,
@{Name="SizeGB";Expression={[math]::Round($_.Size / 1GB,2)}},
@{Name="FreeGB";Expression={[math]::Round($_.FreeSpace / 1GB,2)}}

The resulting output is easier for an administrator to interpret:

Step 4: Check Disk Space on Multiple Domain Computers

The real advantage of remote administration appears when you need to inspect multiple computers.

Create a list of computer names:

$Computers = @(
    "CLIENT-PC01",
    "CLIENT-PC02",
    "CLIENT-PC03",
    "CLIENT-PC04"
)

You can then query each computer:

foreach ($Computer in $Computers) {

    Get-CimInstance `
        -ClassName Win32_LogicalDisk `
        -ComputerName $Computer `
        -Filter "DriveType=3" |
    Select-Object `
        @{Name="Computer";Expression={$Computer}},
        DeviceID,
        @{Name="SizeGB";Expression={[math]::Round($_.Size / 1GB,2)}},
        @{Name="FreeGB";Expression={[math]::Round($_.FreeSpace / 1GB,2)}}

}

This produces a consolidated view of the fixed disks on the selected domain computers.

Step 5: Calculate the Free-Disk Percentage

Total capacity alone does not tell you whether a computer is running out of storage. A percentage makes comparison easier.

The calculation is:

PowerShell can perform the calculation automatically:

Get-CimInstance -ClassName Win32_LogicalDisk `
-ComputerName CLIENT-PC01 `
-Filter "DriveType=3" |
Select-Object DeviceID,
@{Name="SizeGB";Expression={[math]::Round($_.Size / 1GB,2)}},
@{Name="FreeGB";Expression={[math]::Round($_.FreeSpace / 1GB,2)}},
@{
    Name="FreePercent";
    Expression={
        if ($_.Size -gt 0) {
            [math]::Round(($_.FreeSpace / $_.Size) * 100,2)
        }
    }
}

Step 6: Identify Computers with Low Free Space

You can add a threshold to identify computers that require attention. For example, the following example flags drives with less than 15 percent free space.

Get-CimInstance -ClassName Win32_LogicalDisk `
-ComputerName CLIENT-PC01 `
-Filter "DriveType=3" |
Where-Object {
    $_.Size -gt 0 -and
    (($_.FreeSpace / $_.Size) * 100) -lt 15
} |
Select-Object DeviceID,
@{Name="SizeGB";Expression={[math]::Round($_.Size / 1GB,2)}},
@{Name="FreeGB";Expression={[math]::Round($_.FreeSpace / 1GB,2)}},
@{
    Name="FreePercent";
    Expression={[math]::Round(($_.FreeSpace / $_.Size) * 100,2)}
}

GUI-Based Workflow for Domain Administrators

If your objective is to perform the operation from a GUI-oriented administration workflow, use the following approach.

How to Query Computers from Active Directory

In larger environments, maintaining a manual computer-name list may become inconvenient. If the ActiveDirectory PowerShell module is available, administrators can retrieve computer accounts from an OU and then query their disk information.

For example:

Import-Module ActiveDirectory

$Computers = Get-ADComputer -Filter * |
Select-Object -ExpandProperty Name

foreach ($Computer in $Computers) {

    Get-CimInstance `
        -ClassName Win32_LogicalDisk `
        -ComputerName $Computer `
        -Filter "DriveType=3" |
    Select-Object `
        @{Name="Computer";Expression={$Computer}},
        DeviceID,
        @{Name="SizeGB";Expression={[math]::Round($_.Size / 1GB,2)}},
        @{Name="FreeGB";Expression={[math]::Round($_.FreeSpace / 1GB,2)}}

}

Query Computers from a Specific Active Directory OU

A more controlled approach is to query only computers from a particular OU.

$SearchBase = "OU=Workstations,DC=vmorecloud,DC=com"

$Computers = Get-ADComputer `
    -SearchBase $SearchBase `
    -Filter * |
    Select-Object -ExpandProperty Name

You can then pass the returned computer names to the CIM query.

Replace the example distinguished name with the OU structure used in your own Active Directory environment.

Create a Remote Disk-Space Report

Administrators can export the collected information to CSV for documentation, analysis or further processing.

$Results = foreach ($Computer in $Computers) {

    Get-CimInstance `
        -ClassName Win32_LogicalDisk `
        -ComputerName $Computer `
        -Filter "DriveType=3" |
    Select-Object `
        @{Name="Computer";Expression={$Computer}},
        DeviceID,
        @{Name="SizeGB";Expression={[math]::Round($_.Size / 1GB,2)}},
        @{Name="FreeGB";Expression={[math]::Round($_.FreeSpace / 1GB,2)}},
        @{
            Name="FreePercent";
            Expression={
                if ($_.Size -gt 0) {
                    [math]::Round(
                        ($_.FreeSpace / $_.Size) * 100,
                        2
                    )
                }
            }
        }
}

$Results |
Export-Csv `
    -Path "C:\Reports\Domain-Disk-Space.csv" `
    -NoTypeInformation

The resulting CSV can be opened in Microsoft Excel or another compatible data-analysis application.

Improve the Script with Error Handling

A domain may contain computers that are offline, disconnected from the network or unavailable for remote management. A production script should handle those situations rather than stopping at the first failure.

foreach ($Computer in $Computers) {

    try {

        Get-CimInstance `
            -ClassName Win32_LogicalDisk `
            -ComputerName $Computer `
            -Filter "DriveType=3" `
            -ErrorAction Stop |
        Select-Object `
            @{Name="Computer";Expression={$Computer}},
            DeviceID,
            @{Name="SizeGB";Expression={[math]::Round($_.Size / 1GB,2)}},
            @{Name="FreeGB";Expression={[math]::Round($_.FreeSpace / 1GB,2)}}

    }

    catch {

        [PSCustomObject]@{
            Computer = $Computer
            Status   = "Unavailable"
            Error    = $_.Exception.Message
        }

    }

}

Troubleshooting Remote Disk-Space Queries

1. Access Is Denied

Verify that the account running the query has the appropriate administrative permissions on the target computer and that your organization’s remote-management security model permits the operation.

2. The Computer Cannot Be Reached

First verify basic network connectivity and name resolution.

Test-Connection CLIENT-PC01 -Count 2

3. CIM Query Fails

Check Windows Firewall, remote-management configuration, DNS, permissions and network connectivity.

4. Computer Is Offline

A domain computer that is powered off or disconnected cannot provide live disk-space information. Record the computer as unavailable and query it again when it is online.

5. WMIC Commands Are Not Recommended

Older Windows administration guides often use the WMIC command-line utility. Microsoft has deprecated WMIC and recommends PowerShell for WMI administration. Windows Management Instrumentation itself remains available; the deprecation applies to the WMIC utility. :chatgpt-content-reference{index=”5″}

Can GPMC Show Disk Space Directly?

It is important to distinguish between Group Policy management and hardware/storage inventory.

GPMC is primarily designed to manage Group Policy Objects, policy configuration, reporting, modeling and Group Policy Results. It is not a dedicated disk-capacity inventory console. :chatgpt-content-reference{index=”6″}

Best Practices for Remote Disk-Space Monitoring

Practical Example: Finding Low-Disk Computers

Imagine an organization has 100 domain workstations. The IT team wants to identify computers with less than 20 percent free space.

The workflow could be:

1. Retrieve the computers from the appropriate Active Directory OU.
2. Query Win32_LogicalDisk on each computer.
3. Calculate the free-space percentage.
4. Filter results below the defined threshold.
5. Export the results to CSV.
6. Investigate affected computers.

$Results |
Where-Object {
    $_.FreePercent -lt 20
} |
Sort-Object FreePercent

This approach turns raw disk information into a practical administrative report.

Frequently Asked Questions

Get-CimInstance -ClassName Win32_LogicalDisk `
-ComputerName CLIENT-PC01 `
-Filter "DriveType=3"

Conclusion

Remotely checking disk space is an important Windows administration task in environments with multiple domain computers. Instead of manually opening each workstation, administrators can use a centralized Windows Server 2025 administration workstation and query storage information remotely.

The combination of Active Directory for identifying computers, PowerShell for automation, CIM for remote management, and Win32_LogicalDisk for logical-disk information provides a practical foundation for domain-wide storage reporting.

For larger environments, the same approach can be extended to generate CSV reports, identify low-space computers, monitor specific OUs and integrate the results into a broader Windows monitoring workflow.

References & Sources