I just realised that the config-less fleetd agent does not support using Jamf's "Custom Settings" payload for setting the configuration. Orbit seems to iterate through the output of

profiles -C -o stdout-xml

, and looks for a

PayloadIdentifier

matching

com.fleetdm.fleetd.config

. With Jamf custom settings, this identifier is random, so it won't match (example here). Worth mentioning because, if I upload a completely custom profile, none of the settings configured are visible in the Jamf Console, which can be helpful for troubleshooting. Reading the plist at

/Library/Managed Preferences/com.fleetdm.fleetd.config.plist

feels like it might be a bit more universal, if at all possible