Installing and upgrading

The recommended order for installing (or upgrading) NightWatchman Enterprise components is:

1. Installing NightWatchman Management Center

2. Install the NightWatchman console on remote consoles.

3. Installing WakeUp server

   • When configuring integration with WakeUp, add the WMI permissions to the Console service account described in Console service component requirements.

4. Installing Web WakeUp

5. Install the Windows NightWatchman Agent and/or the 1E Client with the WakeUp module enabled, or the Mac 1E Agent. Refer to Installing the 1E NightWatchman Agent for Windows and Installing the Mac 1E Agent.

Important points in relation to upgrading clients:

• You are encouraged to upgrade clients quickly but prudently.

  • This may be days, depending on the complexity of your policies, or weeks for larger organizations.

  • Upgrading all clients (agents) at the same time is generally not practical.

  • It is best practice to phase your deployment to ensure there are no unforeseen compatibility issues.

• If clients previously had both NightWatchman and WakeUp agents enabled and you upgrade to NightWatchman 7.3 first, the WakeUp agent will be uninstalled but the previous settings retained. When you installed the 1E Client with the WakeUp module enabled, the previous settings will be used (unless you override them in the installation command line).

• Version 7.3 of NightWatchman Management Center and WakeUp Server is compatible with earlier versions of NightWatchman and WakeUp clients, except that new features are not available on older clients.

• New features that require client changes will not work on previous versions of clients but do not cause user-adverse issues. For example, with 7.2 there was a new "Logoff then Standby" scheduled action available. 7.1 clients will not recognize this action if they receive a NightWatchman policy that includes it. In that case, they will continue in the state they are currently in; they will not be forced by NightWatchman to either log off or go to standby

Installing NightWatchman Management Center

How to install NightWatchman Management Center using the interactive installer wizard or in unattended mode - also includes basic instructions on uninstalling NightWatchman Management Center.

Installing NightWatchman with the wizard

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. Refer to Supported platforms and prerequisites. You will need to run the installer once for each group of components you want to install separately.

By default, these components are installed to C:\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 Database box, 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.

Click Next to go to the next screen.

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.

Refer to 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.

Refer to 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 1E Platform version 8.0 or later, enter the NetBIOS name of the instance that hosts Content Distribution.

Click Next.

Environment setup

Select the size of your organization and 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.

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.

Ready to install

Click Next to begin installation.

Install

Click Finish when installation is complete.

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 
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 Server installation properties.

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. Refer to Accounts needed to install the WakeUp server.

To implement a repair the NightWatchman Management Center, run:

 Msiexec /fvom NightWatchmanManagementCenter.msi

If you are planning an upgrade. 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.

Installing WakeUp server

In previous releases, the NightWatchman agent and WakeUp agent were part of the 1E Agent installer. From this release:

• 1E NightWatchman Agent installer: Replaces the old 1E Agent installer and includes only the NightWatchman agent

• WakeUp Server installer: No longer includes WakeUp Agent and includes only the WakeUp server

• 1E Client (previously Tachyon Agent) installer: Replaces the old 1E Agent installer and includes a WakeUp client module, for installation on clients and WakeUp servers.

After installation of the WakeUp server you must install the 1E Client with its WakeUp module enabled. This is explained on the Installing the 1E WakeUp Agent page, which has links to documentation for the 1E Client.

Integration choice

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.

Installing the WakeUp server on Configuration Manager hierarchies

The WakeUp server must be installed on all Configuration Manager primary site servers as it will only wake machines for the Configuration Manager site on which it is installed. There is no reason to install WakeUp server on a CAS, given that no clients report directly to a CAS.

If you know the Site server has a remote SMS Provider role, perhaps because a WakeUp Server installation failed, then you will need to provide the installer with an alternative security account instead of allowing WakeUp Server to use the default LocalSystem. For details of how to provide account details, please refer to Integrating WakeUp server with a distributed Configuration Manager setup.

Installing the WakeUp server with the wizard

To install WakeUp server with the interactive wizard:

7. On the Welcome screen, click Next.

8. On the License Agreement screen, accept the license and click Next.

9. On the Customer Information screen, enter the name of your organization together with the license key and click Next. If you do not enter a license key, you are subject to a 30-day evaluation.

   Although the license only needs to be applied to the WakeUp server, you need to purchase licenses for all the Configuration Manager Client seats being serviced.

10. On the Destination Folder screen, accept the default location (C:\Program Files\1E\WakeUp) for the installation or click choose a new location.

11. On the Installation Type screen, choose from:

    • Install Server Components: Installs the server components locally. This may be either the Configuration Manager or NightWatchman Management Center version of the WakeUp server depending on whether the Configuration Manager provider has been found locally installed or not.

    • Configuration Manager: Installs the Configuration Manager version of WakeUp. If this option is selected, the installer detected the Configuration Manager provider installed locally.

    • NightWatchman Management Center: Installs the NightWatchman Management Center version of WakeUp. If this option is selected, the installer did not detect the Configuration Manager provider installed locally.

    • Admin Components: Installs the WakeUp Console. This must be installed when the Install Server Components checkbox is selected.

12. The Installation Options screen is displayed only if you chose the Install Server Components option. Choose the configuration for the WakeUp server:

    • Stand-alone Server: Does not require extra steps after finishing the current installation wizard, other than installing the 1E Client with the WakeUp module enabled on the WakeUp server.

    • Dedicated Agent: You will need to install the 1E Client with the WakeUp module enabled on a dedicated client per subnet, in dedicated agent mode.

    • Multiple Agents: Strongly recommended. You will need to install the 1E Client with the WakeUp module enabled on all clients, in multi-agent mode.

      Although three options exist, choosing multiple agents enables all the WakeUp functionality to be used. We recommend selecting this option unless you have been advised otherwise by a 1E representative.

13. You also set the level and type of encryption used when the WakeUp server communicates with its agents. Tick the Use FIPS Encryption checkbox or choose from:

    • Disabled: All packets are sent unencrypted and WakeUp behave exactly as in previous versions.

    • Partial: Encrypted or unencrypted communication are allowed.

    • Full: All communications are encrypted and any unencrypted packages are discarded.

      If you are using FIPS, ensure that the same settings are made for all WakeUp server and 1E Agent.

14. Click Next to continue.

15. On the NightWatchman Management Center Configuration screen, set the parameters for integrating with NightWatchman Management Center. The NightWatchman Management Center must already be installed and you must have the host server name to hand.

    • Enable reporting: Check this to enable reporting and the other controls on this screen. This option is user configurable only when the WakeUp server installation type is Configuration Manager, which happens when the installer detects a local installation of the Configuration Manager provider. When the WakeUp server installation type is NightWatchman Management Center, this is automatically checked and all the other controls are always be available.

    • Reporting server: Enter the fully qualified domain name of the server where the NightWatchman Management Center Web service component is installed. This field validates the FQDN to ensure the Web service component is contactable.

    • Apply WMI Namespace: Check this to set permissions on the N1E namespace for the account used in the Account or Group – Domain\User field. You must enable this if you want to allow non-administrators to send wake ups or make changes in the WakeUp console. The NightWatchman Management Center Console service connects to this WMI namespace when sending wake ups (alarm clocks, maintenance windows and on-demand wake ups). If you are running the NightWatchman Management Center Console Service as the user to whom you are granting the WMI permissions, and if the Console Service is currently running on the same machine that you are installing WakeUp on, you must restart the NightWatchman Management Center Console service for these permissions to take effect.

    • Account or Group: Domain\User enter the domain and name of the account or group you want to give WMI and DCOM permissions to.

16. Click Next.

17. On the Ready to Install the Program screen, click Next.

18. On the Installation screen, click Finish.

After installation of the WakeUp server you must install the 1E Client with its WakeUp module enabled. This is explained on the Installing the 1E WakeUp Agent page, which has links to documentation for the 1E Client.

Installing the WakeUp server in unattended mode

In the following:

• ABCD-1234-5678-8765-4321 is your license key

• <RepServ> is the server where the NightWatchman Management Center Web service is installed

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. Refer to WakeUp Server installer properties.

Integrating WakeUp server with a distributed Configuration Manager setup

Ensure you meet the prerequisites before you start. Refer to Supported platforms and prerequisites. 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:

1. Install the WakeUp server on the command-line with the WAKEUPSVCUSER and WAKEUPSVCPASSWORD installer switches.

2. If you are using a domain account, add WAKEUPSVCUSERand WAKEUPSVCPASSWORDon the installer command-line. For example WAKEUPSVCUSER=<Domain>\<User> WAKEUPSVCPASSWORD=<Password>where <Domain> is the domain where the account is located, <User> is the account username and <Password> is the password for the domain account.

3. If you are using the network service just add WAKEUPSVCUSERon the installer command-line. For example, WAKEUPSVCUSER="NT AUTHORITY\NETWORK SERVICE"

4. Grant additional security rights to the local WakeUp server (C:\Program Files\1E\WakeUp\) and Agent installation (C:\ProgramData\1E\WakeUpSvr\) directories.

5. Grant modify permissions to these directories for the domain account or network service, whichever is being used. All folders and files below these locations should be set to inherit these permissions.

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

Relicense the WakeUp server

To relicense the WakeUp server, run:

wakeupsvr.exe -relicense=<LicenseKey>

Uninstalling the WakeUp server

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.

Detailed requirements

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

Installing the 1E NightWatchman Agent for Windows

In previous releases, the NightWatchman agent and WakeUp agent were part of the 1E Agent installer. From this release:

• 1E NightWatchman Agent installer replaces the old 1E Agent installer and includes only the NightWatchman agent.

• WakeUp Server installer no longer includes WakeUp Agent and includes only the WakeUp server.

• 1E Client (previously Tachyon Agent) installer replaces the old 1E Agent installer and includes a WakeUp client module, for installation on clients and WakeUp servers.

There are installers for both x86 1ENightWatchmanAgent.msi and x64 1ENightWatchmanAgent-x64.msi so ensure you choose the correct one for your operating system.

The 1E NightWatchman Agent will install on these client operating systems:

• Windows 10 CB 21H2

• Windows 11 CB 21H2

• Windows 10 CB 21H1

• Windows 10 CB 20H2

• Windows 10 CB 2004

• Windows 10 CB 1909

• Windows 10 CB 1903

• Windows 10 CB 1809

• Windows 10 CB 1803

Refer to Accounts needed to install the NightWatchman Agent and 1E Client and Networking.

Installing the 1E NightWatchman agent using CDA

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.

Installing the 1E NightWatchman agent with the wizard

To install the agent with the wizard:

5. On the Welcome screen, click Next.

6. On the License Agreement screen, accept the terms of the agreement and click Next.

7. On the License Wizard screen, if you do not have a license key for NightWatchman, you are subject to a 30-day evaluation.

8. On the NightWatchman Management Center Configuration screen, choose the communication protocols.

   • Enable HTTP.

   • Enable HTTPS: The NightWatchman Management Center website must already have been configured for HTTPS. You can opt to use client certificates from the local certificate store. You can search for these by certificate issuer or the certificate subject depending on which of the Match Certificate Issuer or Match Certificate Subject radio buttons is selected.

   • NMC Web Service: Enter the fully qualified domain name of the server hosting the NightWatchman Management Center web service. For example, MYNWMSERVER.DOMAIN.COM.

   • Checking Use FIPS Encryption configures the NightWatchman Management Center to use FIPS encrypted communications. Ensure that the same setting is is made for all NightWatchman Management Center, WakeUp Server and 1E NightWatchman Agent components.

9. On the Destination Folder screen, click Next to accept the default location C:\Program Files\1E\NightWatchman\ or Browse to choose a new location.

10. On the Ready to Install screen, click Next.

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

1E NightWatchman service

Post-installation you will see the following services running.

Default file locations

• The default for installation folder for both 32 and 64-bit platforms is: C:\Program Files\1E\NightWatchman.

• NightWatchman component files are copied to the respective sub-folders during installation.

  C:\Program Files\1E\NightWatchman

  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.

  %ALLUSERSPROFILE%\1E\Agent\NightWatchman.log

  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.

  %ALLUSERSPROFILE%\1E\Reporting\NightWatchman

Windows registry

The 1E NightWatchman Agent stores its registry information in the following locations.

• HKLM\SOFTWARE\1E\Common

• HKLM\SOFTWARE\1E\NightWatchman

The HKCU\SOFTWARE\1E\NightWatchman registry key is created after first logon.

Default NightWatchman configuration

On a default installation, the NightWatchman component is configured as follows:

• System tray applet is visible: Notification icon is visible with the Keep Active option enabled.

• Logoff mode is active: You are prompted prior to a shutdown.

• Shutdown action is normal: If power management is enabled on the machine, NightWatchman shuts down or restarts as appropriate.

• No shutdowns initially scheduled: Until a shutdown is scheduled, you can only initiate a shutdown from the system tray.

• Advanced sleepless detection is on: By default, processes keeping the machine out of sleep mode are automatically detected.

• Reporting is on: By default, reporting information is sent by the 1E NightWatchman Agent and as long as the NightWatchman Management Center configuration is in place.

Installing the NightWatchman Agent in unattended mode

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.

Licensing the 1E NightWatchman Agent

If you do not have a valid license 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:

1. On the command-line, run the following, where ABCD-1234-5678-8765-4321 is your new license key.

   Copy

   nwmsvc.exe –relicense=ABCD-1234-5678-8765-4321

2. Start the service with:

   Copy

   nwmsvc.exe -start

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 the Support team. Refer to 1E Support.

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.

Using Microsoft System Center Configuration Manager to install the 1E NightWatchman Agent

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.

The 1E NightWatchman Agent, Sysprep and disk imaging

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.

1. NightWatchman creates a GUID when 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 GUID is 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.

2. It is good practice to remove the hardware inventory records so that a new hardware inventory is taken. This eliminates the possibility of previous hardware inventory information being reported for the new computer as it forces a complete hardware inventory to be taken the first time NightWatchman runs on the newly imaged machine.

3. Install the NightWatchman agent with the necessary configuration and then stop its service. Set the service type to manual – this must be changed back to automatic on the newly imaged clients as part of the automated deployment but only after the machine has joined the domain and rebooted. This ensures that all of the information about the computer is correct before the 1E NightWatchman Agents start for the first time.

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:

Uninstalling or repairing the 1E NightWatchman Agent

To uninstall the 1E NightWatchman Agent:

1. Go to Program and Features.

2. Select the 1E NightWatchman Agent.

3. Click Uninstall.

To repair the 1E NightWatchman Agent:

1. Run the installer.

2. Choose the 1E NightWatchman Agent.

3. Click Repair.

Installing the 1E WakeUp Agent

In previous releases, the NightWatchman agent and WakeUp agent were part of the 1E Agent installer. From this release:

• 1E NightWatchman Agent installer replaces the old 1E Agent installer and includes only the NightWatchman agent.

• WakeUp Server installer no longer includes WakeUp Agent and includes only the WakeUp server.

• 1E Client (previously Tachyon Agent) installer replaces the old 1E Agent installer and includes a WakeUp client module, for installation on clients and WakeUp servers.

The 1E Client

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).

The WakeUp client module of the 1E Client replaces the 1E Agent WakeUp components of the 1E Agent and 1E WakeUp Server. If the WakeUp Server is configured in multi-agent mode (recommended) then the 1E Client must be installed with the WakeUp client module enabled on all in-scope devices.

When the 1E Client starts, and the WakeUp client module is enabled, it will only initialize the WakeUp client module if the OS version is Windows 7 or later. The 1E Client will automatically remove any previous installation of the WakeUp component from the 1E Agent, leaving behind the NightWatchman component, and keeping the WakeUp Agent registry settings. For NightWatchman v7.2.500 onwards the NightWatchman Agent has a separate installer, and its settings continue to be managed by the NightWatchman Management Center Web Service.

The WakeUp Server also requires a local WakeUp Agent, and therefore requires the 1E Client to be installed with the WakeUp client module enabled. The WakeUp Server is a 32-bit process and its registry entries are in the 32-bit WOW6432Node area. The 1E Client is a 64-bit process with its registry entries in the 64-bit area. When the 1E Client starts, if the WakeUp client module is enabled the 1E Client will automatically remove any previous installation of the WakeUp Agent component, leaving behind the WakeUp Server component, and moving the existing WakeUp Agent registry settings from the 32-bit to the 64-bit area of the registry.

WakeUp and the WakeUp client module of the 1E Client do not require 1E Platform; only the 1E Client is required, 1E Platform is not required. The full 1E infrastructure is required only if you are integrating NightWatchman with 1E.

The WakeUp client module of the 1E Client is not supported on:

• Non-Windows devices.

• Legacy OS (that is OS which Microsoft no longer support including Windows XP, Vista, 7, Server 2008 etc.)

The following legacy WakeUp features from the 1E Agent do not exist in the WakeUp client module:

• 1E WakeUp Agent service - all WakeUp Agent features are now implemented as the WakeUp client module in the 1E Client service.

• Computer Health feature - is now obsolete.

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 1E Platform infrastructure. The platform infrastructure is only required if using the NightWatchman online status feature. Refer to Enabling Online Status using 1E Platform integration.

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

Installing the 1E Client agent using CDA

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.

WakeUp module 1E Client installer properties

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

The WakeUp screen in the 1E Client installer

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.

Installing the Mac 1E Agent

The process to install the Mac 1E Agent is:

1. Installing the Open SSL libraries

2. Running the configuration script

Prerequisites

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.

Refer to Secure communications.

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.

Installing the Open SSL libraries

To install the Open SSL libraries:

1. Double-click CopyOpensslLibs.command to install the Open SSL libraries.

2. Enter your administrator password. If the Open SSL libraries are already installed, you will not be prompted for your administrator password.

3. A window is displayed to notify you that the process has completed.

4. Close that window.

Running the configuration script

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:

• The installer supports an optional pre-configuration file. This must be located on the computer where the installation is taking place with the following path and file name: /Library/Preferences/com.1E.NightWatchman.PreConfiguration.plist

• If the installer locates the file, it looks for the license number, the location (HTTP or HTTPS) of the server and applies them to the NightWatchman preference file. If the server is not found, it sets reporting to false.

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:

1. Double-click 1E Agent Configure Install.app.

2. Enter your production license key. If you do not provide one, you are subject to a 30-day evaluation period.

   

3. Click Continue.

4. Choose your communications protocol.

   

   1. If the connection protocol you are using is HTTP, check the Connect through HTTP to server option and provide the NetBIOS name of the NightWatchman Management Center website server next to it.

   2. If the connection protocol you are using is HTTPS, check the Connect through HTTPS to server option and provide it's FQDN to the NightWatchman Management Center website server next to it.

   3. If you are using FIPS encryption, check the Use FIPS Encryption option. Ensure that the same setting is made for all NightWatchman Management Center, WakeUp Server and 1E Agent components. Refer to Secure communications.

5. The installer will validate the location of the NightWatchman Management Center Web server. In the even that it fails to locate it, you will be prompted with a message.

   

   1. Click OK.

   2. Check the server name is correct and that the NightWatchman Management Center website is up and running and contactable from the computer where the installation is taking place.

6. When the configuration for the installer is done, click Launch Installer.

   

7. On the Introduction screen, click Continue.

8. On the License agreement screen, accept the terms of the agreement and click Continue.

   

9. On the Installation Type screen, click Install to accept the default installation location which is /Library/Application Support/1E/NightWatchman.

   To install the files to a different location click Change Install Location and select a new destination for the installation files. Click Install when you are done.

   

10. You will be prompted that the machine requires a reboot after the installation takes place.

    Click Continue Installation.

    

11. Enter your administrative password and click Install Software.

    

12. On the Summary screen, click Restart.

    

Licensing the 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:

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:

1. Create the pre-configuration file and push it to the client machines. For example, using Copy Items in Apple Remote Desktop.

2. Create the pre-configuration file using the command-line on the client computer.

   where <NWMC SERVER> is the server where the NightWatchman Management Center website is located and <1ELicKey> is your license key. For example:

   Copy

   defaults write /Library/Preferences/com.1E.NightWatchman.PreConfiguration HTTPServer <NWMC SERVER> defaults write /Library/Preferences/com.1E.NightWatchman.PreConfiguration LicenseNumber <1ELicKey>

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.

Uninstalling the Mac 1E Agent

To uninstall the Mac 1E Agent:

1. Click the installer disk image.

2. Run the Uninstall 1E Agent command script. You must run this with administrator rights.

Beyond the Mac installation

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

Refer to 1E Agent Mac command-line switches and NightWatchman Agent and 1E Agent for Mac.

Agent log files

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.

Installing Web WakeUp

The 1E Client 4.1 or later must be installed with the WakeUp module enabled on target computers if you want to wake them with Web WakeUp.

Installing Web WakeUp with the wizard

To install Web WakeUp using the wizard:

1. On the Welcome screen, click Next.

2. On the License Agreement screen, agree the terms and conditions and click Next.

3. On the Destination Directory screen, choose the installation directory. The default is:

   • On 32-bit systems: C:\Program Files\1E\WebWakeUp

   • On 64-bit systems: C:\Program Files (x86)\1E\WebWakeUp

4. On the NightWatchman Console Service screen, choose the location for the service. The location is not validated by the installer. Optionally, check Enable ActiveX integration (enables Web WakeUp web pages to use ActiveX controls) or Enable Remote Desktop (enables a remote session on a woken up computer).

5. On the Ready to Install screen, click Next.

6. Click Finish.

Installing Web WakeUp in unattended mode

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.

Refer to Web WakeUp installer properties.

Post-installation configuration

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:

• Firewall access – on the server where the NightWatchman Console service is installed, enable TCP port 8750 access from the computer where the Web WakeUp website is installed.

• NightWatchman Console service – set the SPN for the server where the NightWatchman Console service is running with setspn –a WEBWAKEUP/SERVICE <NWMCAccount> where <NWMCAccount> is the account the NightWatchman Console service is running under in the format domain\serviceacct

• Web WakeUp website – set the SPN for Web WakeUp website by editing the <client> element in its web.config file.

  Copy

  <client>
      <endpoint address="net.tcp://ACMENWMC:8750/MachineSearchService"
       binding="netTcpBinding"
       bindingConfiguration="NetTcpBinding_MachineSearchService"
       contract="MachineSearchService.MachineSearchService"
       name="NetTcpBinding_MachineSearchService">
          <identity>
              <servicePrincipalName value="localhost" />
          </identity>
      </endpoint>
      <endpoint address="net.tcp://ACMENWMC:8750/AuthorisedMachineService"
       binding="netTcpBinding"
       bindingConfiguration="NetTcpBinding_AuthorisedMachineService"
       contract="AuthorisedMachineService.AuthorisedMachineService"
       name="NetTcpBinding_AuthorisedMachineService">
          <identity>
              <servicePrincipalName value="localhost" />
          </identity>
      </endpoint>
  </client>

  Update both values for Service Principal Name from:

  Copy

  <servicePrincipalName value="localhost" />

  To (where the SPN NWMCSPN had been previously created):

  Copy

  <servicePrincipalName value="NWMCSPN" />

  By default, web.config is located in:

  • On 32-bit systems: C:\Program Files\1E\WebWakeUp\Website

  • On 64-bit systems: C:\Program Files (x86)\1E\WebWakeUp\Website

Enabling Web WakeUp authorization

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:

• When you install NightWatchman Management Center using the STRICTAUTHORIZATION installer property on the command-line

• Post-installation by setting the AuthorisedMachineModule parameter in the NWM.ServiceHost.exe.config file. Refer to Web WakeUp server configuration.

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:

• UserTicket: The identifier for the user returned by the authentication mechanism. For Windows, it takes the format Domain\User.

• NetbiosName: The NetBIOS name for the computer the user can wake up. Use * if you want the user to wake up any computer.

• DomainName: The domain name for the computer.

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. Refer to Web WakeUp authorization table.

Restricting access to the Web WakeUp authorization service

You must lock down the Web WakeUp authorisation service in IIS as it provides the AddAuthorisedMachine , DeleteAuthorisedMachine , GetAuthorisedMachines, and UpdateAuthorisedMachine methods that make it possible to update the tbWWU_Authorised_UserMachines table programatically. If access is not restricted, any user with web access and the right knowledge can use the Web WakeUp authorization service to grant themselves or other users permissions to wake any computer.

To lock down the service, update the NTFS file permissions for the AuthorisationServices.asmx file to restrict access so that only Web WakeUp administrators can browse to the service. On a default installation, this file is located in C:\Program Files\1E\WebWakeUp\Website\WebServices

Another way of restricting user access to waking arbitrary computers is to configure the Web WakeUp site to not display the wake up computer, search and register pages. If you do this, you will need to register the appropriate computers for all users of the Web WakeUp site with the AddRegisteredMachine and GetRegisteredMachines methods to update the tbWWU_Default_UserMachine_Mapping table. These methods are accessed from http://host/WebWakeUp/WebServices/LocalServices.asmx page. Refer to Web WakeUp Local services API.

Deploying the Web WakeUp ActiveX Control to clients

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 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 described in Website control.

Detailed requirements

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

Installing Enterprise View

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

1. On the Welcome screen, click Next.

2. On the License Agreement screen, accept the terms of the agreement and click Next.

3. On the Prerequisites Checks screen, you will not be able to install components that fail their respective prerequisite checks.

4. In the Custom Setup screen, choose the features you want installed. You must run the installer once for each of the components you want installed separately.

   • Enterprise View Web application: Installs its Web components.

   • Database: Installs the database for Enterprise View.

   • Click Change to install the components in a different location. They are installed in C:\Program Files\1E\Enterprise View\

5. On the Website Configuration screen, set the parameters for the Enterprise View website as follows:

   • Website Port: Sets the port to be used for the Enterprise View website. This defaults to the standard IIS port 80. If changed from the default, users will need to add this to the URL for the Enterprise View Website, for example http://myserver:8080/EnterpriseView

   • IP Address: Sets the IP address for the Enterprise View website.

   • Host Header: Sets the host header for the Enterprise View website. This is the server name used to locate the website when users enter the site URL in their browser. In order to use it when it has been set, you will need to have defined the appropriate DNS settings.

6. In the Database Server screen, set the parameters for installing it Set the Database server that you are installing to: parameter to the server where the database resides. Click Browse... to display a list of server and instances visible from the local computer. The format of the database server identified may be one of the following:

   • (Local): Uses of the local default instance.

   • ServerName: Uses a remote server using the default instance.

   • ServerName\Instance: Uses a remote server and named instance using a dynamic port. For this option to work correctly the SQ browser service must be enabled.

   • ServerName: Port – uses of a remote server and instance defined by its fixed port

7. Set the Name of an existing or new database catalog: field to an existing database on the database server or a new name. If it is on a existing database server, the Enterprise View tables are created in the existing database. If it is on a new server, a new database is created with the new name and the tables are in that database. Clicking the Browse button will display the existing database catalogs on the selected database server.

8. On the Ready to Install screen, click Next.

9. Click Finish.

Post-installation

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

1. Configure the IIS client access policy to allow cross domain access to the Enterprise View website. This is done via the ClientAccessPolicy.xml file which resides in the IIS root folder, typically c:\inetpub\wwwroot. If this file already exists, append the contents of the ClientAccessPolicy.xml file from the Enterprise View %INSTALL_DIR%\Dashboard.web folder to it. If it does not exist, copy it from the Dashboard.web folder to the IIS root folder.

2. Edit the web.config file the Enterprise View %INSTALL_DIR%\Dasboard.web folder and modify the service base URI used to access the Enterprise View website.

3. Locate the line in the file:

   Copy

   <!-- add key="ServiceBaseUri" value="http://<<HostFQDN>>/EnterpriseView/"/-->

4. Remove the comments and update the <<HostFQDN>> placeholder with the base URI for your Enterprise View website.

   Copy

   <add key="ServiceBaseUri" value="http://machineA.acme.com/EnterpriseView/"/

5. Save the file and test the new configuration by accessing the Enterprise View home page using the host FQDN.

Detailed requirements

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

Upgrading NightWatchman Enterprise

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:

1. Direct upgrade – with a direct upgrade, you do not need to step through the intervening releases and instead do a direct upgrade to NightWatchman version 7.3.

2. Phased upgrade:

   Version	Phased upgrade process
   7.2	The process for a phased upgrade from NightWatchman 7.2 is: Upgrade to NightWatchman version 7.2.500 Upgrade NightWatchman version 7.2.500 to version 7.3

In all cases, we advise the following:

• Test your upgrade path and processes in a lab prior to upgrading your production environment, especially if you are upgrading to version 7.3 from and old version such as 7.0 or 7.1.

• Upgrade all NightWatchman Management Center and WakeUp servers before starting the upgrade of any NightWatchman Agents and 1E Clients with the WakeUp module enabled.

• If you are unsure about the upgrade, engage one of our consultants. Contact your 1E account team for more details

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.

Refer to Installing NightWatchman Management Center and Installing WakeUp server.

Custom reports

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.

Approach

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

1. Upgrade to NightWatchman Management Center 7.3

2. Upgrade to WakeUp Server 7.3

3. Upgrade to Web WakeUp 7.3

4. Upgrade to NightWatchman Agent 7.3

5. Upgrade to the latest 1E Client with the WakeUp module enabled.

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.

Licensing

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.

Rollback

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:

1. Uninstall all 7.3 server components – NightWatchman Management Center/Agility Framework/WakeUp.

2. Delete the AgilityFrameworkReporting database using SQL Management Studio.

3. Restore your pre-upgrade version of the AgilityFrameworkReporting database from backup.

4. Install previous version of NightWatchman Management Center (or Agility Framework with NightWatchman and WakeUp product packs) and do not drop database.

5. Copy any import script and/or custom report files to the previous location.

6. Install previous versions of WakeUp servers where you upgraded them.

7. Validate functionality using suggested tests within this document.

Changes in functionality

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:

• WakeUp integration with Nomad

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.

Technical preparation

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

Method 1

If the server is dedicated to NightWatchman Management Center the IIS services can be stopped by running the following command from a command prompt.

iisreset /stop

Method 2

If the server shares IIS configuration with other applications which prevents the IIS services from being stopped, the NightWatchman Management Center application pools can be taken offline. To do this, start IIS Manager, expand the server, select Application Pools and stop:

• NWMC_AFWebservice

• NWMC_ReportConsole

Prior to running the SQL backup, the AFwebservice web service should be taken offline, to prevent clients from reporting data into the server during the upgrade. This is particularly important in a roll-back situation to prevent data loss from occurring.

Common Backup Tasks

Connect to the server hosting the NightWatchman Management Center database and using SQL Server Management Studio, take a full backup of the AgilityFrameworkReporting database.

Using a backup tool, backup the existing 1E software installation folder and all subfolders and files on all servers where NightWatchman Management Center and WakeUp Server have been installed.

If any custom reports have been developed for the existing version of the software (either by 1E or another party), copy the report files (with file extensions .rdlc and .rdlx to a temporary location. By default, these are located in C:\Program Files (x86)\1E\NightWatchman Management Center\ReportConsole\Source (or C:\Program Files (x86)\1E\AgilityFramework\AFConsole for previous versions).

If any stored procedures have been developed for the custom reports, these should be saved as .sql files and copied to the same temporary location. The stored procedures are referenced in the .rdlx files and can be saved as .sql files using SQL Server Management Studio. If a previous version of NightWatchman Management Center is installed, copy any modified or customized import scripts and input files to a temporary location.

By default these are located on the NightWatchman server in C:\Program Files (x86)\1E\NightWatchman Management Center\ConsoleService\ImportScripts and have the file extensions .vbs and .csv

If any customization has taken place with the NightWatchman agent scripts, this configuration should be backed up in order that it can be re-applied after upgrade. Examples are:

• Custom or modified NightWatchman shutdown scripts, default installation path on the agents is C:\Program Files\1E\NightWatchman\Scripts.

• Custom scripts to control NightWatchman processing e.g. prerun.vbs, runalways.vbs

Upgrading to NightWatchman Management Center 7.3

You can upgrade NightWatchman Management Center 7.2 or 7.2.500 to 7.3 directly. Upgrades of prior versions of NightWatchman Management Center have been tested with only their successive version or its successive version and so you should upgrade to intermediate releases if you are using an older version of NightWatchman Management Center. Contact 1E Support if that is not practical.

The process to upgrade an existing NightWatchman Management Center installation to 7.3 is:

1. When running the NightWatchman Management Center installer, accept all default options except where stated otherwise. The installer checks the prerequisite are met and detect that this is an upgrade scenario

2. On the Custom Setup screen, ensure that all components are selected for installation. If NightWatchman Management Center has been installed at a non-default location, ensure that the 7.3 install path matches – click Browse and navigate to the correct location.

3. On the Database Server Configuration screen, ensure that the correct SQL server is selected.

   Ensure that the option to Drop any existing NightWatchman Management Center database is not selected.

4. On the Website Configuration screen, ensure that the same IIS settings are used as the original installation.

5. On the Console Service Configuration screen, ensure that the same domain and account settings are used as the original installation. You will need to enter the password for the NightWatchman service account.

6. On the 1E ActiveEfficiency Server screen, you can enable and configure the integration with ActiveEfficiency - ActiveEfficiency Server must already be installed and be accessible on the network before you do the integration.

   1. See the NightWatchman Enterprise and ActiveEfficiency page for more details

7. On the Environment Setup screen, ensure that the appropriate environment size is selected - this setting governs the default timings and intervals for server and client tasks. On an upgrade, an attempt will be made to default the currency code to the one set in the previous version. If this is not possible the currency code will be set to the one associated with the current system locale.

8. After the installation wizard has completed successfully, if the application pools were stopped using Method 2, these must be stopped again using the previously described steps.

Once executed successfully, the remaining NightWatchman Management Center and WakeUp SQL agent jobs will be enabled.

NightWatchman Console

When all SQL Agent jobs are enabled, start the NightWatchman Console and check all tabs for the preservation of data including structure, power policies, power consumption values and security.

Custom reports

This section can be skipped if using the standard reports. If there is a requirement to re-map custom reports, the following steps can be used.

1. Copy any custom report files (.rdlc and .rdlx) obtained in the preparation steps from the temporary location to the NightWatchman Management Center installation directory. By default this is C:\Program Files (x86)\1E\NightWatchman Management Center\ReportConsole\Source\Report Definitions.

   Depending on version installed prior to the upgrade, these files may exist in C:\Program Files (x86)\1E\NightWatchman Management Center\ReportConsole\Source, if so these can be moved to the Report Definitions subfolder.

2. Check each custom report .rdlx file (open with a text editor) and confirm that the referenced stored procedure exists within the AgilityFrameworkReporting database. If it does not exist, open the equivalent .sql file created during the preparation steps and execute against the AgilityFrameworkReporting database to create the stored procedure.

3. If the SQL Server database is installed locally, check the permissions of the custom stored procedures and ensure that NT AUTHORITY\NETWORK SERVICE has execute permissions.

4. If the SQL Server database is remote, ensure that the machine account DOMAIN\Machine$ has execute permissions

5. Open each custom report .rdlx file with a text editor and note the "category".

   

6. In the reports source directory, which is by default C:\Program Files (x86)\1E\NightWatchman Management Center\ReportConsole\Source, edit reportcategories.xml and add a category name as per the .rdlx file.

   

7. Restart the NightWatchman Management Center Reports Console, select the custom report menu and run the report.

   

8. Repeat steps for all required custom reports.

   If a custom report returns an error on execution and there is an on-going requirement for this information, contact 1E Support for assistance. As custom reports are not covered by the standard 1E support agreement, any remedial work to allow compatibility with 7.2 may be chargeable.

Upgrading the Import Wizard scripts

If import scripts are used to manage the NightWatchman Console structure and assignment of computers, the following steps can be used:

1. Copy any import script files (.vbs and .csv) obtained in the preparation steps from the temporary location to the NightWatchman Management Center installation directory which is by default C:\Program Files (x86)\1E\NightWatchmanManagement Center\ConsoleService\ImportScripts

2. To verify that the import wizard process works following the upgrade, in the NightWatchman Console, move a computer from an in-use location or organization tier to the UNASSIGNED BUILDING or UNASSIGNED DEPARTMENT folder

3. Run the import wizard using the GUI (or using the Task Scheduler if previously configured) and select the appropriate script from the earlier version. Ensure that the import wizard completes successfully and the computer is moved to the expected location or organization tier.

Upgrading to WakeUp Server 7.3

You can upgrade WakeUp Server 7.2 or 7.2.500 to 7.3 directly. Older versions of WakeUp Server must be upgraded incrementally to their next version. Please contact 1E Support if that is not practical.

Information on general installation options and its prerequisites can be found in Installing WakeUp server. Please review Upgrading NightWatchman Enterprise to ensure that the existing 1E software installation folder hierarchy is backed up before running the upgrade.

Please refer to Integrating WakeUp server with a distributed Configuration Manager setup for advice on how to configure WakeUp Server for this type of installation. This is where the Configuration Manager WMI provider (its "SMS Provider") is installed remotely from the Configuration Manager Site Server.

The process to upgrade an existing WakeUp Server to 7.3 is:

1. When running the WakeUp Server installer, accept all default options except where stated.

2. On the Customer Information screen, enter your license key.

3. On the Destination Folder screen, if WakeUp Server has been installed in a non-default location, ensure that the 7.3 path matches – click Browse and navigate to the correct location.

4. On the Installation Type screen, ensure that the correct installation mode is selected. If running on an Configuration Manager Site Server, the installer automatically selects Microsoft Configuration Manager Integration.

5. On the Installation Options screen, ensure you choose the same settings as your original WakeUp Server installation.

6. On the NightWatchman Management Center Configuration screen, ensure you use the same reporting server and service account you used for your original WakeUp Server installation.

Post-upgrade

1. After the upgrade, start the WakeUp Console and check all tabs to ensure your settings have been preserved.

2. Restart the NightWatchman Console and on the Settings tab, check that the WakeUp integration settings are enabled and that the correct server is selected for the WakeUp provider. If incorrect, these can be modified via the NightWatchman Console, and applied by selecting the Apply button.

Previous versions required that a single WakeUp Server was registered with the NightWatchman Management Center. From version 6.0.500 onwards multiple WakeUp Servers can register and handle wake up requests. Settings are preserved during an upgrade, however, depending on the previous version, there may be new settings available within the WakeUp Console.

Validation

We recommend running these tests to validate functionality:

• On-demand WakeUp for an individual computer from the NightWatchman Console.

• On demand WakeUp for an individual computer from the Configuration Manager Administrator Console.

• Scheduled WakeUps for collections of computers from wake up enabled mandatory assigned Configuration Manager advertisements, software updates and task sequences.

• On demand WakeUp for an individual computer from Web WakeUp (if installed).

At this point, the main server functionality has been tested and if all the above steps have been validated then the upgrade has been successful. Repeat the upgrade process using the above steps for all other WakeUp Servers (working down the hierarchy) until all have been upgraded successfully.

Upgrading to 1E NightWatchman Agent 7.3

Please review Upgrading NightWatchman Enterprise to ensure that any NightWatchman agent customizations such as non-standard shutdown scripts are backed up (or included in the upgrade package source) before you run the upgrade.

All standard NightWatchman client settings are preserved during an upgrade, therefore, only the new NightWatchman 7.3 license key is required as a command line option.

There are installers for both x86 (1ENightWatchmanAgent.msi) and x64 (1ENightWatchmanAgent-x64.msi) so ensure you choose the correct one for your operating system.

For readability, we have broken down the command line into separate lines but when you run it, ensure that it is in a single line.

The basic command-line is:

msiexec /i 1ENightWatchmanAgent-x64.msi PIDKEY=XXXXX-XXX-XXX-XXX-XXX /l*v %temp%\NWMAgent.log /qn

The following default paths are set by the installer.

• Installation directory "%PROGRAMFILES%\1E\NightWatchman"

• Log file path C:\ProgramData\1E\Agent"

Following a successful upgrade, any client customization can be re-applied using a post installation script – copying additional or modified shutdown scripts to %PROGRAMFILES %\1E\NightWatchman\Scripts

This command-line and the 1ENightWatchmanAgent.msi installer should be incorporated into the production software distribution tool and run on all clients. (The verbose logging options are optional, but recommended to troubleshoot installation problems).

The recommended approach to the client upgrade is to develop a process (for example Configuration Manager Package, GPO, or scripted installation) that is repeatable and deploy on a representative pilot group of computers. The pilot group should include at least one computer of each hardware type (for example desktop and laptop) and one computer of each operating system version.

Validation

Once deployed, you are recommended to carry out validation tests to verify functionality before upgrading the remainder of your production client environment. You should run the following tests:

• NightWatchman clients continue to receive power management settings by chosen method (e.g. power policies via NightWatchman console, NightWatchman GPO template imported into Active Directory or NightWatchman.exe command-line options.

• On-demand wake up for an individual computer from the NightWatchman Console.

• On demand wake up for an individual computer from the Configuration Manager Administrator Console.

• Scheduled wake ups for collections of computers from wake up enabled mandatory assigned Configuration Manager advertisements, software updates and task sequences.

• On demand wake up for an individual computer from Web WakeUp (if installed).

Once functionality has been verified, install the Agent to the rest of your production environment to complete the process. We recommend you do a phased upgrade so that speed of upgrade is balanced with any impact on operational systems.

Upgrading the 1E Agent for Windows

First, upgrade the NightWatchman Management Center server-side components. These include the NightWatchman Management Center Web service and database and the WakeUp Server sever-side components. If you are only licensed for WakeUp, you will not be able to take advantage of NightWatchman features and vice versa.

1E NightWatchman Agent removes the legacy WakeUp Agent if it was enabled using the legacy 1E Agent. It will uninstall WakeUp Agent but retain registry settings for WakeUp. Use 1E Client to upgrade the WakeUp component of 1E Agent as described in 1E Client - Upgrading 1E Client.

You can use the 1E Client Deployment Assistant (CDA) to assist with deployment of 1E Agent and 1E NightWatchman Agent using Configuration Manager.

When upgrading 1E Agent that has both WakeUp and NightWatchman enabled and you require continuity of WakeUp features, then first deploy the 1E Client with WakeUp client module enabled, and then deploy the 1E NightWatchman Agent.

The legacy 1E Agent installer is replaced by two new installers:

• WakeUp Agent component of legacy 1E Agent is replaced by 1E Client (with its WakeUp client module enabled).

• NightWatchman Agent component of the legacy 1E Agent is replaced by 1E NightWatchman Agent.

The following occurs when upgrading a computer that has a legacy version of 1E Agent installed (with NightWatchman and/or WakeUp Agent enabled).

Upgrade command-lines

To upgrade to 1E NightWatchman Agent, use the following command-line. The PIDKEY is required for the license key. The /i Windows Installer property will either install components should they not already exist or upgrade components that are already there.

msiexec /i 1ENightWatchmanAgent-x64.msi PIDKEY=ACMECO-1234-5678-ABCD-4321 /qn

Changes to the install folder

During an upgrade, the installation folders are moved to a new folder.

C:\Program Files\1E\NightWatchman

Existing batch files or Configuration Manager programs that reference this location will require updating. Alternatively, add the path to the executable into the Windows PATH variable.

Changes to the scripts

During an upgrade, customized power down scripts are handled as follows. As the scripts are just text files, Windows Installer cannot evaluate if the scripts contained within the installer should be kept or if the existing scripts should be used in preference.

• Customer PreRun.vbs and RunAlways.vbs scripts are retained, regardless of customizations.

• New scripts (those not currently provided within the msi) are retained, for example myapp.vbs.

• Scripts stored in any sub folder are retained, for example .\scripts\sub1\excel.vbs.

• Customized scripts in the root of the scripts folder are moved to the following location, and the 1E versions will be used in preference, for example winword.vbs.

  C:\Program Files\1E\NightWatchman\Scripts\Old

Upgrading to 1E WakeUp Agent Module 7.3

1E WakeUp Agent Module including in the 1E Client is upgraded to 7.3 using 1E Client 5.0.

• The WakeUp client is installed with current WakeUp client configuration details if the 1E Client installation enables the module.

• The saved client configuration details are used if the computer had any existing values in WakeUp registry.

When 1E NightWatchman Agent is upgraded to 7.3 from a version prior to 7.2.500, WakeUp client is uninstalled but the WakeUp client configuration details are saved.

When you install or upgrade using 1E Client with the WakeUp client enabled, the WakeUp client will be upgraded using the saved client configuration details.

Refer to Installing the 1E WakeUp Agent.

Upgrading to 1E Client 4.1

1E Client is a replacement for the Tachyon Agent, and also includes client modules for WakeUp, Shopping and Nomad. Installation of 1E Client upgrades WakeUp client to 7.2.600.

When you install or upgrade, the WakeUp client is upgraded using saved client configuration details, only if the WakeUp client module is enabled. An upgrade will use existing registry values in the WakeUpAgt registry unless overridden by 1E Client installer properties.

When 1E NightWatchman Agent is upgraded to 7.2.500 the WakeUp Agent is uninstalled but the WakeUp client configuration details are saved.

Refer to Installing the 1E WakeUp Agent.

Enabling Online Status using 1E Platform integration

NightWatchman online status feature requires 1E Platform. With 1E Platform enabled and 1E Clients installed, you can integrate with NightWatchman to show the online status of NightWatchman clients.

In this version of NightWatchman, the only 1E Platform integration feature is Online Status, which allows NightWatchman to contact 1E Platform to obtain online status of clients.

1E Platform 9.1 authentication

The current 1E Platform release supports the use of Windows as an identity provider. Because of this, If you used 1E Platform versions which relied on NTLM authentication, you can upgrade to the current version of the platform that uses oAuth-based authentication, but you can still take advantage of your on-premises Active Directory infrastructure.

The configuration is the same as 1E Platform 9.0, with the addition of two changes to the Authentication proxy web.config file.

1. The Authentication AppId should be same as the tenantconfig.json file for Windows Authentication, for example:

   <add key="AuthAppId" value="1E1E1E1E-1E1E-1E1E-1E1E-1E1E1E1E1E1E" />

2. Principals in this environment are not defined as UPNs (for example, user@domain) but as Windows domain\user strings. When using the authentication proxy, you specify the “Out” principal mapping in this format, not as a UPN. For example, if you want to map the inbound NTLM account mydomain\incoming to an outbound principal mydomain\outgoing then you configure:

   <PrincipalMapping In="mydomain\incoming" Out="mydomain\outgoing" />

   This causes an incoming request made using the mydomain\incoming NTLM account to be mapped to a platform-neutral authentication request outbound that uses the principal mydomain\outgoing.

   When using an instance of the platform configured for platform-neutral authentication, for all other configured identity providers, the outgoing principal format is a UPN. This is relevant only when the platform is configured to use Windows as an identity provider.

Configuring 1E Platform

You need a platform user with Full Administrator role permissions and your license must have NightWatchman registered as a consumer. The following steps confirm your license details, and manually registers and enables NightWatchman as a consumer. The following process assumes you have already created the service account for your NightWatchman Management Center Console service in your AAD.

1. Login to 1E Platform.

2. Navigate to Settings > License Information.

3. Scroll down to Products.

   • Confirm that NightWatchman is listed as a Consumer under one of the feature items.

   • If it is not, contact your 1E Account Team to have it added to your license, and then follow the steps on 1E Platform - License information page: Reactivating licenses.

4. Navigate to Settings > Consumers.

5. Confirm that NightWatchman is listed as a Consumer, and it is Licensed and Enabled.

   • If it is not listed, then click Add to add a new consumer

   • If it is listed but not enabled, select and click Edit and check Enabled 

   • If it is listed but not licensed, then review your License Information as described above.

6. In the Add / Edit consumer dialog, enter:

   • NightWatchman as the Name.

   • 100 as the Maximum simultaneous instructions.

   • Check Use Windows Authentication.

   • Check Enabled.

7. Click Add (or Save if editing).

8. Navigate to Settings > Permissions > Users and Groups.

9. Click Add to add a new user.

10. Uncheck Security group.

11. Enter the name of the NightWatchman Management Center Console service account, and click the search icon.

12. Select the service account, and click Add.

13. In the list of users, ensure the service account is listed as Activated.

14. Navigate to Settings > Permissions > Assignments.

15. In the Assignments page, click on the All Instructions Viewer role.

16. Click the + button to add a new assignment.

17. In the Users and Groups column, search for the NightWatchman Management Center Console service account that you added earlier, and select it.

18. In the Management Groups column, select All Devices.

19. Click Save.

The Online Status feature does not run any instructions or read responses, it simply requires a platform user that has permissions on at least one Instruction Set, and must be assigned to the All Devices management group.

Configuring NightWatchman

You need Administrator rights on the server that hosts the NightWatchman Management Center Console service.

Using Notepad or a similar text editor.

1. Browse to the C:\Program Files (x86)\1E\NightWatchman Management Center\ConsoleService folder (This is the default path, yours may vary based on the install location of the NightWatchman Management Center).

   1. Open NWM.ServiceHost.exe.config

   2. Search for TachyonIntegrationEnabled and update its value to true.

      Copy

      <add key= "TachyonIntegrationEnabled" value= "true" />

   3. Change the TachyonAPI value to the 1E Platform server URL that you defined earlier.

      Copy

      <add key= "TachyonApiRoot" value= "https://tachyon.acme.local/consumer" />

2. Open the NightWatchman.config file located at C:\Program Files (x86)\1E\NightWatchman Management Center\ConsoleService.

   • Include the Authproxyserver FQDN:

     Copy

     <TachyonApiRoot" value= "https://AuthProxyserver FQDN/consumer" />

     for example:

     Copy

      value=“https://tachyon.acme.local/AuthProxy/consumer”

3. Using Services control panel (services.msc), restart the NightWatchman service.

4. Open the NightWatchman console.

   1. Select the Clients node.

   2. Drill down to one of the lowest clients group.

   3. The traffic light for each client should be red, yellow, gray, or green.

If you have any difficulties with the above, see the platform integration troubleshooting page or the platform documentation.

Verification

The NightWatchman console uses the platform to display traffic lights live status of its clients to indicate whether they are currently online or offline (or unknown). You can also check the status of groups within the NightWatchman client hierarchy.

The statuses are:

• Green: Online.

• Red: Offline.

• Yellow: Computer is not a platform client.

• Gray: Platform integration is not enabled.

Thanks to the platform's ability to deliver near real-time client data, it can be particularly valuable to you when you are using WakeUp to wake clients for urgent maintenance, such as deploying a solution to a zero-day vulnerability.

You can also use platform to optimize NightWatchman by using Endpoint Troubleshooting to return live status on clients to check for:

• NightWatchman or WakeUp client logs which might indicate an issue.

• Clients with pending reboots that have become pending in just the last few hours.

• Clients that don't have appropriate wake-on-LAN settings.

Troubleshooting permissions

View the NWM.ServiceHost.exe.log on the NightWatchman server.

Customizing the integration

NightWatchman platform 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 the platform's responsiveness.

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

1. Connect Object Explorer to the server.

2. Open Databases > AgilityFrameworkReporting > Tables.

3. Right-click the tbNWM_Dimension_GlobalSettings table.

4. Click Edit Top 200 Rows.

5. Modify the values as necessary.

6. Using the Services control panel icon (services.msc), restart the NightWatchman Console service.

By default, the 1E client will wait up to 15 seconds after a computer resumes from standby. During that period, the platform 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:

1. Edit the 1EClient.conf file on the client(s) in C:\Program Files\1E\Client

2. Add a line such as FastReconnectTimeInSeconds=10 (supported values are 5 to 60 seconds).

3. Restart the 1E Client service.