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

Managing computers from SEC remotely

constantin3

Hi there,

I was wondering if there is a way to manage remote computers that are not part of a domain in SEC? I have set up a sophor-mr server for remote clients to access updates which works fine. What I'd like to see in the EC is the list of remote computers so we can verify they are up to date.

Although I have searched the forums, I haven't found a definite guide (though that might just be me not reading correctly).

Using server 5.0 and client 10.0.

Any help would be appreciated,

Stephen

:23401


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

    Hello Stephen,

    personally I'd set up a SUM instead of "just" hosting a share but it is not necessary that a message relay is also a SUM.

    Each CID ("distribution point") can be configured individually. Your current configuration contains at least two shares one being \\sophos-mr\SophosUpdate (or whatever name you use). You'd place the modified mrinit.conf there (...\CIDs\S000\SAVSCFXP), run ConfigCID.exe and reprotect sophos-mr. Clients should pick up the changes with the next update and reconfigure themselves to use sophos-mr as realy to the management server.  Of course the clients must be able to connect to ports 8192 and 8194 on sophos-mr (which in turn ideally can connect to the clients' port 8194).

    Do you have different updating policies for your remote clients (i.e. do they specify \\sophos-mr instead of the management server)? 

    It just looks tricky on the first glance :smileyhappy:

    Christian

    :23407
Reply
  • 0

    Hello Stephen,

    personally I'd set up a SUM instead of "just" hosting a share but it is not necessary that a message relay is also a SUM.

    Each CID ("distribution point") can be configured individually. Your current configuration contains at least two shares one being \\sophos-mr\SophosUpdate (or whatever name you use). You'd place the modified mrinit.conf there (...\CIDs\S000\SAVSCFXP), run ConfigCID.exe and reprotect sophos-mr. Clients should pick up the changes with the next update and reconfigure themselves to use sophos-mr as realy to the management server.  Of course the clients must be able to connect to ports 8192 and 8194 on sophos-mr (which in turn ideally can connect to the clients' port 8194).

    Do you have different updating policies for your remote clients (i.e. do they specify \\sophos-mr instead of the management server)? 

    It just looks tricky on the first glance :smileyhappy:

    Christian

    :23407
Children
No Data