This article addresses the frequently asked questions for transitioning from Red Hat Satellite 5 to Red Hat Satellite 6.
- Is it an in-place upgrade or do I need to install Satellite 6 on a new server?
- Which versions of Satellite 5.x are supported for the transition?
- Which versions of RHEL will Satellite 5 and Satellite 6 support as client systems?
- Are disconnected Satellites supported for the transition?
- Give me the quick version, how will customers transition from Satellite 5 to 6?
- Where do I get more information?
Red Hat Satellite 6 (GA as of September 10, 2014) is the next major release of the Red Hat Satellite product family. Red Hat Satellite 5 will continue to be supported until its EOL (latest version being 5.7). A fully supported transition path including documentation and tooling is available. This FAQ aims to answer questions related to transitioning from Red Hat Satellite 5 to Satellite 6.
Q: Is it an in-place upgrade or do I need to install Satellite 6 on a new server?
A: The underlying technologies between Satellite 5 and 6 are significantly different, so the in-place upgrade process (such as for versions 4.x->5.x or 5.x->5.y) does not apply for version 5->6. Satellite 6 needs to be installed on a new server as part of the side-by-side transition process. Hence, we call this a transition process and not an upgrade process.
Q: Which versions of Satellite 5.x are supported for the transition?
A: The transition path begins with Satellite 5.6. So for customers running a previous version of Satellite 5, they will first need to upgrade to version 5.6 or 5.7.
- Upon future releases of Satellite 6.x (6.3, 6.4 etc.), Red Hat will also support those versions as a platform for moving to Satellite 6
NOTE: if you plan a more passive transition process the prior Satellite 5 version doesn't matter. A passive transition process is more of an adoption process, where legacy workloads remain on Satellite 5 and new workloads are created on Satellite 6, as a separate or parallel platform.
Q: Which versions of RHEL will Satellite 5 and Satellite 6 support as client systems?
|RHEL client system support||Red Hat Satellite 5||Red Hat Satellite 6|
|RHEL 7||Satellite 5.6 or 5.7 only||Yes|
|RHEL 6||Yes||RHEL 6.1+ only|
|RHEL 5||Yes||RHEL 5.7+ only|
- For supported combinations of Red Hat Enterprise Linux as the underlying OS for Red Hat Satellite, please see this Knowledgebase article: "What is the supportability matrix for Red Hat Satellite on RHEL?"
- For Red Hat Enterprise Linux lifecycle support, refer to this page.
Q: Give me the quick version, how will customers transition from Satellite 5 to 6?
- Obtain 1-year Transition Subscriptions. 
- Install Satellite 6, activate with a Manifest and sync RHEL content from CDN
- Learn and understand the basics of the new Satellite 6 product, including new concepts, such as environments.
- Back up the new Satellite 6 databases before using the tooling.
- As root on Satellite 5, run the exporter command line tool.
- Copy the resulting data onto Satellite 6
- As root on Satellite 6, run the importer command line tool. 
- Validate and test the resulting Satellite 6 system for end to end functionality and use-cases of importance to the customer.
 This landing page provides more details on the overall process, as well as steps to request Transition Subscriptions: Transitioning from Red Hat Satellite 5 to Satellite 6
 NOTE: since not all of the concepts can be translated between Satellite 5 and Satellite 6, some manual steps will also need to be taken to fully populate the newly installed Satellite 6 server.
Q: Are disconnected Satellites supported for the transition?
A: Yes, the transition tooling is designed such that disconnected mode is assumed, and neither Satellite 5 nor 6 can directly communicate with each other or the internet in general.
Q: Where do I get more information?
A: More information can be found here (more to come):
You can also contact Red Hat support.