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

Configure message relay in ver 5.2.2

PBJ_Family

I am having trouble configuring a message relay in ver 5.2.2.  I followed the instructions here:

http://www.sophos.com/en-us/support/knowledgebase/14635.aspx

It does not list ver 5.2 on that page but I cannot find any instructions anywhere that do.

The issue I have is that according to the video on that page, the ConnectionCache registry value is supposed to be 20512 to indicate that the machine has converted to a message relay.  The value is 10.

Everything else seems to indicate that it worked, although currently I have no endpoints setup to use that relay yet.  But on the relay machine itself I see that the mrinit.conf located in C:\Program Files (x86)\Sophos\Remote Management System is the one I modified and does list itself as the "ParentRouterAddress".  I understand this is how you would confirm that an endpoint had pulled its configuration from this machine.

:56262


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

    Hello PBJ_Family,

    well, there's a twist but I have no experience with it: The SUM installer comes with its own RMS, version 4.0. The Endpoint product (which provides the relay feature) uses version 3.4. SUM 1.5.2 and higher takes over RMS updating (it downloads the product from the Warehouse, not the CID). While AutoUpdate still downloads and updates RMS from the CID (3.4.x) the install is effectively a no-op as a higher-versioned product is already installed and consequently ClientMRInit is not called (I've just tested it).

    I've no idea how this is supposed to work in the future. Right now it seems that you should install endpoint first , make sure the endpoint has converted to a relay and then install SUM.

    BTW - you can use aliases in prectically all places, quite handy not only for migration but if your sites have their own DNS you can apply them to update locations and RMS as well (I've mentioned it for example here).  You'd set ParentRouterAddress to (just) the alias, say, relayserver.acme.com which resolves to the SEC server at the main site and the respective relay at the remote sites.

    Allow location roaming

    Dunno if changes are planned with RMS 4.0 and the associated AutoUpdate - as said, at the moment RMSNT is not downloaded from Sophos.

    Christian

    :56328
Reply
  • 0

    Hello PBJ_Family,

    well, there's a twist but I have no experience with it: The SUM installer comes with its own RMS, version 4.0. The Endpoint product (which provides the relay feature) uses version 3.4. SUM 1.5.2 and higher takes over RMS updating (it downloads the product from the Warehouse, not the CID). While AutoUpdate still downloads and updates RMS from the CID (3.4.x) the install is effectively a no-op as a higher-versioned product is already installed and consequently ClientMRInit is not called (I've just tested it).

    I've no idea how this is supposed to work in the future. Right now it seems that you should install endpoint first , make sure the endpoint has converted to a relay and then install SUM.

    BTW - you can use aliases in prectically all places, quite handy not only for migration but if your sites have their own DNS you can apply them to update locations and RMS as well (I've mentioned it for example here).  You'd set ParentRouterAddress to (just) the alias, say, relayserver.acme.com which resolves to the SEC server at the main site and the respective relay at the remote sites.

    Allow location roaming

    Dunno if changes are planned with RMS 4.0 and the associated AutoUpdate - as said, at the moment RMSNT is not downloaded from Sophos.

    Christian

    :56328
Children
No Data
Unfiltered HTML