WOL ? Computer boot/start alone
-
@steuve68 have u tried to turn of hibernation by “powercfg -h off” in an evaluated cmd prompt?
-
@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” -
@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
-
@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.
-
@x23piracy I have test “powercfg -h off” with elevated privilege on 2 problematic computers
No change: computers start always alone.For the moment the only solution what I found it’s up to date NIC Drivers …
@Tom-Elliott “Ping hosts just tests the status of a host.” => Can I disable this option into FOG ?
Thanks all
-
@steuve68 yes under fog settings Linux service.
-
@tom-elliott OK thanks
It’s that: PINGHOSTGLOBALENABLED ?No secondary effect if i uncheck this option ?
-
@Tom-Elliott After uncheck PINGHOSTGLOBALENABLED, it’s OK.
Computer don’t start/boot alone.
WOL tasks always good !No secondary effect ?
Thanks all
-
@steuve68 You won’t be able to see if hosts are online with it disabled but that should be it afaik.
-
@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.Regards X23