in my case StorageAllocationGB is showing -1
When you use the Set-OrgVdc with the StorageAllocationGB parameter?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
When I do a get-orgvdc and select name,StorageLimitGB, StorageAllocationGB
StorageLimitGB is showing 3607 but StorageAllocationGB is showing -1
In vCloud Director, the storage policy is showing 3607. I have a few org vdc to change and it takes too many clicks to get there.
It looks like changing the Limit on a Storage Profile is currently only possible through the API, not through a cmdlet.
You might want to have a look at vCloud Director Provider and OrgV DC Storage Profile PowerCLI Module.
But note that this is not an official PowerCLI module!Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz1 person found this helpful
set-OrgVdcStorageProfile -OrgName TEST | Set-OrgVdcStorageProfile -Limit 3694592
PS C:\Users\\Documents\WindowsPowerShell> get-orgvdc LON-TEST-VDC1 | ft name,storagelimitGB
I assume that 1st cmdlet was Get-OrgVdcStorageProfile?
Since the value on the Limit parameter is in MB it seems to have worked (3694592 MB = 3608 GB).
While you had 3607 GB at the start.Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Correct. Thank you so much. We have 5 sites with many customers to update and that made my life much easier. Changes are properly reflected now