We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Managed Workplace

About Wake-on-LAN

  • Last updated on

Barracuda Managed Workplace can wake any device that supports Wake-on-LAN.

For example, with power management, you typically have computers sleep when not in use. If you have customers who access some of their systems remotely, these systems may be asleep when they want to use them.

Barracuda Managed Workplace provides the ability to allow end users to wake their devices through a web portal.

You must give end users at that site a user account to Service Center so that they can wake their computers remotely.

You cannot wake computers that are off or set to hibernate.


Best Practice

Create one user account per customer site for end users. Alternatively, if the customer has more than 500 devices, create a few logins for the site. For example, create logins for each of the different departments.

What if waking a computer doesn't work?

Unless a device is AMT-enabled, Barracuda Managed Workplace uses Wake- on-LAN (WOL) to attempt to wake systems. WOL broadcasts a packet called a Magic Packet targeting the MAC address of the device to be woken. There are a number of reasons why this may not work.

  • The Onsite Manager does not have the MAC address for the device. This is the case if the device is not WMI- or SNMP-enabled.
  • The device is not wake-enabled. Typically devices have a BIOS setting that needs to be configured correctly. Network Interface Cards must also be configured correctly.
  • The device does not support WOL.
  • The device has a Device Manager installed. Since these systems monitor themselves, there is no other device to ask to wake it.
  • The device is on a different subnet from the Onsite Manager. The wake broadcasts are limited to the subnet in which they originate.

Typically it takes a few minutes from the time the wake is requested until the system is accessible.

Last updated on