Watchman Agent mass deployment best practices

Last updated:

When deploying Watchman Monitoring to a number of computers at a time, best practice is to install the Monitoring Client via a post-restore action. This ensures the installation timestamp is accurate, and the Client ID for the computer is unique.

If the client is installed, then copied into a master image, a single Client ID would be restored to every computer imaged from that master. With recent changes the Monitoring Client will see that it is running on a computer with a different serial than it previously had.  The Monitoring Client will rekey itself and report immediately with the new ID the first time.

Watchman Monitoring strongly recommends updating your base image with your Monitoring Client version 6.6.0 or greater.

Before Monitoring Client 6.6.0, all computers would report with a single ID. That ID would be marked for rekey, remaining computers would see this rekey status, and would report in with a new ID. The 2nd computer, which would have created “something changed” emails. The resulting computers didn’t show up as fast with this process.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.