NightWatchman Enterprise

To install NightWatchman Management Center with the wizard, double-click on:

Welcome

This screen provides the version number for NightWatchman Management Center and outlines what the wizard will do.

Click Next to go to the next screen.

License Agreement

This screen provides the license agreement for NightWatchman Management Center.

To accept, click I accept the terms in the license agreement

Click Next to go to the next screen.

Prerequisite Checks

Background checks are run to ensure common prerequisites are met. If a prerequisite fails, the components dependent on those prerequisites are not installed. Later screens may require prerequisites for optional features.

Click Next to go to the next screen.

Setup Type

Select Custom.

Click Next to go to the next screen.

Custom Setup

This screen allows you to select the components you want to install on the local server. You do not need to change anything if you are installing all components on the same server.

Click Next to go to the next screen.

If you are installing separate components in a distributed system, you must ensure each server meets relevant Prerequisites. You will need to run the installer once for each group of components you want to install separately.

Component	Description
Database	Installs database support components on the local application server, as well as the SQL Server database and SQL Agent jobs on the SQL Server database instance that you specify in next screen. You can only have one instance of the database components per implementation. The database holds all the information returned by NightWatchman clients and the WakeUp agents and forms the basis for the reports, as well as the configuration settings, and policies. The default name of the database is AgilityFrameworkReporting.
Report Console	Installs the Reporting website, and the following reports: NightWatchman Reports - power consumption, performance, and computer availability WakeUp Reports You can only have 1 instance of the Reporting Website per implementation. Requires the Database component to be installed at the same time, or already on a remote server. For information about using these reports, please refer to Reporting.
Services	Installs the following: Web Service - manages communications between the NightWatchman clients Console Service - manages communications between the NightWatchman console and the database - includes the optional Import Wizard You can have up to 3 instances of the Web service feeding into a single database. Requires the Database component to be installed at the same time, or already on a remote server. 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	Installs the NightWatchman Management Console. 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 service is running. Requires the Database and Services components to be installed at the same time, or already on remote server(s).
Analysis Reports	Installs the Analysis Teports. For information about how to use these, please refer to: Piloting NightWatchman Enterprise Using a NightWatchman baseline to identify power savings. You can only have one instance of the Analysis reports component per implementation. Requires the Database and Services components to be installed at the same time, or already on remote server(s).

By default, these components are installed toC:\Program Files (x86)\1E\NightWatchman Management Center\

You can select a new location by clicking Change... and navigating to a new folder.

Database server configuration

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

The Browse button allows you to select any SQL Server database instance that has its Browsing service enabled and running.

Check theDrop any existing NightWatchman Management Center Databasebox, if you want to 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.

Check theTLS 1.0 disabled - install using TLS1.1 / 1.2box, 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 installedSQL Server Native Client 11.0on the web server.

Click Next to go to the next screen.

Note

If you are installing with Typical Setup option, then this screen is not displayed if the installation wizard detects a SQL Server database instance on the local server. You must use Custom Setup if you need to do change the following defaults:

• Database Server (local)

• Keep the existing database

• Use TLS 1.0

Website Configuration

Check Use FIPS Encryption

Click Next to go to the next screen.

Console Service Configuration

Enter the user name and password of the NightWatchman Management Center Console service account.

Click Next to go to the next screen.

The user name must use the Domain\Account format.

For more detail about this account, please refer to Preparation: NightWatchman Management Center Console service account.

If the installation account has appropropraite permissions, the installer automatically grants the service account the permissions it needs. However, if you intend to use the NightWatchman Management Center console to implement remote wake-ups, you must manually set additional WMI permissions to the service account for the WakeUp namespaces, as described in Preparation - Accounts needed to install the WakeUp server.

Content Distribution integration with WakeUp

Enable this option by checking Wake up peers that have requested Nomad content if no other peers are available.

Enter the name of the ActiveEfficiency Server

• If you are using Nomad with ActiveEfficiency, enter the NetBIOS name of the ActiveEfficiency Server, for example AESERVER, or enter localhost if it is on the same server as the NightWatchman Management Center

• If you are using Content Distribution with Tachyon Platform version 8.0 or later, enter the NetBIOS name of the Tachyon server that hosts Content Distribution - you will also need to

Click Next.

MSMQ

If the installer detects that the Windows feature MSMQ is not enabled, then you will have to abort the installation, resolve the issue and restart the installation.

If you are using ActiveEfficiency, then MSMQ must also be enabled on the ActiveEfficiency Server.

If you are using Tachyon Platform, then MSMQ is not required on the Tachyon server, and MSQM is only required on the NightWatchman server to enable installation to proceed.

Note

If the installer is unable to contact an ActiveEfficiency or Tachyon server, the installation will not proceed until the issue is resolved, and you click Next again.

Note

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.

Environment setup

Select

• the size of your organization - see below table

• the currency that you want to use for energy tariffs.

Click Next to go to the next screen.

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

Criteria	Very Small (lab)	Small	Medium	Large
Number of clients	10-50	50-5,000	5,000-50,000	>50,000
How often client records are loaded into reporting tables	5 minutes	30 minutes	1 hour	1 hour
How often summary data is updated	10 minutes	1 hour	4 hours	2am nightly
How often clients will retry retrieval of Power Policy on failure	5 minutes	30 minutes	30 minutes	30 minutes
How often clients poll for Power Policy	15 minutes	90 minutes	500 minutes	1500 minutes
The maximum amount of time before a client sends up data	900 seconds	3600 seconds	7200 seconds	14400 seconds
A client will send data as soon as it has this many messages to send	5	5	15	25
How often new unassigned computers are assigned a power policy	5 minutes	5 minutes	30 minutes	60 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.

Install

Click Finish when installation is complete.

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 
ACTIVE_DIRECTORY_SERVER=ACME 
AESERVERNAME=localhost 
ADMINACCOUNT=ACME\NWM_Admins 
SVCUSER=ACME\svc_NWMMC 
SVCPASSWORD=Pa55w0rd
SQLSERVER=ACMESQL
CURRENCYCODE=GBP /qn

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 
ADDLOCAL=Console 
SERVICELOCATION=ACME023 /qn

There are a number of installer properties which are detailed in Installing 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.

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

Component	Product	Notes
OS	Windows Server 2022 Windows Server 2019 Windows Server 2016	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 2019 SQL Server 2016 SP2 SQL Server 2017	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.7 .NET Framework 4.6.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, the 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. Note 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. 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: Run the WMI MMC (wmimgmt.msc) plug-in on the WakeUp Server. Right-click the root node and select Properties. In the WMI Control (Local) Properties dialog, select the Security tab. Navigate to the N1E/WakeUp node and click the Security button. 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

When you install the WakeUp server, you must choose to integrate with either NightWatchman Management Center or Configuration Manager. The installed components are largely the same, however the functionality varies. In either case, you must have a NightWatchman Management Center in order to register and manage WakeUp servers, and for WakeUp reporting.

To install WakeUp server with the interactive wizard:

In the following:

The command-line is broken down into separate lines for clarity. Run it as a single command-line.

To install the WakeUp server for Configuration Manager server, on the server where the Configuration Manager WMI provider is installed, run:

msiexec.exe /i wakeupsvr.msi 
PIDKEY="ABCD-1234-5678-8765-4321" 
SERVERCOMPONENTS=1 
SERVERTYPE=SMS 
AFREPORTING=ON 
REPORTINGSERVER=<RepServ>
/QN /l*v WakeUpServerInstall.log

To install WakeUp for NightWatchman Management Center, run:

msiexec.exe /i wakeupsvr.msi 
PIDKEY="ABCD-1234-5678-8765-4321" 
SERVERCOMPONENTS=1 
SERVERTYPE=NMC 
AFREPORTING=ON 
REPORTINGSERVER=<RepServ>
/QN /l*v WakeUpServerInstall.log

To install WakeUp for Configuration Manager with the Intel® AMT component, run:

msiexec.exe /i wakeupsvr.msi 
PIDKEY="ABCD-1234-5678-8765-4321" 
SERVERCOMPONENTS=1 
SERVERTYPE=SMS 
AFREPORTING=ON 
REPORTINGSERVER=<RepServ> 
SVCUSER=<SVCUser> 
SVCPASSWORD=<SVCPassword>
/QN /l*v WakeUpServerInstall.log 

If you use the evaluation license key to install WakeUp server, then you will need to relicense within 30 days. You can get a license key from 1E Sales, and use the command-line Relicense the WakeUp server.

You can modify the WakeUp installation parameters using the command-line switches detailed in WakeUp Server installer properties.

Ensure you meet the Prerequisites before you start. This section describes how to configure the WakeUp server to work with a distributed Configuration Manager installation, where the Configuration Manager WMI Provider is installed remotely from the Configuration Manager site server, usually on an SQL Server. WakeUp server must be installed on the Configuration Manager Site Server, and the installer queries WMI on the site server to detect the location of the remote Configuration Manager WMI Provider. By default, the WakeUp server service uses the Local System account, but a remote WMI Provider requires the service to use a domain account or network service account.

To do this:

For example (the command-line is broken down into separate lines for clarity. Run it as a single command-line):

To install the WakeUp server for Configuration Manager without AMT using the domain account ACME\ACMESVC with the password ACMEPSWD with reporting enabled on the CFGMGR02 reporting server, run:

msiexec.exe /i wakeupsvr.msi 
SERVERCOMPONENTS=1 
SERVERTYPE=SMS 
WAKEUPSVCUSER=ACME\ACMESVC 
WAKEUPSVCPASSWORD=ACMEPSWD 
AFREPORTING=ON 
REPORTINGSERVER=CFGMR02.ACME.COM 
/QN /l*v WakeUpServerInstall.log

To relicense the WakeUp server, run:

wakeupsvr.exe -relicense=<LicenseKey>

To uninstall the WakeUp server, use Add/Remove Programs in Windows Control Panel.

You will need to uninstall the 1E Client separately. Alternatively if you are using the 1E Client for other purposes, then reconfigure the 1E Client to disable the WakeUp module.

A definitive checklist of prerequisites and dependencies you need to meet in order to install the WakeUp server.

The 1E Client Deployment Assistant (CDA) is designed to help install Windows versions of 1E Client and other 1E agents using Configuration Manager. It includes template transform files for each combination of client/agent for 32 and 64-bit platforms, and automatically creates collections and deployments in Configuration Manager, so that you only need to populate the collections.

To install the agent with the wizard:

To verify the installation, go to Windows Programs and Features (Apps and features on Windows 10).

To deploy the 1E NightWatchman Agent to a large number of machines in unattended mode, use the /qn switch together with other installer properties on the command-line.

For example, to install NightWatchman with the log-off=ACTIVE, run C:\1E_DOWNLOAD>msiexec /i 1ENightWatchmanAgent.msi LOGOFFACTION=ACTIVE PIDKEY=ABCD-1234-5678-8765-4321 REPORTINGSERVER=<NWMCWSrv>/qn where ABCD-1234-5678-8765-4321 is your license key and <NWMCWSrv> is the FQDN or NetBIOS name of the server NightWatchman Management Centre Web service is installed. If the license key is not on the command-line, you are subject to a 30-day evaluation.

If you do not have a valid licence when you install the 1E NightWatchman Agent, you will be subject to a 30-day evaluation. If you need to run it beyond the evaluation period, contact Sales for a new key.

To relicense the 1E NightWatchman Agent:

When a license expires (evaluation or otherwise), the next time the system runs the NightWatchman component service a log entry records that the license is expired. At this point, no NightWatchman behavior is available, NightWatchman shutdown is not supported and information is not logged with NightWatchman Management Center Reporting. If you using a valid commercial license and see this notice, contact our Support team.

There are some configuration differences between an evaluation system and a production system. These differences exist because we expect the evaluation to be run on small test environments where the settings are optimal – they are not suitable for a production environment.

If you upgrade from an evaluation license to a commercial license, update these settings using the command-line on the NightWatchman component or from the NightWatchman Management Center console with a policy.

If you use Configuration Manager to install the 1E NightWatchman Agent, the installer sets ALLUSERS=1 by default so that it is installed on a per-machine basis which also makes is easier to uninstall from Configuration Manager. For example, to install NightWatchman with log-off active, a license key, reporting enabled and WakeUp in multi-agent mode, run this on the command-line:

msiexec /i 1ENightWatchmanAgent-x64.msi LOGOFFACTION=ACTIVE PIDKEY=ABCD-1234-5678-8765-4321 REPORTING=ON REPORTINGSERVER=<NWMCSrv> ALLUSERS=1 /qn

In our example, we have included ALLUSERS=1 but it is not strictly necessary as the installer includes that by default.

If you want to install the 1E NightWatchman Agent on a computer you want to image for subsequent inclusion in base OS configurations, complete the installation described above first.

When deploying a disk image that includes a NightWatchman installation, it is very important to reset some of the registry information and delete some log files from disk before the image is taken. Do not use a disk image with NightWatchman installed without first making the changes outlined below. Once these registry keys and files have been deleted, it is safe to create the gold disk image.

There are three areas of the registry that need to be addressed. The licensing keys contain information specific to the computer name and therefore must be reset otherwise NightWatchman will fail to start as it will appear to have the wrong license information.

In order to prepare the registry for sys prep, take the following action for the respective registry keys:

So that you can be sure you are looking at the correct log files and not old logging from the gold image when you troubleshoot, delete these log files and clear out reporting data:

To uninstall the 1E NightWatchman Agent:

To repair the 1E NightWatchman Agent:

The 1E WakeUp Agent for NightWatchman Enterprise 7.3 is a client module that is installed as part of the 1E Client 5.0 (or later).

For more details on deploying the 1E Client please refer to 1E Client 24.3. You can install the 1E Client with only the WakeUp module enabled, without having a Tachyon platform infrastructure. The Tachyon platform infrastructure is only required if using the NightWatchman online status feature.

The 1E Client does not require a license key. The Tachyon platform, if used, does require a license.

In most cases the 1E Client will be installed silently using a software deployment tool such as Microsoft Configuration Manager.

The 1E Client Deployment Assistant (CDA) is designed to help install Windows versions of 1E Client and other 1E agents using Configuration Manager. It includes template transform files for each combination of client/agent for 32 and 64-bit platforms, and automatically creates collections and deployments in Configuration Manager, so that you only need to populate the collections.

The WakeUp module 1E Client installer properties

Additional WakeUp module installer properties are described on the 1E WakeUp Agent configuration properties page.

If the 1E Client is installed using the interactive installation wizard, the particular installer screen that is relevant to WakeUp is illustrated below.

WakeUp

If you are using version 7.2.500 or later of NightWatchman Management Center or WakeUp Server you must install the 1E Client with this option enabled on client devices and on WakeUp Sever. The 1E Client WakeUp module replaces the WakeUp Agent from previous versions of the 1E Agent.

Setting	Description
Enable WakeUp	Check this box to enable WakeUp integration. WakeUp integration is required to enable 1E WakeUp capabilities on this device. Note If WakeUp Integration is enabled, when the 1E Client starts it will attempt to automatically remove any previous installation of the 1E WakeUp Agent. The 1E NightWatchman Agent is not affected.
Use FIPS encryption	Checking Use FIPS Encryption configures the WakeUp module to use FIPS encrypted communications. You must ensure that the NightWatchman Management Center, WakeUp Server and 1E NightWatchman Agent components are all set to the same option.
Enable HTTP reporting	Check this box if the NightWatchman Management Center Web Service is configured to use HTTP and you want communications from the WakeUp module to use HTTP. Do not use this option when installing on a WakeUp Server. When checked you must set the DNS Name FQDN for the server hosting the NightWatchman Management Center Web Service in the edit field provided.
Enable HTTPS reporting	Check this box if the NightWatchman Management Center Web Service is configured to use HTTPS and you want communications from the WakeUp module to use HTTPS. Do not use this option when installing on a WakeUp Server. When checked you must set the DNS Name FQDN for the server hosting the NightWatchman Management Center Web Service in the edit field provided.
Use client certificate (from local certificate store) for HTTPS reporting	This checkbox is only enabled when the Enable HTTPS reporting checkbox is checked. You will need to check this option if the NightWatchman Management Center Web Service has been configured to request a client certificate. The certificate is retrieved from the local certificate store and is found by providing a certificate issuer or certificate subject search text. The first certificate found that matches the text will be used to authenticate the client with the NightWatchman Management Center Web Service.
Match Certificate Issuer	This option is only enabled when the Use client certificate for HTTPS reporting checkbox is checked. When selected this option sets the search in the local certificate store to match against the certificate issuer field of the certificate.
Match Certificate Subject	This option is only enabled when the Use client certificate for HTTPS reporting checkbox is checked. When selected this option sets the search in the local certificate store to match against the certificate subject field of the certificate.
Search Text	This option is only enabled when the Use client certificate for HTTPS reporting checkbox is checked. When enabled this edit field should be set to the search text used to locate and retrieve the client certificate from the local certificate store. This will be matched against either the certificate issuer or the certificate subject, depending on which option has been selected above.

Note

When installing on client devices, enable HTTP or HTTPS reporting in order for NightWatchman Management Center to track which subnet the client device is on when it powers down. The WakeUp module reports back subnet changes more frequently than the NightWatchman Agent.

WakeUp Server must be installed before installation of the WakeUp client. If WakeUp client is installed first the WakeUp Server installer only provides the WakeUp Administration console installation option.

When installing on a WakeUp Server, do not enable HTTP or HTTPS reporting, because that prevents the server from appearing as a client in the NightWatchman Management Center Admin Console. This will only disable Agent reporting whilst the WakeUp Server itself should have reporting enabled for reporting statistics.

Warning

Enter the DNS Name FQDN for the server hosting the NightWatchman Management Center Web Service, do not enter the full URL.

You must have administrative privileges to the machine to run the installer. Throughout this process, you will be prompted to enter the administrative password at various stages of the installation.

If you are using FIPS communications, ensure that the same setting is made for all NightWatchman Management Center, WakeUp Server and 1E Agent components. See options for secure communications for further details.

Before you can run the installer, you must mount the 1E Agent.dmg disk image. Once you have mounted the disk image, you will see five files in it.

To install the Open SSL libraries:

The main 1E Agent files are installed at the root of the system disk in: /Library/Application Support/1E/NightWatchman

To enable remote deployments in unattended mode:

At the end of installation, the installer creates an installer configuration file in /Library/Preferences. When the installer launches the 1E Agent daemon, the daemon looks for this installer configuration file and updates the installer settings. After applying those changes, it deletes the installer configuration file. APreConfiguration file takes precedence over the installer configuration file.

To install the Mac 1E Agent:

The most important key that must be included in the pre-configuration file is the 1E Agent license. This key is called LicenseNumber and is set using following command-line: defaults write /Library/Preferences/com.1E.NightWatchman.PreConfiguration LicenseNumber <1ELicKey> where <1ELicKey> is your commercial or evaluation license key.

You have two options before you run the installer:

The installer will always use the pre-configuration file if it exists, so any manual updates to LicenseNumber, HTTPServer, HTTPSServer or Reporting will be reverted by the installer.

Post-installation, you must restart the computer in order to enable the version 6 1E Agent daemon to run. If you uninstall it, you will need to restart the computer to completely remove the agent daemon.

To uninstall the Mac 1E Agent:

Using any Mac systems management software product, you can distribute changes to the NightWatchman policies using command-line switches to the NightWatchman executable.

Power downs are handled by the NightWatchman component of the 1E Agent. This is controlled via the NightWatchman command-line, which allows you to set specific attributes for the NightWatchman service. After installation, the nightwatchman executable is located in the following directory:

/Library/Application Support/1E/NightWatchman

For example, to change the shutdown policy for a particular machine to "force" and remove the user's ability to defer shutdown you could open a console on the machine with administrator privileges, change to the /Library/Application Support/1E/NightWatchman directory and enter the following command-line:

sudo ./nightwatchman -s logoffaction Force systemtray off

Another common usage is to change the shutdown time for different days of the week. The following example sets a shutdown time of 20:00 on weekdays and 13:30 at weekends:

sudo ./nightwatchman -scheduledactions WEEKDAYS=20:00,PowerOff,Active WEEKENDS=13:30,PowerOff,Force

To learn more about configuring NightWatchman from the command-line, please refer to 1E Agent Mac command-line switches.

To learn more about the Mac user interface, please refer to The 1E Agents - 1E Agent for Mac.

The 1E Agent Mac keeps a log file of settings, state changes and interactions in /tmp/Nightwatchman agent.log where /tmp is a symbolic link to /private/tmp. This is a temporary location, with files periodically deleted by daily, weekly or monthly cron scripts and/or reboots. You should backup this file to a safer location so that it does not get deleted automatically by system routines.

To install Web WakeUp using the wizard:

To install Web WakeUp in unattended mode, on the command-line, run:

msiexec command-line, run: /i WebWakeUp.msi SERVICELOCATION=<SERVICE> /qn 

where <SERVICE> is the location for the NightWatchman Console service.

For more details on the installer properties, see Web WakeUp installer properties.

If the Web WakeUp website is installed on a different computer to the NightWatchman Console Service and you get errors attempting to access the Web WakeUp website, perform the following post-installation configuration:

You can configure Web WakeUp to prompt users for authentication to wake computers up from the Web interface. When you do this, users can only register or search for computers that they are associated with in the Web WakeUp authorisation database. You can enable wake up authorisation:

To enable users to wake up computers on the network, you must add their credentials to the tbWWU_Authorised_UserMachines table in the AgilityFrameworkReporting database. The columns in this table are:

For example, if you want Joe to wake up ACMEDEV00017 and ACMEDEV00015 and Mary to wake up all the computers on the ACME network, update the table as follows:

The Web WakeUp additions to the Agility Framework database also include a batch job that will populate the table from a .csv input file. See Web WakeUp authorization table for further details.

The Web WakeUp ActiveX control(WebWakeUpActiveX.msi) is supplied in a stand-alone installer. This means that the control can be rolled out across a network without requiring user intervention the first time they visit the Web WakeUp site.

There is a single installer property that controls whether the ActiveX control appears on the pre-approved list which allows it to be enabled in Internet Explorer without user intervention. To run this in unattended mode with pre approval, use: Msiexec /i WebWakeUpActiveX.msi PREAPPROVED=1 /qb

If the Web WakeUp ActiveX control has not been previously installed by the network administrator, the first time you browse to the web service, you will be prompted to install the Web WakeUp software. Installing the ActiveX control enables Web WakeUp to confirm the name of the local computer, specifically for the purpose of registering the computer as the default wake up.

If you choose not to install the ActiveX control, Web WakeUp attempts to use reverse DNS lookup in order to derive the local computer name. The accuracy of this operation is dependent on DNS being correctly configured and up-to-date and may affect Web WakeUp's ability to wake the computer at a later date.

You can use reverse DNS lookup instead of the Web WakeUp ActiveX control by changing a setting as described in Web WakeUp server configuration: ActiveX usage.

Either the Web WakeUp ActiveX control or reverse DNS lookup is required by the Register page (tab). If neither method is available to you then you can choose to remove this page from the website, as decribed in Web WakeUp server configuration: website control.

A definitive checklist of prerequisites and dependencies you need to meet in order to install Web WakeUp.

To install Enterprise View using the wizard, run EnterpriseView.msi.

If you set up an additional host header for the Enterprise View website:

A definitive checklist of prerequisites and dependencies you need to meet in order to install Enterprise View.

To ensure a successful upgrade to NightWatchman Management Center 7.3, we recommend you undertake a planning exercise to understand issues that may arise and agree a suitable approach for the business.

The following 1E product versions are in scope for this upgrade process.

We recommend that you upgrade your NightWatchman version to the latest version before it goes out of support. The installer supports direct upgrades from NightWatchman 7.2 and 7.2.500. You can find the latest 1E releases on the 1E Support Portal, .

There are two options that cover the cases where upgrades from earlier systems are required:

In all cases, we advise the following:

If running earlier versions of the above software, we recommend that a new installation of NightWatchman Management Center 7.3 is implemented instead of performing an upgrade. Detailed information can be found in installing NightWatchman Management Center and installing the WakeUp Server.

If custom reports have been developed for a specific version of the product to extend the standard reporting capabilities, consideration should be given to these as an on-going business requirement. While every effort is made to minimize the changes in the back-end reporting architecture, schema changes in later versions might cause custom reports to run with errors following the upgrade.

The upgrade process provides guidance to back-up and restore custom reports; however, we recommended that the upgrade process is tested prior to implementing on production environments in order to identify any issues. Contact your 1E account team if issues are encountered with custom reports following an upgrade and there is an on-going business requirement for these. As custom reports are not covered by the standard 1E support agreement, any remedial work to allow compatibility with 7.3 might be chargeable.

The overall approach is to upgrade server components first followed by clients:

The approach assumes that the server components are upgraded in a like-for-like configuration. If you plan to relocate your server components to different hosts as part of your planned upgrade, we recommend you contact your 1E account team to arrange a discussion with a specialist for advice.

License keys are required for the NightWatchman Enterprise 7.3 components. These are provided to all customers with active maintenance agreements. WakeUp requires a license key when installing server components and NightWatchman requires a license key as part of the 1E NightWatchman Agent install. If you have a version 7.x license, it will work with 7.3. Version 6 licenses will not work.

The upgrade can be reverted as long as client agents have not been upgraded to 7.3. Rollback requires a valid backup of the AgilityFrameworkReporting database and its associated program files directories (including import scripts and custom reports).

To carry out a rollback:

Certain new features in NightWatchman Enterprise 7.0 and above rely on ActiveEfficiency Server integration. If you are intending to use the following features it is recommended that ActiveEfficiency v1.7 or later is installed prior to upgrading NightWatchman Enterprise:

NightWatchman Enterprise 7.1 and later include the new Power Optimization and Reboot Optimization features, both of which are enabled by default when clients are installed or upgraded – they can be disabled with installation parameters or by toggling client registry values.

The Power Optimization and Reboot Optimization features can also be enabled or disabled by using NightWatchman console policies. New policies have power optimization automatically enabled by default. Existing policies will not exhibit this behavior and so are disabled by default. Enable Power Optimization ore Reboot Optimization when you change policies if you want this feature to continue to be enabled on clients.

NightWatchman Enterprise 7.2 and later includes Improved reporting console, Online / offline status ‘stoplights’ in the NightWatchman console and few Enhancements to NightWatchman policy management. Hardware Utilization is renamed to Computer Reclaim with addition to rarely used computers reports.

NightWatchman Enterprise 7.2.500 and later includes changes in 1E Agent. 1E Agent is renamed to 1E NightWatchman Agent and WakeUp Agent is moved as a module in the 1E Client.The WakeUp ConfigMgr console collection and computer menu extensions now have two more options whenever you run the WakeUp Server installer on a computer that has a ConfigMgr console.Options are - Send WakeUp with Software Update Deployment Evaluation& Send WakeUp with Application Deployment Evaluation. Also the log files for Wakeup Server and the NightWatchman and WakeUp Agents can now rollover multiple times.

In order to create a recovery point, take a backup of the database which can be achieved by one of the following methods:

iisreset /stop

NightWatchman's Tachyon integration is designed to be highly reactive and scalable. However, depending on the size or your organization and the capabilities of your server, you might like to increase or decrease Tachyon's responsiveness. In particular:

You can review and change those values using SQL Server Management Studio:

By default, the Tachyon client will wait up to 15 seconds after a computer resumes from standby. During that period, Tachyon will indicate the computer is offline although it's actually online. This delay ensures that Windows has time to reestablish network connectivity. If this is a concern and you find that your computers reestablish network connectivity faster, you can reduce this delay: