NightWatchman Enterprise 7.3

You can see obsolete clients under the client tab in the Nightwatchman console. To do this right-click on the location group or organization group folder in the respective tabs and select show obsolete clients

No, a machine cannot be woken when it is marked as obsolete.

If you are using Nomad and want to implement the Nomad integration with WakeUp feature you must enable ActiveEfficiency option during installation. This feature was previously known as WakeUp integration with ActiveEfficiency. For more information on this feature, please refer to Frequently asked questions.

In previous versions of NightWatchman, ActiveEfficiency was used for synchronization wit the 1E Cloud for automatic power consumption catalog updates, but this feature is now obsolete. ActiveEfficinecy is now only used for the Nomad integration with WakeUp feature.

1E recommends one WakeUp server per 2,000 subnets when implementing a NightWatchman Management Center strategy

The evaluation license (i.e. when no license key provided during installation), is fully functional for 30 days

When WakeUp is installed on a ConfigMgr site server, it registers the ConfigMgr site boundaries (specifically those boundaries that are used for site assignment) with NightWatchman Management Center. As these are defined in ConfigMgr, they cannot be modified in the NightWatchman console, although additional subnets can be added to the WakeUp server through the NightWatchman Console. The pre-defined subnets are read-only.

You can however, add exclusions to the NightWatchman boundaries in the NightWatchman console if there are particular subnet in the boundaries of the ConfigMgr site that you do not want the Wakeup Server to manage.

In a production environment you would typically install WakeUp either in NightWatchman Management Center mode (if you don’t have Configuration Manager) or in ConfigMgr mode (if you do). In some cases you may have Configuration Manager installed where does not manage all the clients or subnets. In this scenario you can manually add the missing subnets to the WakeUp server via the WakeUp Server tab in the NightWatchman Management Console.

The Register tab in the Web WakeUp portal allows a user to register up to 20 computers that they regularly use, which then appear on the My Computers tab.

You can get the details from 1E Support portal under the software download page and then by selecting the required product and version

After removing a power policy applied to a specific group of computers, using their location group or organization group in the NightWatchman Management Console, the clients may still inherit power policies from further up the hierarchy - so Nightwatchman may still shut down the clients even though no power policy is directly applied to them.

To prevent the inheritance of a power policy with a shut down implemented you should create a ‘blank’ power policy, which may then be applied to the computers you want to specifically except from the inherited policy.

A group can be deleted by simply right-clicking it and selecting Delete Group. You will be asked to confirm, but if you do the group will be deleted immediately. Any clients in the group when it is deleted will effectively be ‘orphaned’, as they are associated with a group that no longer exists and will be excluded from reports. Even if you recreate a group with the same name, those clients will still be 'orphaned’ because the new group will have a different internal ID. It is therefore important to move all clients out of the group into another group before you delete the group.

AFWebService uses Anonymous Authentication whereas ReportConsole uses Windows Authentication. Windows Authentication is required on the ReportConsole application as access to reports can be secured using Active Directory groups.

The user account must have App_reporting_console and App_Reporting_Service on the AgilityFrameworkReporting database.

To ensure that NightWatchman does not shut down a machine during any critical operation it monitors the machine environment at the point when it is scheduled to shut it down and stops if it encounters any of the following:

If you want ignore all the observers, running deployments and software updates and always shut down machines, then set the value 0 (zero) in the following key on the client machines: HKLM\SOFTWARE\1E\Nightwatchman\ConsideredApplicationEvaluationStates.

In the Clients section of the NightWatchman Management Console there is a Queries tab that enables you to focus on a set of computers by querying their properties and displaying specific details for each computer that matches the query. There are two main parts to a query:

Queries and Criteria are used to define which computers are displayed on the Queries tab. You can retrieve computers using Queries related to their NetBIOS names, OUs, particular subnets or applied NightWatchman power policies. The criteria then specify the values for the properties you are checking for. For example you can check for NightWatchman power policies to retrieve all computers that have the myNWMPolicy applied.

Available query options are: All computers, By AD OU, By Hardware, By IP address, By Location Tier, By NetBIOS Name, By Organizational Tier, By Power Policy, By Subnet.

The display part lets you set what data you want to see from the computers that match the Query and Criteria. For example whether you want to see hardware information, Adapter details or Power details etc.

Available Display options: Hardware, Hierarchy, Network Adapters, Power, Software, Summary, Time in State.

You can extend the actions that are available to you when right-clicking on computers or computer groups in the NightWatchman Management Console. These are normally formatted as a parameterized command line, which is based on the context of what has been selected. There are three scopes where you can right click: Computer, ComputerSet and Tier and you can create different options for each of these.

The default extensions for the three scopes are: