Posts made by pbriec

Hi everybody,

I’m going crazy. The Fog client doesn’t work anymore and i don’t know to solve this problem.
I’ve updated to latest fog 1.5.10.1629 on debian 11
I’m running fog client 0.13
here is the fog.log

05/12/2024 16:48:42 Main Overriding exception handling
05/12/2024 16:48:43 Main Bootstrapping Zazzles
05/12/2024 16:48:43 Controller Initialize
05/12/2024 16:48:43 Controller Start

05/12/2024 16:48:43 Service Starting service
05/12/2024 16:48:51 Bus Became bus server
05/12/2024 16:48:51 Bus Emmiting message on channel: Status
05/12/2024 16:48:51 Service Invoking early JIT compilation on needed binaries

---

--------------------------------Authentication--------------------------------

05/12/2024 16:48:51 Client-Info Version: 0.13.0
05/12/2024 16:48:51 Client-Info OS: Windows
05/12/2024 16:48:51 Middleware::Authentication Waiting for authentication timeout to pass
05/12/2024 16:48:51 Middleware::Communication Download: http://172.16.0.8/fog/management/other/ssl/srvpublic.crt
05/12/2024 16:48:52 Middleware::Authentication Cert OK
05/12/2024 16:48:52 Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
05/12/2024 16:48:52 Middleware::Authentication ERROR: Could not get security token
05/12/2024 16:48:52 Middleware::Authentication ERROR: Le fichier ‘C:\Program Files (x86)\FOG\token.dat’ est introuvable.
05/12/2024 16:48:52 Middleware::Communication POST URL: http://172.16.0.8/fog/management/index.php?sub=requestClientInfo&authorize&newService
05/12/2024 16:48:52 Middleware::Response Invalid security token

Can anybody help me, please?
Snapins doesn’t work anymore, i can’t shutdown machines using Power management. It’s very annoying.

I’ve reboot server, client, it doesn’t change.

thanks in advance
Pierre

Hi,

Since several months now, i have some troubles with scheduled shutdown.
PCs have 2 shutdown tasks (5.30PM & 8PM)
I have last fog client 0.13. The 2 tasks are displayed in the Power management page.
Snapins works well.
My PCS are mostly W11 and i’m wondering if the problem come from that.
Can someone help with that? My software update launchs at shutdown so it’s a bit problematic for me.

thanks for your help
Pierre

@JJ-Fullmer it’s a dell usb-c ethernet adapter.
I don’t understand what is wrong. I’ve ever managed to wake up the laptop but it don’t work at all time.
I thought it came from the New fog but i was wrong. I’ve tested with old one, doesn’t work.
As i’m using VM for fog, i’m able to switch between the two version using Snapshot.
Even with old fog, it doesn’t start. Very strange.
Another laptop with builtin ethernet port is working fine.
The specs of the usb-c ethernet adapter is quite clear, it supports wake on lan https://www.dell.com/fr-fr/shop/adaptateur-dell-usb-c-vers-ethernet-25-gbit-s/apd/470-bcfv/wi-fi-et-gestion-de-réseau

@Tom-Elliott

Ok, i’ve updated the init.xz and init_32.xz files. I confirm that i do not have to set the kernel args now.
I’ve registered the laptop from scratch and now it’s the correct mac address.

I’ve noticed some bad things with this new FOG.

An old laptop can be woken up and FOG create a task that is not automatically deleted after.
This new laptop with USB adapter cannot be woken up and the task is remaining in the actives tasks.

I’ve never managed to wake up this new laptop
In the new Fog, i have the following error: “DataTables warning: table id=host-snapin-history-table - Ajax error. For more information about this error, please see https://datatables.net/tn/7”
So it doesn’t start the PC, and if i wake up it manually, it will boot to fog trying to do something that failed.
refind also doesn’t boot correctly the PC.

So the new fog is fine about the mac address problem but the fonctionnalities are strange
Have you noticed that?

Pierre

Hi @Tom-Elliott,

So i’ve tested and it seems to work.
Now, i’ve the same MAC address both in compatibiliy mode and after dhcp process.
I’ve read again my notes and i can’t manager to wake up with WOL.
I don’t know what is wrong.
I will contact Dell tomorrow. I remember it was working before.
I’ve tested another laptop with ethernet, and it’s working fine.
The WOL processus could be unmanaged with usb ethernet adapter?

thanks
Pierre

@george1421 @Tom-Elliott

i’ve downloaded and installed the last kernel 6.1.63 (both x64 & x86).
I still get the mac’s dongle address in the compatibility menu. In debug menu, all is fine.

@Tom-Elliott

how to check that?
I’ve seen that in FOG Configuration: bzImage and bzImage32
I’ve never updated kernel in FOG

Hi @Tom-Elliott

is there any workaround?
thanks

Pierre

@Tom-Elliott

yes, in FOG Configuration > FOG Settings > General Settings > KERNEL ARGS
domacset=1

I hope it’s in the right place.
Pierre

@george1421 @Tom-Elliott

Hi, sorry for the late answer, i’m not everyday in that office, and i can’t make tests at any time.
Ok, so i’ve downloaded and installed the init.xz provided in the other thread.
Now, if i set the PC in debug mode, and run the two command lines.
The laptop is now recognized with 28:xxxxxxxx mac address.
But if i run the compatibility mode in FOG menu, MAC address is 0C:xxxxxxxxx
So i’ve deleted the PC in fog UI, and try a full inventory. The mac address is 0C:xxxxxxxx
So it still doesn’t work

Hi @Tom-Elliott

i’ve run the debug mode and tried the two command lines
The result is the same: mac 0C:xxxxxxxx

anyway, dhcp and tftp before fog menu is using 28:xxxxxxxx mac address

Hi,

i have a question related to FOG and USB-C Ethernet Adapter.
The USB-C Ethernet Adapter has his own MAC Address (0C:xxxxxxxxx)
The Laptop Dell Latitude 3340 (without built-in ethernet port) has all options related to WOL and PXE in the BIOS. The MAC Address passthrough is also configured.
In Windows, with command line “ipconfig /all”, i can see the MAC Address from the PC with passthrough (28:xxxxxxxx)

If i boot to NIC USB, i can see the DHCP check the mac address (28:xxxxxxxxx). FOG doesn’t recognize the PC so i’m starting the full inventory.
When, i check back the inventory in FOG, i can see FOG has registered the PC with the USB-C adapter Mac address (0C:xxxxxxxxx)
If i manually change the mac address in FOG UI then it is recognized by FOG and i can WOL it. I have to check if i can boot it to PXE from WOL.
How FOG can register the good mac address (28:xxxxxxxx) and not the bad one (0C:xxxxxxx)

All the 30 laptops will be in charging cart with ethernet connections. So i want to use ethernet WOL to PXE to deploy images to PCs.

thanks for your answer. I’ve search in the forums but i didn’t find the same case.
Pierre

good job! you are the best.

it seems to work with my VM. I will try with the Opliplex 5260 very soon. I’m not on the same working place today.

thanks
Pierre

@george1421
only that

#!ipxe
chain tftp://172.16.4.8/default.ipxe

Hi @george1421, thanks for taking time to solve this problem

here is my lan where x=0 for site1 and x=4 for site2. They have both the same configuration.

my DHCP/DNS server are 172.16.x.3
my FileServer/TFTPBOOT are 172.16.x.5
my FOG Server are 172.16.x.8

:call_fog
set next-server 172.16.4.8
iseq ${platform} efi && set filename ipxe.efi || set filename undionly.kpxe
chain tftp://${next-server}/${filename}

here is the output from my vm when i hit the new item call_fog

thanks
Pierre

@george1421

Ok, i’ve made some changes on my systems
As i’ve already a pxe server on my enterprise, i’ve tried to swap the PXE server in the configuration so now, the FOG pxe server is the main pxe server. I’ve made changes on the dhcp server.
I’ve deleted the host with FOG gui and now, i can access the full inventory.

How can i use 2 pxe server by using pxe chainloading?
BOOT --> 1st PXE server --> chainloading to FOG iPXE server
What is the best practices?
here is what i have on the pxe menu config

:fogpxe
dhcp
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
#chain http://172.16.6.157/fog/service/ipxe/boot.php?mac=${net0/mac}
chain http://172.16.0.8/fog/service/ipxe/boot.php?mac=${net0/mac}

in fact, all was commented except last line.
If the lines are uncommented, it does’nt boot to FOG from my iPXE server

I’m using the other pxe server for other purposes than FOG
Can you help me?

@george1421

I’ve updated the bios firmware, nothing change.

I’ve tried your FOS and it is starting so the problem come from ipxe

Pierre

@Sebastian-Roth

thanks for your answer
Ok, here is the output with a USB UEFI key

done
exit_boot...

@george1421

I’ve run again the installer. It is the same

@Sebastian-Roth

in fact, i’m new in the FOG world. I’ve tested the pxe with another PC and i can access the Full Inventory. With VMs, it also works. Now i have to deploy 50Pcs with Optiplex 5260 configuration :-(. I hope i will not have to deploy by hands

I don’t have to make videos as here is the output (no bootloop)

Kernel.SR.SKIP_PCI.4.8.11.64... ok
init.xz... ok
done
exit_boot..._

thanks
Pierre

Hi @george1421

thanks for you answer.

I’ve tried to change the kernel by the FOG Configuration page. I also try by hand, but it’s the same.
As soon as the kernel and inits are sent, it returns to the FOG pxe menu. It’s very fast.

What do you mean by latest firmware, the latest BIOS of the PC?
Of course, i’ve disabled the Secure boot.

So i will try tomorrow the kernel 4.15.2, it should work?

thanks
Pierre