Introducing NightWatchman Enterprise 7.3
How it works
Quick starts, evaluations and pilots
Working with NightWatchman Enterprise
Using the core components
Configuring and managing advanced components
Using the NightWatchman console
Using the WakeUp console
Web WakeUp server configuration
Operational best practices
Frequently asked questions
- Using the core components
If there are users logged on the system when a power-off is initiated, the log-off action takes place. If not, NightWatchman proceeds directly to the power-off stage.
There are three log-off modes that can be set:
- Passive – if users are logged on, no attempt will be made to shut down.
- Active – users are asked if the power-off is allowed to continue.
- Force – users are notified that a power-off is about to take place and will be logged off once the countdown expires.
You can set a countdown for a power-off, so in Active and Force modes, users see a countdown to the event. In Active mode, the user has the option to cancel the power-off or enable the event by clicking OK. If the user postpones the event, NightWatchman can be set to retry again later.
If the modes are Active or Force, NightWatchman runs the power-off scripts. The four scripts which enable administrators to power down computers are:
NightWatchman power schemes and reporting data
NightWatchman automatically configures the power scheme to enable processor speed and voltage to vary automatically with system usage, specifically for machines using Intel speed step processors or AMD Cool n' Quiet processors. This results in enhanced energy saving on machines with low average utilization (most office productivity machines). On Windows 7, this involves the creation of a new NightWatchman power scheme based on the Balanced Power Scheme.
From the point of installation, NightWatchman reports inventory and power state data for its local computer back to the reporting server. The inventory information includes:
- the computer name
- the computer's domain
- IP address and subnet
- its network card MAC Address
- the chassis model, type and manufacturer.
Power state data shows how long the computer is in a particular power state and is used in conjunction with associated typical power consumption information to calculate how much power the computer is consuming throughout the day. Inventory information helps identify the computer and determine any information related to its type, such as its typical power consumption figures.
The NightWatchman Management Center Console lets you define:
- Location groups – enables you to model your company according to the physical location of the computers. You can report on and apply location specific power settings to computers according to where they reside. For example, if you know of a forthcoming national holiday, you can apply a one-off policy that sets particular power settings for that specific location only. You can also use these groups to apply specific localized tariffs that increase the accuracy of power cost reports.
- Organization groups – enables you to model your company according to organizational units. You can report on and apply specific power settings to computers according to where they sit in the organization. For example, if you know of an off-site team building exercise for a particular department, you can apply a one-off policy that sets particular power settings for that department only.
NightWatchman pre-event tests
When a scheduled power-down event is triggered (and before the Hibernate, Standby, power-off or Reboot events starts), NightWatchman runs the following tests:
|Last man standing|
Check to see if the computer is set to be last man standing. If so, cancel the scheduled event.
|User activity||Check for user activity, If found, cancel the scheduled event. This test is not performed if:|
|Exception list||Check to see if any processes on the process exception list are currently running. If so, cancel the scheduled event.|
|Configuration Manager running jobs|
If Configuration Manager client exists and
|Configuration Manager pending jobs|
If Configuration Manager client exists and
|Nomad in-progress file transfers||Check to see if the computer is acting as the Nomad P2P master. If so, cancel the scheduled event.|
|Nomad PBA content found||Check to see if the computer has content that Nomad is holding as part of its Peer-Backup Assistant functionality. If so, cancel the scheduled event.|
|Keep active status||Check the Keep Active status on the NightWatchman user interface. If set, cancel the scheduled event.|
|Active maintenance window||If a NightWatchman maintenance window is active, cancel the scheduled event.|
Because the 1E Agent will cancel a scheduled power down event when there are pending or running Microsoft Configuration Manager jobs, it is recommended to set
logoffaction=FORCE when attempting to power down a computer after successfully running a Configuration Manager software distribution Advertisement.
An alternative would be to use the NightWatchman command-line and set a once-off power down with
logoffaction set to
PASSIVE to power down the computer at a specific time and let it retry until the Advertisement has finished running.
The following takes place when a NightWatchman event is triggered.
|Hibernate or stand-by|
|Power-off or reboot|
|Resume from a low-power state|
When you enable the NightWatchman system tray interface, the end-user can:
- Keep their computer active by opting out of passive or active NightWatchman power-offs for a period of time.
- Initiate a local power-off.
- View the list of files backed-up during the last log-off process.
You may also want to audit end-user interaction with the NightWatchman backup dialog and resolve issues with backups that occasionally do not appear in the backup list. The 1E Agent tracks basic end-user choices when selecting the Save or Reject options in the Backup Dialog.
For each file that the user chooses to accept or reject, an entry is added to
NWMAudit.log, which is created in the per-user NightWatchman data folder. for example,
Each entry indicates the time of the operation, the original document name, whether the user chose to Keep or Reject the file and, where applicable, the name of the file that the backup was saved to.