by Duncan Epping
Duncan Epping · ·
Today I noticed the following error at a customer site when I wanted to install the new patch bundle, “Metadata for patch missing”. After a close inspection I noticed VirtualCenter was installed with a different http port number. For VMware Update Manager to work you will have to open up the firewall manually:
esxcfg-firewall -o 81,tcp,out,UpdateManager
(Change the port number, in red, according to the used portnumber for VirtualCenter.)
Duncan Epping · ·
VMware seems to have ditched the product name “3i” and silently introduced “ESXi”. I noticed it when the download page was updated today. But you can also read it on the “product section” of the VMware website. I think this is a better name instead of differentiation in versions, keeping the versions alligned and changing the name makes more sense to me and probably most customers.
Besides this they’ve also ditched the “server” part in VMware ESX Server, for more info check out the blog by John Troyer!
Duncan Epping · ·
There are new iso’s / builds coming up for 3i, 3.5 and VirtualCenter:
VMware ESX 3.5 Update 1
Latest Version: 3.5 | 4/10/2008 | Build: 82663VMware VirtualCenter 2.5 Update 1
Latest Version: 2.5 | 4/10/2008 | Build: 79820VMware ESXi 3.5 Installable Update 1
Latest Version: 3.5 | 4/10/2008 | Build: 82664
Unfortunately the iso’s aren’t available for download yet and the release notes aren’t updated. I guess someone just made a mistake updating this page cause the release date isn’t for another 10 days. We will just have to wait and see.
Duncan Epping · ·
Rob de Veij created a cool tool for checking the status of VMware Tools and easily upgrading to the latest version of the tools by just selecting the appropriate VM.
RVTools is a small .NET 2.0 application which uses the VI SDK to display the version of the installed VMware tools.It also shows if the tools are upgradeable. The button “Upgrade VMware Tools” starts an UpgradeTools_Task for every selected VM.
Duncan Epping · ·
Just stumbled upon this cool article about mounting your VI inventory as a drive via Powershell:
source – Hal Rottenberg aka halr9000:
- Establish a connection to your the server using the Get-VIServer command:
Get-VIServer -Server
for example,Get-VIServer -Server 192.168.10.10
When prompted, provide the administrator’s username and password to authenticate access on the server.- Get the root folder of the server:
$root = Get-Folder -NoRecursion- Create a PowerShell drive named VI, based on the server root folder. You can use the built-in New-psDrive cmdlet.
New-PSDrive -Location $root -Name vi -PSProvider VimInventory -Root '\'
In this release, a single backslash is the required value for the -Root parameter.- Access the new drive by typing the following command:
cd vi:
To list the drive content, use Get-ChildItem or its alias Dir.- Navigate through your server inventory using the cd command with the full path to the host. For a fictional VI inventory it may looks like the following:
cd Folder01\DataCenter01\host\Web\LiveHost01