SOLVED Deploy Software Update Point with WOL enable

[afm_12]

The wol is configured, all the tests have been done successfully, if I right-click the computer and go to the option client notification and wake up it works, but in deploy to software update, the machine does not wake up, it follows an excerpt from the log , would there be any more procedure to do? The software update point is in a server different.

Last WOL trigger for deployment {4CF52303-221E-4888-ACFF-2566455CA286} and collection [16777229] was 05/02/2019 02:59:00 (UTC).
There is not a next WOL trigger for deployment {4CF52303-221E-4888-ACFF-2566455CA286} and collection [16777229].
STATMSG: ID=6510 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_MANAGER" SYS=FCL-SCCM.CORP.COM SITE=FCL PID=10256 TID=12068 GMTDATE=Thu May 02 02:59:00.801 2019 ISTR0="{4CF52303-221E-4888-ACFF-2566455CA286}" ISTR1="2" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=421 AVAL0="2" AID1=415 AVAL1="{4CF52303-221E-4888-ACFF-2566455CA286}"

Thank you

Alan Ferreira Maia

 

[Edy]

sorry for asking this, but did you actually Check the "Send wake-up packets" in your Deployment?

 

[afm_12]

sorry for to delay.
yes, i have doubt about utc or client time local, wich to choose?

Att

 

[afm_12]

In logs , i see three hours diference.

Alan

 

[afm_12]

++ Next WOL trigger for deployment {5A458EC3-003D-46F0-8BA0-A1100C100A10} and collection [16777373] is 05/16/2019 16:58:21 (UTC).
STATMSG: ID=6510 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_MANAGER" SYS=FCL-SCCM.CORP.COM SITE=FCL PID=10256 TID=12068 GMTDATE=Thu May 16 16:58:21.663 2019 ISTR0="{5A458EC3-003D-46F0-8BA0-A1100C100A10}" ISTR1="2" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=421 AVAL0="2" AID1=415 AVAL1="{5A458EC3-003D-46F0-8BA0-A1100C100A10}"

alway with 3 hours diference of Brasil, wich configuration would be correct?

Att

 

[Edy]

do you actually check the Option like the pic below
You can also select As soon as possible after the available time in your scheduling. In my environment its set to UTC, so you can convert your local time to UTC.

 

[afm_12]

Hi, we found out , we have a firewall in network (fortigate)that is not forwarding the packets Magic.

Alan