SUSE Support

Here When You Need Us

A registered client system disappeared from SUSE Manager

This document (7012170) is provided subject to the disclaimer at the end of this document.


SUSE Manager 3
SUSE Manager 2.1


A client system disappeared from the list of the registered systems in SUSE Manager (i.e. it is not longer registered) after the registration of another client. Sometimes the behaviour does not imply the "original" system being removed, but rather the "newer" system simply not being added to SUSE Manager.

Typically this is a problem when working with clones from a template within a virtualization environment (such as VMWare).


First of all it is necessary to find out the client system which has the same Novell Customer Center (NCC) credentials of the disappeared one. For information about the NCC see below NOTE (*).

On SLES 11, NCC credentials are saved in file "/etc/zypp/credentials.d/NCCcredentials". See the example below:

# cat /etc/zypp/credentials.d/NCCcredentials

For SLES 12 the same file exists in the same path with the name SCCcredentials.

On SLES 10 systems, NCC credentials are saved in the files /etc/zmd/deviceid and /etc/zmd/secret.
Please note that these files might still exist in a SLES 11 system (specially, but not only, if it was migrated from SLES 10).

Once the client system with the duplicated NCC credentials is found, make the following steps for fixing the issue:
  1. Remove the client systems in SUSE Manager using the web interface.
  2. Run "mgr-ncc-sync" or "mgr-sync refresh" on the SUSE Manager server from command line.
  3. On SLES 11 client systems, move "/etc/zypp/credentials.d/NCCcredentials", "/var/cache/SuseRegister/lastzmdconfig.cache" and "/etc/sysconfig/rhn/systemid" to "/tmp", or simply delete them (on SLES 10 client systems, remove /etc/zmd/deviceid and /etc/zmd/secret, then restart zmd).
  4. On SLES 11, check if /etc/zmd/deviceid and /etc/zmd/secret exist and delete them anyway, even if those files are legacy ones from SLES 10.
  5. On SLES 12, remove "/etc/SUSEConnect"
  6. In addition, the problem explained in TID 7017994: "Attempt to bootstrap a client to a SUSE Manager 3 Server returns "Internal Server Error" could exist.
    Please remove the machine-id for dbus and regenerate it again as explained in that TID.
  7. Run the bootstrap script on the client systems again.
  8. Run again "mgr-ncc-sync" or "mgr-sync refresh" on the SUSE Manager server from command line.

(*) NOTE:
The Novell Customer Center (NCC) and are not available anymore. SLE10 and SLE11 Systems still registered to the Novell Customer Center (NCC) can be migrated to the SUSE Customer Center (SCC) as outlined at:


The cause of the issue is that a new client system has been registered using the same NCC credentials of an existing one, causing the override of it. Most likely the two systems were cloned.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7012170
  • Creation Date: 19-Apr-2013
  • Modified Date:30-Dec-2021
    • SUSE Manager

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.