Scheduled Wake-on-LAN functionality is available in the platform

(imported topic written by richardzhang91)

We are pleased to announce the availability of Scheduled Wake-on-LAN functionality in the platform. This Scheduled Wake-on-LAN functionality adds to the platform’s existing on-demand Wake-on-LAN capabilities and previously was only available as part of Power Management.

The new content can be found under the “Manage Wake-on-LAN” and “Deployment Health Checks” sections of the BigFix Management domain.

Note: Advanced Wake-on-LAN functionality such as Last Man Standing and other Power Management capabilities are available only through the Power Management product.

Highlights include:

  • Ability to create and maintain one time, daily, weekly or monthly scheduled wake-ups using BigFix Wake-on-LAN technology.
  • Scheduled wake-ups run on client local time, and do not require any special router configuration to run.
  • Central management of wake-up schedules restricted by operator roles.
  • Ability to overcome the PC Narcolepsy condition on Windows Vista/7 computers.

====================================

Affected Fixlet Messages:

  • Wake-on-LAN Analysis (ID 840)
  • Enable Wake-on-LAN Medic (ID 842)
  • Disable Wake-on-LAN Medic (ID 843)
  • Update Wake-on-LAN Medic (ID 847)
  • BES Client Setting: Designate Wake-on-LAN Forwarders (ID 571)
  • BES Client Setting: Remove Wake-on-LAN Forwarders (ID Fixlet 848)
  • Enable Wake-from-Standby by Magic Packet - Windows XP/Vista/Win7/2008 (ID Fixlet 845)
  • Disable Wake-from-Standby by Magic Packet - Windows XP/Vista/Win7/2008 (ID Fixlet 844)
  • PC Narcolepsy: Set System Unattended Sleep Timeout - Windows Vista/7 (ID Fixlet 846)
  • BES Server Plugin Service is not Configured Correctly (ID Fixlet 841)

Affected Wizards/Dashboards:

  • Wizard: Schedule Wale-on-LAN
  • Dashboard: Deployment Health Checks

Actions to Take:

  • Active Wake-on-LAN Analysis (ID 2)
  • Install BES Server Plugin Service (ID 708) if it’s applicable
  • Enable Wake-on-LAN Medic (ID 842)
  • Manage Wake-on-LAN schedules in the Schedule Wake-on-LAN wizard

Published site version:

BES Support, version 827

====================================

Richard Zhang

Application Engineering Team

Tivoli Endpoint Manager

IBM Tivoli Software

(imported comment written by TivoliDon)

Hello Richard,

I have configured designated forwarded for each subnet.

When I right click any computer and select “Send wake on lan request”, it works properly and powers on the machine.

However, when I use “Schedule wake on Lan” wizard it does not work. Any hints to resovle the issue ?

(imported comment written by Zakkus)

You need to have the “Wake-on-LAN Medic” setup to do scheduled wakeups. Check the “Enable Wake-on-LAN” fixlet, and its prerequisite “Install BES Server Plugin Service” and run them on your server, if they are relevant.

(imported comment written by TivoliDon)

Thanks Zakkus.

It finally worked after enabling wake on lan medic. But i also had to add the following registry keys to get it working.

HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\BESReports]

SOAPUsername (String)

Set with the name of your Web Reports user as its value.

HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\BESReports

SOAPPassword (String)

Set with the users password as its value.

HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\BESReports

WRHTTP (String)

(imported comment written by SystemAdmin)

Is it possible to do a manual WOL for an unmanaged asset? If the IP and MAC are known in the unmanaged asset list should it not be possible? However there is no right-click WOL option. Could it be done via a manual task?

In my case it’s a Wyse terminal I’m trying to wake up.

(imported comment written by Zakkus)

You wont be able to wake up unmanaged assets through the platforms built in mechanism. The platform knows how to wake up a device based on some information it picks up when the device registers, however since unmanaged assets dont register (they are just picked up by a scan), the platform wont be able top wake them up.

-Zak

(imported comment written by Zakkus)

You wont be able to wake up unmanaged assets through the platforms built in mechanism. The platform knows how to wake up a device based on some information it picks up when the device registers, however since unmanaged assets dont register (they are just picked up by a scan), the platform wont be able top wake them up.

-Zak

(imported comment written by SystemAdmin)

Is there any method then to have the relays act a WOL forwarders for WOL packets NOT generated through the BigFix method?

(imported comment written by Zakkus)

The platform actually sends wakeup notifications (rather than WOL magic packets) from the server through the relay hierarchy, till it finds a WOL Forwarder in the same subnet as the target computer. The WOLF then sends the actual wakeup broadcast magic packets.

Since the unmanaged assets aren’t real bes clients, the server cant figure out any of this, so there unfortunately isn’t really a way to use it here.

The best you can do is use bigfix to run a WOL exe to wakeup the UA through an action. You would have to figure out which computer is in the same subnet as the target machine (maybe the UA scan point machine?). This actually isn’t too different from the way we used to do it… though it definitely has its drawbacks.

(imported comment written by Nisar533)

Dear Richard,

I have configured LMS & designated forwarded in a subnet.

When I right click any computer and select “Send wake on lan request”, it works properly and powers on the machine.

However, when I use “Schedule wake on Lan” wizard it does not work. I have installed all the pre-requistes. Power Managment Dashboard shows all required steps as PASS.

Kindly suggest what i have to do further.

Regards

Nisar