Hal just pointed me to a new VI Client Plugin that integrates powershell into the VI Console, looks neat…

Download here

comasoft® VI PowerScripter (currently beta 1) is the first and absolutely unique VMware VI Client plug-in for a tight integration of user-defined PowerShell scripts into the object repository of VMware Virtual Infrastructure 3.5.

This plug-in delivers some predefined scripts for common admin tasks and is capable of handling hundreds of custom scripts for direct usage from a dynamically generated context menu within VI Client (for connections to VirtualCenter, ESX 3.5 or ESX 3i).

Thanks to its absolute flexibility, this powerful software is a “must” for professional users looking to administrate the virtual infrastructure in compliance with business-aligned functions in a simple and yet most effective manner.

Features

• Load any VI PowerShell script through a dynamically created context menu (often no change needed)
• Use of VM or Host based PowerShell scripts
• Run Scripts against single or multiple chosen objects (also Cluster, DataCenter)
• Switch between Debug and silent mode
• Use local scripts or scripts from network shares
• Enhance the VI Client or VirtualCenter functionality for your demands
• PowerShell scripts using the correct VirtualCenter access rights
• all script activities are logged
• Usage of predefined scripts provided by icomasoft
• Support for PowerGUI powerpack files

A last minute entry has just come into the VMware PowerShell Comp and its very good….

This script will generate 2 .txt file reports based on your virtual environment.

The first report (report.txt) includes resource utilization across all Clusters including CPU and Memory usage for the cluster as a whole as well as each individual ESX host.
It will also list the VM to Host Ratio for the cluster.

The latter portion of the report includes an overview of total Datastore space allocated to the environment as well as space available and the amount of space used by powered off VMs.

The first report finishes off with a listing of all datastores with details on available space, capacity and % used.The second report is a hotlist (hotlist.txt which includes VM’s that are using, on average, more than 75% of their allocated memory.

It also includes hosts that are using more than 75% of their Memory or CPU.
It continues by listing datastores with less than 10% of their capacity available.
Finally it pulls WARNING messages from each ESX host’s VMKernel log since the beginning of the previous day.

The first report (report.txt) is designed to bring a high level view of the environment for reporting purposes as well as for making decisions on where additional resources may need to be allocated on a cluster level.
It is particularly useful for providing numbers up the chain of command without needing to pore through Virtual Center collecting data.

The second report is useful from a health check standpoint. It automatically identifies vm’s and hosts that are running hot to give an analyst an idea of where they may need to look into problems.

The datastore report is useful for determining ahead of time when additional storage needs to be allocated and where it should be used. Perhaps the most useful part of the report is the ESX logs. It’s a single place for analysts to watch for early signs of issues that may not be apparent when just using Virtual Center.

The script is a perfect item to run at the beginning of the day before heading down the hall to grab a cup of coffee.

Check it out here

More of a note for myself really but others may find this useful, to rescan all the hosts (rather than clicking Rescan in the GUI) you can run the following PowerShell command:

For a Specific Cluster:

get-cluster -name “MY CLUSTER” | get-vmhost | Get-VMHostStorage -RescanAllHBA

All Hosts in VC:

get-vmhost | Get-VMHostStorage -RescanAllHBA

The below is a script that will export various information into Microsoft Word using PowerShell and the VI Toolkit, this is completely risk free and does not alter anything, just feed it your VI server name and sit back, it can also be used as a scheduled task and even set to email you a word attachment.

It even throws in a few graphs and pie charts for good measure, almost all information can be sent to the functions for you to expand on the report easily.

Comments are welcome, the good the bad and the ugly !

Usage: report.ps1 YOURVISERVER

See below or download here:

Reporting Script

I have become a big fan of the Virtual Infrastructure (VI) Toolkit over the last month and it has really helped me learn PowerShell which I knew I would have to learn sooner or later but kept putting off.

I would now like to spread the word and help out those of you wondering what the hype is all about by telling you how to get started.

Do I need to install the VI toolkit on the VI server ?

No, Definitely not, this can be installed on your workstation and can be used to hook into the Virtual Infrastructure, nothing additional will need to be loaded onto the VI server.

What you will need

Download the following and install them in order:

• .Net framework 2.0 (if not already installed)

This is a Next, Next jobbie until completed.

• PowerShell for Windows (For XP/Vista/2003 you will need to download this but for 2008 this will come pre-installed.)  http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx

This is also a Next, Next jobbie until completed.

• VI Toolkit for Windows 1.0 http://www.vmware.com/sdk/vitk_win/index.html

Just to make a change this is a Next Next

That gets the basics but what you also may want to install is the following:

• PowerGUI, This is a GUI for PowerShell which makes editing scripts 10 times easier http://powergui.org/ (you can also use Admin script editor if you prefer http://www.adminscripteditor.com/)
• Download ActiveRoles Management Shell for Active Directory, The ActiveRoles Management Shell for Active Directory is a set of predefined commands for PowerShell. These commands are designed to help administrators automate common, repetitive and bulk management tasks such as creating, removing or updating objects in Active Directory. http://www.quest.com/powershell/activeroles-server.aspx
• VMware PowerPack, add this to PowerGUI to help you step through the VI toolkit without learning PowerShell http://powergui.org/entry!default.jspa?categoryID=21&externalID=1802

Once these have all been installed you are nearly ready.

From your desktop start the VI toolkit via the newly created shortcut or choose it from the Start Menu if you prefer, once started type the following and press enter:

Set-ExecutionPolicy RemoteSigned

You are now all set to start with PowerShell and the VI toolkit, lets do a simple task just to get you started…

From within the Powershell window now open connect to your Virtual Infrastructure server by using the following command or as you are now using powershell they are know as cmdlets.

Connect-VIServer YourServername

Obviously replace YourServerName with you VI Server.  Once connected you will be able to start issuing commands to the session to retrieve information, try the following simple cmdlet and press enter:

Get-VM

You will now see a list of all Virtual Machines.

And so it begins, this is just a simple cmdlet which will get you hooked from the start, issue the following command to list the other VI Toolkit cmdlets:

Get-VICommand

This should list enough for you to get started, now you can explore PowerShell and the VI Toolkit, for quick examples of what can be done take a look at the VMware examples here:

Managing VMware with PowerShell FAQ

Now there will be no looking back, welcome to the Jedi !