If clients do not display in the NightWatchman Management Console, it is caused by reporting failures which will also impact policy actions – they may fail to be assigned or may not work as expected.

 To troubleshoot this issue, you can:

  1. Ensure the NightWatchman Agent Service is running on the client.
  2. Check the license details in the log after a failed service start
  3. Check to see if they are in the load table. If they are, you can eliminate client and Web service issues as likely culprits without having to look at log files. Run the following:

    SELECT * FROM tbNWM_Load_State WHERE MachinteNetBIOSName = 'machinename'


    and

    SELECT * FROM tbNWM_Load_Inventory WHERE MachineNetBIOSName = 'machinename'

    If the queries returns a value then the problem is in the batch jobs. If they don’t, then the problem is in getting data to the database, meaning either the Website has issues (less likely) or the client has issues getting to the website (more likely).

  4. Check to see if reporting is enabled on the client:

     HKLM\Software\1E\NightWatchman\Reporting=ON
  5. Ensure that the service URL is correctly set:

    HKLM\Software\1E\NightWatchman\Reporting\ServiceURL
  6. Check to see if clients have been marked as obsolete
  7. Ensure your firewall or other security applications are not blocking ports (HTTP 80 or HTTPS 443) that NightWatchman Management Center Server uses to communicate with its clients.
  8. If you are using FIPS encryption, ensure that it is enabled for all components – Nightwatchman Management Centre Server, WakeUp Server, 1E Agents etc

    HKLM\Software\NightWatchman\Reporting\UseFipsComplianceEncryption=1
  9. Check in SQL Management Studio that all 1E SQL agent jobs are running with success. If not, start it.
  10. Ensure that the AFWebservice is running in the IIS application pool. If you install the NightWatchman database on a different server, the computer account of the NightWatchman Management Center server would also be added as a user in the AgilityFrameworkReporting database. This is required to allow the AFWebService and ReportConsole Web applications, which both run under the Network Service security principal on the NightWatchman Management Center server, to access the AgilityFrameworkReporting database on the remote SQL server. Also need to check the permission on the database.
  11. Ensure that ASP.NET 4.5 properly configured on the IIS server

 For testing purposes only

You can execute the following command-line on the client to force it to send data:

C:\Program Files\1E\Agent\NightWatchman\nightwatchman.exe -reportnow=1

To verify that client has updated in the Agility Framework Reporting database:

  1. In SQL Server Management Studio, expand AgilityFrameworkReporting database.
  2. Right-click dbo.tbNWM_Load_Inventory table and select Select Top 1000 Rows. You can narrow down the search by adding a WHERE clause:

    Where MachineNetBIOSname like 'client_machine_names%'
  3. Logging – check the Nightwatchman Management Centre Server webservice.log located in C:\ProgramData\1E\NightWatchmanManagementCenter and the NightWatchman.log for an affected client machine located in C:\ProgramData\1E\NightWatchmanManagementCenter for further details.