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

Message Router/Relay

wellsm

I'm hoping someone out there can help me untangle my brain on Message Routers and Relays.

(Question 1 - are Routers and Relays the same think?  What's the difference?)

I have a case where I need to set up another update manager.  We would like all traffic for the endpoints assigned to that location to go through that Update manager and not directly to the server with the Enterprise console on it.

Getting the updates to pull from the new Update Manager is easy enough - I followed the instructions from the documentation on adding a new UM and all is well.  After I created a new Update policy to point to the new UM, updates were being pulled from the new UM.  Great!

But, it appears that the RMS traffic is heading right back to our main server.  After some reading, I figure I need to make that UM a Message Relay as well.  I use This KB article to edit the mrinit.conf, use ConfigCID.exe, etc. without errors or problems.  

BUT - one bit of confusion.  The doc isn't clear WHICH server you should edit and run ConfigCID on - The server with the Console or the new Update Manager server.  I figured I should run this on the master server with the Console, but I didn't see the new mrinit.conf file propogate down.

So, Which server do I update?

Also - if I make the change for a client to point to this new server for updates, will it also use it for Message Routing/relaying?  OR would I need to reprotect for that?

(Thanks in Advance)

:39535


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

    Hi,

    You should be running configcid against the "CID" on "ServerB" I.e. on the relay.

    So if I have 2 computers SECServer and SUMRelayServer.

    Install SEC on SECServer

    This will create local CIDs, etc..

    E.g. \\SECServer\sophosupdate\CIDs\S000\SAVSCFXP

    Install SUM on SUMRelayServer.

    Configure the SUM on SUMRelayServer using SEC to subscribe to packages.

    Once downloaded you will have a CID on SUMRelayServer.

    E.g. \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP


    Edit the CID on SUMRelayServer with the custom mrinit.conf.

    Run config CID against it.e.g.

    Configcid.exe \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP

    (should see that \rms\mrinit.conf) is added to the checksum file)

    Configcid.exe is run from the management server SECServer computer as it needs access to a registry key on SECServer.

    If this is a problem you can use the configcid.exe on SUMRelayServer but you will need to copy over the registry key as mentioned in the article.

    Install SAV on SUMRelayServer by running setup.exe from:

    \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP\

    It will then be a relay once RMS completes.

    Install other computer at the site from:

    \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP

    and they will message and update from SUMRelayServer

    Regards,

    Jak

    :39591
Reply
  • 0

    Hi,

    You should be running configcid against the "CID" on "ServerB" I.e. on the relay.

    So if I have 2 computers SECServer and SUMRelayServer.

    Install SEC on SECServer

    This will create local CIDs, etc..

    E.g. \\SECServer\sophosupdate\CIDs\S000\SAVSCFXP

    Install SUM on SUMRelayServer.

    Configure the SUM on SUMRelayServer using SEC to subscribe to packages.

    Once downloaded you will have a CID on SUMRelayServer.

    E.g. \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP


    Edit the CID on SUMRelayServer with the custom mrinit.conf.

    Run config CID against it.e.g.

    Configcid.exe \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP

    (should see that \rms\mrinit.conf) is added to the checksum file)

    Configcid.exe is run from the management server SECServer computer as it needs access to a registry key on SECServer.

    If this is a problem you can use the configcid.exe on SUMRelayServer but you will need to copy over the registry key as mentioned in the article.

    Install SAV on SUMRelayServer by running setup.exe from:

    \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP\

    It will then be a relay once RMS completes.

    Install other computer at the site from:

    \\SUMRelayServer\sophosupdate\CIDs\S000\SAVSCFXP

    and they will message and update from SUMRelayServer

    Regards,

    Jak

    :39591
Children
No Data