@julio I think my translation is not 100% good. I read “No my firewall is active” from your post.

If you run this command from the FOG server linux command prompt do you get “active”
sudo ufw status

If yes, we turn it off with sudo ufw disable This should respond with stopped and disabled.

When the firewall is off the target computer should connect to FOG server.

@devrick You will still need to glue all of the bits together but in principal it is possible to do and should work well.

@devrick The bash script variables are listed towards the bottom of this post. https://forums.fogproject.org/post/69723

The code to update the registry is listed in the fog.copydrivers section of this post: https://forums.fogproject.org/post/105078

So how should you start, but looking over this tutorial: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

I would copy over the fog.custominstall script as is.

Create a new bash script that looked similar to the fog.copydrivers script from the above post. Name it fog.updatereg

#!/bin/bash
regfile="/ntfs/Windows/System32/config/SOFTWARE"
key="\Microsoft\Windows\MyTags\SystemTag"
devtag= ${othertag1}
reged -e "$regfile" &>/dev/null <<EOFREG
ed $key
$devtag
q
y
EOFREG

Change the regfile and key to the appropriate ones for your enviornment.

Finally update the fog.custominstall replacing the line with fog.copydrivers with fog.updatereg. And the last bit is to hook the fog.custominstall script into fog by following the fog.postdownload section of this post: https://forums.fogproject.org/post/105078

You will need to do this with a FOG Post install script. Let me see if I can get an example for you.

@bdrucci said in FOG Install Error:

unable to ping site and verified that firewalls are not blocking.

Ok this confused me a bit. Can you ping “rpms.remirepo.net” or not? If not is the name resolving to an IP address on the FOG server? Right now its not clear if the issue is a DNS issue (name look up) or a ping issue (connectivity). Its also possible that the remi repo is off line too.

@paul-0 said in Ideale FOG omgeving voor Refurbish afdeling:

So i connect the utp then disable secureboot manualy…then on the fog console push an image… that is the most ideal option. But is that possible?

You can do this using the load and go approach. You would disable secure boot at the target computer then pxe boot into the FOG iPXE menu, then select deploy image from the iPXE menu. You never have to register the computer with FOG. But understand Load and Go method (without registering) means you will not be able to manage the target computer with FOG once the image is deployed.

@paul-0 I think we have a little confusion on how you think FOG works.

You can deploy a single image to a single computer using the FOG Push unicast image.

If your network supports it, you can push a single image to 30 computers all at one using the multicast imaging.

Both ways work but the target computer must be able to take the image you can not mix uefi and bios computers using the multicast method.

Now there is a procedure that system builders can use when using FOG. In this case a system builder will build a computer using FOG and then sell that computer. The FOG server will never see that computer again so there is no need to register the computer with FOG. This procedure is what I call “Load and Go” (load the OS and the target computer Goes some place else).

To use the Load and Go method there are a few requirements.

1. The target image must be full contained in that once the FOG server pushes the image, the FOG server will forget about the computer. The target computer will not have the FOG Client installed so no system renaming, or connecting to AD when using Load and Go (unless you are using an unattend.xml file, then the unattend.xml file can do all of those tasks).
2. The target image must have all of the needed drivers in the image or have the FOG server transfer the drivers post image push

@julio The showmount command is showing the NFS shares that are configured on the FOG server. This is correct.

Did you disable the ubuntu firewall on this FOG server? Something is blocking the NFS mount command from working on pxe boot computer to FOG server.

Is the FOG server and pxe booting target computer on the same TCPIP subnet?

@epsilon52 We that is interesting why they would be different then not. I know at one time we suggest that people use an old boot loader with the surface systems because (at the time) the updated ipxe boot loaders were crashing on the surface devices. The version check was to see if there is a different ipxe boot loader coming into play between the working and not working target computers.

@bdrucci Does your fog server have direct access to the internet?

If not, do you need to go through a proxy server to get to the internet?

Hiren’s BootCD PE x64 (v1.0.1)

Configuration currently works for UEFI only. It appears the wim file is missing bootmgr.exe for the BIOS booting systems

Be aware that your target computer will need at least 4GB of ram to deploy this image. The boot.wim file is 1.3GB in size. So you need 1.3GB of RAM just for the disk image, and then additional RAM to run the OS once its booted

1. First we’ll create the required directories:

mkdir -p /tftpboot/os/Hiren101

2. Now we’ll mount the WinPE iso over the loop directory. Then we’ll copy the contents of the DVD to the directory we built above.

mount -o loop /{full path where you have the iso stored}/HBCD_PE_x64.iso /mnt/loop

cp /mnt/loop/BOOTMGR /tftpboot/os/Hiren101
cp /mnt/loop/boot/bcd /tftpboot/os/Hiren101
cp /mnt/loop/boot/boot.sdi /tftpboot/os/Hiren101
cp /mnt/loop/sources/boot.wim /tftpboot/os/Hiren101
umount /mnt/loop

3. Download and install the latest wimboot kernel and extract it from the zip file. 10-Aug-21: There has been changes to the Hiren's wim file since this tutorial was created. To get Hiren's to properly boot you need to use winboot version **2.7.3** or later found here: https://github.com/ipxe/wimboot/blob/master/wimboot
   The issue was discussed in this post: https://forums.fogproject.org/post/144293

cd /tmp
wget http://git.ipxe.org/releases/wimboot/wimboot-latest.zip
unzip wimboot-latest.zip

4. Copy the wimboot file from the archive directory to root of the os directory (we’ll need this for every windows boot media, so we’ll place it in a common spot).

cp ./wimboot-2.6.0-signed/wimboot /tftpboot/os

5. The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS.
6. In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry
   Set the following fields
   Menu Item: os.Hiren101
   Description: Hirens BootCD PE x64 (v1.0.1)
   Parameters:
   set tftp-path tftp://${fog-ip}/os
   set pe-path ${tftp-path}/Hiren101
   kernel ${tftp-path}/wimboot gui
   imgfetch --name BCD ${pe-path}/bcd BCD
   imgfetch --name boot.sdi ${pe-path}/boot.sdi boot.sdi
   imgfetch --name bootmgr ${pe-path}/BOOTMGR bootmgr
   imgfetch --name boot.wim ${pe-path}/boot.wim boot.wim
   boot || goto MENU

@mikr said that this parameter block worked with Hiren BootCD 1.0.2 in uefi mode ref: https://forums.fogproject.org/post/146996 Well done!

set tftp-path tftp://${fog-ip}
set http-path http://${fog-ip}/images/tools/hbcd102
kernel ${tftp-path}/win/wimboot gui
imgfetch --name bootmgr.exe ${http-path}/bootmgr.exe bootmgr.exe
imgfetch --name bootx64.efi ${http-path}/efi/boot/bootx64.efi bootx64.efi
imgfetch --name BCD ${http-path}/boot/bcd BCD
imgfetch --name boot.sdi ${http-path}/boot/boot.sdi boot.sdi
imgfetch --name boot.wim ${http-path}/sources/boot.wim boot.wim
boot || goto MENU

7. That’s it, just pxe boot your target system and pick ** BootCD PE x64 (v1.0.1)** from the FOG iPXE boot menu.

References: None

@seppim /var/www/html is the base path of the apache server. FWIW the fog program is installed in /var/www/html/fog directory. Its not required to save your iso to the fog directory. But since you are using just the ISO image that also implies you are using memdisk, which is a bios only program. UEFI systems will not be able to use this method of booting.

@seppim While I don’t use hiren’s software, let me download the iso and see what has changed. I know it worked at one time.

@epsilon52 Is the ipxe build version the same number between the working system and not working system. In the OP the build number is g3475f confirm that you are using the same build number between working and not.

@julio Ok if we look back at your 2nd post with the could not connect error.

Is 192.168.56.20 the IP address of your fog server?

If yes did you remember to turn off the linux firewall on that ubuntu server?

If yes then run the following command on the linux console of your fog server. showmount -e 127.0.0.1 That command will show us the exported shares from the FOG server.

@epsilon52 The installer should replace all of the ipxe boot files when it recompiles the boot loaders. Its all of the ipxe files not just the two I mentioned.

@epsilon52 domain shift in DNS domain or windows domain? If your DNS names are different that may have an impact on FOG.

Either way the error is that the certificates for ipxe (ipxe.efi and undionly.kpxe) don’t currently match what apache is running as.

I don’t know if you can fix it by rerunning the installer with the -S switch or not. I have not personally worked with FOG and SSL.

@julio Please help us with what problem you are trying to solve here? You are attempting to use both /home/fog/images/ and /images/ in your fog configuration. There are real reasons to do what you are trying to do. We just want to make sure it fixes your problem and you are just not creating another problem that will haunt you like a ghost in the future.

@julio Please provide a clear picture of the error taken with a mobile phone. Upload the picture to this thread or post a link to the picture. The solution to the problem depends on what error message is displayed.

@epsilon52 The quick answer is the certificate used for apache (HTTP) is not the same certificate used when ipxe.efi was compiled.

How did you enable the https service in the web server? Did you run the fog installer script with the -S option to enable https in FOG?