The Checkmk Agent Bakery builds agent installers that already contain the agent rules, plug-ins, and updater settings selected for a folder or host. Baking a custom package after changing an agent rule gives the target system an installer whose package hash maps back to that exact configuration.
The bakery is available in Checkmk commercial editions from Setup → Agents → Windows, Linux, Solaris, AIX. Agent rules control the package contents, and the bakery creates separate package variants for the default configuration, selected folders, or specific hosts when those variants are actually used.
A baked package can contain scripts, credentials, certificates, or updater configuration. Keep package downloads on trusted transport, scope rules narrowly before baking, and avoid manual edits to files generated by the bakery on the target host because the next agent update can replace them.
Related: How to add a host in Checkmk
Related: How to register a Checkmk agent host
In Checkmk Community, the comparable agent menu opens static download pages instead of the Agent Bakery.
For a simple bakery test, Generic agent options → Allowed agent access via IP address (Linux, Windows) changes the allowed monitoring-server addresses in Linux and Windows agent packages.
For packages that should apply to future hosts in a folder, enable Bake a generic agent package for this folder in the folder properties. Checkmk treats that setting as folder-local and does not inherit it into subfolders.
If the package includes the Agent Updater, use Bake and sign agents and enter the signature-key passphrase when Checkmk prompts for it.
The Agent type column shows whether the package is vanilla, folder-based, or host-specific. The displayed hash identifies the baked package configuration.
$ cmk -Av web-01 Baking packages for targets web-01: web-01..linux_deb: baking...linux_rpm: baking...windows_msi: baking...linux_tgz: baking
Run cmk as the Checkmk site user. Omitting the host name bakes packages for all applicable hosts.