Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 932 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

2 Clients with same name

FK

Hi,

this month I have seen thrice clients with same name, one active and other inactive (offcourse).

Is there any specific reason why this happens?

I could imagine that a newly installed maschine with old name which previouslly existed in EC might cause something like this.

Am I right?

In such case should the Console not alert that the maschine exists or abort the installation.

Kind Regards
FK

:34485


This thread was automatically locked due to age.
Parents
  • 0

    Hello FK,

    guess you are talking about two (or more) entries for the apparently same physical machine. In principle two or more clients can validly have identical names - thus it is not considered an error (and the name is not a unique key in the database).

    While SEC tries to identify "known" clients and attempts to "match" a client when it initially registers to a known entry (there are several threads in this forum discussion this) it's naturally a heuristic algorithm and thus not always correct. If for example the OS or Workgroup/Domain is different from the one of the previous "incarnation" the client is considered a different one.

    Reinstalling from scratch might prevent SEC from "recognizing" the client.

    Even if SEC could reliably identify the (physical) machine there might be legitimately be two entries - consider a dual-boot scenario: Both systems are unique (and more or less independent) installations even if the use the same name.  

    Christian  

    :34499
Reply
  • 0

    Hello FK,

    guess you are talking about two (or more) entries for the apparently same physical machine. In principle two or more clients can validly have identical names - thus it is not considered an error (and the name is not a unique key in the database).

    While SEC tries to identify "known" clients and attempts to "match" a client when it initially registers to a known entry (there are several threads in this forum discussion this) it's naturally a heuristic algorithm and thus not always correct. If for example the OS or Workgroup/Domain is different from the one of the previous "incarnation" the client is considered a different one.

    Reinstalling from scratch might prevent SEC from "recognizing" the client.

    Even if SEC could reliably identify the (physical) machine there might be legitimately be two entries - consider a dual-boot scenario: Both systems are unique (and more or less independent) installations even if the use the same name.  

    Christian  

    :34499
Children
No Data