Introducing NightWatchman Enterprise 7.3
How it works
Quick starts, evaluations and pilots
Working with NightWatchman Enterprise
Connecting to the WakeUp server
The first step is to connect to the required WakeUp Server.
The parameters to connect to the server are:
|Server||The name or IP address of the WakeUP Server you are connecting to. Leave blank if you are connecting to the local computer.|
|Windows authentication||Uses credentials for the currently logged on user to connect to the WakeUp Server.|
|Specified account details||Requires a user name and password for authentication; useful if connecting to a remote server.|
The General screen
The options for General settings are:
|Options||NightWatchman Management Center||Configuration Manager||Notes|
|Enable Multi-Agent Mode|
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.
|Polling Interval||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|
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.
|Maintenance Window Polling (x times Polling Interval)||This parameter sets the time interval between Maintenance Window check cycles. Value of this parameter times value in Polling Interval seconds will be the time interval for Maintenance Window check cycles.|
|Time Zone Support|
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
|Send wakeups on Software Updates Assignments at deadline||If checked, sets the use of WakeUp Server for software updates assignments. Only computers 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.|
|Send wakeups for Maintenance Windows||If checked, sets the WakeUp Server for Maintenance Windows. Only computers inside collections on which Maintenance Window will be applied will be woken up.|
|Send wakeups for Phased Deployments||If checked, sets the WakeUp Server for Phased Deployments. Computers for respective phases will be woken up the specified time as per deployment.|
The Logging/Control screen
The options for Logging/Control are:
|Options||NightWatchman Management Center||Configuration Manager||Notes|
|Logfile Name:||Specifies the name of the log file. Defaults is: |
|Maximum Logfile Size:||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 |
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.
Event log levels
Adds the category of WakeUp logging information to be put into the Windows Event log by the WakeUp Server.
The Advanced screen
Advanced Settings control how WakeUp deals with specific timing or operational requirements. These parameters are typically left at their default values.
|Options||NightWatchman Management Center||Configuration Manager||Notes|
|Minimum advertisement reprocessing interval||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||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||Determines if sub-collections are included when processing advertisements (disabled by default).|
|Auto Throttle||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|
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.
|Check Policy Refresh in Name||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|
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
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.
|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:
|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.
|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.|
The maximum number of connections that WakeUp Server opens at any given time (default is 16). Only relevant if
|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).
|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.
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:
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.
Magic Packet Sending Port:
|The UDP port used to send wake up broadcasts.|
|Magic Packet Delay:||Delay in milliseconds between sending magic packets.|
Number of times to repeat sending magic packets. The maximum repeat count allowed is 3.
Delay in seconds before resending a repeated magic packet.
|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 computers to start up. You can override this setting on the WakeUp Agent using its installer property|
|Enable Wake-on-LAN (Magic) Packets||Sets 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 Packets||Sets 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:
|Add Subnet||Adds 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 Subnet||Removes a subnet from the Agent List. Only enabled when the selected subnet has no registered Agents.|
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.
|De-Reg Alt||De-registers the alternative 1E Agent for the selected Subnet.|
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.
|Export||Export the subnets to a CSV file. In Microsoft Excel or a similar program you can then analyze the subnets to identify problems, review results, etc.|
|Refresh||Refreshes the details for selected 1E Agent system.|
|Search Subnets||Enter the first part of a subnet or subnets you're interested in to and then click Search Subnets to have only subnets starting with that part. For example, "192.168" will return all subnets start with 192.168. Start with a percentage sign if you want any subnets including the part. For example, "%168" will return all subnets that include "168" anywhere in them.|
Explaining the Agent List box
The following describes the columns for the Agent List box:
|Subnet||Lists the subnets managed by the WakeUp server.|
|Agent||Lists the name for the Primary Agent. It is the computer on each subnet that manages wakeup requests for the subnet.|
This is a column in the export file and the icon next to the Agent name in the console.
See the next table (below) for the significance of the status icons.
|Alternate Agent||Lists the name for the Alternate Agent. The computer will serve as the purpose of the primary agent if the primary agent is not available.|
|Alternate state||This is a column in the export file and the icon next to the Alternate Agent name in the console. The icons are the same as the Agent State icons.|
|Queued||Lists the number of wake ups that have been received from the WakeUp server and sent on the subnet.|
|Sent||Lists the number of computers sent a wake up signal|
|Not Sent||Lists the number of computers not sent a wake up signal.|
|Awake||Lists the number of target computers which were already on when the primary or alternate sent out the magic packet. Only available in Multi-Agent mode.|
|Woke Up||Lists the number of target computers waking up in response to the magic packet. Only available in Multi-Agent mode.|
|No Agent||Lists the number of computers already awake but without a 1E Agent installed (and therefore could not respond to wakeup requests).|
|Failed||After sending magic packets, the primary or alternate waits for a pre-determined time for replies. Any computers which have not responded are sent an ICMP ping. Computers 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). Computers 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 MAXBURST value set for the primary and alternate agents.|
|Burst Delay||Lists the BURSTDELAY value set for the primary and alternate agents.|
|In Site||This is a column in the export file that doesn't have an equivalent in the WakeUp Console. Its value is always 1, indicating that the subnet belongs to the WakeUp server you connected the console to.|
See the Understanding WakeUp Status page for more details.
The significance of the status icons are:
|Icon||Export file value||Status||Notes|
|0||Unknown||1E 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.|
|3||OK||1E Agent has been discovered and is working as expected.|
|1||Unavailable||The 1E Agent has de-registered itself.|
|2||Connection failed||Connectivity to the 1E Agent is severed. The machine may have been powered down or a network cable removed so that it could not de-register.|
Clicking on a column a column header will cause the list to be sorted in ascending order of that column. Clicking the column header again will cause the list to be sorted in descending order.
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, 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 computer was found|
|Awake||Lists the number of target computers 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 computers woken up in response to magic packets. Only available in Multi-Agent mode|
|No Agent||Lists the number of computers which were awake already but without a 1E Agent installed|
After sending magic packets, the 1E Agent waits for a pre-determined time for replies. Any computers which have not responded are sent an ICMP ping.
computers 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 computer was awake already. Also, the 1E Agent may not have been installed). computers 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.
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.