Posts made by louis.tasse

Hello george1421,

Got everything working with the USB client.

Thank you for your help.

Louis.

((/assets/uploads/files/1685636674613-fos-usb-01-resized.jpeg) /assets/uploads/files/1685636634643-fos-usb-01-resized.jpeg) @george1421 said in Using FOG without PXE - FOG client on USB key:

https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

Hello george1421,

Got your image, created a USB bootable key (using Rufus) and booted the computer with success. While I was able to get a Fog menu and work with all items except the “1. Fog Image Deploy/Capture”. I tried first (scenario #1) by selecting the item menu and received errors. I then (scenario #2) tried to set a job on the Fog server for a “deploy” for the computer and got a different set of errors the most important seemed to be “unable to locate image store”. Attached are the pictures showing the logs/errors.

Thanks.

Louis.

—> Fog
—> scenario #1 (selecting item menu #1)
—> scenario #2 (selecting item menu with a configured “deploy” job on Fog server)

@RipAU,

Thank you for replying to my support post.

I am trying to understand how your solution works:

1. your create a bootable USB key and boot from it: any specifics on the bootable device?
2. you take the above mention shell script and install it on the USB key?
3. you invoke the shell script which will point to the Fog Server and mimic a typical PXE request?
4. the end results of the script completion is that the Fog runtime is loaded on the device and the resulting Fog menu?

Thanks.

Louis.

Hello george1421,

Thank you for your prompt reply.

Contrary to my recommendation, our organization decided to go with a commercial solution (Ghost @ Broadcomm) and was not able to configure their new DHCP server (BlueCat) to accommodate two PXE servers…

While I would like to continue to use my Fog server, I am left without PXE/network boot. Unfortunately, our environment has 5 different VLAN’s, 3 of them being classrooms and one where the Fog Server is sitting. Upon reading the documentation on “Fog without PXE”, I understand that using a USB client reduces Fog functionality which is fine for doing what I intent to do.

Then yes, if you can provide a starter image for network USB booting that would be awesome.

Greatly appreciated.

Louis.

Hello,

Our organization will not provide its DHCP server to serve our FOG PXE server and thus must rely on a FOG client on a USB key.

As such I have tried using the following procedure “https://forums.fogproject.org/topic/6532/usb-boot-target-device-into-fog-os-live-fosl-for-debugging” to create the FOG client. Unfortunately, I have encountered a problem when trying to install the “grub” bootloader from the command:

sudo grub-install --force --no-floppy --boot-directory=/mnt/boot /dev/sdX

and getting the following error:

Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.

Is there an up-to-date procedure to create the FOG USB client as I believe this may related to new EFI technology?

Specifications on procedure

Fog server (@ version 1.5.10) on Ubuntu
USB client created on Kali Linux

Thank you.

Louis.

@louis.tasse

Problem solved! Thanks!

Louis.

@louis.tasse Thank you prompt replies. I will update to the latest release and keep you posted.

Wayne, you are right if I leave the newly imaged workstation into “Legacy Mode” the workstation cannot see any bootable device on the hard drive. When in “UEFI Mode”, the workstation will boot up accordingly but only if the captured image was done as “RAW”.

Louis.

Cannot deploy UEFI base Windows 10 install.

Server --> FOG version: Running Version 1.3.5-RC-10
SVN Revision: 6066

Client --> ASUS AIO C240z running Windows 10
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
I am unable to deploy a UEFI Windows 10 image correctly. I can capture the image and then deploy it, but when I boot the newly imaged Windows 10 PC I’m getting an error message as follows (blue screen):

Recovery
Your PC/Device needs to be repaired
A required device isn’t connected or can’t be accessed.
Error code: 0xc00000225
You’ll need to user recovery tools.  If you don’t have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.

With the proper Windows 10 Repair Disk I can set the bootloader to point to the right EFI partition with the following commands:
Open Windows Command Prompt

1. diskpart
2. list volume
3. select volume # (# is the volume number matching “EFI”)
4. assign letter=Z
5. exit
6. bcdboot C:\Windows /s Z: /f UEFI
7. system reboot

How can this problem be fixed. If I image the workstation as RAW image everything is fine.

Thank you.

Louis.