Introducing NightWatchman Enterprise 7.2.500
How it works
Quick starts, evaluations and pilots
Working with NightWatchman Enterprise
WakeUp Server installer properties
The following table shows the WakeUp Server installation switches which enable configuration of certain WakeUp console parameters at install time.
|Allows you to install the WakeUp console extensions silently. Assumes the Configuration Manager console is already installed.|
|OFF||The reporting state.|
Listening port used by the WakeUp server to communicate with the 1E Agents.
|5||Delay (in seconds) between each batch of wake-up requests transmitted to a 1E Agent system.|
|0||Determines whether policy refreshes are sent depending on specific text included in the Configuration Manager deployment name and/or comment.|
Determines whether wakeups are sent depending on specific text included in the Configuration Manager deployment name and/or comment.
|Sets the name for the TLS certificate template used for secure communications when running Intel AMT service in enterprise mode.|
|13||The debug level for the WakeUp server.|
Encryption level used in communications between WakeUp Servers and Agents.
Enables or disables 1E Agent reporting on advertisement status.
Optional parameter that determines the installation directory.
|Specifies the name of the log file.|
Path to the log file.
|Specifies the path to a log viewer. This is used to define the path to an alternative log viewer to such as |
|1776||Sets the UDP port used to send wakeup broadcasts.|
|10||The time delay in milliseconds between sending Magic Packets.|
|100||The maximum numbers of wakeup requests that is forwarded to a 1E Agent system in a single hit.|
The maximum number of connections that the WakeUp Server attempts to open at any given time.
|1048576 bytes (1 MB)||Maximum size (in bytes) for the log file. Once the file reaches the specified size, a copy will be made with a |
Number of ping packets to generate in a single burst.
Maximum number of magic packets to be sent per poll interval. This is 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 and is set in order to make it possible to process all outstanding wakeup requests within one hour.
Minimum time (in seconds) before the same advertisement is reprocessed.
Minimum time (in seconds) between wakeups of the same machine. For example, a system may be a member of two or more collections and may have more than one advertisement due.
|0||Auto throttle automatically increases the number of wakeups per polling cycle if the wakeup list grows to the point where all systems cannot be processed within one hour.|
|1||Determines whether all wakeups occur relative to the client or Configuration Manager Server time.|
|30-day evaluation license key||The WakeUp Server license key obtained obtained from Sales. The default behavior if |
Delay (in seconds) between successive ping bursts.
Ttime (in seconds) to wait for a response from the 1E Agents.
|600||Time (in seconds) between reporting spooler directory scans. WakeUp looks for new reporting messages added since the last spooler directory scan, if the Agility Framework server was unavailable at the last scan.|
|120||Time (in seconds) between database scans. This parameter is also used to define the period between wakeups. WakeUp will look for new advertisements added since the last database scan and will action them according to the other WakeUp Server settings.|
Determines the state of the installer Apply WMI Namespace checkbox.
Number of times to repeat sending Magic Packets.
Delay (in seconds) before resending a repeated magic packet.
The reporting state. May be set to:
When using HTTP for communications, set this parameter to the FQDN (recommended) or NetBIOS name of the server hosting the NightWatchman Management Center Web Service.
If HTTP is not using standard port 80 then specify the port number after the server name:
The WakeUp installation scenario.
>When using HTTPS for communications, set this parameter to the FQDN (recommended) or NetBIOS name of the server where the NightWatchman Management Center Web Service component secure site has been installed.
Selects whether to install the WakeUp Server service component.
|SMS is selected if the installer detects it is running on a Configuration Manager Site server and able to connect to an SMS Provider.||The WakeUp service type to install.|
|The location of the WakeUp spooler directory, where NightWatchman Management Center Reporting messages are stored before being sent to the NightWatchman Management Center Web Service. |
|0||Determines if sub collections are included when processing advertisements.|
Time (in minutes) to wait before the WakeUp Server rescans the subnet to detect 1E Agents.
|Sets the password for the WakeUp Intel AMT service account.|
|The service account for the WakeUp Intel AMT service depending on the value for the |
The listening port used by the 1E Agents to communicate with the WakeUp Server.
Controls the use of FIPS for encrypting communications for both WakeUp and NightWatchman components.
|Sets the password for the WakeUp service, used when installing a distributed Configuration Manager configuration where the Configuration Manager Provider is remote from the Configuration Manager server.|
|Sets the user name for the WakeUp service, used when installing a distributed Configuration Manager configuration where the Configuration Manager Provider is remote from the Configuration Manager server.|
The method used by Web WakeUp when determining whether a computer has been awoken.
The AD account or group that is granted administrator rights to the WakeUp Server WMI namespace. This namespace is used by the WakeUp Server Console, the NightWatchman Management Center Console Service and any custom scripts that use the WakeUp Server API.
If required, it should be set in the following format: