A power operation is pending

[plegrand]

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

[plegrand]

@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

[plegrand]

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

[plegrand]

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

[george1421]

@plegrand FOG can’t see bitlocker encrypted disks as being encrypted disks. It will blindly copy sector by sector to a new system. BUT a bitlocker protected system will care since the secuity token won’t match (because that is held in the TPM chip on the source computer) the TPM chip certificate. You must disable bitlocker on the mother image before cloning. If you need bitlocker enabled on the target system issue the command through the windows setupcomplete.cmd batch file or via a GPO policy.

[plegrand]

@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

[george1421]

@plegrand said in A power operation is pending:

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

I’ve seen this only happen when the imaging process actually doesn’t complete. The very last step in the imaging process is for the target computer to send an “all done” command to the FOG server to clear the task. This may be the root of your other issues because “imaging never really completed” according to the fog task manager.

So do you have any kind of post install script running at the end of deployment? Might that script cause the target computer to reboot before the “all done” message is sent?

[plegrand]

@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

[plegrand]

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