VMware Infrastructure Toolkit (for Windows)
VMware Infrastructure Toolkit (for Windows) 1.0 Update 1 Release Notes
VMware Infrastructure Toolkit (for Windows) provides an easy-to-use Windows PowerShell interface to the VMware Infrastructure API (VI API). VI Toolkit (for Windows) includes numerous cmdlets, sample scripts, and a function library.
This document contains the following information:
Update 1 of the VI Toolkit (for Windows) 1.0 improves the performance of the
To use the VI Toolkit (for Windows) console, you need to have installed the following software:
- .NET 2.0 Service Pack 1
- Windows PowerShell 1.0
If Service Pack 1 for .NET 2.0 is not installed, some operations might take long to complete.
VI Toolkit (for Windows) 1.0 works on the 32-bit and 64-bit versions of the following operating systems:
- Windows Vista
- Windows XP (Service Pack 2)
- Windows 2003 Server
VI Toolkit (for Windows) 1.0 supports the following VMware environments:
- VMware ESX Server 3.5
- VMware ESX Server 3i
- VMware VirtualCenter 2.5
- VMware ESX Server 3.0/VirtualCenter 2.0
Obtaining the Software
You can obtain the VI Toolkit (for Windows) 1.0 at:
The VI Toolkit (for Windows) 1.0 has the following known issues:
New-HardDiskcmdlet cannot create
New-HardDiskis run, the
Splitparameter can not be applied to the hard disk.
- Split hard disks can be created only from
Flatdisk type. However, when a
Rawdisk is created with
Splitparameter is set, no error is generated.
RawPhysicaldisks can not be created. However, when
New-HardDiskis run with the
NonPersistentparameters, no error is generated and the created disk is
from RawPhysical IndependendPersistenttype.
ThinProvisioneddisks can be created only from
Flatdisk type. However, when a raw disk is created using
ThinProvisionedparameter is set, no error is generated.
Set-HardDiskcannot move the hard disk to the specified datastore.
Set-HardDiskcannot set the type of a raw virtual disk to
- When a single hard disk is modified using the
Set-HardDiskcmdlet, the result is a collection of one item instead of a single object.
ReadOnlyCommunitieswhen invoked with an empty string or array for
Set-VMHostSNMPfails to enable
VMHostSNMPand to set the
ReadOnlyCommunityStringwhen called for the first time.
Workaround: Run the command again.
- The default value of the
TargetPortparameter is a random number instead of the port number.
Set-VMHostSNMPdoes not take in account the value of the
New-VMHostNetworkAdaptercannot set the value of the MAC address on VirtualCenter 2.5 and ESX Server 3.5.
Updating an array of virtual NICs with
Set-VMHostNetworkAdaptermight not return an array containing all modified virtual NICs.
- Modifying the
DomainPasswordparameters for a Windows OS customization specification using
Set-OSCustomizationSpecresults in an error.
- On a Windows OS customization specification, running
Set-OsCustomizationSpecwrongly sets to
- On a Linux OS customization specification, running
Set-OsCustomizationSpecreturns an error.
Set-OsCustomizationSpecallows to change the OS customization specification from Linux to Windows and from Windows to Linux, without generating an error.
OSCustomisationSpecparameter of the
New-VMcmdlet can be applied only when the new virtual machine is deployed from a template.
During the process of creating a template from a virtual machine,
Get-VMreturns both the virtual machine and template objects.
Get-Logcannot create a bundle log for an ESX Server host on a VirtualCenter connection.
Workaround: Connect directly to the ESX Server host.
(Get-Datastore).FreeSpaceMBmay not return the actual datastore free space after a virtual machine is powered on. A refresh should be made first.
Get-Eventis run for entities other than virtual machines, an incorrect result is returned.
When invoked with the
Quiescedswitch parameter on,
New-Snapshotcreates a snapshot with
Update-Toolsmight hang if the mouse, VGA, and network drivers are not signed. A standard Windows dialog appears and needs a manual interaction.
Get-CDDrivedoes not work on snapshots.
Get-FloppyDrivedoes not work on snapshots.
The output of the
dircommand, run while the Inventory Provider is running, might be difficult to read.
When working without administrator privileges, the user is not able to see debug messages in the VI Toolkit logs.
Workaround: Work as an administrator on the local machine where the VI Toolkit is installed.
Working on 64-bit Platforms
Operations with ESX or VirtualCenter take long to complete when working on 64-bit platforms.
Workaround: This is a .NET 2.0 issue and it is fixed in Service Pack 1. Install Service Pack 1 for .NET 2.0.
The following issues have been resolved in VI Toolkit (for Windows) 1.0:
A new cmdlet
Disconnect-VIServerfor closing VMware Infrastructure connections is available.
Dismount-Toolsnow return an error message when they are invoked without the
New-Datastorecreates new datastores as expected when adding NFS, CIFS, VMFS, and local storages.
Users can specify a datastore when
Move-VMis run between hosts.
Set-VmHostNetworkcmdlet now works against an ESX Server 3i visor.
Installing the VI Toolkit (for Windows)
VMware provides a single installer for the VI Toolkit (for Windows).
To install the VI Toolkit (for Windows)
- Download and install PowerShell 1.0 from the Microsoft PowerShell 1.0 download page .
- Launch the VI Toolkit (for Windows) installer by double-clicking the executable file you downloaded from http://www.vmware.com/go/powershell .
- Follow the instructions of the wizard.
- To install the toolkit in location other than the default, click Change in the Destination Folder page and select a different directory.
- In the Ready to Install the Program page choose whether to create a desktop shortcut.
- Click Install to proceed with the installation.
- Click Finish to complete the installation process.
To find a more detailed description of the VI Toolkit (for Windows) installation process and prerequisites, see the Installation Guide.
Last updated 03-Sep-2008 10:30 am