To install the agent with the wizard:
C:\Program Files\1E\NightWatchman\) or Browse to choose a new location.
To verify the installation, go to Windows Programs and Features (Apps and features on Windows 10).
Post-installation you will see the following services running:
|Display Name||Service Name||Description||Executable||Startup Type||Log On||Recovery||Dependencies|
|1E NightWatchman||NightWatchman||Provides services which enable PC power management||NwmSvc.exe||Automatic||Local System||Defaults||None|
NightWatchman component files are copied to the respective sub-folders during installation:
To run the NightWatchman executable to set additional configuration options you will either need to add this directory to your Windows PATH environment variable, or change to that directory.
These logfiles are created when the services start, depending on the components installed:
Note: if the 1E Endpoint Agent Installer is used, the logfiles location is %ALLUSERSPROFILE%\1E\Agent\NightWatchman.log
These folders are created during installation, depending on the components installed:
The 1E NightWatchman Agent stores its registry information in:
HKCU\SOFTWARE\1E\NightWatchman registry key is created after first logon.
On a default installation, the NightWatchman component is configured as follows:
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
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:
On the command-line, run
ABCD-1234-5678-8765-4321 is your new license key.
Start the service with:
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.
|Settings||Purchased license||Evaluation license|
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.
GUIDwhen it starts for the first time that uniquely identifies a computer. So if the computer is renamed for whatever reason, its power usage is preserved as its recorded in the NightWatchman database with the new name. This
GUIDis held in the registry and must be purged otherwise each new computer that uses the disk image will cause the database record of the original machine to be renamed – and this will happen multiple times for each newly imaged computer.
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: