VM-CdDrive-Report.ps1 -- Minor revision to metadata to confirm to PowerActions standards.

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 commit is contained in:
aaronwsmith
2016-08-03 14:29:19 -05:00
parent c39a39d8df
commit 3cf6bf5d97

View File

@@ -1,17 +1,15 @@
<#
.MYNGC_REPORT
.LABEL
VM CD-Drive Report
.DESCRIPTION
PowerActions Report Script that reports on VMs CD-Drive configuration, making it easy to find VMs holding onto ISOs that you
need to update, or VMs that can't vMotion because they are tied into a physical resource from the ESXi host that is running it.
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. Script is able to report on VMs with multiple CD-Drives as well. Version 1.0, written by
Aaron Smith (@awsmith99), published 07/29/2016.
#>
# AUTHOR: Aaron Smith (@awsmith99)
# VERSION: 1.0
# PUBLISHED: 2016.07.29
# ABOUT : PowerActions Report Script that reports on VMs CD-Drive configuration, making it easy
# to find VMs holding onto ISOs that you need to update, or VMs that can't vMotion
# because they are tied into a physical resource from the ESXi host that is running it.
# 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. Script is able
# to report on VMs with multiple CD-Drives as well.
param
(
[Parameter(Mandatory=$true)]