Recently with vSphere 5 VMware enabled you to deploy the ESXi image via PXE boot to your hosts, to do this you need some PowerCLI knowledge. Now just because I find PowerCLI easy to use and a great product it doesn’t mean the next person will.
Luckily PowerGUI gave us a great way to add an MMC style interface back on top of the cmdlets, this is called a Powerpack.
The Image Builder and Auto Deploy Powerpack is a PowerGUI Powerpack which enables us as VMware admins to have a graphical interface to Image Builder and Auto Deploy which are currently released as PowerShell snap-ins only.
The Powerpack contains a variety of scripts which will allow you to harness the power of custom ESXi images and stateless deployment.
What Do I need ?
In order to use this Powerpack you will need the following:
- PowerShell V2
- PowerCLI 5.0 or later version
- Download the Powerpack from below
Here is a short video which shows you the basics of how to import the Powerpack and how to use it.
To see how to import a Powerpack and how to make sure you always have the latest version check this post here: http://www.virtu-al.net/2009/10/29/vesi-powergui-powerpack-management/
How can I contribute ?
Please add comments to this post if something doesn’t work or you have any ideas on how to make it better – remember this is an initial release !
No it just needs to be on a client which has PowerCLI 5.0 or higher installed.
Does all of this have to be prepared directly on the vCenter server itself? I’m building this on another server at the moment, and “Get-ESXImageProfile” on my vCenter server seems to have no idea that I’m prepping these packages.
(Oh, and great utility, btw!…Making life much easier, on the whole…thanks)
Pingback: Powerpack for Image builder and Autodeploy for VMware | ESX Virtualization
I havent had a chance to test this as yet, hopefully soon !
I was wondering if the issue that Doug was having has been resolved. I’m having the same problem. Since it is listed in the Software Packages tree item on the left, does that mean it has been added?
Thanks for the great feedback Doug, I will take a look at these and try and add/resolve them where possible.
Neat tool. Too bad I beat my forehead flat trying to figure this stuff out without your tool. 🙁
A couple of thoughts
1. Can you provide the option to “Connect As” when connecting to the vCenter server?
2. When adding file system objects to the packager, can you provide a “Browse” button?
3. I would like to be able to either clone an image or start with an empty one and drag packages to it. The image profile would preferably be a child node under Image Profiles in the tree control on the left.
Also, I am getting an error adding packages to an image:
Cannot validate argument on parameter ‘SoftwarePackage’. The argument is null or empty. Supply an argument that is not null or empty and then try the command again. (Add-EsxSoftwarePackage) At line: 11 char: 63
After I clone my base profile and select “List Software Packages” and try to add one, this error appears, and the package is not added to the cloned profile, but does show up when I select the Software Packages tree item on the left.
The package(s) I am trying to add are the HP BL460c G7 components found here: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=4194638&prodTypeId=3709945&prodSeriesId=4194735&swLang=8&taskId=135&swEnvOID=4115
Pingback: Creating an Image Profile without manually downloading a bundle! (stateless ESXi) » Yellow Bricks