Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 3 subscribers
  • Views 11637 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

Change from SMB Share to http not possible

Tamer Kor

Hello,

i changed the updating Profile from \\servername\sophosupdate to http://servername/sophosupdate as Primary Installation Source, but when trying to save, a popup comes up as the attached Image Shows.

Your Help is appreciated.

 

Tamer

 



This thread was automatically locked due to age.
Parents
  • +1

    Hi Tamer,

    I think you are looking at the Initial Install Source tab; this is the location that endpoints will use as part of the bootstrap process and has to be a UNC path.

    The Update policy has Primary and Secondary update Server tabs, these cna be changed to be http if you have setup WebCIDs.

    I hope this helps.

    Stephen

Reply
  • +1

    Hi Tamer,

    I think you are looking at the Initial Install Source tab; this is the location that endpoints will use as part of the bootstrap process and has to be a UNC path.

    The Update policy has Primary and Secondary update Server tabs, these cna be changed to be http if you have setup WebCIDs.

    I hope this helps.

    Stephen

Children
  • 0 in reply to StephenMcKay

    Hi Stephen,

    many thanks for you prompt answer, okay, i changed it this way.

    Another Thing, i have also Clients in the Network, which are in another Domain, how will this be handled. Also Unix based Clients.

     

    many thanks

     

    Tamer

     

  • 0 in reply to Tamer Kor

    Hi Tamer,

    My memory isnt great on SEC, I think the limitation with the other domains is that Protecting from the console wont work, but making an installer using the Sophos Deployment Packager (https://community.sophos.com/kb/en-us/67504) , or running the installation via the share will be fine.

    If the clients in the other domain can reach the SEC server (port 8192/8194) for policy and reporting and access the WebCID via http for updates then they will work fine. This applies to the Unix clients as well.

    If clients cannot reach the SEC server on 8192 and 8194 due to firewalls, then you can use Message Relays to open up access to nominated servers. https://community.sophos.com/kb/en-us/14635 You can do the same with Update Managers on different domains to localise the updating process as well https://community.sophos.com/kb/en-us/51068

    Regards,

    Stephen

  • 0 in reply to StephenMcKay

    Hi Stephen,

    so do we have to build for each Environment an additional Sophos Environment?

    We opened Port 8192/8194 and Port 80 with an IIS instance is also in place. So we Need to create a Manual Installation Package.

    But the question is, can the Clients also be viewed in the Enterprise Console?

     

    Tamer

  • 0 in reply to Tamer Kor

    Hi Tamer,

    Yes, the clients will all show in the Enterprise Console if the ports are open; https://community.sophos.com/kb/en-us/120396 you can test clients can communicate with the Entprise Console using Telnet to 8192

    From the client:

    telnet server 8192

    You should receive back the IOR of the server router.  Again from the client:

    telnet server 8194

    This is the SSL port the server router is listening on and the one pointed to by the IOR as read from 8192 as per above.  It will connect but nothing will be displayed.

    Both ports are TCP.

    Stephen

Unfiltered HTML