Earlier, you learned how to define some of the parameters that are used in the NightWatchman Management Center Reports and in Lab 9 you saw how the Savings reports use Power Behaviors to compare current behavior with previous behavior to determine savings. In this lab, you will explore some of the other key reports, including reports associated with the Hardware Utilization feature. Feel free to explore all the different reports available, as they all have value in managing your enterprise.

Objectives
In this lab, you will learn about the following

• How data is transferred from clients and processed into the database
• Using reports to understand the effectiveness of power management

• Understanding hardware utilization

Investigating Power-down and WakeUp Activity

In this exercise, you will examine the reports that identify power-down and WakeUp activity. These reports can be used to confirm that the solution is working as expected, and can be used to assist with problem diagnosis.

Expediting Processing of Reporting Data

You have already seen that NightWatchman queues data relating to power events and sends these periodically to the NightWatchman Management Center. Incoming data is processed by the SQL Agent batch jobs on the AgilityFrameworkReporting database server. In this task, you will follow the steps to ensure all queued data is sent up from the client, and that this is processed, so we can view the data in the reports.

1. To ensure all the data recorded by the NightWatchman client has been passed to the NightWatchman Management Center, run the following command from the NightWatchman Command Prompt on 1ETRNW71

"c:\Program Files\1E\NightWatchman\NightWatchman.exe" -reportnow=1

2. To ensure all data from the clients has been processed by NightWatchman Management Center, log on to 1ETRNAP and start SQL Server Management Studio
3. Expand the SQL Server Agent node and double-click the Job Activity Monitor node to open the Job Activity Monitor
4. In the Job Activity Monitor, select the 1E NightWatchman, Process load job. Right-click this job and select Start Job at Step…
5. When the Start Job on '1ETRNAP' dialog appears (with step 1 selected), click Start
6. The 1E NightWatchman, Process load job processes incoming data in the Load tables into the appropriate reporting tables
7. When the 1E NightWatchman, Process load job has completed, repeat the process to run the 1E NightWatchman, Process summaries job
8. The 1E NightWatchman, Process Summaries job aggregates data from the daily reporting tables to show weekly and monthly summaries of the data used in the reports
9. When the 1E NightWatchman, Process summaries job has finished, close the Job Activity Monitor

Viewing Power-down Activity

In this task, you will view the power-down activity generated when you worked through Ex 4 - NWM v7.3 - Using - Understanding the User Experience.

10. On 1ETRNAP, open the Reports Console in Internet Explorer (http://localhost/ReportConsole)
11. From the Reports Console home page, select Power Management from the list of Report Categories
12. Click Shutdowns report category from the Power Management list
13. Click the report named Successful to load the Successful Shutdowns report. By default, the last 7 days are defined in the BeginDate and End Date fields and the report loads using these values. To change the reporting period, select a new Begin Date or End Date and click Generate
Note that data for these reports is only kept for 90 days (as defined by the DailySummary_KeepDays setting in the tbNWM_Settings table in the AgilityFrameworkReporting database). Although you can select a Begin Date more than 90 days ago, you will only see data from the last 90 days.
14. The report shows Scheduled Power Downs (those initiated by NightWatchman) and User Power Downs (initiated by the user) for each day of the selected period, grouped by Department
15. To view the details of a particular row in this report, click the > button on the right of the row

Viewing Unsuccessful Power-downs

In this task, you will examine the failed shutdown actions attempted by NightWatchman earlier

16. Select Uncompleted from the list of reports
17. Set the Begin Date on this report to 90 days ago there will be some failures in there
If a power-down fails on any attempt but is successful at a retry of the same event, it is recorded as a success.
18. As with the Successful Shutdowns report, click on the > button to the right of the summarized row to view the details
Please note that it is possible that the backed up AFR database may not contain a shutdown failure, so it is possible that the report may not contain any results.
19. Observe the Failure Description in each case. This column will indicate the reason why the computer didn't shut down, including details of applications or processes that prevented it from shutting down

Identifying Computers with WakeUp Problems

In this task, you will look at a report that shows the 20 computers that have experienced the most failed wakeup attempts in the specified period. This report is useful for identifying computers that may have BIOS configuration or other issues.

20. On 1ETRNAP, return to the NightWatchman Enterprise Reports home page
21. Click on the Wakeups report category
22. Click on the Top 20 failing clients report in the WakeUp issues section
23. Adjust the Begin Date to include data from the last 90 days and click Generate
24. To examine the individual failed attempts for each machine returned in this report, click the > button to the right of the row

Understanding the Impact of Sleepless Processes

Sleepless client detection is a key feature of NightWatchman. Processes that are marked as 'sleepless' will prevent a computer going into a low power state because of an inactivity timer (i.e. Windows power setting). To understand how these behaviors are affecting your environment, you can run the Busy and sleepless processes report to identify the processes that are preventing optimal power savings during the day. You can then use this data to define sleepless processes to override, will ensure clients are successfully powered down by an inactivity timer even if there are busy processes running.

25. On 1ETRNAP, return to the Home page of the Report Console and select the Power Management Report Category
26. Scroll down and select the Sleepless Clients report category from the Power Management page
27. Select the Busy and sleepless processes report from the Sleepless clients page
28. Set the Begin Date to about three months ago, and click Generate
29. Note the Sleepless Processes that are listed, ordered by frequency of occurrence. To view specific machines that were running these processes, click the > button to the right of the row

Viewing Computer Reclaim

The Computer Reclaim feature is an enhancement of the Hardware Utilization feature that was introduced in NightWatchman Enterprise 6.5. This feature allows administrators to identify computers that are on but are not being used. When this feature is enabled in the NightWatchman Policy (General Settings), the NightWatchman client checks the state of the computer at a frequency defined by the Sample Interval setting (default 600 seconds) and aggregates the modal state for each period defined by the Aggregation interval (default 10 minutes).

In this exercise, you will view the report that identifies unused computers.

View the Computer Reclaim Reports

30. From the Report Console select the Computer Reclaim report category and then select the Unused computer counts by location, yearly report. The report shows the utilization data for the current year and is good for providing a high-level view of unused hardware
31. To report on a particular location, use the Location dropdown to select the tier level, then select the desired location from the secondary dropdown that appears to the right, Select 2018 from the year dropdown
32. The report includes a chart that summarizes used and unused PCs. Used PCs are further divided into desktops and laptops, whereas unused PCs are not
33. Further usage detail can be seen using the Unused and rarely used computer counts by location, weekly report. Return to the Computer Reclaim report category and select the Unused and rarely used computer counts by location, weekly report
34. In this report, you must select a week defined in the Period drop-down. Select a period 2 months ago to ensure we have some data from the restored database
35. Below the chart is a table that identifies the specific values for each day of the week. Click on the > button to the right of the day row to see detailed usage throughout that day. This view gives a granular breakdown of what PCs are doing at any specific hour of the day, which can be quite valuable in fine tuning power policies to further maximize savings

Viewing Power Optimization Reports

Power Optimization data helps you optimize the power related benefits of your battery-enabled devices. The Power optimization feature collects power related data from the operating system and collates it within the AFR database. The reports also capture data related to 'Connected Standby' or 'Modern Standby.'

View the Hardware Utilization Reports

36. From the Report Console select the Power Optimization report category and then select the Summary report. Change the start date to approximately 3 months ago
37. The report shows the machines in your environment that are battery powered, as well as details on battery usage
38. To report on a particular location, use the Location dropdown to select the tier level, then select the desired location from the secondary dropdown that appears to the right
39. Explore the other reports under the Power Optimization report category

Viewing Reboot Optimization Reports

Reboot Optimization helps you to minimize security issues by ensuring that security changes (such as security-related software updates) are effective as soon as possible. Historically, NightWatchman has helped you with shut downs, and thus reboots, by allowing open applications to be saved prior to shutdown. Reboot Optimization builds on that legacy by helping you to understand when your computers are rebooting, how commonly reboots are pending (needed but not done), and how long they are taking.

View the Hardware Utilization Reports

40. From the Report Console select the Reboot Optimization report category and then select the Summary report. Change the period to Last 3 months
41. The report shows information related to reboots in the enterprise, including Rebooted Clients per Day, Reboot Speed, Pending Reboots per Day, and How Long Reboots Pend
42. To report on a particular location, use the Location dropdown to select the tier level, then select the desired location from the secondary dropdown that appears to the right

Lab Summary

In this lab, you have learned to use some of the NightWatchman reports to determine the effectiveness of power management in your organization, identifying the cause of power-down failures and analyzing failed wakeups. In order to view the most recent data in the reports, you learned how to expedite the process of getting data from the client into the database tables used by the reports by forcing the client to send its data, then manually running the Process Load and Process Summaries batch jobs on the SQL server.