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

On this page:

Installing the WakeUp server with the wizard

To install WakeUp server with the interactive wizard:

  1. On the Welcome screen, click Next.
     
  2. On the License Agreement screen, accept the license and click Next.
     

  3. 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.
  4. On the Destination Folder screen, accept the default location (C:\Program Files\1E\WakeUp) for the installation or click choose a new location.
     
  5. 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.
     
  6. 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.

    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.

    Click Next to continue.
     

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


  8. Click Next.
     

  9. On the Ready to Install the Program screen, click Next.
     
  10. 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 in 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 below.

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

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

Integrating WakeUp server with a distributed Configuration Manager setup

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

To do this:

  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 WAKEUPSVCUSER and WAKEUPSVCPASSWORD on 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 WAKEUPSVCUSER on 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.

ComponentProductNotes
OS
  • Windows Server 2016
  • Windows Server 2012 R2
WakeUp server will install on systems running these server OSes.
System Center Configuration Manager
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910
  • SCCM CB 1906
  • SCCM CB 1902
  • SCCM CB 1810
  • SCCM CB 1806
  • SCCM 2012 R2 SP1
WakeUp server integrates with these Configuration Managers.
Runtime libraries

n/a


Installation and service accounts

To install the WakeUp server, you will need:

Installation account

  • Must be a domain user account with local admin rights on the server

If you are installing the WakeUp server in a distributed Configuration manager environment, WakeUp Server must be installed on each Configuration Manager site server. The installation account requires:

  • a SQL Login with db_datareader rights in each Configuration Manager SQL database
  • Administrator rights in the Configuration Manager Administrators Console - this can be Full Administrator or spfic rights decrobed below:
    • Application – Read
    • Boundaries – Read
    • Boundary Group – Read
    • Collection – Read, Read resource
    • Configuration policy – Read
    • Package – Read
    • Query – Read
    • Site – Read
    • Software Updates – Read.

WakeUp Server service account

  • Must be a domain user account, or Network Service account, to validate the WakeUp server in the NightWatchman Management console and to edit the priority of the WakeUp servers and their subnets or IP ranges
  • Must have a security role in the NightWatchman console that includes a minimum of View and Edit rights for WakeUp servers.

If you are installing the WakeUp server in a distributed Configuration manager environment, WakeUp Server must be installed on each Configuration Manager site server. The service account requires the following rights on each site server:

  • Have Log on as service rights on the Configuration Manager site server
  • Be a member of the local administrators group on the Configuration Manager site server or at least have full read and write access to the 1E registry key.
    • 32-bit platforms: HKEY_LOCAL_MACHINE\SOFTWARE\1E
    • 64-bit platforms: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\1E
  • Have the following NTFS permissions:
    • Minimum Read and Execute rights on the INSTALLDIR folder
    • Minimum Full rights on the LOGPATH and the following folders if located anywhere other than LOGPATH (DATAFILESDIRSPOOLDIRWUSPOOLDIRHEALTHSTATUSDIR).
  • Have full WMI permissions for the following WMI namespaces - some of these are set already for the Network Service account and SMS Admins group, these permissions are set manually in Computer Management/Services and Applications/WMI Control/Security,or can be set using our free WmiConfigPerms utility.
    • root\ccm
    • root\cimv2
    • root\sms
    • root\sms\site_<SiteCode>
  • In the Configuration Manager Console, grant the account specific Configuration Manager class security rights as described below for the relevant version of Configuration Manager.

The service account requires the following Administration rights in Configuration Manager before installing WakeUp Server. We recommend creating a new security role and adding the permissions. Doing this causes the specified account/group to be added to the SMS Admins local group on the provider server.

  • Collection class – Read, Read resource
  • Configuration policy class – Read
  • Query class – Read
  • Site class – Read.

NightWatchman Management Center Console service account

The service account for the NightWatchman Management Center Console service connects to the WMI namespace on the WakeUp server when requesting wake-ups (alarm clocks, maintenance windows and on demand wake-ups from the NightWatchman Management Center Console including Web WakeUp if installed). Therefore, to have the necessary WMI permissions, this service account must be one or more of the following:

  • A member of the Administrators local group on the WakeUp Server
  • Specified during WakeUp Server installation as the WakeUp Server's  WMIACCOUNT
  • A member of the AD Group which is specified during WakeUp Server installation as the WakeUp Server's  WMIACCOUNT

Administrators using remote WakeUp server Admin Consoles require remote access rights to the WMI namespace and DCOM Security, as a result administrators require one or more of the following:

  • Membership of the Administrators local group
  • WMIACCOUNT is specified as an AD group containing the administrator accounts or groups.

The service account for the NWM Console service connects to the WMI namespace on the WakeUp server when requesting wake-ups. Therefore, the service account requires one or more of the following: 

    • Membership in the Administrators local group
    • Is the same as the WMI account
    • Is a member of a group that is specified as the WMI account.

NWM Console service account will be added by the NightWatchman Management Center Installer to the N1E and WakeUp namespaces with the following permissions:

    • Execute Methods
    • Full Write
    • Enable Account
    • Remote Enable.