Migrating individual systems from SCC to RGS Customer Center is as easy as running the command below, with your specific registration codes that we sent over previously.
Table of Contents
Previously registered w/SUSE
If this system was previously registered with SUSE directly, we want to take a snapshot of the modules that are currently activated so they can be re-registered after.
- Get listing of activated products for later reactivation
-
Get listing of activated products that we can reactivate
ACTIVE_PRODUCTS=$(SUSEConnect -l | grep Activated -A1 | grep -i suseconnect | awk '{print $NF}') -
Verify products are captured. You should see a listing of products and version paths with your specific version and extensions / modules.
IMPORTANT: If the command below returns EMPTY, the previous modules were not captured. Please STOP and reach out to RGS Support for assistanceecho $ACTIVE_PRODUCTS
-
-
Disconnect system from SCC Portal and cleanup forcefully
SUSEConnect -d ; SUSEConnect --cleanup -
Connect to RGS Customer Center
SUSEConnect --url https://rgscc.ranchergovernment.com --write-config -r <REGCODE FROM RGS> -
Re-enable products from earlier
for PRODUCT in $ACTIVE_PRODUCTS; do SUSEConnect -p $PRODUCT ; done -
Refresh zypper to pull updated metadata
zypper ref -
Update your system
zypper up - You're done!
Fresh installations of SLES
-
Log into your system via SSH. Run the following command:
SUSEConnect --url https://rgscc.ranchergovernment.com --write-config -r <REGCODE FROM RGS> -
Refresh zypper to pull updated metadata
zypper ref -
Update your system
zypper up - You're done!
Fresh installations of SL Micro
-
Log into your system via SSH. Run the following command:
SUSEConnect --url https://rgscc.ranchergovernment.com --write-config -r <REGCODE FROM RGS>OR
transactional-update register --url https://rgscc.ranchergovernment.com --write-config -r <REGCODE FROM RGS> -
Update your system
transactional-update - You're done!
Comments
0 comments
Article is closed for comments.