The system works great when I do a PXE boot; but that is only part of what I need the BareMetal for.
I am attempting to make a WINPE Boot Disk using the TPMFOSD webconsole.
It will create a Boot CD, however when it boots, it detects in needs WinPE x86-64 and reboots; but can never find the 64-bit WINPE. Any ideas as to what I did wrong? Or what I need to do to remedy the problem?
I have already started the rbagent using the 64-bit file and re-crated the CD; but alas, that didn’t work.
We did not get around and have time with the last release to test this functionality. I believe we suspect there would be issues with generating deployment media. So at this point it may be broken, but is definitely something we plan to fix short term.
Also, I see you’re using 7.1.1.12, which I believe is an unreleased version, but I don’t think that is going to be causing the issue. I’ll follow up with the team and get back to you on all this.
I just heard back from someone about this. As I said earlier, there is still some work to do to get this fixed and fully working.
From what I gather, it currently only works with 32-bit OS being deployed and some additional steps. Below are the abbreviated notes I have for creating the deployment media.
Use Deployment Media Wizard in TPMfOSD UI.
Create a standard Windows PE-based network boot cd/dvd
Select Windows PE 3.0
Specify IP of TPMfOSD server by way of list
You’ll probably want to make sure drivers are bound properly for the 32-bit deployment engine before starting.
Once the deployment starts, at the very beginning an extraneous panel is shown with an IBM logo. An option will offer to install an Operating System. Select the other option instead that offers to exit to command prompt. The operations will continue from that point on, and shortly after that the binding menu listing the images should be shown.
This is just relaying the instructions I received from someone else. I personally have not tested. This is something we are currently working on in order to behave as you would likely expect but will not be until the next release.
The directions that you gave me are for PXE, which works. When you are using a boot CD you do not get the first screen, it automatically goes to the bind menu.
When you do a network book CD (windows PE based network boot CD) the result is CD that loads WinPE when booted. This WinPE will connect to the OSD server and shows the binding menu. In this way the machine does not perform a PXE boot.
In an integrated TEM/OSD environment, you can create the Network Boot CD logging to the OSD console of the system acting as PXE server in the TEM infrastructure. You say that you do not get the first screen with the IBM logo, so this leads me to suspect you are generating the Network Boot CD from a stand alone OSD installation, that has no link or integration with the TEM.
If this is the case then your network boot CD should work with no limitation.
Another suspect statement early in the thread is that you were provided with “.12. The same issue occured in .11 and .10”. The last available supported version of OSD for both the integrated version with TEM and the stand alone version is 7.1.1.11 Build 190.17.