Installing NightWatchman with the wizard

To install NightWatchman Management Center with the wizard:

  1. On the Welcome screen, click Next.
  2. On the License agreement screen, click Next.
  3. On the Prerequisites check screen, a number of checks are run before the installation can continue. If a prerequisite fails, the components dependent on those prerequisites are not installed.
  4. On the Setup type screen, choose:
    • Typical – a default installation where all components are installed on the local server
    • Custom – a distributed installation where you choose where to install the components
  5. The Database server configuration screen is only displayed if the wizard cannot locate a default instance on the local server when you opt for a typical install. This option allows you to install the database on a remote server and the rest of the NightWatchman Management Center components on the local server. The database can be specified using the following formats:
    • (Local) – uses the local default instance
    • ServerName – uses a remote server using the default instance
    • ServerName\Instance – uses a remote server and named instance on a dynamic port
    • ServerName,Port – uses a remote server and instance on a fixed port
    Other options:
    • If you tick the Drop any existing NightWatchman Management Center Database box, the installer will remove the existing database before installing the new one. Leave this box unchecked to use the existing database, in case of a re-install or upgrade.
    • Tick the checkbox TLS 1.0 disabled - install using TLS1.1 / 1.2 if TLS 1.0 is disabled in your environment and TLS 1.1 or TLS 1.2 is enabled. If you tick the checkbox then you must have installed SQL Server Native Client 11.0 on the web server.
  6. On the Service account information screen, setup the service account using the Domain\Account format. Appropriate permissions are granted to this account by the installer. However, if you intend to use the NightWatchman Management Center console to implement remote wake-ups, you must set additional WMI permissions to the service account for the WakeUp namespaces, as described in Preparation - Accounts needed to install the WakeUp server.
  7. On the 1E ActiveEfficiency server screen, tick the Enable ActiveEfficiency checkbox and enter the location of the ActiveEfficiency server by providing its NetBIOS name or localhost if it is on the same machine as the NightWatchman Management Center. This will enable Nomad integration with WakeUp – if you are using Nomad 2012 or later and want to use this feature. Click Next.

    The installer checks that MSMQ is enabled and that the ActiveEfficiency Server is accessible using the NetBIOS name provided. If either of these are not configured, a dialog is displayed informing you that the installer cannot access ActiveEfficiency server and the installation will not continue until the issue is resolved. If the issue is related to an incorrect NetBIOS name, correct the information in the installer and click Next again. If the issue is related to MSMQ not being enabled, you will have to abort the installation, resolve the issue and restart the installation.

    In previous versions of Nightwatchman, ActiveEfficiency was also used for the 1E Cloud synchronization feature, which is now obsolete. ActiveEfficiency is now only used for the Nomad integration with WakeUp feature, previously known as the WakeUp integration with ActiveEfficiency feature.

  8. On the Environment setup screen, select the size of your organization and choose the currency that is used for energy tariffs.

    The NightWatchman database makes use of this information to provide the correct balance between responsiveness and database load

    CriteriaVery Small (lab)SmallMediumLarge
    Number of clients10-5050-5,0005,000-50,000>50,000
    How often client records are loaded into reporting tables5 minutes30 minutes1 hour1 hour
    How often summary data is updated10 minutes1 hour4 hours2am nightly
    How often clients will retry retrieval of Power Policy on failure5 minutes30 minutes30 minutes30 minutes
    How often clients poll for Power Policy15 minutes90 minutes500 minutes1500 minutes
    The maximum amount of time before a client sends up data900 seconds3600 seconds7200 seconds14400 seconds
    A client will send data as soon as it has this many messages to send551525
    How often new unassigned computers are assigned a power policy5 minutes5 minutes30 minutes60 minutes

    The currency is selected from a drop-down list of available currencies. For fresh installations the currency set on the machine where the installation is taking place will be selected from the list by default. For upgrades the default selected currency will be the one set in the earlier version of NightWatchman Management Center.

  9. On the Ready to install screen, click Next.
  10. On the Install screen, click Finish.
On this page:

Installing NightWatchman on a distributed environment

  1. For a distributed installation, follow steps 1-3 above.
  2. On the Setup Type screen, choose Custom. Ensure you have the supported platforms in place before you start. You will need to run the installer once for each group of components you want to install separately. These features are:
    • Database – installs the NightWatchman Management Center reporting database. It holds all the information returned by NightWatchman clients and the WakeUp agents and forms the basis for the reports. You can only have one instance of the database per implementation.
    • Report console – view NightWatchman (power consumption and performance) and WakeUp (computer availability) reports from the Reporting Website. You can only have 1 instance of the Reporting Website per implementation.
    • Services – Web services (manages communications between the NightWatchman clients) and Console service (manages communications between the NightWatchman console and the database). You can have up to 3 instances of the Web service feeding into a single database. Multiple-instances also cover hybrid environments using both HTTP and HTTPS communications (for example, HTTP for intranet-based and HTTPS for internet-based communications). Set the NightWatchman clients and ~WakeUp implementations in each region to communicate with the Web service using their respective protocols.
    • Console – install the NightWatchman Management Console on separate computers. You can have up to 10 instances of the console but they must be installed on computers with network access to the server where the console is running.
    • Analysis reports – installs the analysis reports
    By default, these components are installed to C:\Program Files\1E\NightWatchman Management Center. You can select a new location by clicking Change and navigating to a new folder.
  3. Follow steps 5-10 above.

Installing NightWatchman Management Center in unattended mode

You can install NightWatchman Management Center to a large number of machines by choosing to install it in unattended mode using the /qn switch in the installer command-line.

For example, to carry out a default installation where all the components are installed locally, run (the command-line is broken down into separate lines for clarity. Run it as a single command-line):

msiexec /i NightWatchmanManagementCenter.msi 

To install only the NightWatchman console where the NightWatchman Management Center console service is installed, run (the command-line is broken down into separate lines for clarity. Run it as a single command-line):

msiexec /i NightWatchmanManagementCenter.msi 

There are a number of installer properties which are detailed in Installing NightWatchman Management Center.

Prerequisite checks are still carried out when you run in unattended mode. If they are not met, components will not install.

Uninstalling or repairing the NightWatchman Management Center

The NightWatchman Management Center can be removed using the Add or Remove Programs in Control Panel. To uninstall, select the NightWatchman Management Center item in the Currently Installed Programs list and click the Remove button. You can also access support information for the product in the Add or Remove Programs dialog.

When you carry our a repair or re-installation, certain information stored for the WakeUp server is not available to the installer. You may need to configure additional WMI permissions to the service account for the WakeUp namespaces, as described in Preparation - Accounts needed to install the WakeUp server.

To implement a repair the NightWatchman Management Center, run: Msiexec /fvom NightWatchmanManagementCenter.msi or if you are planning an upgrade, please refer to Upgrading NightWatchman Enterprise.

Detailed requirements

A definitive checklist of prerequisites and dependencies you need to meet in order to install NightWatchman Management Centre.

  • Windows Server 2016
  • Windows Server 2012 R2
NightWatchman Management Center will install on systems running these server OSes.
  • It is not supported on servers configured as domain controllers.
Database servers
  • SQL Server 2017
  • SQL Server 2016 SP1
  • SQL Server 2014 SP2
SQL server must be configured to use a case-insensitive, accent-sensitive collation as the server default (the preferred collation is SQL_Latin1_General_CP1_CI_AS).
  • You can only have one instance of the NightWatchman Management Center database per implementation
  • The SQL Server Agent must be started and set to automatic
Runtime libraries
  • .NET Framework 4.6.2
  • .NET Framework 4.5.2

Installation and service accounts

To install NightWatchman Management Center, you need the following accounts and groups.

Installation account

  • Must be domain user account 
  • Must have local admin rights on the server where NightWatchman Management Center is being installed
  • Must have sysadmin rights on the SQL Server instance unless the AgilityFrameworkReporting database and SQL Server Agent jobs are pre-created by a DB administrator. This right can be temporary.
  • Will be set as the primary NightWatchman Console administrator

Console service account

  • Must be a domain account configured where the password does not expire and the user can never change the password
  • Must have local admin rights on the server where NightWatchman Management Center is being installed
  • Will be granted the following during installation:
    • Log on as service and Access the computer from the network privileges on the local machine
    • Added to the public role on the AgilityFrameworkReporting database
  • If using WakeUp, ihe service account will require rights on WakeUp Server WMI namespaces on each WakeUp Server, as described below.

User accounts or AD Groups

User account or AD Security Groups are required for use as administrators in the NightWatchman Management Center Console.

If you are using the import Wizard to populate hierarchies, check that:

  • You are typically the person who installed the NightWatchman Management Center components
  • You will already have db owner rights on the AgilityFrameworkReporting database
  • You are :
    • Either sysadmin on the SQL Server instance
    • or have been added to the db_NWMConsoleImportWizard database role on the AgilityFrameworkReporting database, that is created when the Import Wizard is installed.

Any user or group that needs to use the Import Wizard must:

  • Be a member of the db_NWMConsoleImportWizard database role
  • Have a login on the SQL Server instance that must be added to the Users of the AgilityFrameworkReporting database
  • Have NTFS permissions to modify the directory for the Import Wizard log file.

member of the db_NWMConsoleImportWizard database role

If you are installing NightWatchman Management Center across multiple servers, install the database component first – it can be done remotely from a server where one or more of the other components are installed.

If you are performing a clean NightWatchman Management Center installation or are upgrading NightWatchman Management Center and all the WakeUp Server components, permissions for the service account are set automatically as part of the installation process. The NightWatchman Console administrator account (used to define primary NightWatchman Console administrators) can be a domain user or group account.

If you are upgrading NightWatchman Management Center, have legacy WakeUp Servers or intend to use the NightWatchman console to implement remote wake-ups (which is done after installing the WakeUp Server):

  • add the Console service account to the N1E/WakeUp namespace and grant the following permissions:
    • Execute Methods
    • Full Write
    • Enable Account
    • Remote Enable

To set permissions:

    1. Run the WMI MMC (wmimgmt.msc) plug-in on the WakeUp Server.
    2. Right-click the root node and select Properties.
    3. In the WMI Control (Local) Properties dialog, select the Security tab.
    4. Navigate to the N1E/WakeUp node and click the Security button. 
    5. In the Security for ROOT\N1E\WakeUp dialog, add the console service account and check the permissions listed above.

For a default installation, the programs and files associated with NightWatchman Management Center are created in C:\Program Files\1E\NightWatchman Management Center