The problem was the client version. (old version: 0.9.12)
I had to install the new one on each computer (0.11.9), then reboot each computer.
Then “reset encrypted data” on the group
Now it works fine.
I thought that once there was a new version on the server the client updated “alone”.

@wayne-workman i used " your packages line" and it seems to work.
Then now i have to test pxe boot, capture and deploy !!

THanks for your help

@george1421
Hello, it seems that the problem came from the configuration left over on the workstation, which still contained snappins that were no longer needed and no longer applicable.
.

Hi, I’m looking for a solution to customize the default profile (Windows 10 and 11).
I don’t want to use the “sysprep + copyprofile” solution.
Profiletool seems to be out of development and neither does defprof.
And defprof doesn’t seem to create a “clean” profile, as we have a lot of problems with startup times once defprof has been applied.
So if you have a miracle solution for this kind of task, I’d love to hear from you!
Thanks in advance for your help.
Pascal

@need2 now i agree with you : if you accept that mysql root has no password
and if you know that if installer told you to go to http://192.168.39.243/fog it means you have to go to http://192.168.39.243/html/fog.
I know it’s a ridiculous bug of the default installer (without parameters) but it disturbed me

any way fog seems to be a great program, the forum is very reactif and it permit me to go on
Then thanks again for your help i appreciate
sorry for my poor english
@Tom Elliot : i will try with --docroot to tell you if it works.
But can you confirm me that the installer without parameters make a mistake between http://192.168.39.243/fog and http://192.168.39.243/html/fog to be sur we are agree ?

Thanks again for your help everybody !!

Hello,
in first thank a lot for your answer.
For my test i’m going to work with a virtual machine with only one interface, then forget the “3 networks”
I begin by installing fog like that :
(i use my own dhcp server)

Type d’installation : N
IP du serveur FOG : 192.168.39.243
Would you like to setup a router address for the DHCP server? : n
Would you like to setup a DNS address for the DHCP server and client boot image? : n
Would you like to change the default network interface from eth0? : n
Would you like to use the FOG server for DHCP service? n
This version of FOG has internationalization support, would you like to install the additional language packs? n

My own dhcp server is configured like that (it has 192.168.39.247 for ip address):
subnet 192.168.39.0 netmask 255.255.255.0 {
range 192.168.39.40 192.168.39.230;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.39.255;
option routers 192.168.39.254;
next-server 192.168.39.247;
filename “pxelinux.0”;
}
then next server is the dhcp server itself

Here is a part of the PXE configuration (on my own dhcp server. (The dhcp server act as dhcp, tftp and pxe server)

DEFAULT vesamenu.c32
KBDMAP fr.kbd
MENU BACKGROUND splash.jpg
menu color title 1;37;40 #ffffffff #00000000 std
menu color timeout_msg 37;40 #80ffffff #00000000 std
menu color timeout 1;31;40 #ffff0000 #00000000 std
menu color border 30;44 #00000000 #00000000 none

TIMEOUT 300
ALLOWOPTIONS 0
PROMPT 0

MENU TITLE MENU
LABEL BootNormal
MENU LABEL Boot local
MENU DEFAULT
COM32 chain.c32
APPEND hd0

LABEL Drivers_Universels
MENU LABEL Drivers Universels
KERNEL memdisk
APPEND keeppxe floppy initrd=ghost/universels.img

LABEL hdt
MENU LABEL Hardware Detection Tool
COM32 hdt/hdt.c32
APPEND modules=hdt/modules.pcimap pciids=hdt/pci.ids

LABEL memtest
MENU LABEL Memtest86+
LINUX hdt/memtest86±4.20.bin

My question is how i could add entry for fog server using ipxe while i’m iusing pxe (pxelinux.0)
Thanks again for your help

Hello, i think i’ve got the same problem except i made modification on the web interface :
i didnt want the “images” directory be at the root (/images)
then i copy the images directory into /home/images.

Then i modify the image path on the web interface, i thought it would modify the export file also but it seems not.

then i had to modify manualy the export file. Now it works fine.
Could it be the problem ?

@Jbob Hello
In first sorry for this long delay
I just made the test today with the latest client. Everything seems to work fine !!

@Wayne-Workman said:

@plegrand said:

It’s not our dns servers

You don’t have to use them. You can make your own and direct all hosts to use yours.

I install dynamique DNS with bind and it works fine. Thanks again

@Wayne-Workman
I just made the test unicast (deploy and not multicast)
It’s a room with 12 stations.
2 stations failed
10 works fine (1.6 GB/min)
i’ll tell you more tomorrow

I have just upgraded from Debian 11 to Debian 12.
No problems except this error in the apache logs:
[proxy:error] [pid 2033] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (127.0.0.1:9000) failed
and unable to access Fog.
I re-run “installfog.sh” and everything seems to be working correctly.
I don’t use LDAp so I don’t have any problems there.
Thanks

@Sebastian-Roth
Hello, I’ll get back to you to know if, today, it’s possible to consider migrating our fog server from debian 11 bullseye to debian 12 bookworm (FOG 1.5.10).
Thank you in advance for your help.

@george1421
None of our switches are configured with dhcp snooping and everything works fine.
The only problem is this room with these network cards.

@george1421
Hello george1421 and thanks for your answer

• Our dhcp server is a separate server not running on the fog server
• It’s the only dhcp server on the network.
• It works very fine and we have no problem for all computers of our network.
• We use this switch for other computers without problem
• dhcp snooping is for multicast no ?
  The only problem is for these computers with these kind of NIC

Thanks again

For information, this is our dhcp configuration:
…/…
option client-architecture code 93 = unsigned integer 16;
…/…

…/…
next-server 192.168.39.243; #FOG
if exists client-architecture {
if option client-architecture = 00:00 { #LEGACY
filename “ipxe.pxe”;
} elsif option client-architecture = 00:02 { #UEFI-32bits
filename “i386-efi/ipxe.efi”;
} elsif option client-architecture = 00:06 { #UEFI-32bits
filename “i386-efi/ipxe.efi”;
} elsif option client-architecture = 00:07 { #UEFI-64bits
filename “ipxe.efi”;
} elsif option client-architecture = 00:08 { #UEFI-64bits
filename “ipxe.efi”;
} elsif option client-architecture = 00:09 { #UEFI-64bits
filename “ipxe.efi”;
}
}
}
…/…

Hello,
We are experiencing major problems on about fifteen workstations equipped with the following network card: Intel I219-V.
We use FOG in many rooms without any problems, but this one is causing us a lot of trouble.
Debian Stable
FOG 1.5.10

The workstations boot PXE with difficulty, and the boot time increases as more workstations are connected.
Subsequently, the deployment happens with a calamitous throughput
The only things I can see are in our DHCP server logs, where dhcp requests from these workstations occur every 2-3 seconds.
The curious thing is that these requests only appear via the switch’s mac address.
…/…
oct. 27 13:52:30 tamtam dhcpd[26231]: DHCPDISCOVER from 2c:fa:a2:1a:eb:b0 via enp2s0
oct. 27 13:52:31 tamtam dhcpd[26231]: DHCPOFFER on 192.168.39.156 to 2c:fa:a2:1a:eb:b0 (vxTarget) via enp2s0
oct. 27 13:52:31 tamtam dhcpd[26231]: DHCPREQUEST for 192.168.39.156 (192.168.39.247) from 2c:fa:a2:1a:eb:b0 (vxTarget) via enp2s0
oct. 27 13:52:31 tamtam dhcpd[26231]: DHCPACK on 192.168.39.156 to 2c:fa:a2:1a:eb:b0 (vxTarget) via enp2s0
…/…
The switch is working properly, as it has already been used in other rooms without any problems.
I could see on the net that this card could cause this kind of problem without really finding a solution.
Have you got any idea about this problem ?

Hello,
I’m coming back to you regarding my initial request.
Has anyone of you tried to upgrade from Debian 11 (bullseye) to Debian 12 (bookworm) with FOG 1.5.10?

@george1421
Hello, it seems that the problem came from the configuration left over on the workstation, which still contained snappins that were no longer needed and no longer applicable.
.

@george1421
Could old Snappins assigned to this computer be the cause of this malfunction?
These snappins are no longer applicable. (activate old windows, activate old office …)
Thanks for your help

@george1421
Hello and thank you for your reply,
Then, how to explain the problem encountered:

• Image correctly deployed.
• Computer restarted.
  However, the deployment task is still active/ongoing in the fog web interface, and when renaming the workstation, an error message is present in the fog client logs “HostnameChanger A power operation is pending, aborting module”.
  As a result, the computer is not renamed and reboot in loop

Thanks again
Pascal