I explain:
When a user stop the computer with windows menu Starts => Stop, the computer power off.
That’s OK.
But … avg 5 minutes after that a WOL signal wake up the computer … and it boot on fog menu pxe wait 5 sec with the fog menu and boot on the HDD.

I explain:
When a user stop the computer with windows menu Starts => Stop, the computer power off.
That’s OK.
But … avg 5 minutes after that a WOL signal wake up the computer … and it boot on fog menu pxe wait 5 sec with the fog menu and boot on the HDD.

I have used the wolbroadcast plugins. For the moment i have delete this plugins for see if the problems come from him.

I precise, the problem appear on DELL Optiplex 9020.
Several machines are concerned.
Computers are conf for boot on HDD 1frst.
BIOS are conf for WOL with PXE

Have you any idea ?

Thanks for answers/idea.

]]>https://forums.fogproject.org/post/113482https://forums.fogproject.org/post/113482Tue, 12 Jun 2018 06:51:58 GMTI have not heard of the fog server sending out random wake up commands before. Are there any active tasks in the fog task manager?

I think you are testing right, just unplug the network cable that goes to the fog server and see if the issue stops. I have seen windows computers wake on their own before too.

We may be able to create a specific capture string and have tcpdump program on the FOG server see if its sending out the magic wake packets to confirm if its FOG or something else waking up these computers. I must think about that task.

]]>https://forums.fogproject.org/post/113496https://forums.fogproject.org/post/113496Tue, 12 Jun 2018 11:59:42 GMT@steuve68 can you please try to use “powercfg -h off” from one of the problematic computers? will they still turn on? You will need an evaluated cmd prompt to do this.
]]>https://forums.fogproject.org/post/113497https://forums.fogproject.org/post/113497Tue, 12 Jun 2018 12:05:32 GMT@steuve68 said in WOL ? Computer boot/start alone:

IP IPFOGSERVER.35593 > IPOFCOMPUTER.445

This I can tell you is the fog server “pinging” the computer to see if its up. I can tell you that fog “pings” using this method instead of a traditional icmp ping. Why ?? I don’t know.

This does sound like what x23 says a fog “ping” will wake up the host. After fog starts I don’t know what those packets are.

I wonder of FOG will wake up the computer from a power up off state instead of a windows shutdown state?

]]>https://forums.fogproject.org/post/113514https://forums.fogproject.org/post/113514Tue, 12 Jun 2018 13:27:23 GMT@steuve68 have u tried to turn of hibernation by “powercfg -h off” in an evaluated cmd prompt?
]]>https://forums.fogproject.org/post/113515https://forums.fogproject.org/post/113515Tue, 12 Jun 2018 13:29:40 GMT@x23piracy No, i have just update NIC Device for test on this machine.
But hibernation mode is off
When i run: powercfg -a
“La mise en veille prolongée n’a pas été activée”
]]>https://forums.fogproject.org/post/113517https://forums.fogproject.org/post/113517Tue, 12 Jun 2018 13:41:20 GMT@steuve68 here is a link for the 2 years old conversation i had with tom about it:https://pastebin.com/L1ixBrZd@tom-elliott don’t bash me for sharing this :)
]]>https://forums.fogproject.org/post/113518https://forums.fogproject.org/post/113518Tue, 12 Jun 2018 13:43:39 GMT@x23piracy why would I bash you. The only wake up code is in fog scheduler still.

Ping hosts just tests the status of a host. The reason we use 445 @george1421 is so we can get a status. Ping itself just tests if the host is pingable, but that doesn’t necessarily mean anything. Using 445 we can get a real status like refused, no address, etc…

So fog isn’t causing the problem being seen, but it is playing a part. That part is not by any means “fogs” fault, rather a configuration issue on the workstations.

]]>https://forums.fogproject.org/post/113568https://forums.fogproject.org/post/113568Wed, 13 Jun 2018 08:24:04 GMT@steuve68 You won’t be able to see if hosts are online with it disabled but that should be it afaik.
]]>https://forums.fogproject.org/post/113570https://forums.fogproject.org/post/113570Wed, 13 Jun 2018 09:07:49 GMT@steuve68 and in the end it was the online check from fog activating that computers, like i told you ;) I still have the ping check enabled i solved my problems around that with hibernating off und pattern match in nic drivers disabled.