1.1 SLES 12 Support

This release adds patch support for SUSE Linux Enterprise Server 12.

To patch these endpoints, register your endpoints using YaST, register them with SUSE Customer Center , and then add your Customer Center credentials to the Subscription Service Settings.

1.1.1 SLES 12 Support Instructions

  1. Confirm that SLES12 agent systems are registered with SUSE Customer Center (SCC) Configuration via the following steps:

    1. On each system, launch YaST by selecting Applications > System Tools > YaST.

    2. Next select SUSE Customer Center Configuration under Support settings.

    3. If the system is currently registered with SCC, a The system is already registered message is displayed. Otherwise, enter the email address and Registration Code, which can be found by logging into and selecting the Subscriptions (or Systems) menu option.

      Figure 1-1 Registration Code

    4. Now confirm the agent system is listed under the Systems menu.

      Figure 1-2 Systems Menu

  2. Copy the system credentials by selecting the Details drop-down option:

    Figure 1-3 Detail Drop Down

    NOTE:The SCC credentials will also be stored on the agent systems in the following folder: /etc/zypp/credentials.d/

    1. Navigate to Credential Vault on Configuration page and Add or Edit SLES 12 credentials using the copied systems credentials from SUSE Customer Center.

      Figure 1-4 Edit Credentials

    2. If necessary, perform similar credential creation or modification for SLES fro\\\\11 using corresponding subscription credentials obtained through SUSE (prior to SCC – SUSE 12).

  3. Navigate to Subscription Service Settings page via Configuration > Subscription Service Settings.

    1. Select each of the corresponding credentials defined in the Credential Vault under the Patch Subscription Credentials section. Example:

      Figure 1-5 Patch Credentials

    2. Select Apply or OK button to commit the credentials per each distribution.

The patch subscription credentials are now set. Patch subscriptions and deployments can now be performed per all three agents.