Using the NightWatchman console

You run the NightWatchman console from the Start menu and use it to do the following:

• Model the physical and logical locations of the computers in your organization and use the import wizard. Refer to Using NightWatchman group hierarchies and Using the Import Wizard to populate hierarchies.

• Define Power schemes and Power policies and apply them. Refer to Using NightWatchman group hierarchies.

• Configure tariffs for energy costs and power consumption values according to hardware types. Refer to Tariffs and Setting power consumption data.

• Manage WakeUp servers. Refer to WakeUp servers.

• Define console security. Refer to NightWatchman console security.

• Configure general settings for the NightWatchman Management Center. Refer to The NightWatchman Settings section.

Starting the NightWatchman console

The NightWatchman Console is run from the Start menu and consists of:

• Clients.

• Power Schemes.

• Power Policies.

• Power Consumption.

• Tariffs.

• WakeUp Servers.

• Settings.

• Security.

Clients

When Clients is selected, the right-hand side shows the Location and Organization groups that are used for organizing computers with NightWatchman clients installed. When the NightWatchman Console is started, these groups are populated from the data held in the Agility Framework database. As you make changes to the Location and Organization groups, these are saved back to the Agility Framework database.

Initially, before either of the group hierarchies have been modified, the Location and Organization groups each contain a single node – the UNASSIGNED BUILDING and UNASSIGNED DEPARTMENT nodes, that always exist and contain computers with NightWatchman clients installed that have sent information back to the Agility Framework.

To learn how to add, rename and delete groups or to add remove computers from specific departments or buildings, refer to Managing client groups.

Location and Organization hierarchies are each constructed of 5 tiers, always with buildings and departments at the lowest tier, with the exception of UNASSIGNED BUILDING and UNASSIGNED DEPARTMENT.

Location groups

Location groups enable you to model your company according to the physical location of the computers. You apply location specific power settings to computers according to their region. For example, if you are aware of a specific national holiday, you can apply a one-off policy that sets a power setting for that particular country. There are five levels to both the Location and Organization hierarchies.

The Location group hierarchy is constructed of 5 tiers which use the following names in NightWatchman reports: Region, Country, State, City and Building, with clients assigned to Buildings.

Organization groups

Organization groups, in contrast, enables you to model your company according to organizational units. This structure lets you apply specific power settings to computers according to where they sit in the organization. For example, if you are aware of a specific departmental off-site team building exercise, you can apply a one-off policy that sets power setting for that particular department only.

The Organization group hierarchy is constructed of 5 tiers which use the following names in NightWatchman reports: Company, Subsidiary, Division, Business Unit and Departments, with clients assigned to Departments.

Queries

Queries enables you to display a set of computers that match your selection criteria. This allows you to explore the computers in your estate. You can copy, sort and export the results of a query, and wake up one or more computers from the list. Administrators can define custom actions which can be run against the results.

Power Schemes

Power Schemes let you define named groups of settings that control NightWatchman clients to set the power management properties of the computer it is running on. Power schemes are not directly applied to computers but are part of the definition of the power policies. In the Power Schemes section, you can view summaries of the power schemes, add new ones or edit, copy and delete the existing ones.

Power Policies

Power Policies let you define a combination of NightWatchman and WakeUp settings to power off and wake up machines together with a specific Power Scheme. These can be applied at any level of the location or organization hierarchies. The behavior of a power policy is inherited by all the computers associated with that hierarchy. In the Power Policies section, you can view summaries of the power policies, add new ones or edit, copy and delete the existing ones.

Power Consumption

NightWatchman Console lets you define power consumption figures for the various types of hardware encountered and reported back by the NightWatchman clients. In the Power Consumption section you can view the power consumption table and edit the power consumption values for the different power states for each type of hardware found.

Tariffs

The Tariffs section lets you define power costs that are applied to particular locations so that reports can more accurately show the actual costs for an organization. The Tariffs section lets you create a combined set of localized CO2 emissions per unit of power used and the cost per unit of power. Tariffs can only be applied to the Location group hierarchy, not to the Organization group hierarchy.

WakeUp Servers

NightWatchman Management Center can communicate with multiple WakeUp Servers to enable scalable wake up support across large and geographically diverse networks. These WakeUp Servers automatically register themselves with the NightWatchman Management Center. The WakeUp Servers section shows a list of registered servers where you can configure which subnets are managed by each server.

Settings

The Settings section lets you define default parameters for NightWatchman Client Policies along with units used by the NightWatchman reports.

Security

NightWatchman Console lets you modify computer power states across your entire network, so you need to control who has access. In the Security section, you can view currently assigned users and groups, add new ones or edit, copy and delete the existing ones. Users and groups have security roles assigned to them.

Using the Import Wizard to populate hierarchies

If you have large number of computers, manually populating the building and department groups is an onerous task. NightWatchman comes with an Import Wizard that lets you leverage information from the Active Directory to automate this process.

You can run the import by using the Import Wizard (an interactive process) or from the command-line, allowing the whole process to be batched to enable easy synchronization with the source data. It comes with scripts that support importing Organization Unit or Sites and Subnet data and rely on input files to define how this information maps on to the NightWatchman Group hierarchies. To learn more about these scripts, refer to Import scripts and input files.

Recommendations

Before running the Import Wizard in a production environment, we recommend that you perform the following steps:

1. Define the script input files.

2. Stop the NightWatchman central service.

3. Create a backup of the Agility Framework Reporting database.

4. Start the NightWatchman central service.

Running the Wizard

You can run the Import Wizard interactively from the Start Menu\NightWatchman Management Center\ImportWizard.exe menu item or from a command prompt. Refer to Command-line parameters.

1. Backup your NightWatchman database before you continue.

2. The Welcome screen, click Next.

3. On the Data Import Script screen, provide the following:

   

   • Location of the import script to be used to populate the temporary staging table.

   • Location of the NightWatchman Management Center database.

   • The destination group, location or organization.

4. On the Confirmation screen, click Next.

   

5. On the Import Progress screen, you can see the progress of the import.

   

   You may also be prompted for input in the conflict resolution stage.

   

6. On the Completion screen, you can see the results of the import.
   

Step through populating hierarchies with the Import Wizard tutorial

The UNASSIGNED BUILDING group has a number of computers that need to be assigned to various buildings in the London node. The London node is empty – there are no buildings for this location.

In this tutorial, we are going to:

1. Run an unattended import using the map machines to groups script to associate computers with buildings in the London group.

2. Discover conflicts after the silent install.

3. Run the import again in interactive mode to resolve these conflicts.

You are not able to resolve conflicts that arise because the Conflict Resolution dialog is not used in an unattended import. You need to run the import again but in interactive mode to determine what to do with the conflicts.

Before you start the Import Wizard

Before you start the Import Wizard, you need to populate the input file for the script you are going to use. We also recommend you do the following:

1. Stop the NightWatchman ConsoleService.

2. Create a backup of the Agility Framework Reporting database.

3. Restart the NightWatchman central service.

To run the Import Wizard successfully, you must be a database administrator or have been added to the Import Wizard database on the Agility Framework database server.

To enable the Import Wizard to do the work for us, we need to tell it how certain named computers map onto specific buildings. NightWatchman import script have an associated input file located in the same directory.

C:\Program Files\1E\NightWatchman Management Center\ConsoleService\ImportScript

For Map Machines, the import script is called Map_Machines_To_NWM_StagingTable.vbs. For the Import wizard to process this file successfully, we edit the associated input file where the format of each line is

Level1,Level2,Level3,Level4,Level5,NetBiosName,DomainName

• Levels 1-5 are the levels of the group hierarchy that the computer (identified by its NetBiosName and DomainName) is placed.

For example, to import a computer called ACMERR13 on the ACME domain into the London node we update the file with:

EMEA,UK,England,London,12a Trafalgar Road,ACMERR13,ACME

where the hierarchy is EMEA, UK, England, London, 12a Trafalgar Road. As the 12a Trafalgar Road group does not yet exist in the hierarchy, it will be created during the import.

We define a new line for each computer we import to the hierarchy.

Starting a unattended import

To run the Import Wizard in unattended mode, open a command prompt and change directory to where the Import Wizard is located:

C:\Program Files\1E\NightWatchman Management Center\ConsoleService

Run:

Copy

ImportWizard.exe 
-IsSilent 
-provider_vbscriptfile="ImportScript\Map_Machines_To_NWM_StagingTable.vbs" 
-tierleveltype='"location"

If you want to know more about import parameters, see Command-line parameters.

The Import Wizard can be run in unattended mode, during which it will not display any user interface. This is particularly suited to running the Import Wizard as a scheduled task. However, note that any conflicts encountered during a silent import will not be resolved, and these machines will not be moved to the appropriate location/organization tier. Please check ImportWizard.exe.log for more information. To address the conflicts, we run the Import Wizard interactively (without the -isSilent switch).

Running an interactive import to resolve conflicts

To run the Import Wizard in interactive mode, change to the directory where it is located.

C:\Program Files\1E\NightWatchman Management Center\ConsoleService

Run:

Copy

ImportWizard.exe -provider_vbscriptfile="ImportScript\Map_Machines_To_NWM_StagingTable.vbs" -tierleveltype='"location"

If you want to know more about import parameters, see Command-line parameters.

1. On the Welcome screen, click Next.

   

2. In the Data Import Script dialog, the Select the script: field is already populated with the location of your input file (derived from the command-line).

• 

3. Click Next to continue.

4. In the Confirmation dialog, click Next to start the import, Back to return to the Data Import Script dialog or Cancel to abort the import.

   

5. On the Import Progress screen, the progress of your import is displayed.

   

   The statuses are:

   • Succeeded

   • Failed

   • In progress

   • Not started

   • To do

     You may be prompted to resolve conflicts. In this particular instance, ACMESMRT2 has been referenced twice.

     

     To resolve the conflict:

     1. Choose the correct location for ACMESMRT2 and click OK. The import resume with until all records have been successfully imported.

     2. Click Next to go to the final page of the Import Wizard.

     3. To exit the Import Wizard, click the Finish button.

     NightWatchman Console displays the resolved conflict.

     

6. After the import, ACMESMRT2 is placed under 6 Peach Street

   

Import scripts and input files

The import Wizard comes with a number of sample scripts that use information from a number of sources to modify NightWatchman Management Center data to associate computers with their respective departments and buildings. These scripts are found in <installdir>\ConsoleService\ImportScripts.

• The scripts are all named <scriptname>.vbs.template. Copy and rename them to <scriptname>.vbs before you use them with the import Wizard.

• The input files are all named <inputfilename>.csv.template. Copy and rename to <inputfilename>.csv before you used them with the import Wizard.

For example, copy NWM_StagingTable_With_StoredProcedure.vbs .template and rename it to NWM_StagingTable_With_StoredProcedure.vbs.

The sample scripts do the following:

• Imports Active Directory Organizational UnitsImports Active Directory Organizational Units.

• Imports Active Directory sites.

• Maps computers to groups.

• Maps Subnets to groups.

• Resolves import conflicts.

Importing data

Once the import script, target database and target hierarchy have been selected in the Import Wizard, the import process performs the following steps to import the information from Active Directory.

1. Import data into the staging table – the tbNWM_Dimension_Group_Staging table is used to hold the information gathered from the source prior to converting it to the NightWatchman Console format.

2. Resolve computers by name – the script selected in the Import Wizard Data Import Script page is run and populates the NetBiosName, DomainName, GroupPath and SourceDataPath columns in the staging table.

3. Look for computers in more than one group – this step identifies any conflicts in the information being imported where a computer is being allocated to more than one group in either the Organization or Location group hierarchies. When running the wizard interactively, the administrator is prompted to resolve conflicts as they arise.

4. Add new groups – creates new groups necessary, arising from processing the import data.

5. Move computers to groups – the identified computers are moved to their allocated groups.

6. Queue computers for policy refresh – an existing group may have its own power policy assigned, any computer moved into a group is prompted to refresh its policy.

7. Clear staging table – once the import is completed, the staging table is purged of content.

Command-line parameters

By default the Import Wizard is located in the following directory:

32Bit Machines:C:\Program Files\1E\NightWatchman Management Center\ConsoleService
64Bit Machines:C:\Program Files(x86)\1E\NightWatchman Management Center\ConsoleService

It can be run from a command-line with:

ImportWizard.exe <command-line parameters>

For example, to run the Import wizard in unattended mode on a particular SQL Server instance and using the built-in machine mapping script to assign machines to organization groups:

ImportWizard.exe 
-IsSilent 
-AfrServer SQLSERVER\INSTANCE,14333
-Provider_VBScriptFile="ImportScripts\Map_Machines_To_NWM_StagingTable.vbs"
-TierLevelType="organization"

The command-line parameters for the Import Wizard are:

The default values for these parameters are stored in the ImportWizard.exe.config file which also contains the name of the database, however the isSilent value is ignored, which means isSilent parameter must be used to run the process silently.

Exploring Computers

NightWatchman lets you retrieve a set of computers that match a specific selection criteria. This is done from the Clients section of the NightWatchman Console via the Queries tab.

Retrieving computers

To retrieve a particular set of computers you can follow these general steps:

1. Select a query from the Query: field and any associated criteria from the Criteria: field.

2. Select the information you want to display for those computers from the Display: field.

3. Select whether to include obsolete computers in the results.

4. Click the Submit button to run the query to retrieve the computers.

Step through retrieving computers using queries tutorial

In this tutorial, we are going to display the results of a query:

1. Select a query.

2. Set the criteria for the query.

3. Select the display associated with the query.

4. Submit the query.

Displaying the results of a query

Queries are defined on the Clients/Queries tab.

To show how to display the results of a query we will use an example where the computers are selected according to the Location Tier they belong to. Select a query, in this example we select the By Location Tier option.

When the Query: has been selected you will see that the Criteria: field changes to match. In this case the Criteria: field changes to a list of the lowest level location tiers containing computers. In our example we select the 108 Rue Duval location tier.

After selecting the criteria for the selected query you then decide which information you want to display for the results. In our example we set the Display: field to Power, this will enable us to see what Power Policies have been applied to the computers in the results.

After selecting the criteria for the selected query you then decide which information you want to display for the results. In our example we set the Display: field to Power, this will enable us to see what Power Policies have been applied to the computers in the results.

Finally, you click Submit to tell the console to query the database for the computers matching the Query: and Criteria: values, then display the columns corresponding to the Display: value. In our example this returns all the computers in the 108 Rue Duval location tier and shows for each assigned Power Policy and Power Scheme.

Here you can see that all the example computers in the selected location tier have their Power Policy set to Always On and their Power Scheme set to None.

After the results have been displayed you can then sort the columns or export the data, refer to the following.

Step through sorting the results to better view the data tutorial

In this tutorial, we are going to sort the results of a query:

• Click on a column heading to sort the results by that column.

• Click again to reverse sort by that column.

Sorting columns

In the previous tutorial we showed how to display the Power Policies for the computers in a particular location tier, another way to check which computers are assigned which Power Policy is to use the All computers query and then select the Power display.

Notice how there is no criteria available when All computers is selected.

Here you can see a number of different Power Policies that have been applied to the computers in the results.

Sometimes it is useful to sort the contents of the table. For example if you want to see all the computers that have a particular Power Policy defined you can sort the results of the All computers query by clicking on the Assigned Policy column heading.

Initially you would likely see something similar to the picture shown above where all the computers that have no Power Policy assigned are displayed first. You can either scroll down to see the other Power Policy values or click the Assigned Policy column heading again to reverse the order of the sort.

Step through exporting the results of a query tutorial

In this tutorial, we are going to export the results of a submitted query:

1. Export the results using the Export items to CSV file... link.

2. Select the file name and location for the exported file.

3. See the confirmation that the file has been exported.

4. View the file after export.

Exporting data

Sometimes it is useful to export the results of a query to a file so that it can be used in other applications. NightWatchman will export the data to a file containing comma separated values that correspond to each row of the data and the display columns returned as a result of submitting the query.

The following picture shows the Export items to CSV file... link that initiates the export process.

Clicking the link displays the Save query results dialog. You can set the name for the exported file and choose where it is saved. Click Save to export the data.

After the data has been exported a confirmation dialog show where the file is saved and provides an option to open the file directly. The data is exported in the original order the results were returned in, for example any sorting done using the column headings are ignored.

Out of the box, NightWatchman Enterprise provides a set of built-in queries, criteria and display options - though these may be extended by an administrator, see Extending the Console Query interface for more details. The following headings describe the available built-in queries, criteria and display options.

Built-in queries and criteria

The following table describes the built-in queries and associated criteria available from the Query: and Criteria: fields:

Built-in display options

The display options control what columns of information are displayed for the results of the query. There are three columns that are shown for all display options:

The following table describes the built-in display options available from the Display: field.

Obsolete computers

NightWatchman will set a computer to obsolete if it has not been in touch with NightWatchman Enterprise for a configurable number of days. You can control the number of days (between a minimum of 7 and a maximum of 90) using the Hide obsolete clients after days setting in the The NightWatchman Settings section.

By default obsolete computers are not displayed in the returned results of a query. You can turn the display of these on by checking the Include obsolete machines in results. When the checkbox is checked an additional Obsolete column is displayed in the results that indicates whether a computer row comes from an obsolete computer or not.

Step through including obsolete computers in the results tutorial

In this tutorial, we are going to show how to include obsolete computers in the results of a submitted query:

1. Checking the Include obsolete machines in results.

2. Viewing the obsolete machine data.

Including obsolete computers

You can elect to include obsolete computers in the results of a query by checking the Include obsolete machines in results checkbox prior to submitting the query.

When you run the query, the results include an Obsolete column.

Reverse ordering the results on the Obsolete column shows all the obsolete computers in the query results.

Interacting with the results

When the results are displayed you can select rows of computers in the results table and interact with them using a right-click context menu. There are three options that are provided, as described in the following table:

Step through running actions on the results tutorial

In this tutorial, we are going to show how to run actions on the query results using the right-click context menu:

1. Performing an on-demand wakeup.

2. Running an action on the results.

3. Displaying the Properties dialog for a single computer in the results.

Performing an on-demand wakeup

You can perform an on-demand wakeup on one or more computers in the results.

1. Submit a query to retrieve the computers you want to wake up.

2. Select the computers from the results list.

3. Right-click the selection.

4. Select On-demand Wakeup from the right-click context menu.

5. A notification dialog will appear showing that the selected number of computers have wakeup requests queued.

Running an action on the results

Following a fresh installation the Actions right-click context sub-menu is not visible. This section can be enabled and extended by a NightWatchman Management Center administrator, see Extending the Console Query interface for more details.

When the Actions menu has been enabled you can perform the following outline steps, the real steps will depend on what actions the NightWatchman Administrator has enabled.

1. Submit a query to retrieve the computers you want to display properties for.

2. Make a single or multiple selection from the results.

3. When you right-click the selected computers a context menu is displayed.

4. If any actions have been defined these will be available in the Actions sub-menu. The actions that are displayed are dependent on the scope that has been assigned to the action and whether the selection contains a single computer or multiple computers.

5. Select the action you want to perform from the Actions sub-menu.

The example shows a system where a number of actions have been defined for the single computer scope. In this example, a ping action is selected. The results of running an action are completely dependent on the action's definition.

Displaying the properties dialog for a single computer

You can select to view the properties dialog for a single computer in the results.

1. Submit a query to retrieve the computer you want to display properties for.

2. Select the computer from the results list.

3. Right-click the selection.

4. Select Properties from the right-click context menu.

5. The Properties dialog is displayed for that computer.

   

Power schemes

Power schemes provide a convenient structure for defining and re-using commonly required power management settings. A NightWatchman power scheme is a collection of power management settings that can be selected and applied through a power policy.

Managing power schemes in the NightWatchman console

Using NightWatchman Console you can:

• Create power schemes. Refer to Creating a new power scheme.

• Edit existing power schemes. Refer to Editing power schemes.

• Create new power schemes by copying existing ones. Refer to Creating a new power scheme.

• Delete power scheme. Refer to Deleting power schemes.

Creating a new power scheme

To add a new power scheme in the NightWatchman console:

1. In the Power Schemes section, click Add.

2. Set the required values in the Add Power Scheme dialog.

3. Click OK to save the new power scheme.

Step through creating power schemes tutorial

In this tutorial, we are going to:

1. Create the Reasonable user power scheme.

2. Define the properties for it.

To create power scheme called Reasonable user:

1. In the Power Scheme section, click the Add button.

2. In the Add Power Scheme dialog, enter Reasonable user for the new power scheme.

3. Define the properties for this power scheme. These properties determine the behavior for the display, hard disks and computer and correspond to the power settings in the Power Management section in Control Panel.

• 

4. Click OK to save the new power scheme.

The Add Power Scheme dialog

The Add Power Scheme dialog lets you define properties for the new power scheme:

• Name field: The name for the new power scheme. This field cannot be left blank.

• Turn off display after: Sets when the power scheme turns the monitor off after a period of inactivity. You can set different values for this parameter for use when the computer is plugged in or running on batteries.

• Turn off hard disks after: Sets when the power scheme turns the computer's hard disks off after a period of inactivity. You can set different values for this parameter for use when the computer is plugged in or running on batteries.

• Standby: Sets when the power scheme puts the computer into standby mode after a period of inactivity. You can set different values for this parameter for when the computer is plugged in or running on batteries. This parameter must be set to a shorter time than the Hibernate parameter.

• Hibernate: Sets when the power scheme puts the computer into hibernate mode after a period of inactivity. You can set different values for this parameter for when the computer is plugged in or running on batteries. This parameter must be set to a longer time than the Standby parameter

• Prompt for password when computer wakes up: Check this checkbox if you want the computer to prompt the user when it awakes from a standby or hibernate mode.

Editing power schemes

To edit an existing power schemes in the NightWatchman Console:

1. In the Power Schemes section, select the Power Scheme you want to edit.

2. Click the Edit button.

3. Change the required values in the Edit Power Scheme dialog, which has the same parameters as the Add Power Scheme dialog.

4. Click OK to save the changes to the Power Scheme.

Step through editing power schemes tutorial

In this tutorial, we are going to:

1. Update the Hibernate property for the Infrequent User power scheme.

2. Set the new value to 20 minutes

To edit an existing power scheme:

1. In the Power Scheme section, select the Infrequent User power scheme.

2. Click the Edit button.

3. In the Edit Power Scheme dialog, we update original hibernate value from never to a new value. You must set the hibernate value to be greater than the standy value. If you fail to do so, the constraints set by this dialog is broken and an error is displayed in the dialog. We are going to set hibernate to 20 mins.

• 

4. Click OK to save the new value.

• 

Copying power schemes

To copy an existing power schemes in the NightWatchman Console:

1. In the Power Schemes section, select the Power Scheme you want to copy.

2. Click the Copy button. This takes a copy of the settings of the selected Power Scheme and opens the Edit Power Scheme dialog.

3. Change the values in the Edit Power Scheme dialog if necessary. It the same parameters as the Add Power Scheme dialog.

4. Click OK to save the Power Scheme.

Step through copying power schemes tutorial

You can copy an existing power scheme to save time if you are creating a new power scheme with similar properties. This is especially useful for more complex power policies.

In this tutorial, we are going to:

1. Copy an existing power policy.

2. Update the properties for the new power policy.

To copy an existing power scheme:

1. Select the power scheme to copy.

2. Click the Copy button.

3. In the Copy Power Policy dialog, rename the power policy.

4. Update the values for Turn off display:, Turn off hard disks:, Standby:, Hibernate: and Prompt for password when computer wakes up.

5. Click OK to save the new power scheme.

Deleting power schemes

To delete an existing power schemes from the NightWatchman Console:

1. In the Power Schemes section, select the Power Scheme you want to delete.

2. Click the Delete button.

3. If the warning option is turned on the Confirm delete dialog is displayed. Click Yes to continue with the deletion or No to cancel.

4. Clicking Yes attempts to continue with the deletion. If the Power Scheme has previously been associated with a Power Policy an Unable to delete scheme warning dialog is displayed indicating that the Power Scheme is in use and you are able to delete the selected scheme.

5. If the Power Scheme is not currently associated with a Power Policy, clicking Yes permanently removes Power Scheme from the NightWatchman Console.

Disabling the deletion warning dialog

To prevent NightWatchman from displaying the deletion warning dialog every time you delete a power scheme, power policy, tariff, security role or security account, check the Don't ask me again checkbox, located on the warning dialog itself.

Step through deleting power schemes

In this tutorial, we are going to:

• Delete the Frequent User power scheme.

Deleting a power scheme removes it from the Agility Framework database.

To delete an existing power scheme:

1. Select the Frequent User power scheme.

2. Click the Delete button.

3. In the Confirm delete dialog, click Yes to delete the power scheme or No to cancel the delete. You can disable this dialog by checking the Don't ask me again checkbox.

   

4. If the Frequent User power scheme is associated with a power policy, you will not be able to delete it.
   

Disabling the deletion warning dialog

To prevent NightWatchman from displaying the deletion warning dialog every time you delete a power scheme, power policy, tariff, security role or security account, check the Don't ask me again checkbox, located on the warning dialog itself.

Power policies

A NightWatchman power policy is a collection of NightWatchman settings that can be applied to a computer to determine how it behaves in terms of its power consumption. Using the NightWatchman power policies, you can apply consistent behaviors for power schemes, shutdowns and wakeups across the network for specific groups of computers. Like power schemes, these power policies are maintained in a library.

Daily scheduled actions

NightWatchman Enterprise supports setting different times, actions and logoffs for each day of the week, letting you tailor NightWatchman behavior to suit your weekly business working practices. Daily scheduled actions are controlled from on the The Scheduled Actions tab.

Alarm clocks

An alarm clock definition consists of a weekday and time when it takes place. For example, you may want all the machines in a development department to be available at 08:00am Monday to Friday, except Thursday when there is a team meeting, so the machines should be available at 10:00am.

Alarm clocks wake up the NightWatchman client computer for 60 minutes. If you want the computer to wake up for a different duration, use Maintenance windows instead. You can set an alarm clocks from the NightWatchman command-line or from its console.

You can define an alarm clock by creating and applying a power policy. An advantage of using a power policy over the command-line for alarm clocks is that if WakeUp integration is enabled, you can bring a computer out of a power-off state. Using the command-line, you can only bring a computer out of a sleep state. Details on how to configure an alarm clock as part of a power policy can be found here: The Power Policy dialog.

Maintenance windows

A maintenance window definition consists of a weekday and time when it takes place, the duration and the action it takes at the end of the event. For example, you may want all the machines in a network to be available for 1 hour at 02:00h every Wednesday to receive Windows updates and shut down afterwards. You can set maintenance windows from the command-line or from its console.

You define maintenance windows by creating and applying a power policy. An advantage of using power policies over the command-line for maintenance windows is that if WakeUp integration is enabled, you can bring a computer out of a power-off state. Using the command-line, you can only bring a computer out of a sleep state. Details on how to configure a maintenance window as part of a power policy in the NightWatchman Console can be found using the The Power Policy dialog.

Computer reclaim

Computer reclaim (formerly hardware utilization) aims to identify the number of computers which are actually being used in an organization – the aim is to identify hardware waste where you have 50,000 computers in your organization but it turns out that no more than 30,000 are actively used at any given time. See the Using Computer Reclaim section for best practices on this.

You can gather computer reclaim data by creating a power policy where the Monitor Computer Reclaim option is enabled and then applying it to the machines you want to monitor. Alternatively, you can enable this feature by setting the 1E Agent HARDWAREUTILIZATION installer property to ON during its installation on the machine you want to monitor.

The sample and aggregation intervals for is set in the NightWatchman Console (more details under the Computer Reclaim section in The NightWatchman Settings section). Reports are available in the Reports console. Refer to Reporting.

Sleepless client detection

Sleepless client detection helps optimize your NightWatchman client computers ability to go into a sleep state, and as a result increasing power savings and energy efficiency in your organization. There are two levels of sleepless detection – the basic level is enabled by default.

The advanced level requires explicit enabling. It is possible that some applied operating system updates may prevent the advanced sleepless detection feature from functioning correctly. For this reason it is not enabled by default. To benefit from the additional process name information provided by advanced sleepless detection you must enable it. This is done from the Sleepless Client Detection tab in the NightWatchman console. Refer to The Sleepless Client Detection tab.

In basic mode, it reports on faulty input devices and flags potential causes why an unattended computer is failing to enter into a sleep state.

In advanced mode, where possible, it additionally identifies specific processes that prevent the unattended computer from entering into a sleep state. These processes can be added to the sleepless exclusion list to enable the computer to enter into a sleep state where appropriate, regardless of whether the named processes are running at that time.

The process for the basic sleepless detection is:

1. NightWatchman monitors the keyboard and mouse and if it does not find a period of inactivity that is greater than 30 seconds over a 24 hour period it will report back to Agility Framework Reporting with the input device as potentially being unreliable.

2. If the input devices are verified as allowing the computer to enter a sleep state, NightWatchman then examines the running processes:

   1. If a process causes overall CPU usage to exceed 20%, it will prevent the computer from going to sleep when it should have and is reported as a busy process.

   2. If a process sets a system required flag, it is noted in the basic sleepless detection mode but the information about the process requesting it will not be available. The <unknown process> is reported as a sleepless process.

3. The busy and sleepless process information is batched together with other NightWatchman client data and recorded in the Agility Framework Reporting at the next transmission time.

Advanced sleepless detection adds the following information to the basic sleepless detection:

1. If a process sets a system required flag, the system is analyzed and the actual process name derived and reported as a sleepless process in place of the <unknown process> reported by the basic sleepless detection.

2. The sleepless detection information from the client is sent back to Agility Framework Reporting and appears in two NightWatchman reports under the heading Sleepless Client Detection:

   1. Busy and Sleepless Processes: Indicates the processes running on the client computer that are the likely cause for it not entering into a sleep state.

   2. Untrusted input device: Indicates potentially faulty input devices that are the likely cause for a client computer not entering into a sleep state.

Once you have reviewed the NightWatchman reports that identify potential reasons why a particular client computer is being kept from entering into a sleep state, you can add any processes named in the report to the sleepless exclusion list for that particular NightWatchman client. Refer to The Process Exceptions tab. This is where the extra process name resolution of the advanced sleepless detection really comes into its own. We recommend that the Power Policy with the excluded processes only gets applied to the computers reported against in the NightWatchman Busy and Sleepless Processes report.

When a NightWatchman client computer is at the point where it should enter a sleep state, NightWatchman checks any named processes on the sleepless exclusion list. If the only processes preventing sleep are in the sleepless exclusion list NightWatchman will force the computer to enter into a sleep state regardless.

Managing power policies in the NightWatchman console

NightWatchman power policies define configuration settings for both NightWatchman and WakeUp. Together, they control the availability of computers and maximize power savings while minimizing any impact on productivity. Power policies are not assigned directly to computers but they are assigned to the groups that contain the computers. This is done from the Location or Organization group hierarchies. Refer to Using NightWatchman group hierarchies.

Creating a new power policy

To add a new power policy:

1. In the Power Policies section, click the Add button.

2. Set the required values in the Add Power Policy dialog.

3. Click OK to save the new power policy.

Step through creating power policies tutorial

In this tutorial, we are going to:

1. Create a new power policy for Sales.

2. Put computers in a hibernate state at 18:00 Mondays to Fridays using a passive logoff so as not to interrupt users. Over the weekend, power off computers at 13:00 and use a force logoff to ensure that computers are powered off at that time.

3. Set the behavior for the weekday hibernate and weekend power off events.

4. Wake up computers at 07:00 on Mondays only and for the rest of the week at 07:00. We will not be waking up computers over the weekend.

To create a new power policy:

1. In the Power Policies section, click the Add button to open the Add Power Policy dialog.

   

2. In the General tab, we create a new power policy called Sales.

3. In the Power Schemes drop-down, select the Frequent User scheme and associate it with the Sales power policy.

   

   We choose this policy to minimize the impact of power management settings for sales personnel so that their displays do not turn off so often, the hard disks power down less, etc. We also leave the boxes for both the Show System Tray Icon and Allow Shutdown Deferral at their default settings. By doing this, we configure the NightWatchman client to display its system tray icon and enable the user to defer scheduled shutdowns. This option enables sales personnel to have control over the conditions of the shutdown and not interrupt a task they are involved in, such as a sales call.

   Scheduled actions lets you determine the behavior of computers for Sales when a power down event takes place. In this tutorial, we are going to put computers for Sales into a hibernate state at 18:00 every Monday to Friday, but if staff are still logged in and working, they have the option to defer the hibernation. On Saturday and Sunday, we are going to power off computers at 13:00.

   

4. Click the Scheduled Actions button to determine what happens each day of the week.

5. Check the boxes for each of the days you want the event to take place and set the time, action and shutdown action for it. We set the value for Legacy Agent to 18:00 just in case we still have legacy 1E Agents in the environment (they do not support individual scheduled actions). These legacy agents will use the values for Action and Logoff in the Power Down Default tab. Power down defaults determines the behavior of scheduled actions.

6. Click the Power Down Defaults tab to set the default behavior for Scheduled Actions.

   

   The Action: field is applicable to NightWatchman once off and legacy 1E Agents that do not support the individual daily scheduled actions of version 6.1. The Logoff: field is used by maintenance windows, NightWatchman once off and legacy 1E Agents. The rest of the fields are applicable to all scheduled actions. We are going to leave these at their default values.

7. Click the Alarm Clock tab. Alarm clocks lets you control when computers gets woken up. In this example, we are going to wake up computers on Mondays at 06:00 because we know that staff turn up early on Mondays and at 07:00 for the rest of the weekdays.

   To configure these options, you will need to have set the WakeUp integration option during installation.

8. Check the Enable Alarm Clock checkbox to enable wake up functionality. If you also want to turn the displays on, check the Turn On Monitor checkbox.

9. Set the wake up time for Monday at 06:00.

   The wake up time entered must comply with a valid hh:mm format, including use of a leading zero for hours 0-9am.

10. Set the wake up time for Tuesday through to Friday at 07:00.

11. Clock OK.

Editing power policies

To edit existing power policies:

1. In the Power Policies section, select the power policy you want to edit.

2. Click the Edit button.

3. Change the required values in the Edit Power Policy dialog, which has the same parameters as the Add Power Policy dialog.

4. Click OK to save the changes to the power policy.

Step through editing power policies tutorial

In this tutorial, we are going to:

• Edit an existing power policy

To edit an existing power policy:

1. In the Power Policies dialog, select the power policy to edit from the list.

2. Click the Edit button to display the Edit Power Policy dialog.

3. Update the values for the General, Scheduled Actions, Power Down Default and Alarm Clock tabs.

Copying power policies

To copy existing power policies:

1. In the Power Policies section, select the power policy you want to copy.

2. Click the Copy button. This takes a copy of the settings of the selected Power Policy and opens the Edit Power Policy dialog.

3. Change any required values in the Edit Power Policy dialog, which has the same parameters as the Add Power Policy dialog.

4. Click OK to save the copied power policy.

Step through copying power policies tutorial

In this tutorial, we are going to:

1. Copy the Sales power policy.

2. Rename it to Marketing.

3. Change the time we hibernate the computers as they typically leave the office later than sales staff.

4. Change the time we wake up their computers as they typically arrive in the office later than sales staff.

To create a copy of the Sales power policy:

1. Power Policies dialog, scroll down the list and select the Sales power policy.

2. Click the Copy button.

   

3. We rename the copied power policy to the new one.

   

   Change Copy of Sales to Marketing.

4. Click the Scheduled Actions tab.

   

   As we know that personnel in Marketing work later than those in Sales, we change the time we hibernate their computers to 20:00 on Mondays to Fridays.

5. Update the values in the Time: fields from 18:00 to 20:00 for Monday to Friday.

6. Update the Legacy Agent field from 18:00 to 20:00.

7. Click the Alarm Clock tab.

   

   We also know that the people in Marketing arrive in the office later than Sales so we can safely set their computers to wake up at a later time.

8. Update the Time: fields from 07:00 to 08:00 for Monday to Friday.

9. Click OK to save the Marketing policy.

Deleting NightWatchman power policies

To delete an existing power policy:

1. In the Power Policies section, select the power policy you want to delete.

2. Click the Delete button.

3. If the warning option is turned on the Confirm delete dialog will be displayed. Click Yes to continue with the deletion or No to cancel.

4. Clicking Yes attempts to continue with the deletion. If the power policy has previously been associated with a group in either the Organization or Location hierarchies, a warning dialog is displayed indicating that the power policy is in use and that you are able to delete it.

5. If the power policy is not currently associated with a group, clicking Yes permanently removes the selected security role from the NightWatchman Console.

Step through deleting power policies tutorial

In this tutorial, we are going to:

• Delete the Zone 1 power policy.

To delete the Zone 1 power policy:

1. In the Power Policies dialog, scroll down the list and select Zone 1.

2. Click the Delete button.

3. In the Confirm delete dialog, click Yes to delete the power scheme or No to cancel the delete.You can disable this dialog by checking the Don't ask me again checkbox.

   

4. If the Zone 1 power policy is associated with a group, you will not be able to delete it.

   

The Power Policy dialog

The Power Policy dialog is displayed whenever you Add, Copy or Edit a power policy. The tabs in the Power Policy dialog are:

• General: Lets you set the power scheme and control the NightWatchman client scripts.

• Scheduled Actions: Lets you define scheduled action days, times, actions and logoff combinations for a power policy.

• Power Down Defaults: Lets you define default settings that are used across a variety of NightWatchman Enterprise functions.

• Alarm Clock: Lets you set wake up call options for the power policy.

• Maintenance Window: Lets you set actions and a schedule for any maintenance window requirements for the power policy

• Process Exceptions: Lets you set definitions for particular process names to prevent a NightWatchman shutdown.

• Sleepless Client Detection: Lets you enable NightWatchman functionality that puts client computers into standby mode.

The General tab

The General tab lets you set the power scheme and control the NightWatchman client scripts.

Control	Notes
Power Scheme	Displays a list of the currently defined NightWatchman power schemes. Select one to associate it with the current power policy.
Execute 'PreRun' Script	Controls whether the NightWatchman PreRun script (PreRun.vbson Windows andPreRun.scpton the Mac) is run prior to a scheduled NightWatchman power down on a client computer.
Ignore Script Errors	NightWatchman ignores script errors during a scheduled sequence and will not abort the event.
Execute 'RunAlways' script on power off	Determines whether the NightWatchman RunAlways script is run on NightWatchman power off actions: Poweroff, Logoff and Reboot. On Windows, it is called RunAlways.vbs; on the Mac, it is RunAlways.scpt.
Execute 'RunAlways' script on sleep	Controls whether the NightWatchman RunAlways script (RunAlways.vbson Windows andRunAlways.scpton the Mac) is run on NightWatchman Hibernate and Standby sleep actions.
Execute 'RunOnResume' script on resume	Determines whether the NightWatchman RunOnResume script (RunOnResume.vbson Windows andRunOnResume.scpton the Mac) is run whenever the client resumes from a low-power state. Scripts can be configured to enable the RunOnResume script to return a computer to a similar state to the one it was in prior to running any NightWatchman scripts on entering the low-power state.
Script Timeout (sec)	Timeout (in seconds) for application responses to the NightWatchman shutdown scripts.
Show System Tray Icon	When checked, displays the NightWatchman system tray icon on the client computer. Uncheck it if you do not want users to interact with NightWatchman.
Allow 'Keep Active'	Enables users on the client computer to defer NightWatchman power downs.
Monitor Jobs	Enables detection of pending Configuration Manager jobs on the client computer at the point when NightWatchman powers down.
Pending Job Window (mins)	Duration (in minutes) for detecting pending Configuration Manager jobs on the client computer at the point when NightWatchman powers down.
Monitor Computer Reclaim	Enables Computer Reclaim (formerly Hardware Utilization) monitoring and configures the 1E Agent to retrieve information from computers to determine which ones are in use during the day.
Monitor Power Optimization	Enables power monitoring and configures the 1E Agent to retrieve information from computers to determine which ones are using battery and connect standby features correctly.
Monitor Reboot Optimization	Enabled reboot monitoring and configures the 1E Agent to retrieve information from computers to determine when they are rebooting or should be rebooted

The Scheduled Actions tab

Control	Notes
Day checkboxes	Ticking the day checkbox enables a NightWatchman scheduled action on that day. Each day can have its own Time, Action and Logoff settings.
Time	Time the scheduled action starts for that day.
Action	Action for the event which may be one of: Poweroff: Turns the power for the client computer off. Standby: Puts the client computer into standby mode. Hibernate: Puts the client computer into hibernate mode. Reboot: Reboots the client computer. Logoff: Logs off the current user of the client computer. Logoff then Standby: Logs off the current user of the client computer and if successful then puts the client computer into standby mode.
Logoff	Behavior of NightWatchman when users are logged on to the client computer: Passive: If a user is logged on to the client computer at the scheduled time, no action is taken. If there is no user logged on to the client computer at the scheduled time, NightWatchman runs the selected Action. Active: If a user is logged on to the client computer at the scheduled time, a NightWatchman countdown dialog is displayed allowing the user to proceed immediately or delay the shutdown on the computer. If there is no user logged on to the client computer at the scheduled time, NightWatchman runs the selected Action. Force: If a user is logged on to the client computer at the scheduled time, a NightWatchman countdown dialog is displayed to the user. The user has no option to delay the shutdown. If there is no user logged on to the client computer at the scheduled time, NightWatchman runs the selected Action.
Legacy Agent	Scheduled action time for earlier releases of the 1E Agent that do not support daily shutdown actions. This time is applied on the days checked on the Scheduled Actions tab. Legacy 1E Agents uses the Logoff and Action values set in the The Power Down Defaults tab.

The Power Down Defaults tab

Control	Description
Action	The behavior for for once-off and legacy 1E agent events when they start and may be one of: Poweroff: Turns the power for the client computer off Hibernate: Puts the client computer into a hibernate state Standby: Puts the client computer into a standby state Logoff: Logs off the current user of the client computer Reboot: Reboots the client computer
Logoff	The behavior for maintenance windows, once-off and legacy 1E Agent events when users are logged on to the client computer. Passive: If a user is logged on to the client computer at the scheduled time, no action is taken. If no user is logged on to the client computer at the scheduled time, NightWatchman runs the selected Action. Active: If a user is logged on to the client computer at the scheduled time, a NightWatchman countdown dialog is displayed allowing the user to proceed immediately or delay the shutdown on the computer. If no user is logged on to the client computer at the scheduled time, NightWatchman runs the selected Action. Force: If a user is logged on to the client computer at the scheduled time, a NightWatchman countdown dialog is displayed to the user. The user has no option to delay the shutdown. If no user is logged on to the client computer at the scheduled time, NightWatchman runs the selected Action. Retry Attempts: Sets the number of times NightWatchman attempts a shutdown if deferred by the user. Retry Interval (mins) – interval (in minutes) between shutdown attempts User Activity Idle (mins) – duration (in minutes) a user is inactive on the NightWatchman client before a scheduled action. If they have been active on the computer during the specified period prior to a NightWatchman scheduled action, the action is postponed. The deferment is governed by the time set in the Retry Interval field. If the Logoff field is set to Force, the user activity is not monitored and the computer is shutdown regardless. If this value is set to anything other than 0, any local command on the NightWatchman client to run shutdown now will not work. Countdown (secs): Duration (in seconds) the countdown timer is displayed to a user if they are logged on to a computer Message: Message displayed on the NightWatchman countdown dialog

The Alarm Clock tab

Control	Description
Enable Alarm Clock	Enables the alarm clock feature and the rest of the controls on the Alarm Clock tab.
Turn On Monitor	Switches on the display and computer when the alarm call occurs.
Day checkboxes	Schedules the days the alarm clocks takes place.
Time fields	The time to wake the client computer for the corresponding day. If a NightWatchman client computer is in a suspend or hibernate state when the alarm clock time is reached, it will wake itself. Wake-On-LAN is triggered for an alarm clock event when the: client computer is powered off. client computer is connected to the LAN. NightWatchman Console WakeUp integration is enabled. By design, the alarm clock option has no effect on laptop computers. This is to prevent them powering on from suspend at inappropriate times, such as when they are in transit.Wake up time values use an hh:mm format. For hours 0-9, a leading zero must be used.

The Maintenance Window tab

The options for the maintenance window are:

Control	Description
Enable Maintenance Window	Enable the maintenance window feature and the rest of the controls in this tab.
Turn On Monitor	Switches on the display and computer when the maintenance window occurs.
Day checkboxes	Schedule the days the maintenance window takes place. The options for each window are: wakeup at: Start time for the maintenance window for minutes: Duration (in minutes) for the maintenance window then: Event that follows at the end of the maintenance window, which may be one of the following: Do nothing: Take no action when the maintenance window expires, leaving the client computer on. Hibernate: Puts the computer into hibernate mode when the maintenance window expires Standby: Puts the computer into standby mode when the maintenance window expires. Poweroff: Powers-off the computer. By design, the alarm clock option has no effect on laptop computers. This is to prevent them powering on from suspend at inappropriate times, such as when they are in transit.

The Process Exceptions tab

The options for defining process exceptions are:

Control	Description
Process exceptions list	Add the name of a process to this window if you want its presence in the client computer's running processes list to prevent the computer from shutting down when a NightWatchman scheduled action occurs.

The Sleepless Client Detection tab

Control	Description
Sleepless process exception list	List processes you want to prevent from keeping the client computer from going into standby state.
Enable Advanced Sleepless Detection	Enables Advanced Sleepless Detection on client computers with this power policy applied. This option allows the sleepless client detection feature to discover exactly which process, running on the client, is preventing the computer from going to sleep when the power scheme timers expire. It is possible that some applied Operating System updates may prevent this feature from functioning correctly. Before enabling this feature in a production environment, we recommend you test against specific versions of Windows deployed in your environment.

Tariffs

Managing tariffs in the NightWatchman console

• You can define power costs in the NightWatchman console which can be applied to particular locations so that reports can more accurately show the actual costs for an organization.

• The Tariffs section lets you create a combined set of localized CO2 emissions per unit of power used and the cost per unit of power.

• Tariffs can only be applied to the Location group hierarchy, not to the Organization group hierarchy.

The Tariff dialog

The Tariff dialog is displayed whenever you Add, Copy or Edit Tariffs. The fields in the Tariff dialog are:

• Name: The name of the tariff; used when applying tariffs to location groups. The tariff name must be unique and is validated when you click OK.

• Description: Holds supplementary information about the cost and CO2 emissions settings for the tariff.

• Cost per kWh: The cost per kWh of energy used for this particular tariff. Cost is displayed in the currency that was set during installation but this can be changed in The NightWatchman Settings section.

• CO2 per kWh: Localized values for the amount of CO2 created per kWh of power generated.

• Utility Provider: The name of the utility provider for the location where the tariff is applied. This is the name that will appear in Reports.

Currency and CO2 per kWh units are global and dependent on the values defined in The NightWatchman Settings section.

Creating a new Tariff

To add a new tariff in the NightWatchman Console:

1. In the Tariffs section, click the Add button.

2. Set the value for the tariff.

3. Click OK to save the new tariff.

Step through creating a new tariff tutorial

In this tutorial, we are going to:

• Define a tariff for the state of California that is based on the 2009 average commercial retail price of 11.6 cents per kWh and .724 lb/kWh of CO2 emissions.

To create a new tariff for California:

1. In the Tariffs section, click the Add button.

   

2. In the Add Tariffs dialog, update New tariff 1 to California.

   

3. In Description, enter a description for this tariff.

4. In Cost per kWh:, enter .116. This is average commercial retail price for a kWh (11.6 cents) from 2009.

   The cost units are initially set during installation but this can be changed in the NightWatchman Settings.

5. In CO2 per kWh:, enter .724. This is the pound to kilowatt-hour ratio for CO2 emissions from 2009.

6. In Utility Provider: enter the name for the utility provider.

   

7. Click OK.

Editing Tariffs

To edit an existing tariff in the NightWatchman Console:

1. In the Tariffs section, select the tariff to edit.

2. Click the Edit button.

3. Update the value for the tariff.

4. Click OK to save the changes for the tariff.

Step through editing an existing tariff tutorial

In this tutorial we are going to:

• Edit an existing tariff "California" with new Cost Per KWh and CO2 per KWh values

1. In the tariff section, select tariff "California.Click on Edit button.

   

2. Update Cost per Kwh value to: .229

3. Update CO2 emissions per KWh: .658 Ibs/KWh

4. Click on OK.

Copying Tariffs

To copy an existing tariff in the NightWatchman Console:

1. In the Tariffs section, select the tariff to copy.

2. Click the Copy button. The Copy Tariff dialog opens with a copy of the settings from the selected tariff.

3. Update the values for the tariff as necessary in the Copy Tariff dialog.

4. Click OK to save the tariff.

Step through copying an existing tariff tutorial

In this tutorial we are going to:

• Copy an existing tariff "California"

To copy an existing tariff:

1. In tariff section, select existing tariff "California". Click on Copy button.

   

2. In the Copy Tariff dialog, update Copy of California to Texas.

   

3. In Description, add the description for this tariff.

4. In Cost per KWh: enter .555.

5. In CO2 per KWH: enter .666.

6. In Utility Provider: enter name of the utility provider

7. Click OK.

   The copied tariff is listed under Tariff section.

   

Deleting Tariffs

To delete an existing tariff from the NightWatchman Console:

1. In the Tariffs section, select the tariff to delete.

2. Click the Delete button

3. If the warning option is turned on the Confirm delete dialog is displayed. Click Yes to continue with the deletion or No to cancel.

4. Clicking Yes continues with the deletion. If the tariff has previously been associated with a group in either the Organization or Location hierarchies, a warning dialog is displayed indicating that the tariff is in use and that you cannot delete it.

5. If the tariff is not currently associated with a group, clicking Yes removes it from the NightWatchman Console.

Step through deleting an existing tariff tutorial

In this tutorial we are going to:

• Delete an existing tariff "California"

To delete an existing tariff:

1. In the tariff section, select tariff "California". Click on Delete button.

   

2. Click Yes.

The California tariff is deleted.

Disabling the deletion warning dialog

To prevent NightWatchman from displaying the deletion warning dialog every time you delete a power scheme, power policy, tariff, security role or security account, check the Don't ask me again checkbox, located on the warning dialog itself.

Using NightWatchman group hierarchies

Managing power policies in the NightWatchman console

The NightWatchman console lets you use the Location and Organization group hierarchies to apply power policies across your network. You can also interact with the hierarchies to perform immediate tasks and control how the power policies are applied.

The power policy used by a computer is set according to its position in the NightWatchman group hierarchies. You fine tune the way this works with, Inheritance, overriding and precedence. The Location and Organization group hierarchies help to model real world scenarios. In Organisation versus Location, you can learn how these are mapped to known situations.

Using NightWatchman console you can:

• Apply power policies to Location and Organization groups. Refer to Applying power policies.

• Apply tariffs to Location group. Refer to Applying tariffs.

• Directly wake up a computer. Refer to On-demand wake ups.

• View a computer or group's properties. Refer to Viewing properties.

Inheritance, overriding and precedence

Group hierarchies provide for the inheritance and overriding of power policies. A group, at any level in the hierarchy, can have a power policy applied to it which is inherited by all the groups it contains. A locally applied group power policy overrides any inherited power policy for it and all the groups it contains.

A given computer resides in both a building and a department bringing it under the influence of both the Location and Organization group hierarchies. Power policies can be applied to both hierarchies. In this case, the power policy coming from the Organization group hierarchy takes precedence but you can override this default for a specific Location group. Refer to Overriding organization groups.

Tier Names

The Location group hierarchy is constructed of 5 tiers which use the following names in NightWatchman reports:

• Region.

• Country.

• State.

• City.

• Building (clients reside here).

The Organization group hierarchy is constructed of 5 tiers which use the following names in NightWatchman reports:

• Company.

• Subsidiary.

• Division.

• Business Unit.

• Department (clients reside here).

Organisation versus Location

It is worthwhile taking a moment to consider how the Organization and Location group hierarchies are used and why you would want to specify a preference for one over the other.

The Organization group hierarchy is used to define policy according to business use. In this way, you set up behaviors for users in specific departments. For example, you can typify the behavior of the sales department as being different from the marketing department and define different policies for each that then get applied to the appropriate department.

The Location group hierarchy is used to define policy according to where a machine physically resides. In the previous example, the power policy is specifically designed for an office renovation. Perhaps the power policy specifies that the machines in the building are all shut down at 10PM on a Friday and not awoken until 9AM on a Monday. In this case you would want to allow the extraordinary circumstance of a particular building being renovated over a weekend to take precedence over any behaviors defined for the departments contained in that building.

NightWatchman reports report time in state, power consumption, CO2 emissions, costs and savings. Typically the location group structure is used for reporting and the organization group structure used for applying power policies, however both structures can be used for reporting and for policies.

Applying power policies

To apply an existing power policy to a group in either the Organization or Location hierarchies:

1. In the NightWatchman Clients section, select the group from the Organization or Location hierarchies you want to apply the power policy to.

2. Right-click the group to display the context menu.

3. Select the power policy from the Apply Power Policy sub-menu.

Once the power policy is applied, the icon for the group changes to include a red star. This helps to locate the nodes in the hierarchy where power policies are applied.

A power policy applied to a particular group cascades down to all the groups it contains in the hierarchy, unless another power policy is applied lower down the hierarchy. See Inheritance, overriding and precedence for further details.

Computers retrieve their assigned power policies on their next policy refresh cycle. By default, this is 25 hours but can be re-configured on the NightWatchman client.

Step through applying power policies tutorial

Location and organization group hierarchies enable business structures to be modelled and power policies applied according to local conditions or business functions. To find out more about location and organization group hierarchies refer to Using NightWatchman group hierarchies.

In this tutorial, we are going to:

• Assign the Sales power policy to Sales.

To assign a power policy to Sales:

1. In the Clients section, click the Organization tab.

2. Under the Organization Groups tree, select Sales and right-click your mouse.

3. Select Apply Power Policy.

• 

4. Select the Sales power policy.

The Sales power policy is applied to the Sales group (the folder icon changes). When you hover your mouse over the Sales folder, the Tooltip displays the power policy for that group. Computers in this group will retrieve their assigned power policy in their next policy refresh cycle.

You can change the name of the power policy or update the power policy for a group from the Group Properties dialog. You can also set a local power policy to override any organization power policy.

For example, the properties for Sales are illustrated in the Group Properties dialog.

Overriding organization groups

To override the power policies in the Organization group hierarchy with those from the Location group hierarchy:

1. In the Clients section, select the group in the Location Group hierarchy that you want to take precedence over the Organization group hierarchy.

2. Right-click the group to display the context menu and select the Properties menu item.

3. In the Properties dialog on the Power Policy tab, check the Override organization group priority for this group only checkbox.

Step through overriding organization group priorities tutorial

In this tutorial, we are going to:

• Choose 104 Banjo Drive from the Winnipeg building group.

• Override the existing power policy with the Office renovation power policy.

1. In the Clients section, click the Location Groups tab.

2. Select 104 Banjo Drive and right-click your mouse.

3. On the context menu, select Properties.

4. In the Group Properties dialog, choose the Office renovation power policy.

   

5. Check the Override organization group priority for this group only checkbox.

   

   The significance of this is that this power policy is used in preference to any set in the Organization group hierarchy.

Applying tariffs

To apply an existing NightWatchman tariff to a group in the location hierarchy:

1. In the Clients section, select the group from the Location hierarchy you want to apply the tariff to.

2. Right-click on the group to display the context menu.

3. Select the tariff from the Apply Tariff sub-menu.

Once the tariff is applied, the icon for the group will change to include a green T. This helps to locate the nodes in the hierarchy where the tariffs are applied.

A Tariff applied to a particular group will cascade down to all the groups inside in the hierarchy, unless another tariff is applied lower down. See Inheritance, overriding and precedence for further details.

Tariffs are used by reports to calculate energy costs and CO2 emissions from energy used.

Step through applying tariffs tutorial

In this tutorial, we are going to:

• Apply the California tariff to the California group hierarchy.

To apply the California tariff to the California group:

1. In the Clients section, click Location Groups tab.

2. Select the California location group and right-click your mouse.

3. On the menu, select Apply Tariff.

• 

4. Select the California tariff.

The California tariff is applied to the California group (the folder icon changes). When you hover your mouse over the California folder, the Tooltip displays the power policy and tariff for that group. Computers in this group will retrieve their assigned power policy in their next policy refresh cycle, which by default is 25 hours. You can change this value in the NightWatchman client.

On-demand wake ups

To perform an on-demand wake up for a group in or a particular computer:

1. In the Clients section, select the group or computer you want to wake up from either the Organization or Location hierarchies.

2. Right-click the group or computer.

3. Select On-demand wakeup from the context menu.

Step through on-demand wake ups tutorial

In this tutorial, we are going to:

• wake up computers in Sales on-demand

To wake up a computer on-demand:

1. In the Clients section, locate Sales group.

2. Select Sales and right-click your mouse.

• 

3. Select On-demand Wakeup from the menu.

Viewing properties

To view properties for a group or computer in the NightWatchman Group hierarchies:

1. In the Clients section, select the group or computer from the Organization or Location group hierarchies you want to view the properties for.

2. Right-click the group or computer to display the context menu.

3. Select Properties.

Step through viewing properties tutorial

In this tutorial, we are going to:

1. View the properties for the computer ACMERRAL000001 in Logistics by using the right-click context menu.

2. View the properties for Sales in the Organization group hierarchy.

To view the properties for ACMERRAL000001:

1. Select the Logistics node from the ACME Transport group hierarchy.

2. Select ACMERRAL000001 and right-click your mouse.

• 

3. On the context menu, select Properties. The Computer Properties dialog displays the properties for that computer.

• 

WakeUp servers

NightWatchman Management Center can communicate with multiple WakeUp servers to enable scalable wake up support across large and geographically diverse networks. These WakeUp servers automatically register themselves with the NightWatchman Management Center.

Site Boundaries

Normally NightWatchman uses subnets or Configuration Manager site boundaries to determine which WakeUp server is used to wake up a client computer with a particular IP address.

In non-Configuration Manager environments, the site boundaries for the WakeUp servers are set in the NightWatchman console. In this configuration, the first WakeUp server to register is initially given a global site boundary so that it may cover all wake up requests until the boundaries for all the registered WakeUp servers have been configured.

In a Configuration Manager environment, the site boundary for each WakeUp server corresponds to the site boundary of the Configuration Manager server where the WakeUp server is installed. In the NightWatchman console, the site boundaries are imported automatically from Configuration Manager and are read-only, though additional inclusion and exclusion lists can be added.

For both Configuration Manager and non-Configuration Manager environments, additional exclusion and inclusion lists can be defined to tailor the coverage of the WakeUp servers.

WakeUp servers have an implied order that governs which server is used when the site boundaries overlap. This Server order can be modified in the NightWatchman console. You can delete WakeUp servers from the NightWatchman console, doing this prevents the deleted server from processing any future wake up requests. If a deleted WakeUp server subsequently re-registers with NightWatchman Enterprise, it will re-appear in the NightWatchman console.

Site Codes

As an alternative to boundaries, NightWatchman can use Configuration Manager site codes in Configuration Manager environments. By default, NightWatchman will use check the site code first and only use the boundaries if a match is not found. This feature was introduced with 7.0.0 and was announced in the release notes as "WakeUp server mapping process able to map based on assigned Configuration Manager site". However, there is a known issue with this feature in 7.0.0, so you must also use the latest NightWatchman Accumulated hotfix for 7.0.0.

The NightWatchman console enables the network address for a particular WakeUp server to be modified. The new address is used when building the WMI namespace for connecting to the server to issue wake up requests. The validity of the namespace can be verified in the NightWatchman console.

The legacy WakeUp server

When an upgrade is made from a version prior to 6.0.500, a legacy server will appear in the NightWatchman console with a global boundary so that it handles all wake up requests. In earlier versions, only one WakeUp server could be registered with the NightWatchman Management Center.

Following the upgrade, this previously used WakeUp server appears in the NightWatchman console as #Upgrade# and has a global boundary of 0.0.0.0 - 255.255.255.255. As you upgrade your WakeUp servers, these will automatically register with NightWatchman Management Center and you can adjust the server boundaries as necessary to provide scalable coverage.

Managing WakeUp servers in the NightWatchman console

In the NightWatchman console, the WakeUp servers section displays a list of registered servers where you can:

• Edit each server's subnet site boundaries.

• Edit IP address.

• Edit the server order which dictates which WakeUp server gets takes precedence in the event of subnet and IP addresses overlapping.

• Delete server registrations to prevent a particular WakeUp server from being used.

Editing server site boundaries

WakeUp servers use site boundaries that determine which server is used to wake up a client computer with a particular IP address. Site boundaries are defined using IPv4 and are represented using either subnets or IP ranges or a combination of the two. These are configured with inclusions and exclusions to allow maximum control over which IP addresses are covered by the WakeUp server.

In ConfigMgr environments, there are entries for subnets that come from the ConfigMgr server where the WakeUp server is installed. These entries cannot be removed but they can be adjusted by adding further inclusions or exclusions.

To edit a particular server's site boundaries, select the server from the WakeUp server list and click the Edit button to open the Edit WakeUp server Properties dialog. For example, WakeUp server kedevw2104 has 2 inclusions and no exclusions.

Adding a subnet inclusion or exclusion

To add new subnet:

1. Click the Subnets tab in the Edit WakeUp Server Properties dialog.

2. Click the Add... button for Includes: or Excludes: to open the Enter IPv4 subnet dialog.

   

3. Enter the subnet address and subnet mask. Each subnet is defined using its base subnet address and a subnet mask.

   

4. Click OK to save the new subnet inclusion or exclusion.

Adding an IP range inclusion or exclusion

To add an IP range, select the IP ranges tab in the Edit WakeUp Server Properties dialog, as shown, then click on the Add... button below either the Includes or Excludes lists.

1. Click the IP ranges tab in the Edit WakeUp Server Properties dialog

2. Click the Add... button for Includes: or Excludes: to open the Enter IPv4 range dialog.

   

3. Enter the IP addresses for the range you want created.

   

4. Click OK to save the IP range.

Server order

WakeUp servers have an implied order that governs which server is used when site boundaries overlap. This order is maintained in the NightWatchman Console. The servers at the top of the list takes precedence over those below it.

To change the order of the WakeUp servers:

1. Select the server to promote or demote from the list.

   

2. If the server is already at the top of the list, click the Move down one place or Move to bottom arrow to reposition the selected server in the list.
   

   If the server is not the top most in the list, click the Move up one place or Move to the top arrow to reposition the selected server in the list. Click the Apply button to accept the new order for the server.

Deleting servers

You can delete WakeUp servers from the NightWatchman Console to stop it from processing wake up requests. If a deleted WakeUp server subsequently re-registers with NightWatchman Enterprise, it will re-appear in the NightWatchman Console.

To delete an existing WakeUp server:

1. Select the server from the WakeUp servers list.

2. Click the Delete button.

3. In the Confirm delete dialog, click Yes to delete the server or No to cancel.

   

WakeUp servers which do not report for 30 days are deregistered and no longer displayed in console.

Managing network address for WakeUp servers

The NightWatchman Console enables the network address for a particular WakeUp server to be modified. The new address is used when building the WMI namespace for connecting to the server to issue wakeup requests. The validity of the namespace can be verified in the console. As WakeUp only returns the NetBIOS name for the WakeUp server, you will need to change it if:

• The DNS in your environment is not fully configured, set this to the FQDN for the WakeUp server.

• Your network is configured to only use FQDN, set this to the FQDN for the WakeUp server.

• You have load balanced the WakeUp server for high-availability, set this to the cluster node name for the WakeUp server.

To change the network address for a particular WakeUp server:

1. Select the server from the WakeUp server list.

2. Click the Edit button.

3. In the Edit WakeUp Server Properties dialog, enter the new network address.

4. Click the Verify button to check its validity.

Setting power consumption data

Managing power consumption data in the NightWatchman console

You can view and modify the power consumption figures of the hardware found on your network in the NightWatchman console. Editing these values affects the information in NightWatchman reports. They are based on information available from your computer vendors. This information is usually available on the support pages of your vendors' web sites, where you download manuals and other documentation. The regulatory documents are most likely to contain the needed data.

The NightWatchman power consumption information is divided into three tabs: Desktops, Laptops and Monitors with information for each category shown in its own tab. Default values are used when hardware information cannot be found; these are <default chassis> for the desktop type, <default laptop> for the laptop type and <default monitor>.

The Desktops tab

In the Desktops tab, you can set power consumption values for specific types of computers in four operation states; namely, on, standby, hibernate and off.

• Manufacturer: The hardware manufacturer.

• Type: The type of computer.

• Model: The model of the computer.

• On: The power consumption when the computer is on.

• Standby: The power consumption when the computer is in standby mode.

• Hibernate: The power consumption when the computer is in hibernate mode.

• Off: The power consumption when the computer is connected but turned off.

• Source: The source of the information.

The Laptops tab

In the Laptops tab, you can set power consumption values for specific types of laptops in five operation states; namely, on, on with screen in standby, standby, hibernate and off.

• Manufacturer: The hardware manufacturer.

• Type: The type of computer.

• Model: The model of the computer.

• On: The power consumption when the computer is on.

• On with screen in standby: The power consumption when the computer is on but the display is in standby mode.

• Standby: The power consumption when the computer is in standby mode.

• Hibernate: The power consumption when the computer is in hibernate mode.

• Off: The power consumption when the computer is connected but turned off.

• Source: The source of the information.

The Monitors tab

In the Monitors tab, you can set power consumption values for specific types of monitors in two operation states; namely, on and off.

• Model: The model of the computer.

• On: The power consumption when the computer is on.

• Standby: The power consumption when the computer is in standby mode.

• Source: The source of the information.

Automated power consumption catalog updates

As of August 2018, NightWatchman Enterprise can no longer integrate with ActiveEfficiency to enable the power consumption tables to be automatically updated via the cloud. 1E is still pleased to provide the same data to you using a slightly more manual process. Contact 1E Support for details.

Support will ask you to:

1. Open SQL Server Management Studio on your NightWatchman database server or a console that can access it.

2. Click on New Query to create an empty query window.

3. Ensure the AgilityFrameworkReporting database is selected in the Available Databases dropdown list.

4. Paste these queries into the query window:

   Copy

   select [Type], SubType, Manufacturer, Model, HardwareID, count(*) 'Count' from tbAFR_Lookup_HardwareComponent hw 
   join tbAFR_Dimension_ComputerSystem systems on hw.HardwareId=systems.HardwareComponentId 
   where IsDefault=0 group by [Type], SubType, Manufacturer, Model, HardwareId order by Count(*) desc

   Copy

   select [Type], SubType, Manufacturer, Model, HardwareID, count(*) 'Count' from tbAFR_Lookup_HardwareComponent hw 
   join tbAFR_Dimension_DisplayMonitor systems on hw.HardwareId=systems.HardwareComponentId 
   where IsDefault=0 group by [Type], SubType, Manufacturer, Model, HardwareId order by Count(*) desc

5. Click the Execute button.

6. Two results tables will appear. Right click each and select Save Results As. Save the first as "computers.csv" and the second as "monitors.csv" in a location that is convenient for you.

7. E-mail the two CSV files to 1E support.

Support will e-mail you a file with SQL statements that you will execute in the same manner to populate the power consumption table.

Modifying Power Consumption values

To modify the power consumption values:

1. Tick the Custom column checkbox for the row you want to update.

2. Click the value in the field to display the edit field.

3. Edit the value. This supports accuracy up to the first decimal place.

4. Press Enter on the keyboard or click another row in the table to save the value.

Step through modifying power consumption values tutorial

In this tutorial, we are going to:

1. Modify the power consumption value for the VLML 200 desktops from 52.1 watts to 40.2 watts when they are on.

2. Update the source column to include ACME website.

3. Revert the values back to their defaults from the automatically updated power consumption catalog

To update the power consumption for the VML200 desktops:

1. In the Power Consumption section, click the Desktops tab.

2. Click the Custom checkbox for the Horizon Inc. VML 200 desktop.

   

6. Click the On field and change the value from 52.1 to 40.2.

7. Click the Source field and enter ACME Website.

8. Press the ENTER key to save the updates.

   

   If you decide that the custom value you have added is no longer applicable you can revert to the default at any time by un-checking the Custom checkbox.

9. Doing this displays a confirmation dialog asking if you want to proceed. If you click Yes any custom values you have entered will be set back to their defaults.

   

NightWatchman console security

Managing security in the NightWatchman console

NightWatchman security lets you control who has access to specific NightWatchman features (it relies on the account information provided by the Active Directory). With NightWatchman, you can:

• Add new users or groups.

• Delete users or groups.

• Add new security roles.

• Change permissions for security roles.

• Assign security roles to users or groups.

• Delete security roles.

• Set viewing and access options for the group hierarchies.

Adding new user or group security accounts

To add a new user security accounts:

1. In the Security section, select Users and Groups tab.

2. Click the Add button.

3. In the Select Users or Groups dialog, type the name of the user or group.

4. Click the Check Names button to search the AD for the user or group.

5. Click the OK button to create the security account.

Details for the account are sourced from the AD.

Step through adding a new user or group security account tutorial

In this tutorial, we are going to:

• Add a new user security account for dsohnmendel.

To add a new user security account:

1. In the Security section, select the Users and Groups tab.

2. Click the Add button.

3. In the Select Users or Groups dialog, start typing the first few characters for name of the user you want to add.

   

4. Click Check Names. (The Select Users or Groups dialog is linked to the Active Directory and suggests a list of names matching the string you type). In our tutorial, the search has resolved to dsohnmendel as there is only one matching user.
   

5. Click OK to add the user.

Deleting users or groups

To delete an existing user or group security account:

1. In the Security section, select the Users and Groups tab.

2. Select the account you want to delete.

3. Click the Delete button.

4. If the warning option is turned on the Confirm Delete dialog is displayed. Click Yes to delete or No to cancel.

Step through deleting a user or groups security account tutorial

In this tutorial, we are going to:

• Delete the user security account for dsohnmendel.

To delete and existing user security account:

1. In the Security section, select the Users and Groups tab.

2. Select the dsohnmendel account.

   

3. Click the Delete button. The Confirm delete dialog prompts you to confirm the deletion.

   

4. Click Yes to delete the account.

To prevent NightWatchman from displaying the deletion warning dialog every time you delete a power scheme, power policy, tariff, security role or security account, check the Don't ask me again checkbox, located on the warning dialog itself.

Before checking this box, make sure that you definitely do not want the deletion warning dialog to appear as deleting a NightWatchman Console Power Scheme cannot be undone.

Turning off the deletion warning dialog

To prevent NightWatchman from displaying the deletion warning dialog every time you delete a power scheme, power policy, tariff, security role or security account, check the Don't ask me again checkbox, located on the warning dialog itself.

Adding new security roles

To add a new security role:

1. In the Security section, select the Roles tab.

2. Click the Add button

3. In the Add Security Role dialog, enter a name and description.

4. Click OK to save the new security role.

After creating the new security role you will need to define the permissions for it.

Step through adding a security role tutorial

In this tutorial, we are going to:

1. Create a new NightWatchman Console User security role that enables members to access all sections of the console except Security.

2. Grant permissions for this security role.

To add a new security role that grants access to all sections of the NightWatchman Console except Security:

1. In the Security section, select the Roles tab.

   

2. Click the Add button.

3. In the Add Security Role dialog, enter a name and a description for the role.

   

4. Click OK to save the new role.

Granting permissions to the role

To grant permissions to the newly created NightWatchman Console User security role:

1. In the Security section, select the Roles tab.

2. Select the NightWatchman Console Users role

3. In the Permissions panel, enable the Launch Console permission. The role must already have this permission before others can be granted.

   

4. Enable all permissions except for Security. If the Modify permission for Location groups and Organisation groups is not enabled, the role:

   • Cannot add, rename, delete groups.

   • Cannot remove members from groups.

   • Cannot move computers across groups.

     

5. Notice when you select the Queries: View checkbox, a notification appears at the top warning of a potential security risk.
   

   Click the notification to view the warning for the security risk.

   

6. When you have granted all the permissions for the role, click Apply.

Changing permissions for security roles

To change permissions for security roles:

1. In the Security section, select the Roles tab.

2. Select the role you want to amend.

3. Check or uncheck the checkboxes for the permissions you want this role to have.

4. Click Apply to enable the new permissions or Discard to revert the permissions to their original settings.

Refer to Step through adding a security role tutorial.

Assigning security roles to users or groups

To assign security roles to users or groups:

1. In the Security section, select the Users and Groups tab.

2. Select the user or group from the list to assign the role to. Unassigned roles are identified by the

   icon.

3. Click the next to the role to assign it to the user or group.

Step through assigning roles to users and groups tutorial

In this tutorial, we are going to:

• Assign the NightWatchman Console User role to "dsohnmendel".

To assign the NightWatchman Console User role to dsohnmendel:

1. In the Security section, select the Users and Groups tab.

2. Select the user dsohnmendel.

   

3. Click the NightWatchman Console User role to assign it to the user account. The icon changes to

   to signify the association.

   

4. Click Apply.

Deleting security roles

To delete an existing security role:

1. In the Security section, select the Roles tab,

2. Select the role you want to delete.

3. Click the Delete button.

4. If the warning option is turned on, the Confirm delete dialog is displayed. Click Yes to delete or No to cancel.

5. If the role is associated with a user or group, another Confirm delete dialog is displayed indicating that the security role is use. Click Yes to delete or No to cancel.

Step through deleting security roles tutorial

In this tutorial, we are going to:

• Delete the NightWatchman Console User security role.

To delete the NightWatchman Console User security role:

1. In the Security section, select the Roles tab.

2. Select the NightWatchman Console User security role.

3. Click the Delete button.

   

   The Confirm delete dialog prompts you for confirmation.

4. Click Yes to delete the security role. In this tutorial, as the NightWatchman Console User security role is also associated with other members, the prompt is displayed.

   

5. Click Yes to delete this role or No to cancel.

To prevent NightWatchman from displaying the deletion warning dialog every time you delete a power scheme, power policy, tariff, security role or security account, check the Don't ask me again checkbox, located on the warning dialog itself.

Setting viewing and access options for group hierarchies

To set viewing and access options for group hierarchies:

1. In the Security section, select the Roles tab.

2. Define a security role with the View (but not the View All) permissions.

3. Select the Users and Groups tab.

4. Assign the security role to the user or group.

An administrator with Change Security permissions must set the security properties for the node in either the Location or Organization hierarchies in order of the user or group to view that it. To do this:

1. In the Clients section, right-click your mouse on the node.

2. Select Properties from the menu.

3. Click the Security tab in the Properties dialog.

4. Select the user or group from the list.

Step through setting viewing and access options for the group hiererchies tutorial

In this tutorial, we are going to:

1. Create an Allow to view Location and Organization security role.

2. Grant view permissions to group hierarchies.

3. Assign this role to the US IT Managers group

4. Grant view permissions to the US IT Managers group at the folder level.

To assign an Allow to view Location and Organization security role to the US IT Managers group:

1. In the Security section, select the Roles tab.

   

2. Click the Add button.

3. In the Add Security Role dialog, enter Allow to view Location and Organization and add description for the role.

4. Click OK to save the role.

5. Select the Allow to view Location and Organization role.

6. In the Permissions panel, enable the Launch Console permission, the View Location groups and View Organization groups for Clients.

7. Click the Apply button to save the permissions for this role.

8. Click the Users and Groups tab.

9. Select the US IT Managers group.

10. Select the Allow to view Location and Organization role to assign to this group.

    

11. Select the Clients section.

12. Select the USA group and right-click your mouse.

13. On the context menu, select Properties.

    

14. In the Group Properties dialog, select the Security tab.

    

15. Click the US IT Managers to grant viewing permissions for the tree. With the permission granted, the US IT Managers group can now see the tree.

    

The NightWatchman Settings section

The default values for the policies applied to the Clients section are controlled in Settings section where you define:

Changing parameter values

To change the value for a parameter, click the value in the field – it changes to an edit field.

Parameter value constraints

Specific values have constraint tests associated with them. Each time you change a value, they are evaluated and if the value does not pass the tests, the field is highlighted in red and when you hover the mouse over the value, a notification is displayed.

Changing client policy values

When changing any of the values under NightWatchman reporting, NightWatchman client power policy and Power policy headings you will see the following dialog displayed when attempting to Apply the changes.