Hrm, I thought that on RHEL5 jabberpy gets picked up as a dependency... As far as your other questions go, use an activation key with the kickstart. osad ought to be started on boot once the kickstart is done and the system comes back up. Activation keys can subscribe systems to groups, software channels, and configuration channels. I'm not sure about the monitoring pieces, I haven't had enough time to play with that yet. Deploying managed files is a bit trickier. I've found that the Satellite 5.3 "Configuration File Deployment" option in activation keys isn't very useful for us. The reason is that some of my configuration files key off of the short system hostname (NETBIOS name), and unfortunately I can't seem to find a way to set that until a custom %post script, which runs AFTER the activation (which deploys config files). To work around that I turn off deployment and manually run 'rhncfg-client get' from my %post script. Jeffrey. P.S. As I've said before, I'm working with Satellite 5.3 so some things may be different. <div class="gmail_quote">On Thu, Feb 4, 2010 at 4:21 PM, Kennedy, Ryan <<a href="mailto:rkennedy@paml.com">rkennedy@paml.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div link="blue" vlink="purple" lang="EN-US"> <div> So here’s a question… I kickstarted a new system using a similar list of packages (to that listed by Jeffrey below) in my ks profile. They all installed but osad failed to start until I installed jabberpy (which is in the EPEL repo). Is there any way around that? Since I didn’t have a previous notion of that client it wasn’t subscribed to any software channels. Along those lines, when I ks a new system there are a number of things I want to do on all the systems in a particular configuration channel. E.g… - add the "monitoring" entitlement (management and provisioning are already added) - add location info blah etc. - subscribe to the CentOS_x86_64 software channel all 4 of its child channels - run "/etc/init.d/osad start" - subscribe system to a default configuration channel - join a default system group - deploy managed config files (e.g. /etc/ntp.conf) - configure scout monitoring for load, mem, and disk checks Obviously there are ways to script this with RHN commands, although I am not familiar enough to do that yet. But does the spacewalk UI provide some other means that I am not seeing for doing some of these things. Basically I am going to use this to roll-out/kickstart new Linux VMs and want to automate as much as possible with Spacewalk. </div></div></blockquote></div>