Great work !! :clap_tone1:
J
Best posts made by jmeyer
-
RE: Remove Legacy client and replace with latest new client?posted in FOG Problems
I just made a .bat with this inside and it looks to work fine.
@echo off msiexec /qn /x "FOG Service Installer.msi" msiexec /qn /i "FOGService.msi"Thank you.
-
RE: Remove Legacy client and replace with latest new client?posted in FOG Problems
@Wayne-Workman I’ll work a bit more on the script.
edit :IF %PROCESSOR_ARCHITECTURE%==AMD64 set programpath=%programfiles(x86)% IF %PROCESSOR_ARCHITECTURE%==x86 set programpath=%programfiles% IF EXIST "%programpath%\FOG\fog.ca.cer" GOTO END set FogServerIP=fogserver set GetID=wmic product where "Version like '3.0.29' and name like 'FOG Service'" get IdentifyingNumber for /F "skip=1 delims=" %%i in ('%GetID%') do if not defined ID set "ID=%%i" IF "%ID%" NEQ "" start /wait msiexec /x %ID% /q start /wait bitsadmin /transfer FOGService /download /priority normal http://%FogServerIP%/fog/client/FOGService.msi %temp%\FOGService.msi start /wait msiexec /i %temp%\FOGService.msi /quiet WEBADDRESS="%FogServerIP%" :ENDThis should works but I don’t know wwhy my download end in queue when there is nothing else to do and I can’t install client silently… I love computers…
-
RE: Send message to Slackposted in Feature Request
@sourceminer Hello, I never tested using a channel but using a private message works fine with test token.
You can also create your bot : https://my.slack.com/services/new/bot
Here is my conf :
-
WAPT snapinsposted in Tutorials
Hello,
I am working on WAPT packages import directly in snapins.
I am writing single line powershell script to rename to zip, extract to directory, find command and run it.This is my first test script for VLC from windows :
$packwapt = "tis-vlc_3.0.16-12_x64_windows_0f4137ed1502b5045d6083aa258b5c42_5.1_PROD.wapt"; $packname = [System.IO.Path]::GetFileNameWithoutExtension($packwapt); Copy-Item $packwapt $packname".zip"; Expand-Archive -LiteralPath $packname".zip" $packname; Remove-Item $packname".zip"; $s = Get-Content -Path $packname"\setup.py" | Select-String -Pattern "silentflags = "; if ($s -ne $null) { $s=[regex]::matches($s,'(?<=\").+?(?=\")').value; Get-ChildItem -Filter $packname"\*.exe" | ForEach {&$_.Fullname $s} }; Remove-Item $packname –recurse;I’m not sure where I am going and if this is useful… lol
-
RE: New FOG client shutdownposted in Bug Reports
@Jbob It’s working.
I found something else.
In the MSI détails, I don’t have the right version displayed.
It’s write : {16B0BCD7-423F-49A9-B757-E457D7312A33}Can you display version during install ?
Shouldn’t we be able to update client from tray or from GUI ?
I didn’t find how do this without overwriting.
-
RE: (SVN) Adding needed repository... Failed!posted in FOG Problems
@george1421 Just found proxy in ~/.bashrc
I run install again. -
RE: WAPT snapinsposted in Tutorials
I have review my first idea.
I have used Snapin Pack.
Zip the wapt and the ps1 script and it’s working for VLC WAPT package.Get-ChildItem -Filter '*.wapt' | ForEach { Set-Variable -Name packwapt -Value $_.Fullname Set-Variable -Name packname -Value $packwapt.Substring(0,$packwapt.Length-5) Copy-Item $packwapt $packname'.zip' Expand-Archive -LiteralPath $packname'.zip' $packname Set-Variable -Name s -Value (Get-Content -Path $packname'\setup.py' | Select-String -Pattern 'silentflags = ') if ($s -ne $null) { Set-Variable -Name s -Value ([regex]::matches($s,'(?<=\").+?(?=\")').value) Get-ChildItem -Path $packname -Filter '*.exe' | ForEach { Start-Process -FilePath $_.Fullname $s -Wait; } } }
-
RE: Fog 1.6 - Kernel Panicposted in Bug Reports
@Sebastian-Roth
I make new install of Fog under Debian.
I was using Ubuntu years ago so it’s old install (3 years old).I have been testing Fog version since years with Tom.
And as i work with VM, i can revert change easily. -
RE: (SVN) Adding needed repository... Failed!posted in FOG Problems
@george1421 Was this !! But needed a reboot after.
Thank you very much to all of you.
Latest posts made by jmeyer
-
RE: FOG Secure Boot with Shimposted in Tutorials
I remplaced grubx64 by grubnetx64 (not sure if needed but was recommanded for PXE) and create a “grub” directory in tftpboot with “grub.cfg” inside.
Grub signed look for cfg file in a subdir called “grub” by default.cp /usr/lib/grub/x86_64-efi-signed/grubnetx64.efi.signed /tftpboot/grubx64.efi mkdir /tftpboot/grub chmod -R a+rX /tftpboot/grubI get grub menu.
update (10 am) :
I copied snponly.efi in grub directory and signed it with the FOG-MOK key I generated before.sbsign --key /root/secureboot/FOG-MOK.key --cert /root/secureboot/FOG-MOK.crt /tftpboot/snponly.efi --output /tftpboot/grub/snponly.efiI end with “error ; bad shim signature”.
I think I need to import the key on the computer with command “mokutil --import /chemin/vers/FOG-MOK.der”I keep on searching…
2nd update (12:30 am):
To enroll key :
cp /usr/lib/shim/mmx64.efi.signed /tftpboot/mmx64.efiand in tftpboot/grub/grub.cfg
menuentry 'Enroll MOK' { insmod tftp insmod chain chainloader (tftp,192.168.69.10)/mmx64.efi boot } menuentry 'Boot FOG (iPXE)' { insmod efinet insmod tftp insmod chain net_bootp chainloader (tftp,192.168.69.10)/grub/snponly.efi boot }Copy the .der on usb key, put it on the computer, run “Enroll MOK” in pxe grub menu then “Enroll from disk”
Reboot and run “Boot FOG” in pxe menu.And at least I have the FOG menu !
I think I’m in the right way.
Let’s keep on working.
-
RE: FOG 1.6.0-beta.2644 DHCPposted in FOG Problems
@Tom-Elliott no, i have bypass dhcp configuration during install.
-
RE: FOG Secure Boot with Shimposted in Tutorials
Here is my first steps.
Install signing tools on your FOG server
apt update apt install sbsigntool openssl mokutilInstall shim & grub
apt install shim-signed grub-efi-amd64-signed cp /usr/lib/shim/shimx64.efi.signed /tftpboot/shimx64.efi cp /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed /tftpboot/grubx64.efiI end with this at PXE boot :
Shim signature give this : (sbverify --list shimx64.efi)
warning: data remaining[831016 vs 957136]: gaps between PE/COFF sections? signature 1 image signature issuers: - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 image signature certificates: - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Windows UEFI Driver Publisher issuer: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 issuer: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation Third Party Marketplace Rootand grub sinature return :
signature 1 image signature issuers: - /CN=Debian Secure Boot CA image signature certificates: - subject: /CN=Debian Secure Boot Signer 2022 - grub2 issuer: /CN=Debian Secure Boot CAI tried creating MOK key but I’m stuck with security violation :
mkdir /root/secureboot cd /root/secureboot openssl req -new -x509 -newkey rsa:2048 -keyout FOG-MOK.key -out FOG-MOK.crt -nodes -days 3650 -subj "/CN=FOG Secure Boot/" openssl x509 -in FOG-MOK.crt -outform DER -out FOG-MOK.derFOG-MOK.key <-- private key (protect!)
FOG-MOK.crt
FOG-MOK.der <-- enroll this on clientsSign ipxe.efi and rename it to grubx64.efi
cd /tftpboot cp ipxe.efi ipxe.efi.original sbsign --key /root/secureboot/FOG-MOK.key --cert /root/secureboot/FOG-MOK.crt /tftpboot/ipxe.efi --output /tftpboot/ipxe-signed.efi cp ipxe-signed.efi grubx64.efiI think I need to work more and as Fog default exit type is refind, I’ll make more research.
-
RE: FOG 1.6.0-beta.2644 DHCPposted in FOG Problems
drwxr-x— 2 _kea _kea 4096 8 juil. 12:39 /etc/kea
total 12
drwxr-x— 2 _kea _kea 4096 8 juil. 12:39 .
drwxr-xr-x 81 root root 4096 8 juil. 11:31 …
-rw-rw-r-- 1 root root 2236 8 juil. 12:39 kea-dhcp4.confPRETTY_NAME=“Debian GNU/Linux 13 (trixie)”
NAME=“Debian GNU/Linux”
kea-dhcp4
kea-lfc
/usr/sbin/kea-dhcp4 (938) kea-dhcp4I don’t have error log anymore.
-
FOG 1.6.0-beta.2644 DHCPposted in FOG Problems
Hello,
I have installed FOG 1.6.0-beta.2644 with DHCP.
I end withSetting up and starting DHCP Server (Kea)...................Failed Kea base configuration failed validation (kea-dhcp4 -t); see /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.2644.logError logs :
'/etc/kea/kea-dhcp4.conf' <-> '/etc/kea/kea-dhcp4.conf.1783500988' renommé Syntax check failed with: Unable to open file /etc/kea/kea-dhcp4.confThis break TFTP directory creation even with the -X option.
Looks to come from Kea.
root@FOGSERVERDEV:~/fogproject/bin# kea-dhcp4 -t /etc/kea/kea-dhcp4.conf Syntax check failed with: Unable to open file /etc/kea/kea-dhcp4.confTemporary fix is to run a second time installfog.sh and put a # before “configureDHCP”.
-
RE: FOG Secure Boot with Shimposted in Tutorials
@Florent @KMEH
First problem I see in the ipxe release is “x86-64 UEFI Secure Boot only”.
So, if SB is not enable, it doesn’t work at all ?
It also means that we need to make a SB check to say what efi file the computer need to use ?I’ll have some time this week, I’ll try make some tests.
-
RE: FOG Secure Boot with Shimposted in Tutorials
I don’t understand well everything but maybe it’s more complex than this and I understand nothing at all. haha
On my server I have a “shimx64.efi” in “/boot/efi/EFI/debian/” can I use it directy or I must install shim-signed and use the shimx64.efi.signed ?
-
RE: No pending hostposted in FOG Problems
Hello,
It’s working again.
I have update to the last version (1.6.0-beta.2273) but I’m not sure it’s fixed with this.
I have also clean DB using this : https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_CommandsThank you.
-
RE: No pending hostposted in FOG Problems
@Tom-Elliott Sorry for the lack of clarity in my explanations and the use of screenshots unrelated to my problem.
I have upgrade to the last beta and deploy on registered host works well.
Thank you.I’ll check if not registered host now appear in Pending Hosts.
-
RE: No pending hostposted in FOG Problems
@Tom-Elliott said in No pending host:
SELECT * FROM history;
It’s not my capture, it’s just to show what deploy task display on host.
Here is a screen of my version :
Here are the logs of this morning.
- I import host (412 to 437).
- Added them to groups to edit image ID and AD (438 to 445)
- Create deploys tasks and went to start computers.
- Seeing tasks was not starting, I tested to start task from PXE without deleting host on GUI (446 to 448) without luck.
- I have delete one host on GUI (449) then create an account with password and delete unused one (450 to 460).
- Run one task manually on one computer then on each other computer from PXE menu.
- I added imported all host after deploy (461 to end) to let fog rename and join domain.
| 412 | [2026-01-20 09:51:19] Host ID: 138 NAME: salle17-01 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 413 | [2026-01-20 09:51:19] MACAddressAssociation ID: 408 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 414 | [2026-01-20 09:51:19] Host ID: 139 NAME: salle17-02 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 415 | [2026-01-20 09:51:19] MACAddressAssociation ID: 409 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 416 | [2026-01-20 09:51:19] Host ID: 140 NAME: salle17-03 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 417 | [2026-01-20 09:51:19] MACAddressAssociation ID: 410 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 418 | [2026-01-20 09:51:19] Host ID: 141 NAME: salle17-04 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 419 | [2026-01-20 09:51:19] MACAddressAssociation ID: 411 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 420 | [2026-01-20 09:51:19] Host ID: 142 NAME: salle17-05 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 421 | [2026-01-20 09:51:19] MACAddressAssociation ID: 412 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 422 | [2026-01-20 09:51:19] Host ID: 143 NAME: salle17-06 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 423 | [2026-01-20 09:51:19] MACAddressAssociation ID: 413 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 424 | [2026-01-20 09:51:19] Host ID: 144 NAME: salle17-07 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 425 | [2026-01-20 09:51:19] MACAddressAssociation ID: 414 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 426 | [2026-01-20 09:51:19] Host ID: 145 NAME: salle17-08 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 427 | [2026-01-20 09:51:19] MACAddressAssociation ID: 415 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 428 | [2026-01-20 09:51:19] Host ID: 146 NAME: salle17-09 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 429 | [2026-01-20 09:51:19] MACAddressAssociation ID: 416 has been successfully updated. | fog | 2026-01-20 09:51:19 | 10.121.76.19 | | 430 | [2026-01-20 09:51:20] Host ID: 147 NAME: salle17-10 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 431 | [2026-01-20 09:51:20] MACAddressAssociation ID: 417 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 432 | [2026-01-20 09:51:20] Host ID: 148 NAME: salle17-11 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 433 | [2026-01-20 09:51:20] MACAddressAssociation ID: 418 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 434 | [2026-01-20 09:51:20] Host ID: 149 NAME: salle17-12 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 435 | [2026-01-20 09:51:20] MACAddressAssociation ID: 419 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 436 | [2026-01-20 09:51:20] Host ID: 150 NAME: salle17-15 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 437 | [2026-01-20 09:51:20] MACAddressAssociation ID: 420 has been successfully updated. | fog | 2026-01-20 09:51:20 | 10.121.76.19 | | 438 | [2026-01-20 09:52:07] Group ID: 12 NAME: TOUS has been successfully updated. | fog | 2026-01-20 09:52:07 | 10.121.76.19 | | 439 | [2026-01-20 09:52:21] Group ID: 12 NAME: TOUS has been successfully updated. | fog | 2026-01-20 09:52:21 | 10.121.76.19 | | 440 | [2026-01-20 09:52:49] Group ID: 12 NAME: TOUS has been successfully updated. | fog | 2026-01-20 09:52:49 | 10.121.76.19 | | 441 | [2026-01-20 09:53:10] Group ID: 13 NAME: SALLE 17 has been successfully updated. | fog | 2026-01-20 09:53:10 | 10.121.76.19 | | 442 | [2026-01-20 09:53:24] Group ID: 13 NAME: SALLE 17 has been successfully updated. | fog | 2026-01-20 09:53:24 | 10.121.76.19 | | 443 | [2026-01-20 09:53:29] Group ID: 13 NAME: SALLE 17 has been successfully updated. | fog | 2026-01-20 09:53:29 | 10.121.76.19 | | 444 | [2026-01-20 09:54:12] Group ID: 13 NAME: SALLE 17 has been successfully updated. | fog | 2026-01-20 09:54:12 | 10.121.76.19 | | 445 | [2026-01-20 09:54:40] Group ID: 12 NAME: TOUS has been successfully updated. | fog | 2026-01-20 09:54:40 | 10.121.76.19 | | 446 | [2026-01-20 10:11:38] Task ID: Name: Hardware Inventory Task - salle17-12 2026-01-20 10:11:38 has failed to save. Error: Required database field is empty: storagegroupID -> val: 0 | fog | 2026-01-20 10:11:38 | 10.121.76.19 | | 447 | [2026-01-20 10:11:49] Task ID: Name: Hardware Inventory Task - salle17-12 2026-01-20 10:11:49 has failed to save. Error: Required database field is empty: storagegroupID -> val: 0 | fog | 2026-01-20 10:11:49 | 10.121.76.19 | | 448 | [2026-01-20 10:11:54] Task ID: Name: Hardware Inventory Task - salle17-12 2026-01-20 10:11:54 has failed to save. Error: Required database field is empty: storagegroupID -> val: 0 | fog | 2026-01-20 10:11:54 | 10.121.76.19 | | 449 | [2026-01-20 10:12:05] Host ID: 149 Name: salle17-12 has been successfully destroyed. | fog | 2026-01-20 10:12:05 | 10.121.76.19 | | 450 | [2026-01-20 10:14:15] HookEvent ID: 159 NAME: USER_ADD_FIELDS has been successfully updated. | fog | 2026-01-20 10:14:15 | 10.121.76.19 | | 451 | [2026-01-20 10:14:49] HookEvent ID: 160 NAME: USER_ADD_POST has been successfully updated. | fog | 2026-01-20 10:14:49 | 10.121.76.19 | | 452 | [2026-01-20 10:14:50] User ID: 2 NAME: emmir has been successfully updated. | fog | 2026-01-20 10:14:50 | 10.121.76.19 | | 453 | [2026-01-20 10:14:50] HookEvent ID: 161 NAME: USER_ADD_SUCCESS has been successfully updated. | fog | 2026-01-20 10:14:50 | 10.121.76.19 | | 454 | [2026-01-20 10:15:09] HookEvent ID: 162 NAME: USER_GENERAL_FIELDS has been successfully updated. | fog | 2026-01-20 10:15:09 | 10.121.76.19 | | 455 | [2026-01-20 10:15:09] HookEvent ID: 163 NAME: USER_CHANGEPW_FIELDS has been successfully updated. | fog | 2026-01-20 10:15:09 | 10.121.76.19 | | 456 | [2026-01-20 10:15:09] HookEvent ID: 164 NAME: USER_API_FIELDS has been successfully updated. | fog | 2026-01-20 10:15:09 | 10.121.76.19 | | 457 | [2026-01-20 10:15:32] HookEvent ID: 165 NAME: USER_DELETE_POST has been successfully updated. | fog | 2026-01-20 10:15:32 | 10.121.76.19 | | 458 | [2026-01-20 10:15:32] User ID: 2 Name: emmir has been successfully destroyed. | fog | 2026-01-20 10:15:32 | 10.121.76.19 | | 459 | [2026-01-20 10:15:32] HookEvent ID: 166 NAME: USER_DELETE_SUCCESS has been successfully updated. | fog | 2026-01-20 10:15:32 | 10.121.76.19 | | 460 | [2026-01-20 10:16:16] User ID: 3 NAME: 1234 has been successfully updated. | fog | 2026-01-20 10:16:16 | 10.121.76.19 | | 461 | [2026-01-20 11:11:26] Host ID: 151 NAME: salle17-01 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 462 | [2026-01-20 11:11:26] MACAddressAssociation ID: 421 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 463 | [2026-01-20 11:11:26] Host ID: 152 NAME: salle17-02 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 464 | [2026-01-20 11:11:26] MACAddressAssociation ID: 422 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 465 | [2026-01-20 11:11:26] Host ID: 153 NAME: salle17-03 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 466 | [2026-01-20 11:11:26] MACAddressAssociation ID: 423 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 467 | [2026-01-20 11:11:26] Host ID: 154 NAME: salle17-04 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 468 | [2026-01-20 11:11:26] MACAddressAssociation ID: 424 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 469 | [2026-01-20 11:11:26] Host ID: 155 NAME: salle17-05 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 470 | [2026-01-20 11:11:26] MACAddressAssociation ID: 425 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 471 | [2026-01-20 11:11:26] Host ID: 156 NAME: salle17-06 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 472 | [2026-01-20 11:11:26] MACAddressAssociation ID: 426 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 473 | [2026-01-20 11:11:26] Host ID: 157 NAME: salle17-07 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 474 | [2026-01-20 11:11:26] MACAddressAssociation ID: 427 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 475 | [2026-01-20 11:11:26] Host ID: 158 NAME: salle17-08 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 476 | [2026-01-20 11:11:26] MACAddressAssociation ID: 428 has been successfully updated. | fog | 2026-01-20 11:11:26 | 10.121.76.19 | | 477 | [2026-01-20 11:11:27] Host ID: 159 NAME: salle17-09 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 478 | [2026-01-20 11:11:27] MACAddressAssociation ID: 429 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 479 | [2026-01-20 11:11:27] Host ID: 160 NAME: salle17-10 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 480 | [2026-01-20 11:11:27] MACAddressAssociation ID: 430 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 481 | [2026-01-20 11:11:27] Host ID: 161 NAME: salle17-11 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 482 | [2026-01-20 11:11:27] MACAddressAssociation ID: 431 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 483 | [2026-01-20 11:11:27] Host ID: 162 NAME: salle17-12 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 484 | [2026-01-20 11:11:27] MACAddressAssociation ID: 432 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 485 | [2026-01-20 11:11:27] Host ID: 163 NAME: salle17-13 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 486 | [2026-01-20 11:11:27] MACAddressAssociation ID: 433 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 487 | [2026-01-20 11:11:27] Host ID: 164 NAME: salle17-14 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 488 | [2026-01-20 11:11:27] MACAddressAssociation ID: 434 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 489 | [2026-01-20 11:11:27] Host ID: 165 NAME: salle17-15 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 490 | [2026-01-20 11:11:27] MACAddressAssociation ID: 435 has been successfully updated. | fog | 2026-01-20 11:11:27 | 10.121.76.19 | | 491 | [2026-01-20 11:11:58] Group ID: 13 NAME: SALLE 17 has been successfully updated. | fog | 2026-01-20 11:11:58 | 10.121.76.19 | | 492 | [2026-01-20 11:12:10] Host ID: 151 NAME: salle17-01 has been successfully updated. | fog | 2026-01-20 11:12:10 | 10.121.76.19 | | 493 | [2026-01-20 11:12:14] Host ID: 151 NAME: salle17-01 has been successfully updated. | fog | 2026-01-20 11:12:14 | 10.121.76.19 |