Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 4 subscribers
  • Views 7618 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

Unmanaged machines and RMS

Darren EricksonJoquico

I have a lot of Unmanaged machines in SEC. I search some knowledge base and it has something to do with Remote Management Service.

May I know the reasons/causes why the RMS fails?



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

    Once protected, the Remote Management System (RMS) product is installed along with Sophos AutoUpdate, SAV, etc..

    As part of the install of RMS, the configuration file mrinit.conf if copied by setup.exe from the root of the distribution point to the install directory of RMS. This config is then stored under:
    hklm\software\sophos\messaging system\router
    ParentAddress being a key value to check. This should typically point at the management server. Maybe the first thing to check. Beyond that in terms of firewalls:
    Open TCP 8192 and 8194 on the server so the clients can connect to the routernt.exe process on the server and open TCP 8194 on the client. Not opening 8194 on the client isn't a show stopper but downstream message delivery will be delayed as the client will have to poll for messages instead of being notified to get them.

    I hope this helps get you started.

    Regards,
    Jak
Reply
  • 0
    Hi,

    Once protected, the Remote Management System (RMS) product is installed along with Sophos AutoUpdate, SAV, etc..

    As part of the install of RMS, the configuration file mrinit.conf if copied by setup.exe from the root of the distribution point to the install directory of RMS. This config is then stored under:
    hklm\software\sophos\messaging system\router
    ParentAddress being a key value to check. This should typically point at the management server. Maybe the first thing to check. Beyond that in terms of firewalls:
    Open TCP 8192 and 8194 on the server so the clients can connect to the routernt.exe process on the server and open TCP 8194 on the client. Not opening 8194 on the client isn't a show stopper but downstream message delivery will be delayed as the client will have to poll for messages instead of being notified to get them.

    I hope this helps get you started.

    Regards,
    Jak
Children
No Data
Unfiltered HTML