Watchman Monitoring allows for the addition of script to the post-flight of the Monitoring Client installer for your subdomain. This could potentially include forced client settings and or the installation of an RMM agent. Your code will need to reside in a private repository with access permission provided to Watchman Monitoring.
Custom Post-flight Installer Scripting is available to subscribers with Custom Branding for their subscription.
What can be included?
You can include any additional installer(s) or preference setting that you would like set upon the system. The following is a list of what we deem acceptable inclusions for the post-flight:
Any defaults settings for the Watchman Monitoring Monitoring Client and or other applications.
Include your favorite screen sharing tool (TeamViewer QuickSupport, SplashTop, ScreenConnect, etc.) or RMM Agent (munki, Addigy, SolarWinds Mac-MSP, Filewave, JAMF Pro, etc.).
It is highly recommended that you install a package management tool as part of this process, and allow the package manager to handle the additional installation of your required tools and settings.
Bash or Python?
The scripting language you use really is your choice. The Monitoring Client post-flight scripts are written in Python, but we can easily call your preferred scripting environment.
Post-flight Build Inclusion
A post-flight here would apply to all installations.
A post-flight script here would apply to all enrollment code installations in addition to any post-flight scripts in the Main Installation.
A post-flight script here would apply to all auto-enrollment installations in addition to any post-flight scripts in the Main Installation.
A post-flight script here would apply to all group-specific installations in addition to any post-flight scripts in the Main Installation.