Category Archives: VMware

How to enable SSH on ESX 3i

This one has been around for a while but I thought I would document it on my blog as I just used it and there is a growing demand for 3i help due to it now being free !

How to enable SSH on VMware ESX 3i.

After reading the VMTN forum use the following steps to enable SSH

  • From the console press ALT-F1
  • Type unsupported and press ENTER
  • Enter the root password
  • Enter the following command vi /etc/inetd.conf
  • Search for the #SSH settings
  • Remove the # from the SSH row
  • Save the config by using :wq!
  • Type ps | grep inetd on the console
  • Send a hangup signal by using the following command kill -s HUP

You can now use Putty to SSH to your 3i server.

Free VMbook – Business Continuity and Disaster Recovery

This Free VMware VMbook focuses on business continuity and disaster recovery (BCDR) and is intended to guide the reader through the step-by-step process to set-up a multisite VMware Infrastructure that is capable of supporting BCDR services for designated virtual machines at time of test or during an actual event that necessitated the declaration of a disaster, resulting in the activation of services in a designated BCDR site.

Downloadable here

Last minute entry…Its great !

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

Virtualise in Minutes with VMware ESXi

Now its free why not give it a go with help from this new podcast from VMware…

VMware ESXi is the leanest, meanest hypervisor on the market today.

Discover the benefits of VMware virtualisation by learning how to get started in four easy installation steps.

John Gilmartin, Group Product Manager, Product Marketing, VMware Amir Sharif, Sr. Product Manager, Product Marketing, VMware

Listen: Listen or Download MP3 * (7 MB 10:15 mins)

Rescan all hosts for new storage

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

VI Toolkit Webinar by Carter Shanklin

For those who haven’t had much exposure to the Powershell Toolkit and what it can do, there is a recording of a webinar presented by the Carter Shanklin at this link. It is pretty basic and intended for those with little or no exposure to the toolkit.

If you’ve ever wondered what it is or why you might want to use it (like disconnecting the CD from 45 or 50 VMs so you can VMotion them without having to deal with the right-click – pick-from-the-pop-up-menu process manually 45-50 times) then you might want to check this out.

More recorded webcasts are available on :

Original Source and great site: here

Exporting Virtual Infrastructure Information to MS Word

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

Getting Started with the VI Toolkit

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.

This is also a Next, Next jobbie until completed.

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:

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:


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:


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 !

More on the Update 2 Issue

Email received from VMware:

ESX/ESXi 3.5 Update 2

Dear VMware Customers,

Please find the latest update about the product expiration issue. From this point on, we’ll provide an update every two hours. Thanks.


An issue has been discovered by many VMware customers and partners with ESX/ESXi 3.5 Update 2 where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a build timeout that was mistakenly left enabled for the release build.

Affected Products:

  • VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2
  • Reports of problems with ESX 3.5 U1 with the following 3.5 Update 2 patch applied.
            1. ESX350-200806201-UG
  • No other VMware products are affected.

What has been done?

  • Product and Web teams pulled the ESX 3.5 Update 2 bits from the download pages last night so no more customers will be able to download the broken build.
  • VMware Engineering teams have isolated the cause of the problem and are working around the clock to deliver updated builds and patches for impacted customers.
  • A Knowledgebase article has been published (, but traffic to the knowledgebase is causing time outs. A new static page has been published at that customers and partners will be able to view.
  • The phone system has been updated to advise customers of the problem
  • Vmware partners have been notified of the issue.


1. Do not install ESX 3.5 U2 if it has been downloaded from VMware’s website or elsewhere prior to August 12, 2008.

2. Set the host time to a date prior to August 12, 2008. This workaround has a number of very serious side affects that could impact product environments. Any Virtual Machines that sync time with the ESX host and serve time sensitive applications would be broken. These include, but are not limited to database servers, mail servers, & domain administration systems.

Next Steps:
VMware to notify customers who have downloaded this version and provide an update every two hours.


VMware Engineering has isolated the root cause and is working to produce an express patch for impacted customers today. The target timeframe is 6pm, August 12, 2008 PST.


1. What would this express patch do?
More information will be provided in subsequent communication updates.

2. Will VMware still reissue the upgrade media and patch bundles in the timeframe that has been communicated?
Yes. We still plan to reissue upgrade media by 6pm, August 13 PST (instead of noon, August 13 PST) and all update patch bundles later in the week. We will provide an ETA for the update patch bundles subsequently. NOTE: the "patch bundles" referred to here are for the patches listed above under "Affected Products" and the other bundles released at GA. They are not the same as the express patch which is targeted for 6pm, August 12, 2008 PST as stated above.

3. Why does VMware plan to reissue the upgrade media before the patch bundles? That is a wrong priority call!
This is not a matter of priority. Since we can get done building and testing the upgrade media before the patch bundles, we want to make that available to customers first instead of reissuing all the binaries later in the week.

4. Can VMware issue a patch that opens the licensing backdoor in the next hour as a critical measure?
There is no licensing backdoor in our code.

5. Does this issue affect VC 2.5 Update 2?

6. What is VMware doing to make sure that the problem won’t happen again?
We are making improvements on all fronts. The product team had endeavored to deliver a release with support customers deem important. But we fell short and we are deeply sorry about all the disruption and inconveniences we have caused. We have identified where the holes are and they will be addressed to restore customers’ confidence.