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

Excluding AD OU from Sophos + mass re-configuration of Sophos client Server location

hi guys,

Is there a way to exclude a specific AD OU from being detected as unmanaged computers? the reason for this is we have about 800 linux vms on the network and we want to exclude them.

Also, what is the best way to re-configure Sophos Clients' primary and secondary update servers on all computers and servers? Group policy with changing the registry files or re-deploy sophos with SCCM. Is it possible to set secondary server to point to the internet instead of the update server?

Thank you for any assistance.

:53307


This thread was automatically locked due to age.
Parents
  • Hello khey,

    Sounds like you have a lot of endpoints.

    the best way to re-configure Sophos

    is, as Jak has stated, via policies from SEC (registry won't work anyway as the policies aren't kept in/backed with the registry). 

    if it is possible to point the secondary [to] Sophos

    Sure - Sophos is available in the Address drop-down menu of the Updating Policy editor.  While it's not impossible to configure updating by other means it's, frankly, pretty retro.

    Christian

    :53327
Reply
  • Hello khey,

    Sounds like you have a lot of endpoints.

    the best way to re-configure Sophos

    is, as Jak has stated, via policies from SEC (registry won't work anyway as the policies aren't kept in/backed with the registry). 

    if it is possible to point the secondary [to] Sophos

    Sure - Sophos is available in the Address drop-down menu of the Updating Policy editor.  While it's not impossible to configure updating by other means it's, frankly, pretty retro.

    Christian

    :53327
Children
No Data