Configuration for this is managed from the WakeUp Console (started from the WakeUp program group on the Start menu). Configurations options vary depending on whether you are using Configuration Manager or NightWatchman Management Center.

Configuration consists of:

On this page:

Connecting to the WakeUp server

The first step is to connect to the required WakeUp Server.

You need full permissions on the WakeUp server root\N1E\WakeUp WMI namespace in order to run the WakeUp console; alternatively connect as a local administrator.

The parameters to connect to the server are:

ParameterNotes
ServerThe name or IP address of the WakeUP Server you are connecting to. Leave blank if you are connecting to the local computer.
Windows authenticationUses credentials for the currently logged on user to connect to the WakeUp Server.
Specified account detailsRequires a user name and password for authentication; useful if connecting to a remote server.

The General screen

The options for General settings are:

OptionsNightWatchman Management CenterConfiguration ManagerNotes
Enable Multi-Agent Mode(tick)(tick)

Multi-Agent mode is the recommended mode of operation for WakeUp. Ensure this is enabled to support functionality such as Last Man Standing and WakeUp Success Reporting.

If you modify this parameter, you must restart the WakeUp server.
Polling Interval:(tick)(tick)The time in seconds between database scans. This parameter is also used to define the period between wake ups (default is 30 seconds). WakeUp looks for new advertisements or jobs added since the last scan and actions them according to other service settings.
Maximum Wakeups per polling interval(tick)(tick)

Sets the maximum number of magic packets to be sent per poll interval (default is 1000 wake ups per polling interval). This should be set based on the maximum number of systems likely to require waking in one hour of advertisement processing. This figure also depends on the poll interval itself and should be set in order to make it possible to process all outstanding wake up requests within one hour.

For example:

Number of systemsPoll intervals (secs)Max wake up per poll

1000

30 (120 per hour)8 (1000/120)
500020 (180 per hour)28 (5000/180)
1000060 (60 per hour)166 (10000/60)
Time Zone Support(error)(tick)

If checked, all wake ups occur in the correct time for the local client system. If disabled, all wake ups occur in local time on the Configuration Manager server. This parameter is unchecked by default

If you modify this parameter, you must restart the WakeUp server.
Send wakeups on Software Updates Assignments at deadline(error)(tick)If checked, sets the use of WakeUp Server for software updates assignments. Only machines that are non-compliant (those needing the patch) are woken.  The wake ups occur when the deployment deadline (when the Software Updates must be installed by) is reached.

The Logging/Control screen

The options for Logging/Control are:

OptionsNightWatchman Management CenterConfiguration ManagerNotes
Logfile Name:(tick)(tick)Specifies the name of the log file. Defaults is: %ALLUSERSPROFILE%\Application Data\1E\WakeUpSvr\WakeUpSvr.log
Maximum Logfile Size:(tick)(tick)Sets the maximum size for the log file in bytes (default is 524288 bytes). When the file reaches this size, a copy is made with a .lo_ extension in the same directory as the original file. A new log file is then created.
Logging Levels:(tick)(tick)
Determines the level of detail recorded in log file. Under normal circumstances, the default settings should be enough; however more detailed logging can be enabled by increasing the logging levels and events to watch.

Logging levels

  • Standard – All standard logging info, we recommend this level is always kept on.
  • Comms – All communication between WakeUp Server and 1E Agents, this is very important when using Agents. Mostly TCP-IP type information.
  • Advertisement List – When using WakeUp without Configuration Manager, checking this level of logging will not produce any extra output to the log file as that version of WakeUp does not handle advertisements.
  • Registry Changes – Log all changes to settings in the registry (displaying old and new value). This setting should stay on by default so that it is possible to see the changes made to any settings.
  • Extra Information – More verbose debugging information, this should not be on by default but is useful when trying to locate a problem.

Event log levels

Adds the category of WakeUp logging information to be put into the Windows Event log by the WakeUp Server.

This only restricts the events that are logged during the wake up process, events such as service start and stop events and major communications failures and exceptions will always be logged.
  • Information –  events such as the status for wake ups for a particular advert ID.
  • Warnings – events such as no agent could be found on a subnet expired wake ups deleted.
  • Errors – events encountered during the wake up attempt, such as no agent was found for a subnet.

Other controls

  • Stop Server button – stops WakeUp Server. Enabled when the service is running.
  • Start Server button– starts WakeUp Server. Enabled when the service has been stopped.
  • Watch Log button – starts the default log file viewer for the most recent entries in the WakeUp log file.
  • Clear Log button – purges the the log file.

The Advanced screen

Advanced Settings control how WakeUp deals with specific timing or operational requirements. These parameters are typically left at their default values.

OptionsNightWatchman Management CenterConfiguration ManagerNotes
Minimum advertisement reprocessing interval(error)(tick)The minimum time in seconds before the same advertisement is reprocessed default is 60 seconds). This timer is only relevant if short poll intervals are required.
Minimum Re-wakeup Interval(tick)(tick)Minimum time in seconds between wake ups for the same machine (default is 200 seconds). The minimum re-wakeup interval is designed to prevent a system from receiving multiple magic packets when it has already been woken up.
Process Subcollections(error)(tick)Determines if sub-collections are included when processing advertisements (disabled by default).
Auto Throttle(tick)(tick)If enabled, WakeUp automatically increases the number of wake ups per polling cycle to ensure that all systems can be processed within one hour (enabled by default).
Check Wakeup in Name(error)(tick)

Determines whether wakeups are sent depending on specific text included in the Configuration Manager deployment name and/or comment (unchecked by default). When unchecked, wakeups are sent unless the text 'NoWakeUps' is used. When checked, wakeups are sent only when the text 'WakeUpsEnabled' is used.

If checked, any Software Updates Assignment in Configuration Manager that you want to associate with WakeUp must have the text 'WakeUpsEnabled' in the name or comment.
Check Policy Refresh in Name(error)(tick)Determines whether policy refreshes are sent depending on specific text included in the Configuration Manager deployment name and/or comment (unchecked by default). When unchecked, Policy Refreshes are sent unless the text 'NoPolicyRefresh' is used. When checked, Policy Refreshes are sent only when the text 'PolicyRefreshEnabled' is used.
Allow NightWatchman auto shutdown after Wakeup(error)(tick)

Enables interaction between WakeUp and NightWatchman. Computers woken by WakeUp are shut down providing there are no pending Configuration Manager jobs. Autoshutdown does not occur for manually requested wake ups, i.e. those from a right-click option from the Configuration Manager console, from the WMI interface or on the WakeUp command-line

In NightWatchman, MONITORJOBS must be ON and PendingSMSJobWindowMins be non-zero, otherwise computers will not have time to process pending Configuration Manager jobs before shutting down again. These are the default values.


You can override the general auto shutdown option and prevent shutdown on a per Configuration Manager Advertisement basis by including the text 'NoAutoShutdown' in the advertisement name or comment.

The Agent Finder screen

The Agent Finder screen controls how 1E Agents are discovered (using ping packets) when using Multi-Agent mode. You can set the number and frequency of pings sent, the timeout for receiving a response and how often the subnet is rescanned. This lets you set a balance between successfully finding all the Agents against the amount of network traffic generated.

The following options are only available if Enable Multi-Agent is enabled in the General screen.

SettingsNotes
Max Pings Per Burst:The number of ping packets to generate in a single burst (default is 256 packets).
Ping Burst Delay:The delay in seconds between successive ping bursts (defaults is 2 seconds).
Ping Timeout:The time in seconds to wait for a response from the 1E Agents (default is 1 second).
Subnet Rescan Delay:The time in seconds to wait before rescanning the subnet to detect 1E Agents (default is 300 seconds).

The Communications screen

The Communications parameters are:

SettingsNotes
Agent TCP Port:

The 1E Agent listening port (default is 1776). Used for WakeUp Server to talk to 1E Agent services. This must be the same for WakeUp Server and all its 1E Agents.

If TCP is not supported in your environment, contact 1E Support for further information.
Server TCP Port:WakeUp Server listening port (default is 1777). Used to communicate with the WakeUp Server. This must be different to Agent TCP Port and must be the same for the WakeUp Server and all its 1E Agents.
Maximum Connections:

The maximum number of connections that WakeUp Server opens at any given time (default is 16). Only relevant if TCP/IP Agent communication is used. This defaults to 16 connections.

There is an in-built maximum limit of 64.
Maximum Burst Size:Sets the maximum numbers of wake up requests forwarded to a 1E Agent in a single burst (default is 100).
Burst Delay:Sets the number of seconds between each batch of wake up requests being transmitted to a 1E Agent (default is 5 seconds).
Enable Agent Reporting:

Enables or disables 1E Agent reporting Advertisement status (on by default).

If 1E Agent reporting is disabled, WakeUp reports are unavailable.
Enable FIPS Compliance Encryption

Enables or disables the use of FIPS for NightWatchman Management Center communications. Enabling this sets the NightWatchman Management Center to use FIPS encrypted communications.

When setting this option, ensure that the same setting is made for all NightWatchman Management Center, WakeUp Server and 1E Agent components.
Encryption Level:
Controls the level of encryption used for communications between WakeUp Server and 1E Agents during operations. Encryption prevents packet sniffers from examining the contents of the WakeUp packet and discovering information about your network. Options are:
  • Disabled – all packets sent are unencrypted.

    When disabled, ensure that all 1E Agents are set not use encryption. 
  • Partial – enables either encrypted or unencrypted communication to be accepted. Used as an interim mode when upgrading 1E Agents to use encrypted communications while they are rolled out across the network.
  • Full – the most secure option. It specifies that all communications are encrypted and any unencrypted packages found are discarded

    When enabled, ensure that all 1E Agents are set to use encryption.  Enabled is the default setting on the Server, but disabled is the default setting on the Agent.

The WakeUp Packets screen

WakeUp Packets enables 1E Agent configuration (regardless whether the system is in Multi-Agent or dedicated Agent mode). When a wake up request is sent, agent configuration parameters is also broadcast to the 1E Agents ensuring that they function according to WakeUp Server and not by settings made during the 1E Agent installation.

SettingsNotes

Magic Packet Sending Port:

The UDP port used to send wake up broadcasts.
Magic Packet Delay:Delay in milliseconds between sending magic packets.
Repeat Count:

Number of times to repeat sending magic packets. The maximum repeat count allowed is 3.

If you suspect your network is prone to dropping datagram packets, try setting different values for Repeat Count and Repeat Delay.
Repeat Delay:

Delay in seconds before resending a repeated magic packet.

If you suspect your network is prone to dropping datagram packets, try setting different values for Repeat Count and Repeat Delay.
Wakeup Result Delay:Configures the time, in seconds, for the Primary Agent to wait and see if it has woken a machine.  It waits for the WakeUp Agent to announce it has just woke, or tries an ICMP ping.  The delay should be set to how long it normally takes for machines to start up. You can override this setting on the WakeUp Agent using its installer property WURESULTDELAY .
Enable Wake-on-LAN (Magic) PacketsSets the use of a standard Wake-On-LAN packet to power on a system from sleep state (selected by default). You should test your systems to determine which packet type is needed.
Enable Unsuspend PacketsSets the use of a directed packet (required by some newer systems) to wake those systems from standby or suspend state (selected by default). You should test your systems to determine which packet type is needed.

The Exclusions screen

This is a Configuration Manager only screen and is used to prevent wake ups for taking place during certain times of the day. Check the Enable WakeUp Exclusions box and define the time periods for the exclusion. For example:

  • To define an All Hours exclusion, click the shaded cell next to All Hours.
  • To define an exclusion for a particular day, click the shaded cell next to the day.
  • To define an exclusion for a particular hour for all days, click the shaded cell below the hour of the day.

Choose Prevent Wake Ups or Allow Wake Ups to define the behavior of the exclusion. An example below illustrates an exclusion that disables wake ups between 8AM to 8PM, Monday to Friday

Click Apply to enforce the WakeUp exception.

The Agents screen

The Agent screen displays a list of all discovered 1E Agent systems and enables centralized control over their settings. When a subnet is discovered, the Primary and Alternative Agents are displayed under Agent List.

In Dedicated Agent mode the 1E Agent systems populate the list box by registering with the WakeUp Server at service start-up. In multi-agent mode the 1E Agents are listed after they have been found. In the Agent screen, you can:

ControlsNotes
Add SubnetAdds a specific subnet to the Agent List. Once the subnet is added, you can check for 1E Agents on it. Subnets are added automatically as these are checked when a scheduled wakeup is performed.
Remove SubnetRemoves a subnet from the Agent List. Only enabled when the selected subnet has no registered Agents.
De-Reg Agent

Only enabled when a subnet is selected from the Agent List. De-registers the primary agent for the selected subnet from use by WakeUp Server. If a previously discovered alternate agent exists it will become the new primary agent.

1E Agents re-register at start-up so the de-registered 1E Agent may re-appear. If you do not want that machine to be used as an 1E Agent, remove the 1E Agent from the machine.
De-Reg AltDe-registers the alternative 1E Agent for the selected Subnet.
Check Agents

Checks the primary agent and alternative agent on the selected subnet. The check pings selected 1E Agents. If the scan fails for the primary and alternative agents, a complete scan for the subnet is done.

The process is completely automatic as the Primary and Alternative Agents are also checked when a scheduled wakeup is performed.
RefreshRefreshes the details for selected 1E Agent system.

Explaining the Agent List box

The following describes the columns for the Agent List box:

  • Subnet – lists the subnet for the discovered 1E Agent.
  • Agent – lists the name for the Agent and its current status.
  • Alternate Agent – lists the name for the Alternative Agent and its current status
  • Queued – lists the number of wake ups waiting to be sent.
  • Sent – lists the number of many machines sent a wake up signal
  • Not Sent – lists the number of machines not sent a wake up signal.
  • Awake – lists the number of target machines which were already on when the 1E Agent sent out the magic packet Only available in Multi-Agent mode.
  • Woke Up – lists the number of target machines waking up in response to the magic packet. Only available in Multi-Agent mode.
  • No Agent – lists the number of machines already awake already but without a 1E Agent installed.
  • Failed – after sending magic packets, the 1E Agent waits for a pre-determined time for replies. Any machines which have not responded are sent an ICMP ping. Machines responding to this are classified as No Agent (they are awake, but WakeUp cannot be certain if this is due to a magic packet or if the machine was awake already. Also, the 1E Agent may not have been installed). Machines not responding to the ping are classified as Failed.
  • Last Sent – lists the last time a wake up signal was sent.
  • Max Burst – lists the Max Burst value set for the 1E Agent.
  • Burst Delay – lists the Burst delay value set for the 1E Agent.

The significance of the status icons are:

IconStatusNotes

Unknown1E Agent has an unknown status. When a new subnet is added the primary and alternative agents have not yet been discovered thus having unknown status.
OK1E Agent has been discovered and is working as expected.
Resolve failedThe 1E Agent has de-registered itself.
Connect failedConnectivity to the 1E Agent is severed. The machine may have been powered down or a network cable removed.

Manually adding a new subnet

The Agent Discovery Process is a background task that automatically locates and processes new subnets. It is also possible to manually add a new subnet – most useful in lab environments or during a roll-out when performing targeting testing.

You can manually add a new subnet to the WakeUp discovery by clicking on the Add Subnet button to open the Add Subnet dialog.

Once a new subnet has been added, it is displayed in the console. Adding the subnet also triggers a discovery, though you may have to wait for the WakeUp Console to refresh before the 1E Agents are listed.

You can always force a discovery by selecting the subnet and clicking the Check Agents button.

Modifying the discovered agents

Agent discovery is largely automatic, but from the console you do have the ability to de-register both the primary and alternate agents and trigger a discovery for a particular subnet. You can modify the primary and alternate agents for a subnet by selecting a subnet in the Agent List. If the subnet has already been discovered, the De-Reg Agent, De-Reg Alt and Check Agents buttons are enabled.

  • Clicking the De-Reg Agent button de-registers the primary agent for the selected subnet. If an alternate agent has been previously discovered, it will become the new primary agent.
  • Clicking the De-Reg Alt button de-registers the alternate agent for the selected subnet.
  • Clicking the Check Agents button forces a rediscovery of the selected subnet. This may rediscover previously de-registered 1E Agents.

The Advertisements screen

Only applicable to Configuration Manager, displays the statistics of WakeUp behavior in relation to Configuration Manager advertisements that have been sent. The Software Distribution Advertisements table lists the successful wake ups for each Advertisement sent to clients of this particular Configuration Manager site.

The Software Updates screen

Only applicable to Configuration Manager, displays the statistics of WakeUp behavior in relation to Configuration Manager Software Update Assignments that have been sent. The Software Update Assignments table displays the successful wake ups for each Software Update Assignment sent to clients of this particular Configuration Manager site.

The Applications screen

Only applicable to Configuration Manager 2012, displays the statistics of WakeUp behavior in relation to Configuration Manager Application Assignments that have been sent. The Application Assignments table displays the successful wake ups for each Application Assignment sent to clients of this particular Configuration Manager site.

Explaining the Software Distribution Advertisements, Software Update Assignments and Application Assignments table columns

  • Advertisement – lists the name of the Configuration Manager Advertisement, Software Update Assignment or Application Assignment.
  • Queued – the queued wake ups for the Advertisement, Software Update Assignment or Application Assignment.
  • Sent – lists the total number of wakeups sent.
  • Not Sent – indicates an error; i.e. no TCP route to the machine was found.
  • Awake – lists the number of target machines which were already on when the active 1E Agent sent out magic packets. Only available in Multi-Agent mode
  • Woke Up – lists the number of target machines woken up in response to magic packets. Only available in Multi-Agent mode
  • No Agent – lists the number of machines which were awake already but without a 1E Agent installed
  • Failed – after sending magic packets, the 1E Agent waits for a pre-determined time for replies. Any machines which have not responded are sent an ICMP ping. Machines responding to this are classified as No Agent (they are awake, but WakeUp cannot be certain if this is due to a magic packet or if the machine was awake already. Also, the 1E Agent may not have been installed). Machines not responding to the ping are classified as Failed.
  • Last Run Time – lists the last time the recurring Advertisement, Software Update Assignment or Application Assignment ran.
  • Refresh – updates the Advertisement, Software Update Assignment or Application Assignment table.

The console reporting can be enabled or disabled by checking the Enable Agent Reporting checkbox in the Communications screen.

If 1E Agent reporting is disabled, WakeUp reports are unavailable.

Configuring 1E Agents

In general, 1E Agents are configured at install time (see installing the 1E Agent. You can, additionally, set wake up parameters for 1E Agents at runtime using the WakeUp Server console.