Posts made by plegrand

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

Additional information:

Is it possible that the problem is BitLocker?
This was activated on the machine.
It seems to me that FOG did not support BitLocker being enabled.
However, we didn’t get any error message concerning BitLocker, neither during capture nor during deployment.

Thanks for your help

Pascal

Additional information:

While everything suggested that the image deployment task for this workstation had been completed (workstation rebooted with the correct image installed),
in “Active task” it was still present and therefore not finished, without me really knowing why.
So I cancelled it from the FOG web interface.

After that, the computer rebooted (initiated by the fog client) and the various tasks were completed (renaming and joining to the domain).

Why is it that, even though the computer has restarted, fog considers that the task has not been completed?

Thanks for your help.
Pascal

Hello,
I’m having a little problem with a computer where FOG can’t perform various tasks, including changing the name and joining the domain.
I can perform these 2 tasks manually without any problem.

Each time, I get the following message in the logs: HostnameChanger A power operation is pending, aborting module.
Is it possible to find out what operations FOG performs to detect a “power operation pending”?

The computer keeps rebooting to perform these 2 tasks without succeeding.

In the FOG web interface, when I look in “Power management”, no task is scheduled.
As a result, I can’t see where the problem might be coming from.

Any ideas?

Thanks in advance for your help.
Pascal

@Lee-Rowlett said in upgrade Debian 11 to 12:

@plegrand yes i would wait, i wouldn’t recommend updating your production server.

if you don’t rely on the LDAP plugin then everything else is functioning as it should but i still wouldn’t recommend it in a production environment.

Would it be possible to tell me when it is reasonable to update, in this thread?

@Lee-Rowlett
So, does this mean that I’d better wait before updating my production server?

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

So for the moment, no particular advice for upgrading from Debian Bullseye(11) to Debian Bookworm(12)?

@Sebastian-Roth
Yes, it seems that i’m using the 1.5.10 version

But my question was about the upgrade of the Debian distribution
Debian bullseye(11) => bookworm(12)

Hello,
is it reasonable to consider updating Debian bullseye(11) => bookworm(12)
Is Fog supposed to work correctly after this update?
PHP, among other things, is upgraded to version 8

Thanks for your answers

@Sebastian-Roth
Thank you for your answer.
I didn’t touched anything in the deposits.
I use Fog as it is, without changing anything.
So I will do the update and I will come back here to tell you if everything went well.
Thanks again.