PXE Manager – Part III

by tomarentsen on Monday, July 4th, 2011 | No Comments

PXE Manager Part III – Configuration of PXE Manager

Follow the following instructions to configure the PXE Manager and add an ESXi 4.1 Update 01 build.

Open the vSphere Client, Home, PXE Manager to open PXE Manager
Click to activate the “Configuration” tab, right click the agent of the PXE Manager server itself and click “Disable”, this will disable the TFTP & DHCP components on the PXE Manager server itself as we don’t need it)
Right click the PXE Agent and click “Edit” (do this for both PXE Agents you have installed).
Choose whether you wish to use PXE or GPXE and click “Next”
Leave defaults and click “Next”
Enter the IP information and click “Next”
In case you wish to enable “locked down mode”, activate it here otherwise leave defaults and click “Next”
Enter your NTP servers and your syslog server here and click “Next”
Click “Next”
Click “Finish”
Click to activate the “Repository” tab and click to activate the “Stateful Build”
Right the empty window and click “Add build”
Select the ESXi 4.1 Update 1 Installable ISO and click “Next”
Once the files are extracted, click “Next”
Accept default and click “Next”
Wait till the files are verified and click “Finish”
Using explorer, navigate to the <Program Data>\VMware\… folder you will see a new build has been created. Remember the location as we are going to replace the “imagedd.bz2″ and “imaged.md5″ files with the one that has the Emulex OneConnect driver integrated.

Update: PXE Manager checks the MD5 value of each file, therefore by copying the “imagedd.bz2″ file directly into the build folder, PXE Manager will determine it is corrupt and will overwrite the file. In order to get a around this, you would have to make a new ISO image and create a new build based on the custom made ISO image. Please refer to http://blog.arentcs.com/pxe-manager-part-iv/