Introducing NightWatchman Enterprise 7.2.500
How it works
Quick starts, evaluations and pilots
Installing and upgrading
Installing NightWatchman Management Center
Installing the WakeUp server
Installing the 1E NightWatchman Agent for Windows
Installing the 1E Client - WakeUp client
Installing the Mac 1E Agent
Installing Web WakeUp
Installing Enterprise View
- Upgrading NightWatchman Enterprise
Enabling Online Status using Tachyon integration
- Installing NightWatchman Management Center
Working with NightWatchman Enterprise
Following a successful upgrade, any client customization can be re-applied using a post installation script – copying additional or modified shutdown scripts to
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 (e.g. 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 (e.g. desktop and laptop) and one computer of each operating system version.
Once deployed, it is recommended that validation tests are carried out in order to verify functionality before upgrading the remainder of the production client environment. We recommend running 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 7.2.500 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 4.1 - Upgrading 1E Client.
You can use the 1E Client Deployment Assistant 1.4 (CDA) to assist with deployment of 1E Agent and 1E NightWatchman Agent using Configuration Manager.
- Page not found for multiexcerpt macro.
To upgrade to 1E NightWatchman Agent, use the following command-line. The
PIDKEY is required for thelicense key. The
/i Windows Installer property will either install components should they not already exist or upgrade components that are already there.
Changes to the install folder
During an upgrade, the installation folders are moved to a new folder.
Existing batch files or Configuration Manager programs that reference this location will require updating. Alternatively, add the path to the executable into the Windows
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.
RunAlways.vbsscripts are retained, regardless of customizations
- New scripts (those not currently provided within the msi) are retained, for example
- Scripts stored in any sub folder are retained, for example
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