`$Datastores` needs to be initialized as an empty array `@()` rather than `$null`. Furthermore, if `$DsStroageOvercommit` is empty it is only initialised with a single element where there should be one element per datastore. I've moved the test into the loop instead.
Updated Set-HVPool to address issue #132. The -Start and -Stop parameter tested the wrong variable in the loop. $item is undefined. Furthermore, in general if the key/value pair specified $false as the value then the parameter wasn't seen in simple logic test such as if ($key -and $value) {}. I've updated to use $PSBoundParameters instead.
If no match was found in the first 1000 results then the QueryService_GetNext() was never called as it used the length of the result array to detect the second pass through the loop
Add three new internal functions Get-HVHostOrClusterID, Get-HVResourcePoolID and Get-HVAccessGroupID to search the tree results of HostOrCluster_GetHostOrClusterTree(), ResourcePool_GetResourcePoolTree() and AccessGroup_List() respectively. Previously only the top level of the result tree from these calls where considered which was raised as issue #88. The solutions provided in the discussions were point fixes as they changed the level of the tree which was searched which missed matches at the other and the original levels.
Removed parameter -Deleting which isn't used and is a read-only property anyway
Corrected automatic Logoff Minutes validation range which is 1.. rather than 1..120
Updated the validation set for delete or refresh machines after log off. From the API, valid options are Never, Delete, Refresh not Never, Delete, After
Allowed selecting the AD Container when creating Linked Clones
Add -globalEntitlement parameter to Set-HVPool to allow pool to be associated with a globalentitlement. Previously this was only possible through the New-HVPool cmdlet. Added cmdlet Set-HVGlobalEntitlement to allow global entitlements to be updated
This script will interrogate vcenter to find the peak users of network or storage usage.
This was quite handy for me to quickly identify the source of issues such as an inbound DDOS, outbound DOS or a server pummiling storage due to swapping/etc.
