@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.

@Sebastian-Roth
Hello,
until now I was using the “dev-branch” branch of git:

git branch -vv
* dev-branch ddb9904a7 [origin/dev-branch] Fix https build failing due to inline tests
 master 171d63724 [origin/master] FOG 1.5.9 Officially Released

For the latest update of fog: 1.5.10, is it better to switch to the master branch?
This is a production server and I don’t want to “break” it.

Once the choice of the branch is made, the update procedure is always the same?

Change the reference branch to master or dev-branch (To be done the first time)
	git checkout master or git checkout dev-branch
Initialize git :
	git init
Update the git repository:
	git pull
Install FOG
cd bin/
./installfog.sh

Thanks for your help.
Pascal

@Tom-Elliott
So no problem to upgrade from 1.5.9.111 (dev-branch) to 1.5.9.235(dev-branch) ?
Thanks

Hello,
I am currently using FOG version 1.5.9.111 (dev-branch).
It seems that the last version of “dev-branch” is 1.5.9.235.

On github I don’t see the changelog concerning this version.
Can I upgrade from 1.5.9.111 to 1.5.9.235 without any problem?
They are minor corrections?
Thanks for your help.
Pascal

When I click this button, if I leave FOG and go back to the same host, the button is displayed again.
But it seemed to me that once I had clicked on this button, it was not supposed to be displayed again for the same host

Hello,
I have a little problem on the web interface.
I have to regularly click on the “reset encryption data” button of some hosts and it seems that this action is not remembered.
What could be the problem?
Thanks for your help
Pascal

@sebastian-roth
I think i 've got the solution :
in fogsettings,

storageLocation was ='/images',

then
/etc/exports was :

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

After correcting fogsettings (storageLocation =‘/home/images’,
/etc/exports :

/home/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/home/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

and it seems to works

@sebastian-roth Hello
The migration is done and I think I followed the documentation.
During a test I encounter the following problem:

Could not mount images folder (/bin/fog.download)
Reason: mount: mounting 192.168.39.243:/home/images/ on /images failed: Permission denied

My images directory is in /home/images.
Do i miss something ?