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

Won't discover a new server

JimH

I just added a new DC to our domain. It replaced an old DC. The new server is named the same as the old DC. While the old DC has been renamed a different name and demoted.

Sophos is finding the old server under its new name but will not accept updates. How do I get it to update?

Also, Sophos is NOT finding the new DC which is now in the "Domain Controllers" OU.  My question is how do I get Sophos to discover the new DC? I have inherited this from a previous admin and do not want to risk the current Sophos install by having it search the entire AD. The group setup in Sophos does not necessarily map directly to our existing OU structure.

If I run "Discover Computers" by IP and simply enter the IP address for the new server, will Sophos just find that one machine and add it to the unmanaged computers group without messing with anything else? In other words, will it not blow away the other 300 machines that Sophos is already managing?

:40495


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

    Hello JimH.

    Discover (the naming of the button/procedure is somewhat unfortunate as it in turn consists of 1 Import and 3 Discover methods) is cumulative, i.e. it won't remove any existing client (for that matter even sync would not remove a client which has "disappeared" from the synced container-tree - just move it to the Unassigned group). "True" discover also won't move any client from the group it's in.

    Sophos is finding the old server under its new name but will not accept updates

    You're saying that the old server fails to update? SEC doesn't have to "find" the computer - as the Sophos installation hasn't been modified on the demoted DC it (the RMS component) will continue to report to the management server. As it uses a unique identifier (which is independent from name, IP or role) SEC will notice that this is a known client and just accept the changes to its attributes (like name). Likely there's an issue with the impersonation account (SophosSAU<computername>0) - this is a domain account for a DC and a local account otherwise. There might also be a problem with the Sophos security groups membership (again, domain  groups on a DC). Don't have a solution at hand though, sorry.

    Sophos is NOT finding the new DC

    SEC does not find a computer by itself (unless you are using AD sync) - if you (manually) install Sophos on a client it will start reporting to SEC (and thus "appear") otherwise you'd have to use one of the Discover/Import methods or Import from a file. With Import from AD you can select a container to import from (and a group to import to) - this will move all the (i.e. also existing ones) computers in this container to the specified group (and if applicable create the necessary subgroups to mirror the container hierarchy).

    HTH

    Christian

    :40517
Reply
  • 0

    Hello JimH.

    Discover (the naming of the button/procedure is somewhat unfortunate as it in turn consists of 1 Import and 3 Discover methods) is cumulative, i.e. it won't remove any existing client (for that matter even sync would not remove a client which has "disappeared" from the synced container-tree - just move it to the Unassigned group). "True" discover also won't move any client from the group it's in.

    Sophos is finding the old server under its new name but will not accept updates

    You're saying that the old server fails to update? SEC doesn't have to "find" the computer - as the Sophos installation hasn't been modified on the demoted DC it (the RMS component) will continue to report to the management server. As it uses a unique identifier (which is independent from name, IP or role) SEC will notice that this is a known client and just accept the changes to its attributes (like name). Likely there's an issue with the impersonation account (SophosSAU<computername>0) - this is a domain account for a DC and a local account otherwise. There might also be a problem with the Sophos security groups membership (again, domain  groups on a DC). Don't have a solution at hand though, sorry.

    Sophos is NOT finding the new DC

    SEC does not find a computer by itself (unless you are using AD sync) - if you (manually) install Sophos on a client it will start reporting to SEC (and thus "appear") otherwise you'd have to use one of the Discover/Import methods or Import from a file. With Import from AD you can select a container to import from (and a group to import to) - this will move all the (i.e. also existing ones) computers in this container to the specified group (and if applicable create the necessary subgroups to mirror the container hierarchy).

    HTH

    Christian

    :40517
Children
No Data