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
vtool : manual time required : calculated against
Many of these needs improvement, the script is written in what i call street smart way, not exactly the standard best practices but it will nonetheless work. May be others will see, use, update and improve it. Many functions like creating drs rules etc., are still at their infant stage and are not working.
vTool>create cluster
vTool>Add hosts 1+ hour per 60 blades
vTool>Configure HA
vTool>Configure DRS
vTool>DRS Rules
vTool>vApp
vTool>Add Datastores 1+ hour per 60 datastores
vTool>SNMP 2+ hour per 60 blades
vtool>syslog ip 2+ hour per 60 blades
vtool>dns 15 minutes per 60 blades
vtool>ntp 10 minutes per 60 blades
vtool>any advanced 15 minutes per 60 blades
vtool>firewall 15 minutes per 60 blades
vtool>scratch 20 minutes per 60 blades
vtool>performance settings 5 minutes per 60 blades
vtool>core dump 10 minutes per 60 blades
vtool>power management 5 minutes per 60 blades
vtool>esxi services 10 minutes per 60 blades
vtool>vmkernel services 10 minutes per 60 blades
vtool>hostfile entries 5 hours per 60 blades
vtool>vSwitch 5 minutes per 60 blades
vtool>vswitch ports 5 minutes per 60 blades
vtool>update nic 10 minutes per 60 blades
vtool>update mtu 10 minutes per 60 blades
vtool>vm portgroup 15 minutes per 60 blades
vtool>vmkernel portgroup 1 hour per 60 blades
vtool>sync portgroup 5 minutes per 60 blades
vtool>l3 vmotion 1 hour per 60 blades
vtool>create vds per 60 blades
vtool>dvportgroups 15 minutes per 60 portgroups
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.
