To use NightWatchman's online status feature you will need a Tachyon server. For most organizations a simple Tachyon server installation will work well. Or if you are evaluating this feature in a lab you can certainly use a simple Tachyon server installation.
With Tachyon server and agents installed, you can integrate Tachyon with NightWatchman in order to show online status of NightWatchman clients.
Integrating Tachyon with NightWatchman Enterprise
- Using Notepad or a similar text editor:
- Browse to the
C:\Program Files (x86)\1E\NightWatchman Management Center\ConsoleServicefolder (This is the default path, yours may vary based on the install location of the Nightwatchman Management Center.)
- Open NWM.ServiceHost.exe.config
TachyonIntegrationEnabledand update its value to true:
TachyonAPIvalue to the Tachyon server URL that you defined earlier:
- Browse to the
- Using Services control panel (
services.msc), restart the NightWatchman service.
- Open the NightWatchman console:
- Select the Clients node.
- Drill down to one of the lowest clients group.
- The traffic light for each client should be red, yellow, gray, or green.
If you have any difficulties with the above, see the Tachyon integration troubleshooting page or the Tachyon documentation.
The NightWatchman console uses Tachyon to display traffic lights live status of its clients – indicating whether they are currently online or offline (or unknown). You can also check the status of groups within the NightWatchman client hierarchy.
The statuses are:
- Green – online
- Red – offline
- Yellow – computer is not a Tachyon client
- Gray – Tachyon integration is not enabled.
Thanks to Tachyon's ability to deliver near real-time client data, it can be particularly valuable to you when you are using WakeUp to wake clients for urgent maintenance, such as deploying a solution to a zero-day vulnerability.
You can also use Tachyon to optimize NightWatchman by using Tachyon Explorer to return live status on clients to check for:
- NightWatchman or WakeUp client logs which might indicate an issue
- Clients with pending reboots that have become pending in just the last few hours
- Clients that don't have appropriate wake-on-LAN settings.
Customizing the integration
NightWatchman's Tachyon integration is designed to be highly reactive and scalable. However, depending on the size or your organization and the capabilities of your server, you might like to increase or decrease Tachyon's responsiveness. In particular:
GroupHierarchyMaxComputersInList– the number of clients (default 1,000) listed in the console when you click a lowest-level group in the client location or organizational hierarchies
GroupHierarchyMaxComputersInProperties– the number of clients (default 1,000) Tachyon online/offline status is returned for when you check the properties of a group in the client location or organizational hierarchies. A larger value is appropriate if the groups are large but more queries will be done on the Tachyon database
MaxClientsForGetDevicesMatchingScopeTachyonCall– the number of clients (default 250) NightWatchman passes to Tachyon on each call to check online/offline status. Calls are made as quickly as Tachyon can respond.
TachyonIntegrationClientStatusCacheExpirySeconds – how long NightWatchman will retain Tachyon client status before it returns to Tachyon for updated status (default 30). A larger value reduces the SQL queries to Tachyon but a smaller value ensures the NightWatchman console reflects the current status sooner. A small value is especially desirable for demonstrations
You can review and change those values using SQL Server Management Studio:
- Connect Object Explorer to the server.
- Open Databases, AgilityFrameworkReorting, Tables.
- Right-click the
- Click Edit Top 200 Rows.
- Modify the values as necessary.
- Using the Services control panel icon (
services.msc), restart the NightWatchman Console service.
By default the Tachyon client will wait up to 15 seconds after a computer resumes from standby. During that period, Tachyon will indicate the computer is offline although it's actually online. This delay ensures that Windows has time to reestablish network connectivity. If this is a concern and you find that your computers reestablish network connectivity faster, you can reduce this delay:
- Edit the Tachyon.Agent.conf file on the client(s) in C:\Program Files\1E\Tachyon\Agent
Add a line such as "FastReconnectTimeInSeconds=10" (supported values are 5 to 60 seconds)
- Restart the 1E Tachyon Agent service