VMware Cloud Director Capacity & Storage Profile Reporting with PowerCLI

Why a per-storage-profile report

Most quick PowerCLI snippets for VMware Cloud Director capacity reporting pull a single blended storage figure per Org VDC. That's fine until a VDC has more than one storage tier — say a flash-backed "Gold" profile and a capacity-backed "Bronze" profile — at which point one number hides exactly the detail you need for capacity planning or a migration sizing exercise. This script instead emits one row per storage profile, so a VDC with two tiers becomes two rows, each with its own allocated/used/limit figures and percentage used.

It also enumerates every Organisation it can see, not just one — useful if you're managing a multi-tenant estate or auditing capacity across several customer Orgs in one pass.

Prerequisites

• VMware PowerCLI installed, with the VMware.VimAutomation.Cloud module available (Install-Module VMware.PowerCLI).
• Network access to your vCD cell's API endpoint on port 443.
• An account with at least read access to the Orgs/VDCs you want reported on. Org Admin is generally enough; System/Provider Admin sees more (and unlocks the admin-level storage profile query the script tries first — see below).
• Optional, for -GridView on PowerShell 7+: Install-Module Microsoft.PowerShell.GraphicalTools and a desktop (non-headless) session.

How the script works, step by step

The script runs in four phases. Each one maps directly to a section of the code, so if you're reading the source alongside this, you'll recognise the boundaries.

The StorageProfiles gotcha

The "friendly" Get-OrgVdc object exposes a StorageProfiles property that, on paper, gives you exactly the per-profile breakdown this report needs. In practice, against some vCD versions and account types, that property comes back empty for every single VDC — not because the data doesn't exist, but because the friendly wrapper's link resolution doesn't always populate it. The deprecated VDC-level aggregate properties (StorageUsedGB, etc.) still work in many environments, but they collapse multiple storage tiers into one blended figure and Broadcom has flagged them for removal.

To get a reliable answer regardless of which scenario you're in, the script tries three sources in order and only moves to the next one if the current one comes back empty:

The comma-vs-period decimal bug

[math]::Round() always returns the mathematically correct number. How that number gets displayed — in Out-GridView, on the console, or written into the CSV — depends on the current culture/regional settings of the machine running the script, not on the script's logic. On a system whose region uses a comma as the decimal separator (common across continental Europe), 12.34 renders as 12,34. The value was never wrong; only its text rendering was locale-dependent.

Fixing this needed two settings, not one. Setting only the calling thread's culture fixes the CSV and console output, but Out-GridView opens its window on a separate UI thread that doesn't inherit that override — it falls back to the system's regional settings unless the process-wide default is also set. The script sets both ([Threading.Thread]::CurrentThread.CurrentCulture and [CultureInfo]::DefaultThreadCurrentCulture) to InvariantCulture for the duration of the run, and restores your original settings afterwards in a finally block — so it never leaks into the rest of your session.

$origCulture           = [Threading.Thread]::CurrentThread.CurrentCulture
$origUICulture          = [Threading.Thread]::CurrentThread.CurrentUICulture
$origDefaultCulture     = [CultureInfo]::DefaultThreadCurrentCulture
$origDefaultUICulture   = [CultureInfo]::DefaultThreadCurrentUICulture

try {
    [Threading.Thread]::CurrentThread.CurrentCulture     = [CultureInfo]::InvariantCulture
    [Threading.Thread]::CurrentThread.CurrentUICulture   = [CultureInfo]::InvariantCulture
    [CultureInfo]::DefaultThreadCurrentCulture           = [CultureInfo]::InvariantCulture
    [CultureInfo]::DefaultThreadCurrentUICulture         = [CultureInfo]::InvariantCulture

    # ... rest of the script ...
}
finally {
    [Threading.Thread]::CurrentThread.CurrentCulture     = $origCulture
    [Threading.Thread]::CurrentThread.CurrentUICulture   = $origUICulture
    [CultureInfo]::DefaultThreadCurrentCulture           = $origDefaultCulture
    [CultureInfo]::DefaultThreadCurrentUICulture         = $origDefaultUICulture
}

Usage & parameters

Server names and credentials below are placeholders — swap in your own vCD cell's address.

.\Export-vCDOrgCapacityReport.ps1 -VCDServer vcloud.contoso.com

$cred = Get-Credential admin@automatewithravi.com
.\Export-vCDOrgCapacityReport.ps1 -VCDServer vcloud.contoso.com -Credential $cred -GridView -NoCsv

Sample output

An illustrative excerpt — Org, VDC and customer names below are all generic placeholders, not real environments:

Troubleshooting

• Every StorageDataSource shows "VDC Aggregate (legacy)". Both Search-Cloud query types came back empty for that account — usually a permissions limitation rather than a script issue. Confirm the account can see storage profiles in the vCD UI for the affected Org.
• Connect-CIServer fails with "No Cloud server was found on .../api/". This happens before authentication — it means the initial /api/versions negotiation failed. Test Invoke-WebRequest https://<your-vcd-server>/api/versions directly: clean XML back means a PowerCLI/version mismatch (try updating PowerCLI); an HTML/login page back means the FQDN you have is a tenant portal address, not the actual API endpoint.
• Numbers still show commas in the grid after the culture fix. Check $PSVersionTable.PSVersion — on PowerShell 7+, Out-GridView comes from the Microsoft.PowerShell.GraphicalTools module, which is a different implementation to classic Windows PowerShell's and may need the column values formatted as invariant-culture strings explicitly rather than relying on thread culture alone.
• PowerCLI scripts should not use the 'Client'/'Uid' property warnings. These come from inside the module itself during Connect-CIServer/Get-Org, not from this script — safe to ignore.