Posts made by caw001

Hello,

We are using Fog to image a host of HP Machines. 640’s, 840’s, desktops, laptops, etc…

We cannot seem to get the machines to boot to the Fog menu when Secure Boot is turned on.

The machine boots, receives an IP address, downloads the NBP file, then jumps right into bios with an HP Error Screen that reads “Selected boot image did not authenticate”.

Of course when we google this, it says to switch to legacy. Well we just converted our DHCP over to 2012 Server to hopefully get away from Legacy and start using EFI.

Anybody have any ideas on what we might need to do here to get this to work? We have had a hell of a time trying to get UEFI boots working.

Hello,

We are trying to image HP 640G3 and 840 G3/4 laptops. We’re unable to get the pc’s to boot to Fog using UEFI.

This same issue is also preventing us from imaging our Gen2 Hyper-V machines. We know UEFI is supported, but what is necessary to get these machines to boot?

If we reconfigure bios to enable Legacy support they boot fine, however that is not a great solution.

Thanks

@wayne-workman Ok thanks. I think we are going to find a way to do this through Powershell. We name our workstations with a combination of their asset tag #. So there is no logical way for Fog to figure that out and we really don’t want to have to go in and modify the host in between every image.
Thank you for the suggestions.

Correct. I understand it gives it a name, but it does not follow our naming convention. So let me rephrase the question, is there any way “customize” the name during the domain join?

Is there any way to rename the PC and join the domain during the imaging process?

@sebastian-roth Sorry, just spoke to her. (She’s working on trying our Mac capture at the moment). The issue she was experiencing at that moment was because she had no selected the OS type when setting up the capture. Once she did that we were able to successfully capture and image. That’s when we ran into the issue of restoring the image back to a larger disk and it not expanding to the full size.

@sebastian-roth I work with Robyn. This looks good. We are now able to boot and capture images. We are just having trouble restoring them back to drives of a larger size. I don’t see that covered in your guide anywhere unless I missed it. We are still continuing to test… But don’t don’t really have a resolution yet.

@george1421 Interesting. Ours are also EUFI I believe. Current model HP ProBook 640.

Does the boot type matter? Legacy vs EUFI?

@george1421 I am having the same issue. How do we get the image to deploy and utilize the full disk? I have a very similar disk setup. Standard Windows disk layout.

Hello,

We are testing with Fog and therefore turned off DHCP because we already have a dhcp server. However in testing in our isolated environment we realized we need the DHCP Services running on the fog server. How can I install/configure them now that Fog is already installed?

@george1421 Thank you. I “think” I am where I need to be, but still getting the same error. I created the host. I created the image (then went back and assigned it to the host) and then was able to schedule the capture task. However I am still getting the same error when trying to run the capture task from the machine.

Is there something else that I am missing?

@george1421 I’d like to say last question, but I know better… I managed to get my host registered. Whether or not this equates to scheduling the import I don’t know. However, after registering the host and selecting image deploy/capture I am getting the following error: see screenshot if it attaches

@george1421 You mentioned that when using the USB boot image that I need to schedule the import of the image as well as the imaging job itself. I am having trouble locating how to do that. I don’t see any way to create a new scheduled task. Are these supposed to be created under Import hosts?

@george1421 I’m guessing the last option is probably the one we would need to choose within our network. At least for now. WDS also uses PXE so I can’t mess with anything that will search for that on DHCP such as the DHCP Proxy.

Booting into the FOG engine is what I thought I was trying to do with the ipxe file. Apparently I did not understand what I was reading but I thought I would be able to point it directly at the FOG server for booting.

I’m using WinSCP on a Windows client.

We currently have a Windows WDS server in production on our network. We are testing FOG because of its ability to work with multiple operating systems. I cannot change our production DHCP to point to FOG for testing, so I am trying to create a bootable USB drive that I can use to PXE boot directly to the FOG server without using DHCP to get that information.

From the command line on the fog server if I try to cd to /tftpboot I receive the message no such file or directory. I’ve been unable to locate this folder.

Server

• FOG Version: 1.4.4
• OS: Ubuntu 16.4.4

Client

• Service Version:
• OS:

Description - Hello, I am trying to follow the guide to create a bootable USB drive for the PXE boot sequence. I am not totally new but not all that experienced in Linux. The guide says to go to /tftpboot/ipxe.efi and copy the ipxe.efi file, however I am unable to locate it in the Linux OS.

Can someone help me with the full path?