Integration with Tachyon to support NightWatchman Online Status

The NightWatchman Online Status feature is described in Enabling Online Status using Tachyon integration. You must have:

  1. Tachyon Platform 5.0
  2. 1E Client 5.0, with Tachyon client enabled

Please refer to Tachyon 5.0 - Implementing Tachyon for how to install Tachyon Platform, and 1E Client 5.0 - Implementing 1E Client for how to install the 1E Client with Tachyon and other client features enabled.

1E Client also includes WakeUp client - you only need to enable WakeUp client if you are using WakeUp features with NightWatchman.

NightWatchman Agent is available as a separate installer. You can use 1E Client Deployment Assistant 1.4.100 or 1.4.200 to deploy NightWatchman Agent 7.2.500 and 1E Client 5.0 via Configuration Manager.

Integration with ActiveEfficiency to support Nomad integration with WakeUp

The feature Integrating Nomad with WakeUp is available only with Nomad 7.0.100 and 7.0.2100, using ActiveEfficiency. It is not available with Nomad 7.1 which no longer uses ActiveEfficiency. A revised feature is planned for a future version of Nomad.

You must have:

  1. ActiveEfficiency Server 1.10 or later installed and available on the network. Please refer to ActiveEfficiency 1.10 documentation
  2. Microsoft Message Queuing (MSMQ) enabled on the ActiveEfficiency Sever and the server where NightWatchman Management Center will be installed
  3. Enable firewall ports on the server OS
  4. 1E Client 5.0 with Nomad and WakeUp clients enabled.

ActiveEfficiency Server 1.10 is available free from 1E and its installer can be downloaded from the 1E Support Portal. 

Alternatively, ActiveEfficiency Server 1.10 can be optionally installed by Tachyon Setup if you have a Tachyon license for Tachyon Platform 5.0.

1E Client also includes Nomad client - you will need to enable Nomad and WakeUp clients if you are using Nomad integration with WakeUp. NightWatchman Agent is available as a separate installer.

If you are using the Nomad integration with WakeUp feature, you can use 1E Client Deployment Assistant 1.4.100 or 1.4.200 to deploy NightWatchman Agent 7.2.500 and 1E Client 5.0 (Nomad and WakeUp) via Configuration Manager.

Accounts needed to install NightWatchman Management Center

To install NightWatchman Management Center, you need:

  1. Installer account:
    • Must be domain user account 
    • Must have local admin rights on the server where NightWatchman Management Center is being installed
    • Must have sysadmin rights on the SQL Server instance unless the AgilityFrameworkReporting database and SQL Server Agent jobs are pre-created by a DB administrator. This right can be temporary.
    • Will be set as the primary NightWatchman Console administrator
  2. Console service account:
    • Must be a domain account configured where the password does not expire and the user can never change the password
    • Must have local admin rights on the server where NightWatchman Management Center is being installed
    • Will be granted the following during installation:
      • Log on as service and Access the computer from the network privileges on the local machine
      • added to the public role on the AgilityFrameworkReporting database
    • Will require rights on WakeUp Server WMI namespaces on each WakeUp Server, as described below.
  3. User accounts or AD Groups for use as administrators in the NightWatchman Management Center Console. 

If you are using the import Wizard to populate hierarchies, you:

  • are typically the person who installed the NightWatchman Management Center components
  • Will already have db owner rights on the AgilityFrameworkReporting database
  • are either:
    • either a sysadmin on the SQL Server instance
    • or have been added to the db_NWMConsoleImportWizard database role on the AgilityFrameworkReporting database, that is created when the Import Wizard is installed

Any user or group that needs to use the Import Wizard must:

  • be a member of the db_NWMConsoleImportWizard database role
  • have a login on the SQL Server instance that must be added to the Users of the AgilityFrameworkReporting database
  • have NTFS permissions to modify the directory for the Import Wizard log file.

member of the db_NWMConsoleImportWizard database role

On this page:

Additional steps when installing NightWatchman Management Center on a distributed environment

If you are installing NightWatchman Management Center across multiple servers, install the database first – it can be done remotely from a server where one or more of the other components are installed.

If you are performing a clean NightWatchman Management Center installation or are upgrading NightWatchman Management Center and all the WakeUp Server components, permissions for the service account are set automatically as part of the installation process. The NightWatchman Console administrator account (used to define primary NightWatchman Console administrators) can be a domain user or group account.

If you are upgrading NightWatchman Management Center, have legacy WakeUp Servers or intend to use the NightWatchman console to implement remote wake-ups (which is done after installing the WakeUp Server):

  • Add the Console service account to the N1E/WakeUp namespace and grant the following permissions:
    • Execute Methods
    • Full Write
    • Enable Account
    • Remote Enable

To set permissions:

    1. Run the WMI MMC (wmimgmt.msc) plug-in on the WakeUp Server.
    2. Right-click the root node and select Properties.
    3. In the WMI Control (Local) Properties dialog, select the Security tab.
    4. Navigate to the N1E/WakeUp node and click the Security button. 
    5. In the Security for ROOT\N1E\WakeUp dialog, add the console service account and check the permissions listed above.

Accounts needed to install the WakeUp Server

To install the WakeUp Server, you will need:

  1. Installation account:
    • Must be domain user account 
    • Must have local admin rights on the server where WakeUp Server is being installed
    • Must have full Administrator rights in Configuration Manager Administrators Console. These rights can be temporary.
    • Should be an administrator in the NightWatchman Management console with a minimum of View and Edit rights for WakeUp Servers, to allow it to edit the priority of the WakeUp Servers and their subnets or IP ranges
  2. WakeUp Server service account:

    By default, the WakeUp Server service account is Local System which automatically has the necessary WMI rights to query Configuration Manager. No preparation is required if the SMS Provider role is on the Configuration Manager site server.

    If the SMS Provider role is remote to the site server, or there are multiple SMS Provider servers, then the following apply:

    The WakeUp Server installation account must have:

    • Full admin rights in the Configuration Manager Administrators Console
    • Sysadmin rights to the SQL Server instance used by the Configuration Manager SQL database

    The WakeUp Server service must use a domain account or Network Service account instead of the default Local System account. This service account must have the following:

    • Have Log on as service rights on the site server.
    • Be a member of the local administrators group on the 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 DATAFILESDIRSPOOLDIR ,WUSPOOLDIR ,HEALTHSTATUSDIR, if these folders are located anywhere other than LOGPATH folder.
    • 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>
      • root\N1E
    • The following Configuration Manager class security rights, as relevant for your version of Configuration Manager. 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.

      • Application
      • Boundaries
      • Boundary Group
      • Configuration policy
      • Package
      • Query
      • Site
      • Software Updates
      • Read
      • Collection
      • Read, Read resource
  3. Details of:

    • The Console service account used by NightWatchman Management Center
    • Or an AD group containing this service account, plus any WakeUp Admin Console operator accounts
    • This account or AD Group is specified during WakeUp Server installation in the NightWatchman Management Center Configuration screen, or as the WakeUp Server installation property WMIACCOUNT for a command-line installation

      • This can be a domain account or AD group. The AD group must be Universal if implemented in a multi-domain environment
      • Used for any users who need to connect the WakeUp Server WMI namespaces called N1E and N1E\WakeUp who do not already have local administrator rights on the WakeUp Server server. Examples are:
        • the NightWatchman Management Center Console service account. The Console service connects to this WMI namespace when sending wake ups (alarm clocks, maintenance windows and on-demand wake ups)
        • any users who need to use the WakeUp Admin Console to administer the WakeUp Server either locally or remotely
      • Recommended, you should specify an AD group that contains the Console service account and users accounts for WakeUp operators
      • Alternatively, you can simply specify the Console service account, and then later manually configure WMI rights for WakeUp operators, or allow operators to have local administrator rights on each WakeUp server
      • If you are upgrading and you specify the Console service account then you must ensure the NightWatchman Management Center Console service is restarted for these permissions to take effect.

      The WakeUp Server installation grants the following rights on the N1E and N1E\WakeUp namespaces:

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

Accounts needed to install Web WakeUp

To install Web WakeUp, you will need:

  1. Installation account:
    • Must be domain user account with local admin rights on the server where Web WakeUp is being installed
  2. Application pool account:
    • Only if the Web WakeUp website is running on a different server to the NightWatchman Management Console service, then you must configure the Web WakeUp Application Pool to use Network Service or a domain account
  3. 1E Agent 7.0 or 1E Client 4.1 or later (with WakeUp client enabled):
    • Must be installed on target computers if you want to wake them with Web WakeUp

Accounts needed to install the 1E NightWatchman Agent and 1E Client

To install the 1E NightWatchman Agent and 1E Client, you will need:

  1. Installation account:
    • Must be domain user account 
    • Must have local admin rights on each computer where the Agent and Client are being installed

For details on installing the 1E NightWatchman Agent, please refer to Installing the 1E NightWatchman Agent for Windows.

For details on installing the 1E Client with the WakeUp module enabled, please refer to 1E Client 4.1 - Deploying 1E Client on Windows: WakeUp.

WakeUp Servers also require the 1E Client to be installed with its WakeUp module enabled. The WakeUp Server must be installed first. If the 1E Client is installed first then the WakeUp Server installer only allows only the Administration Console installation option, and not WakeUp Server.

Accounts needed to install Enterprise View

To install Enterprise View, you will need:

  1. Installation account:
    • Must be domain user account 
    • Must have local admin rights on the server where Enterprise View is being installed
    • Must have sysadmin rights on the SQL Server instance unless the EnterpriseView database is pre-created by a DB administrator. This right can be temporary.


1E NightWatchman Agent and 1E WakeUp client

For NightWatchman Enterprise 7.2.500 and later, the legacy 1E Agent has been split into 1E NightWatchman Agent and 1E WakeUp client module of the 1E Client.

UDP 1776Inbound and OutboundCommunication with 1E WakeUp client and magic packets. 
TCP 80 (HTTP)OutboundCommunication with the NightWatchman Web service. 
TCP 80 (HTTP)OutboundCommunication with the NightWatchman Management Center. 
  • RPC/WMI with admin rights is required between 1E NightWatchman Agent (NWM) when using a remote NightWatchman.exe command-line
  • Incoming Internet Control Message protocol (ICMP) must be whitelisted on routers. It is used by the 1E WakeUp Server to discover 1E WakeUp clients.

The 1E WakeUp client and 1E NightWatchman Agent can each use both HTTP and HTTPS protocols, configurable during installation using command-line installer properties, and after installation by changing registry values. YOu can set values so tha tthe client agents communicate with the NightWatchman Management Center Web Service using the following protocols and security levels in the following order:

  1. HTTP.
  2. HTTPS without certificate.
  3. HTTPS using certificate subject match.
  4. HTTPS using certificate issuer match.


ActiveEfficiency is required only for the NightWatchmand catalog update service, which is not used by NightWatchman 7.2.500 and later.

TCP 135 (RPC)Between NightWatchmand and ActiveEfficiency serversCommunication with the queue managers. A dynamic port typically assigned by remote procedure calls (RPC) for handshaking with an independent client or with an RPC server for the message queuing server to determine the fixed ports. 
TCP 1801 (MSMQ)Between NightWatchmand and ActiveEfficiency serversCommunication with the queue managers. 

NightWatchman admin console

TCP 8732 (SMB)OutboundCommunication with the NightWatchman console service. 

NightWatchman console service

TCP 1443 (ADO .NET)OutboundCommunication with the NightWatchman (AFR) database. 
TCP 135 (RPC)OutboundCommunication with the ActiveEfficiency server. 

Import wizard

TCP 1443 (ADO .NET)OutboundCommunication with the NightWatchman (AFR) database. 

Reporting console

TCP 80 (HTTP)InboundCommunication with the NightWatchman Reporting Website. 
TCP 1443 (ADO .NET)OutboundCommunication with the NightWatchman (AFR) database. 

NightWatchman AFWebService website

TCP 80 (HTTP)InboundCommunication with the NightWatchman and WakeUp 1E WakeUp client and from WakeUp Server for registration, boundary maintenance and statistics reportingCommunication with the database. 
TCP 8732InboundCommunication wth the Import wizard and NightWatchman Admin console. 
TCP 8750InboundCommunication with Web WakeUp. 
TCP 1443 (ADO .NET)OutboundCommunication with the NightWatchman (AFR) database. 

Web Wakeup

TCP 8750OutboundCommunication with the NightWatchman Web service. 

WakeUp Server service

The WakeUp Server also has an installation of a WakeUp client and should therefore included their communications.

TCP 443 (HTTPS)OutboundCommunication with the NightWatchman Web service. 
TCP 1777InboundCommunication with 1E WakeUp clients. 
TCP 1776OutboundCommunication with 1E WakeUp clients. 
  • IPv4 network is necessary
  • RPC/WMI incoming from the NightWatchman Management Center Console service, any remote WakeUp Server consoles, any SCCM Console WakeUp extensions. Potentially used by custom WakeUp applications, however Web WakeUp is recommended instead for custom wakeup applications)
  • Internet Control Message protocol (ICMP) must be whitelisted on routers. It is used by the WakeUp server to discover 1E WakeUp clients (WakeUp).

Things to bear in mind

  • RPC/WMI incoming from the NightWatchman Management Center server and any remote consoles.
  • Incoming Internet Control Message protocol (ICMP) must be whitelisted on routers. It is used by the WakeUp server to discover agents. 
  • Port 135 is a dynamic port typically assigned by remote procedure calls (RPC) for handshaking with an independent client or with an RPC server for the message queuing server to determine the fixed ports.
  • IPv4 network is necessary

Preparing a server for web applications

NightWatchman Management Center deploys Web applications which are built on .NET (Report console and Web service). We recommend preparing the Web server by installing the runtime libraries for these applications as follows:

  1. Web server (IIS) role with default role services (which should include Windows authentication and ASP.NET role services).
  2. Application server role with .NET 4.5 and HTTP Activation role services.
  3. .NET 4.5 or later, ensuring that the OS specific ASP.NET is installed and enabled.

If these runtime libraries are installed in a different order, or other applications hosted on the same Web server have modified the default IIS ASP.NET settings, it may be necessary to re-register the ASP.NET 4.5 runtime with IIS prior to running the NightWatchman Management Center installer. You can do this with (we assume you are using the default paths):

  • On 32-bit systems: C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -iru
  • On 64-bit systems: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
It is important to specify the -iru switch to avoid causing problems with other web applications which are running under .NET 2.0.

General security measures

To comply with security certification criteria, we recommend the following measures for our products on your production environment:

  1. Folders and user data – restrict the \Program Files\1E folder to administrators to prevent unauthorized modification to configuration files
  2. Secure 1E product communications – when using products that make use of a centralized web component, restrict access to the configuration files and XML transforms as well as any spooler directories running on the clients. Additionally, use HTTPS communications between the centralized web component and its local agents. The NightWatchman Management Center and associated components can be configured for FIPS compliance.

    This property must be the same value for the NightWatchman Management Center, WakeUp Server, 1E NightWatchman Agents and 1E Clients.
  3. Secure operational environments  – secure networks running our products by preventing magic packets from outside the enterprise network boundary from being routed to machines inside the network by configuring network routers/firewalls boundary devices to prevent magic packets routing.
  4. Restrict physical access to servers – restrict access to these devices to authorized administrators only.
  5. Secure 1E administration consoles – install 1E administration consoles on a secure environment and follow best practices such as changing administrative passwords on a regular basis.

Guidelines for large environments

NightWatchman deployments range from 500 to 300,000 seats and are supported by a single management service and is highly scalable. For customers at the upper end of this range (100,000+), these guidelines ensure optimal performance.

Performance is difficult to predict and is affected by many factors such as server hardware, disk configuration, network bandwidth, etc. Customers with similar numbers of clients can experience different performance. Our scalability testing is run against simulated activity from 300,000 computers over two years and is executed on mid-range enterprise hardware.

Server specifications are typically: 8 core machine, 12-16 GB RAM, 5-6 SAS disks in 2-3 sets of RAID 0, gigabit Ethernet

Data retention

If you have particular requirements or concerns about your deployment, contact 1E for further information and assistance. When you install NightWatchman Management Center, you will be asked approximate size of your environment (number of clients). This figure is used to configure how often agents report power data and request policies as well as the frequency and workload size of the batch jobs. Make sure you select the most appropriate option for your environment.

As a general guideline, assuming all features are being used with their default configuration, the database storage required after a year is approximately 1MB per client. For each machine being managed, NightWatchman stores detailed power consumption data, as well as aggregated data (for reporting purposes). Data is aggregated by day, month and year. To help keep the database size down, each of these data stores is periodically trimmed. For large (100,000+ seats) deployments, we recommend changing the default retention values to:

Table and Configuration Setting (in tbNWM_Settings)Setting nameDefaultSuggested
Detailed consumption (tbNWM_Report_Consumption)ReportConsumption_KeepDays9015
Aggregated daily (tbNWM_Report_Consumption_Daily)DailySummary_KeepDays9030
Aggregated monthly (tbNWM_Report_Consumption_Monthly)MonthlySummary_KeepDays731366 (1 year)
Aggregated yearly (tbNWM_Report_Consumption_Yearly)YearlySummary_KeepDays36531826 (5 years)

Increase ReportConsumption_KeepDays if you are not yet certain how you wish to compare ongoing energy, cost and emission savings with previous periods in different parts of the organisation. The raw consumption table (tbNWM_Report_Consumption) is used when creating power behaviours and by the NightWatchman analysis reports wizard.

A power behavior is a snapshot of how a specific group of machines behaved over a specific period of time. Typically, you create a power behaviour to act as a baseline in order to calculate ongoing savings for that group of machines. Increasing the number of days kept allows you to delay the choice of which groups to analyse. However, it is good practice to decide early on how many days are kept and use this as a deadline for the baseline of your power savings project. For more information about power savings projects, see Using a NightWatchman baseline to identify power savings.

Tariffs and hardware power consumption values do not affect power behaviors but do affect energy, cost and emission reports, and aspects of the reports produced by the NightWatchman analysis reports wizard. It can take time for these variables to be finalized, at which point reports can be produced for different periods and compared.


Almost all NightWatchman Management Center reports (particularly those related to energy, cost and emissions) are run against aggregated data tables (see data retention). Where possible, we recommend running reports which use monthly/yearly data (rather than daily data) – this will not provide as much detail in the report itself, but will give better performance and should be sufficient for most data analysis.

Batch jobs

Be aware that system performance is impacted while the batch jobs are running, so allow for this. Batch jobs can be monitored using Operations reports from NightWatchman Report Console. If they are significantly impairing performance, they can be reconfigured to run less frequently and at more convenient times.

SQL Server

SQL Server offers enormous scope for configuration. We pre-configure our database based on the type of environment you select during installation; other configuration options are better suited to per-installation tuning. Specifically, you may wish to monitor database growth rates and adjust them accordingly. There is also potential to use file groups to improve performance. 

Hardware configuration

ProcessorNightWatchman server-based components have greater I/O than CPU needs; that is to say that a server's disks are more likely to become a performance-limiting factor than its processors. Configuration options such as HTTPS and SQL Server processor affinity can affect this, so for large-scale deployments, we recommend a quad-core server. However, an eight core server is preferable.
DisksDisks are a very important consideration in achieving consistently high system performance. Where possible, we recommend the use of enterprise-class disks (SAS, 10-15k RPM) supported by a hardware RAID controller. To make best use of disk resources, it is common to place SQL Server data, log and temporary files on different disks to maximize throughput. Contact 1E for more information. It is also worth mentioning that disk space can be consumed very quickly in a large deployment. A database supporting 100,000 clients will grow to several hundreds of gigabytes of disk space, therefore proactive monitoring and adjustments to data retention settings is advised.
RAMFor large-scale deployments, we strongly recommend use of 64-bit operating and SQL Server systems, preferably using the most recent Microsoft OS and SQL versions. 32-bit architectures have inherent memory limitations and later Microsoft platform versions continue to be optimized for performance. We recommend a minimum of 16GB of RAM for hosting SQL Server in a large NightWatchman deployment – typically most of this memory will be required for the SQL Server caching subsystems.
NetworkEven with hundreds of thousands of computers reporting, a NightWatchman deployment typically uses very little network bandwidth. During intensive scalability testing, we see send/receive peaks of no more than 2-3 megabytes per second (20mbps). This kind of throughput can be handled comfortably by gigabit-enabled networking hardware.
Virtualized HardwareFor large-scale deployments, we recommend physical, rather than virtualized hardware where possible, especially for the database server. If you have a specific requirement to support a large-scale virtualized deployment we would recommend use of a bare-metal or native type hypervisor.

Scaling-up versus scaling-out

NightWatchman Management Center Web and database components can be deployed across multiple servers to help distribute workload. Although this can increase administrative complexity, using separate database and web-servers (scaling-out) can dramatically improve performance.

However, consider this option only if you are unable to achieve acceptable performance with a single server. Additional hardware, especially disk resources, can help improve the performance of a single server (scaling-up).

Client hardware requirements

To utilize Wake-On-LAN (WoL) technology you need all of the following hardware configurations:

Network card - a network card which can support Wake-On-LAN. Your network card vendor can tell you if your network adapter supports Wake-On-LAN. If it does, it must be configured to enable remote wake up. Some adapter drivers are disabled by default within the operating system.

System BIOS - Wake-On-LAN must be enabled in the system BIOS. This option can usually be found in the Boot menu of the BIOS configuration program.  Some BIOS have a 'Maximum Power Savings' or 'Low Power S5' option, which should be disabled in order to allow some power to the network card.

Power management - APM or ACPI should be enabled, otherwise the user of the machine should ensure that it is powered off by hitting the off button after shutdown.

A quick way to tell if a system is Wake-On-LAN ready is to power down the system then look at the network adapter display LED's. If the lights are still on, then chances are that the system is OK.  Windows must have been powered down gracefully in order for it to prepare the network card.

1E also provides a diagnostic tool called Magic Test that determines if a machine can react to a magic packet wake up. Download Magic Test and other free tools from 1E’s Free Tools page.

Please contact 1E if you require guidance with WoL configuration on Windows operating systems and enterprise vendor hardware including Dell, HP and Lenovo computers.

Sizing and deployment considerations

For a single-server NightWatchman deployment:

Number of machines5,00025,00050,000100,000
Benchmark configuration
Number of clients polling and posting messages per hour5,00012,50025,00050,000
Messages per batch/client12151518
Number clients to be deployed concurrently2,5002,5005,0005,000
NightWatchman server
CPU cores1123
SQL Server instance max memory2 GB2 GB4 GB4 GB
Database connection max pool size10151520
Total disk space required for databases6.5 GB30 GB55.5 GB111 GB
SQL Server HDD requirements
NightWatchman database MDF5 GB24 GB45 GB90 GB
NightWatchman database LDF1 GB5 GB9 GB18 GB
TempDB MDF100 MB500 MB1 GB2 GB
TempDB LDF40 MB200 MB400 MB800 MB
For a distributed Nightwatchman deployment:

Number of machines50,000200,000500,000
Benchmark configuration
Number of clients polling and posting messages per hour25,000100,000250,000
Messages per batch/client151818
Number clients to be deployed concurrently5,0005,0005,000
NightWatchman server
CPU cores124
Database server
CPU cores124
RAM810 GB12 GB
SQL Server instance max memory4 GB6 GB8 GB
Database connection max pool size154070
Total disk space required for databases55.5 GB222 GB554 GB
SQL Server HDD requirements
NightWatchman database MDF45 GB180 GB450 GB
NightWatchman database LDF9 GB36 GB90 GB
TempDB LDF400 MB2 GB4 GB
For the WakeUp servers:

Number of machines5,00025,00050,000100,000200,000500,000
Number of WakeUp servers1112410
Wakeup server
CPU cores222222
Time to wake-up (approximate)5 mins10 mins15 mins15 mins15 mins15 mins

Benchmarking criteria

  • Benchmarked against Windows Server 2012 R2 Hyper-V infrastructure, with database and application server components setup on separate VMs
  • CPU (NWM Server) - Hyper-V host CPU configuration - 2x Intel Xeon CPU E5-2407 v2 @ 2.40GHz, 10M Cache, 4C, Max Mem 1333MHz
  • CPU (WakeUp Server)  - Hyper-V host CPU configuration - Intel Xeon Processor E5-2620 v3 @ 2.40GHz, 15M Cache, 6C/12T, Max Mem 1833MHz
  • All VMs connected over a 1Gbps link through a 1Gbps physical switch
  • Database storage – Samsung 850 EVO solid state drives attached locally to the Hyper-V host, with up to 98k/90k IOPS (4K random read/write QD32), and MDF, LDF and TempDB on separate SSDs.


  • Servers can be deployed either on physical or virtual machines. For deployment on a virtual machine, assign the CPU cores at 100% virtual machine reserve
  • NightWatchman server:
    • based on the numbers of clients machine, tune the Max Pool Size database connection parameter in C:\Program Files (x86)\1E\NightWatchman Management Center\WebService\Web.config
    • install no more that 2,500 new clients concurrently in environments up to 25,000 machines
    • install no more that 5,000 new clients concurrently in environments with 50,000 machines or more
  • NightWatchman database server:
    • deploy data, logs and TempDB on separate physical disks
    • configure SQL Server with maximum server memory limit and not at the defaults to consume unlimited memory
    • 4GB RAM should be added for the operating system on top of SQL Server instance RAM requirements
  • WakeUp Server
    • have separate Wakeup servers for every 50,000 clients