The software described in this documentation is either no longer supported or is in extended support.
Oracle recommends that you upgrade to a current supported release.
- 10.4.1 Using Custom Information Keys
- 10.4.2 Defining Custom Information Keys Using the Spacewalk Web Interface
- 10.4.3 Defining Custom Information Keys Using spacecmd
- 10.4.4 Working with Configuration Channels Using the Spacewalk Web Interface
- 10.4.5 Working with Configuration Channels Using spacecmd
- 10.4.6 Subscribing Client Systems to Configuration Channels Using the Spacewalk Web Interface
- 10.4.7 Subscribing Client Systems to Configuration Channels Using spacecmd
- 10.4.8 Deploying Configuration Files to Client Systems Using the Spacewalk Web Interface
- 10.4.9 Deploying Configuration Files to Client Systems Using spacecmd
The client system must permit the Spacewalk server to deploy files, the activation key for the system must permit the provisioning add-on entitlement and configuration file deployment, and the provisioning entitlement must be enabled for the system. See Section 6.4, “Enabling Remote Configuration in a Kickstart Profile Using the Spacewalk Web Interface”, Section 6.6, “Enabling Remote Configuration Manually for Non-managed Client Systems”, and Chapter 3, Creating Activation Keys.
In the same way that a software channel in Spacewalk contains packages for installation on multiple client systems, a configuration channel contains files for configuring client systems. For example, the files might contain configuration information for services, applications, or users.