theforeman · AkshayGadhaveRH · Sep 30, 2025 · Oct 7, 2025 · Oct 7, 2025 · Oct 14, 2025
diff --git a/guides/common/assembly_updating-satellite.adoc b/guides/common/assembly_updating-satellite.adoc
@@ -4,6 +4,8 @@ include::modules/proc_updating-server.adoc[]
 
 include::modules/proc_updating-disconnected-server.adoc[]
 
-include::modules/proc_updating-disconnected-server-on-EL9.adoc[leveloffset=+1]
+include::modules/proc_preparing-repos-for-export.adoc[leveloffset=+1]
+
+include::modules/proc_updating-the-disconnected-project.adoc[leveloffset=+1]
 
 include::modules/proc_updating-smart-proxy.adoc[]
diff --git a/guides/common/modules/con_updating-project-to-next-patch-version.adoc b/guides/common/modules/con_updating-project-to-next-patch-version.adoc
@@ -3,6 +3,7 @@
 [id="updating-project-to-next-patch-version_{context}"]
 = Updating {Project} to the next patch version
 
+[role="_abstract"]
 You can update your {ProjectServer} and {SmartProxyServer} to a new patch release version, such as from {ProjectVersion}.0 to {ProjectVersion}.1, by using the {Project} maintain tool.
 The patch releases are non-disruptive to your operating environment and often fast.
 

diff --git a/guides/common/modules/con_updating-project.adoc b/guides/common/modules/con_updating-project.adoc
@@ -3,6 +3,7 @@
 [id="updating-{project-context}"]
 = Updating {Project}
 
+[role="_abstract"]
 ifdef::orcharhino[]
 {Team} provides updates for your base operating system and backported bugfixes for {Project}.
 You can use this procedure to apply those updates.

diff --git a/..._updating-disconnected-server-on-EL9.adoc → ...ules/proc_preparing-repos-for-export.adoc b/..._updating-disconnected-server-on-EL9.adoc → ...ules/proc_preparing-repos-for-export.adoc
@@ -1,11 +1,12 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="Updating-Disconnected-{project-context}-on-EL9_{context}"]
-= Updating a disconnected {ProjectServer} on {RHEL} 9
+[id="preparing-repos-for-export_{context}"]
-[id="preparing-repos-for-export_{context}"]
+[id="preparing-the-repositories-for-export"]
-[id="preparing-repos-for-export_{context}"]
+[id="preparing-the-repositories-for-export"]
+= Preparing the repositories for export
 
-You can update your disconnected {Project} on {RHEL} 9 by synchronizing the required repositories on the connected {Project} and syncing the content to the disconnected {Project} using `reposync`.
+[role="_abstract"]
+Prepare the required repositories on the connected {Project} to export to the disconnected {Project}. 
 
-.Procedure on the connected {ProjectServer}
+.Procedure
 . Ensure that you have synchronized the following repositories in your connected {ProjectServer}:
 +
 * {RepoRHEL9BaseOS}
@@ -88,63 +89,3 @@ This downloads the contents of the repositories from the connected {ProjectServe
 # tar czf {Project}-repos.tgz -C ~ {Project}-repos
 ----
 . Use the generated `{Project}-repos.tgz` file to update in the disconnected {ProjectServer}.
-
-.Procedure on the disconnected {ProjectServer}
-. Copy the generated `{Project}-repos.tgz` file to your disconnected {ProjectServer}.
-. Extract the archive to anywhere accessible by the `root` user.
-In the following example `/root` is the extraction location.
-+
-[options="nowrap" subs="+quotes,verbatim,attributes"]
-----
-# tar zxf {Project}-repos.tgz -C /root
-----
-. Create a Yum configuration file under `/etc/yum.repos.d` with the following repository information:
-+
-[options="nowrap" subs="+quotes,verbatim,attributes"]
-----
-[{RepoRHEL9BaseOS}]
-name=Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)
-baseurl=file:///root/{Project}-repos/{RepoRHEL9BaseOS}
-enabled = 1
-
-[{RepoRHEL9AppStream}]
-name=Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)
-baseurl=file:///root/{Project}-repos/{RepoRHEL9AppStream}
-enabled = 1
-
-[{RepoRHEL9ServerSatelliteServerProjectVersion}]
-name={ProjectNameX} for RHEL 9 Server RPMs x86_64
-baseurl=file:///root/{Project}-repos/{RepoRHEL9ServerSatelliteServerProjectVersion}
-enabled = 1
-
-[{RepoRHEL9ServerSatelliteMaintenanceProjectVersion}]
-name={ProjectName} Maintenance 6 for RHEL 9 Server RPMs x86_64
-baseurl=file:///root/{Project}-repos/{RepoRHEL9ServerSatelliteMaintenanceProjectVersion}
-enabled = 1
-----
-. In the configuration file, replace the `/root/{Project}-repos` with the extracted location.
-. Use the health check option to determine if the system is ready for update.
-On first use of this command, `{foreman-maintain}` prompts you to enter the hammer admin user credentials and saves them in the `/etc/foreman-maintain/foreman-maintain-hammer.yml` file.
-+
-[options="nowrap" subs="+quotes,verbatim,attributes"]
-----
-# {foreman-maintain} update check \
---whitelist="check-upstream-repository,repositories-validate"
-----
-. Review the results and address any highlighted error conditions before performing the update.
-. Due to the lengthy update time, use a utility such as `tmux` to suspend and reattach a communication session.
-You can then check the update progress without staying connected to the command shell continuously.
-+
-If you lose connection to the command shell where the update command is running, you can see the logged messages in the `{installer-log-file}` file to check if the process completed successfully.
-. Perform the update:
-+
-[options="nowrap" subs="+quotes,verbatim,attributes"]
-----
-# {foreman-maintain} update run \
---whitelist="check-upstream-repository,repositories-setup,repositories-validate"
-----
-
-include::snip_steps-needs-reboot.adoc[]
-
-.Additional resources
-* To restore the backup of the {ProjectServer} or {SmartProxyServer}, see {AdministeringDocURL}Restoring_from_a_Full_Backup_admin[Restoring {ProjectServer} or {SmartProxyServer} from a Backup].
diff --git a/guides/common/modules/proc_updating-disconnected-server.adoc b/guides/common/modules/proc_updating-disconnected-server.adoc
@@ -3,7 +3,8 @@
 [id="Updating-Disconnected-{project-context}_{context}"]
 = Updating a disconnected {ProjectServer}
 
-Update your air-gapped {Project} setup where the connected {ProjectServer}, which synchronizes content from CDN, is air gapped from a disconnected {ProjectServer}, to the next patch version.
+[role="_abstract"]
+Update your air-gapped {Project} setup where the connected {ProjectServer}, which synchronizes content from CDN, is air-gapped from a disconnected {ProjectServer}, to the next patch version.
 You can follow this process to update the underlying operating system between minor release versions.
 
 .Prerequisites

diff --git a/guides/common/modules/proc_updating-foreman-server.adoc b/guides/common/modules/proc_updating-foreman-server.adoc
@@ -3,6 +3,7 @@
 [id="updating-{project-context}-server"]
 = Updating {ProjectServer}
 
+[role="_abstract"]
 You can update your {ProjectServer} to the latest packages published by {Team}.
 
 .Procedure

diff --git a/guides/common/modules/proc_updating-server.adoc b/guides/common/modules/proc_updating-server.adoc
@@ -3,6 +3,7 @@
 [id="Updating_Server_{context}"]
 = Updating {ProjectServer}
 
+[role="_abstract"]
 ifdef::satellite[]
 Update your connected {ProjectServer} to the next patch version.
 You can follow this process to update the underlying operating system between minor release versions.
@@ -47,8 +48,8 @@ If you lose connection to the command shell where the update command is running,
 ----
 # {foreman-maintain} update run
 ----
-
++
 include::snip_steps-needs-reboot.adoc[]
 
 .Additional resources
-* To restore the backup of the {ProjectServer} or {SmartProxyServer}, see {AdministeringDocURL}Restoring_from_a_Full_Backup_admin[Restoring {ProjectServer} or {SmartProxyServer} from a Backup]
+* {AdministeringDocURL}Restoring_from_a_Full_Backup_admin[Restoring {ProjectServer} or {SmartProxyServer} from a Backup]
diff --git a/guides/common/modules/proc_updating-smart-proxy-server.adoc b/guides/common/modules/proc_updating-smart-proxy-server.adoc
@@ -3,6 +3,7 @@
 [id="updating-{smart-proxy-context}-server"]
 = Updating {SmartProxyServer}
 
+[role="_abstract"]
 You can update your {SmartProxyServer} to the latest packages published by {Team}.
 
 ifdef::orcharhino[]

diff --git a/guides/common/modules/proc_updating-smart-proxy.adoc b/guides/common/modules/proc_updating-smart-proxy.adoc
@@ -3,6 +3,7 @@
 [id="Updating-Smart-Proxy_{context}"]
 = Updating {SmartProxyServer}
 
+[role="_abstract"]
 Update {SmartProxyServers} to the next patch version.
 
 .Procedure
@@ -38,5 +39,5 @@ endif::[]
 ----
 # {foreman-maintain} update run
 ----
-
++
 include::snip_steps-needs-reboot.adoc[]
diff --git a/guides/common/modules/proc_updating-the-disconnected-project.adoc b/guides/common/modules/proc_updating-the-disconnected-project.adoc
@@ -0,0 +1,67 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="Updating-the-Disconnected-{project-context}_{context}"]
+= Updating the disconnected {ProjectServer}
+
+[role="_abstract"]
+Create local repositories on your disconnected {Project} and update the disconnected {Project}.
+
+.Procedure
+. Copy the generated `{Project}-repos.tgz` file to your disconnected {ProjectServer}.
+. Extract the archive to anywhere accessible by the `root` user.
+In the following example `/root` is the extraction location.
++
+[options="nowrap" subs="+quotes,verbatim,attributes"]
+----
+# tar zxf {Project}-repos.tgz -C /root
+----
+. Create a Yum configuration file under `/etc/yum.repos.d` with the following repository information:
++
+[options="nowrap" subs="+quotes,verbatim,attributes"]
+----
+[{RepoRHEL9BaseOS}]
+name=Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)
+baseurl=file:///root/{Project}-repos/{RepoRHEL9BaseOS}
+enabled = 1
+
+[{RepoRHEL9AppStream}]
+name=Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)
+baseurl=file:///root/{Project}-repos/{RepoRHEL9AppStream}
+enabled = 1
+
+[{RepoRHEL9ServerSatelliteServerProjectVersion}]
+name={ProjectNameX} for RHEL 9 Server RPMs x86_64
+baseurl=file:///root/{Project}-repos/{RepoRHEL9ServerSatelliteServerProjectVersion}
+enabled = 1
+
+[{RepoRHEL9ServerSatelliteMaintenanceProjectVersion}]
+name={ProjectName} Maintenance 6 for RHEL 9 Server RPMs x86_64
+baseurl=file:///root/{Project}-repos/{RepoRHEL9ServerSatelliteMaintenanceProjectVersion}
+enabled = 1
+----
+. In the configuration file, replace the `/root/{Project}-repos` with the extracted location.
+. Use the health check option to determine if the system is ready for update.
+On first use of this command, `{foreman-maintain}` prompts you to enter the hammer admin user credentials and saves them in the `/etc/foreman-maintain/foreman-maintain-hammer.yml` file.
++
+[options="nowrap" subs="+quotes,verbatim,attributes"]
+----
+# {foreman-maintain} update check \
+--whitelist="check-upstream-repository,repositories-validate"
+----
+. Review the results and address any highlighted error conditions before performing the update.
+. Due to the lengthy update time, use a utility such as `tmux` to suspend and reattach a communication session.
+You can then check the update progress without staying connected to the command shell continuously.
++
+If you lose connection to the command shell where the update command is running, you can see the logged messages in the `{installer-log-file}` file to check if the process completed successfully.
+. Perform the update:
++
+[options="nowrap" subs="+quotes,verbatim,attributes"]
+----
+# {foreman-maintain} update run \
+--whitelist="check-upstream-repository,repositories-setup,repositories-validate"
+----
++
+include::snip_steps-needs-reboot.adoc[]
+
+.Additional resources
+* {AdministeringDocURL}Restoring_from_a_Full_Backup_admin[Restoring {ProjectServer} or {SmartProxyServer} from a Backup]