FOG 33b - installation - HP Elite 8300 SFF
-
yes
-
And could I have a definitive answer on if it is necessary with 33b to modify the bind-address= in /etc/mysql/my.cnf to my fogserver ip address? (as it was necessary with 32)
-
i recommend setting 66=10.0.1.40 on your DHCP server, so there isn’t any question if it’s resolving the hostname
-
Probably still necessary. I don’t have a definitive answer because this varies per system.
-
I have also tried one of the new HP clients. It does not find the pxe file either.
-
Please make sure you listen to Tom FIRST!
Sometimes after a restart you need to restart the tftp service.
[CODE]sudo restart tftpd-hpa[/CODE]
Edit:
Also, use the ip address of the fogserver for option 66. -
Thanks Junkhacker, I forgot to put in a DNS reference to fogserver.
Now PXE is working on the old HP
The registration works.
But now when the PC is rebooted, and I don’t touch anything, when it defaults past the FOG options, whilst the FOG pxe page is still visible, I see:“Booting from SAN device 0x80”
and it freezes there. Nothing I press takes me further …
I have not set an imaging task or anything like that.
I’ll try the new HP and get back to you.
-
SAN device 0x80 is the local hard disk. is there a valid OS on the drive?
-
Ubuntu 12.04.4
-
i mean on the client that is pxe booting, not the server
-
This post is deleted! -
I have just changed the boot order on the client with Ubuntu 12, to boot straight to the HD and Ubuntu booted as expected.
The harddisk is not corrupt.It’s definitely the fog pxe file creating the problem.
-
Just to explain, I want to put Ubuntu 12 on all the old HP PCs as a way of both erasing the hard drives and also making it possible for the parents in the school to have a free linux PC if they want, instead of throwing them away.
But the real priority is getting the new Windows 8.1 HP clients deployed.
-
:eek: side stepped us there lol. so [U]Client is Ubuntu 12.04.4[/U]
-
i’m not sure why it is failing to boot to the hard drive of the computer after ipxe loads, but fog appears to be working properly. I would actually be willing to bet that if you took an image of the computer, then imaged it again with fog, it would work fine when not pxe booting. fog is typically used on windows clients, but many people have it working on linux as well.
-
sanboot --no-describe --drive 0x80 is the line in BootMenu.class.php that deals with how to pass to the harddrive. That said, not all systems like this method. If your systems are freezing. Try changing those lines to just say: exit.
Thank you,
-
a bit of research says that this is likely a hardware/firmware specific bug that occurs a lot on HP machines
-
Tom, do you think it would be a good idea to change that line from [CODE]sanboot --no-describe --drive 0x80 || goto MENU[/CODE] to [CODE]sanboot --no-describe --drive 0x80 || exit[/CODE] or would that not work, since it sounds like it may lock up on the first bit
-
Interesting comments and advice.
But to the real priority now: All the new PCs are HP Elite 8300.
Most are USDT (ultra slim) and some are SFF (Small form format).The BIOS in the SFF model allows the use of legacy network boot.
As I had hoped, it worked almost perfectly and I registered the client.
But note that the FOG pxe option window went past in a split second.
I had to reboot to catch it again. It was VERY fast. How can I slow that down?The USDT did not work. I have already had a long back and forth with Experts Exchange on how to get the network boot to work.
There are 2 ways.1 - UEFI boot options: IP4 Network boot at the top of the list.
I never saw any sign of the FOG page. It waited for the pxe file for a short time and then booted to windows. -
the PXE boot menu configuration page allows you to choose how long the menu shows up
