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

Cannot deploy Sophos protection to trusted domain

I'm a new Sophos customer and I have a new installation of Sophos Endpoint protection server.  I successfully installed Sophos protection to all my domain1.com computers.  I have a domain2.com that I am trying to deploy it to as well. 

I have a two way trust setup.  I have synchronized the domain with the console.  When I try to protect the computers I get:

   Installation failed                     Date/time                Code      Description                            

                                           12/20/2016 9:23:45 AM    0000002e  The installation could not be started. The computer may need additional configuration before installation. See article 29287.

 

Firewall is turned off

On PC: Service - Task Scheduler (Started), Service - Windows Installer (not Disabled), Service - Remote Registry (Started)

On Enterprise server:Firewall is turned off, Service - Remote Registry (Started)

 

I've ensured a nslookup of the Desktop PC from my SEC server matches the ipconfig result on the Desktop PC.

I can go to \\<SophosServerName>\SophosUpdate from the Desktop PC, it doesn't prompt for credentials

C:\ProgramData\Sophos\Update Manager\Update Manager folder (default location) is shared and the group 'Everyone' has read access.  Ensured these accounts are there with full control permission: SYSTEM, NETWORK SERVICE

From the endpoint computer I can open the central share in Windows Explorer (Start | Run | Type: \\<servername>\SophosUpdate\)

Created and ran a scheduled task on remote PC.

 

 

I have a support ticket but have not gotten anywhere with that.  Any Sophos users have an idea of what to check?  Does Sophos deploy to the computer as Computer.domain2.com?  or just computer?  Where are the logs on the server to see what the issue is?

 



This thread was automatically locked due to age.
Parents
  • Ran into a problem with this configuration.  When two computers have the same name on the different domains.  PC1.domain2.com and PC1.domain2.com.  The system never deploys to PC1.domain2.com.

     

    Any thoughts?

  • Hello April Beachy,

    SEC uses the (NetBIOS) name displayed to resolve the name, specifically it doesn't append any domain info. As the information (name) came from an external source you can't modify it easily..
    I haven't tested whether SEC relies relies solely on the resolver - likely it does. Protection is normally a one-time event and frankly for rather complex topologies I'd use a GPO or some other alternative means. Temporarily modifying etc\hosts could be a work-around.

    Christian

Reply
  • Hello April Beachy,

    SEC uses the (NetBIOS) name displayed to resolve the name, specifically it doesn't append any domain info. As the information (name) came from an external source you can't modify it easily..
    I haven't tested whether SEC relies relies solely on the resolver - likely it does. Protection is normally a one-time event and frankly for rather complex topologies I'd use a GPO or some other alternative means. Temporarily modifying etc\hosts could be a work-around.

    Christian

Children
No Data