WakeUp client requirements
Information that will help you design and plan the implementation of WakeUp client in your organization. This includes all the prerequisites and dependencies, which are necessary to install 1E Client with WakeUp client enabled.
Tip
WakeUp client features are not required if the 1E Client is being installed only to support 1E, Content Distribution, or Shopping.
NightWatchman and WakeUp infrastructure dependencies
For a full understanding of WakeUp and NightWatchman features and their configuration, please refer to NightWatchman Enterprise 7.3 documentation.
If implementing WakeUp, or Content Distribution integration with WakeUp, then you require at least one WakeUp Server. If you have Configuration Manager, you require a WakeUp Server on each Site server that has clients reporting to it. If you do not have Configuration Manager, you require one or more independent WakeUp Servers.
A NightWatchman Management Center server is required when implementing a WakeUp solution. Your 1E Account Team will explain whether your license also includes NightWatchman client features. 1E NightWatchman Agent is a separately installed client agent, that can optionally be used to help with power management of computers. It is not included in 1E Client, but is included in the Introducing Client Deployment Assistant which assists with deploying Windows versions of 1E Client via Configuration Manager. As well as providing power management features, when 1E NightWatchman Agent is installed alongside the WakeUp client, it will optionally manage the computer returning to its original power state after being woken using 1E WakeUp and the computer is not busy, for example, installing patches.
Web WakeUp is an optional server component that is typically installed on the NightWatchman Management Center server. It is a web portal for users and administrators to search for computers to wake. It optionally provides a remote desktop link to the woken computer.
Client hardware requirements for WoL
To utilize Wake-On-LAN (WoL) technology, you need the following hardware configurations:
Hardware | Configuration |
|---|---|
Network card | A network card that can support Wake-On-LAN. Your network card vendor can tell you if your network adapter supports Wake-On-LAN. If it does, it must be configured to enable remote wake-up. Some adapter drivers are disabled by default within the operating system. |
System BIOS | Wake-On-LAN must be enabled in the system BIOS. This option can usually be found in the Boot menu of the BIOS configuration program. Some BIOS have a 'Maximum Power Savings' or 'Low Power S5' option, which should be disabled in order to allow some power to the network card. |
Power management | APM or ACPI should be enabled, otherwise, the user of the machine should ensure that it is powered off by hitting the off button after shutdown. |
A quick way to tell if a system is Wake-On-LAN ready is to power down the system and then look at the network adapter display LED's. If the lights are still on, then chances are that the system is OK. Windows must have been powered down gracefully (either off or asleep) in order for it to prepare the network card for WOL.
Tip
Please contact 1E if you require guidance with WoL configuration on Windows operating systems and enterprise vendor hardware including Dell, HP and Lenovo computers.
1E NightWatchman Agent
If you are deploying WakeUp as part of a NightWatchman Enterprise power management solution then you will also need to consider 1E NightWatchman Agent requirements.
Firewall Ports
Please refer to NightWatchman Enterprise communication ports.