Options for deploying Watchman Monitoring

Last updated:

Watchman Monitoring offers a number of methods for deploying the Monitoring Client software. The right choice is the one which fits your workflow in the moment. The final result will be the same.

Available package formats

Group-Specific Installers (pkg, msi)

Group-specific installers are built and signed as new Groups are created. These pre-configured .pkg and .msi format installers have the Group name built in, which streamlines and ensures a uniform Group name.

Group-specific installers can be downloaded from the Installers button at the top of each Group page. These packages do not contain the payload directly, instead , they download the latest installer, and therefor require internet access.

Group-Specific Installers (pkg, msi)

The Mac formatted pkg works in both Installer.app and in a command-line environment such as /usr/bin/installer or Remote Desktop.

The Windows MSI can be distributed using a Group Policy.

Suggested use cases

  • Create a new Group and email the resulting pkg to an end user.
  • Use a Group specific installer to prevent re-entering a Group name on each computer in a given office.
  • Leave a copy of the Group-specific installer on the end user's file server for later use.

Stock Package (pkg, msi, rpm, deb)

Stock Package (pkg, msi, rpm, deb)

The stock installers are signed packages which allow a user to assign a Group name during installation. Entering an existing Group name will add this computer to the group, if there is no match in your Watchman Monitoring Dashboard a new Group will be created dynamically.

Groups can be merged or renamed in your Dashboard. Group names can also be changed in the PreferencePane, and the Dashboard will send you an alert that the Group has changed.

Suggested use cases:

  • Linking to your stock installer from your own website. (Read More)
  • Keep a copy on a thumb drive, for handy installation.

To ensure the most accurate reporting, Watchman Monitoring recommends replacing out of date installers at least quarterly.

Editable (Unsigned) Package for Use in Mass Deployment (zip)

Watchman Monitoring also provides an editable, bundle-format package. The package and related readme are available in as a .zip file on the Installers page on your Dashboard.

then  includes a ReadMe describing how to pre-set the Group and other default settings.

When installing the Monitoring Client using tools such as Deploy Studio, System Image Utility, or InstaDMG, adding the package as a post-restore action prevents undesirable "something changed" emails.

Prepare the bundle-installer to set the Group and install, even when internet access is not available:

  • Download the unsigned, bundle-style package
  • Unzip the contents.
  • Right-click the enclosed pkg and choose "View Package Contents"
  • Navigate to Contents/Resources/postflight file and make changes as directed.
  • Additional instructions are located in the included the .zip


Choosing Show Package Contents reveals a postflight script which can be edited and embedded as post-restore or first boot package in any deployment system. Read more about package customization.

No matter which deployment method you choose, Watchman Monitoring encourages all subscribers to re-download any offline installers as new releases are posted.

Editable packages are ideal for mass-deployments where changes to the defaults are required.

Enrollment Codes

Enrollment Codes

Watchman Monitoring features Enrollment Codes which can allow an end user to self-enroll a computer for Proactive Support.

Enrollment Codes are ideal for retail environments, and can be distributed to your end users via gift card, email, etc.

When a user redeems an Enrollment Code, the computer can be autmatically placed into a specific Group, and an expiration can be attached to the account.


Generate Enrollment Codes

Learn more about Enrollment Codes in this article.

Deployment Tools

Watchman Monitoring is compatible with many deployment tools for a quick and easy installation on multiple computers.

Installing the Monitoring Client via automated deployment or command line

See also: Watchman Agent mass deployment best practices

Apple Remote Desktop (Script)

Apple Remote Desktop (Script)

Additional Details

All of these methods can also be installed over any existing agent, helpful when auto-update has been disabled.

Your installer can be renamed as a part of your Custom Branding

Authentication is not required for downloading installer packages. Learn more

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


Please sign in to leave a comment.