Hello, I've got a query about best practice for config management. We have several Configuration Channels, each with a bunch of files in. Machines are subscribed to appropriate channels based on role and distro. We want to push those files out daily to subscribed machines, replacing any that have been edited on-server. We currently achieve this with a bash script on the Uyuni vm, called by crontab overnight, using "spacecmd -y -- configchannel_forcedeploy channelname" This works fine, but I'm wondering if that's the best way, as it's configured and monitored only outside of the webui? Forcing a regular high state appears to push those files, plus updates the .repo files and generally getting things as Uyuni thinks they should be. The recurring schedule seems to be designed to do this. But I can't see a way to automatically set a recurring schedule? Whilst I can set one for existing machines using SSM, I can't see a way to add one via Activation Key nor automatically enroll all machines into setting a highstate once a day or so. How do others approach this? Is there a gui way, or should I stick with the spacecmd route? S