System information

Note
Not all of the concepts can be translated between Satellite 5 and 6. Some manual steps
are required to fully populate the newly installed Satellite 6 server.
Will t h e transition t o o ls wo rk with a discon n ected server?
Yes, the transition tools are designed such that a disconnected environment is assumed, and
neither Satellite 5 nor 6 can directly communicate with each other or the Internet in general.
Will t h e transition t o o ls t ran sitio n all d at a f ro m Satellite 5 t o Satellit e 6 ?
No. In some situations, Satellite 5 and Satellite 6 take different approaches to the tasks of
synchronizing and provisioning hosts, managing entitlements, and dealing with disconnected
environments. Some configuration, system, and host data is also created and stored differently.
Consequently, not all data can be successfully transitioned.
In Satellite 6, the following information cannot be transitioned:
Activation-keys that use "Red Hat default"
Anything history- or audit-related (events, oscap runs, and so on)
Anything monitoring-related
Configuration-channel ordering
Distribution-channel mapping
Kickstart data (other than snippets)
Organization entitlement-distribution (users need to create their own manifests)
Organization-trusts settings
Snapshots
Stored package-profiles
Custom system information, such as key/value pairs, system notes, and system properties in
general. The latter is completed when a system registers to Satellite 6 and connects to the
created profile.
User preferences
Can I ru n t h e tran sit ion t o o ls an d p ro cess mu ltip le times?
Yes, the transition tools are idempotent. You can reuse the tools to create Satellite 6 data and
preserve previous information. A small data file on the Satellite 6 server preserves the history of
previous runs and tracks what has already been imported.
⁠Chapt er 3. T ransit ioning from Sat ellit e 5 t o 6
19