Implemented below Items:
1) Formatting DesktopSummaryData/MachineNamesView
2) Example typo correction
3) Start,Stop, Enable and Disable tasks moved from Start to Set for both
(Pool/Farm)
4) Internal functions Renaming
5) Start-HVPool --> Start-HVPool + Start-HVPoolSummary
6) Start-HVFarm --> Start-HVFarm + Start-HVFarmSummary
7) Plural function names to singular
Not implemented review comment get-hvevent output to be
(get-hvevents).Events
To pipe events to CSV file via Export-Csv cmdlet, events should be
PSCutomObject/PSObject. if we return only events, it will be hard user
to export events to CSV.
I will Implement rest of comments in next pull request.
Created for use when migrating over to PowerCLI 6.5
Functions which can be used to detect where scripts (.ps1) are referencing either the PowerCLI Initialization script or Add-PSSnapin functions to start working with PowerCLI:
Get-PowerCLIInitialization
Get-PowerCLISnapinUse
Function used to update the path to the Initialization script found by the above function:
Update-PowerCLIInitialization
Function used to change from adding in the PowerCLI snapins to now importing the PowerCLI modules:
Update-PowerCLISnapinUse
Ready for merge if accepted. PowerActions Report Script that reports on
VMs with snapshots along with their description, size of the snapshot in
GB, the VM's provisioned vs. used space in GB,
if the snapshot is the
current one being used, its parent snapshot (if there is one), and the
Power state of the VM itself. VM object is key (as it's the first
managed object in the output), enabling you the ability to right-click
an entry in the report to edit the target VM.
Figured out you have to explicitly escape the () characters when editing
a PowerActions script within the Web Client. Added in KEY(VM) to tell
PowerActions which column to use for Context Menu support within Web
Client. Also seemed to speed up execution of the script!
Added .LABEL and .DESCRIPTION fields in place of the custom comments
that documented the script. Tried to specify KEY(VM) under
.MYNGC_REPORT section but that triggered validation errors for me in
PowerActions.
This script will create a Report of LUNs with Paths that have more than
one unique LUN ID or have more than the defined Paths. Information’s
will be gathered via ESXCLI. This is necessary to report also hidden
Paths!
1.0 PowerActions report script for Cluster objects. Reports on status
of all VM's CD-Drives, making it easy to find VMs connected to a given
ISO or that might be using a physical ESXI host drive and unable to
vMotion.
