Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 5060 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

Two computers wuth the same name

Toxo

I have two computers with the same name but in different workgroups. When I installed the first ine it appear in the console without any problems but, when I installed the second one, the first one disappear from the console and now i can't find it.

I thought the console identified computers by their IP address. Am I wrong? Will I have to change the name of one of the computers?

Thank you.

:1509


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

    Sorry for the incorrect information, Toxo.

    I verified that a known MessageSystemAddress takes precedence - thus cloned computers will appear as one with constantly changing attributes and accumulated errors/alerts.

    Note: I'm talking about installing Sophos on the client - not from SEC (either by Protect Computers or AD sync)

    I'm an ignorant when it comes to SQL  but I can tell that the ComputerAdd stored procedure has changed (I didn't doubt that you are right, Nathan). If ComputerAdd is indeed the one called when a new computer registers with the console the I can see it will "replace" a computer with the same name when there is no domain/workgroup (e.g. linux) or when domain/workgroup also matches.  Can't see where it would do so if the workgroups differ.

    Anyway - if a computer is "replaced" when the name matches then it could a problem: we don't have administrative rights over most of our clients (this a university ...), users download an installer package. We can neither enforce a certain name on the computer nor use the setup switch. And given that users often don't care about the workgroup it's not unlikely they also match.

    Admittedly I have only a handful of "pairs" among some 2000 managed computers (not counting the "army of clones" which is out there - they are much more of a problem) - still, it's not perfect.

    Christian

    :1537
Reply
  • 0

    Sorry for the incorrect information, Toxo.

    I verified that a known MessageSystemAddress takes precedence - thus cloned computers will appear as one with constantly changing attributes and accumulated errors/alerts.

    Note: I'm talking about installing Sophos on the client - not from SEC (either by Protect Computers or AD sync)

    I'm an ignorant when it comes to SQL  but I can tell that the ComputerAdd stored procedure has changed (I didn't doubt that you are right, Nathan). If ComputerAdd is indeed the one called when a new computer registers with the console the I can see it will "replace" a computer with the same name when there is no domain/workgroup (e.g. linux) or when domain/workgroup also matches.  Can't see where it would do so if the workgroups differ.

    Anyway - if a computer is "replaced" when the name matches then it could a problem: we don't have administrative rights over most of our clients (this a university ...), users download an installer package. We can neither enforce a certain name on the computer nor use the setup switch. And given that users often don't care about the workgroup it's not unlikely they also match.

    Admittedly I have only a handful of "pairs" among some 2000 managed computers (not counting the "army of clones" which is out there - they are much more of a problem) - still, it's not perfect.

    Christian

    :1537
Children
No Data
Unfiltered HTML