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

    Well I got to 3/4 configured.  Looks like having 'Allow Location Roaming' turned on in the update policy was preventing RelayServer from converting to a relay.  I turned that off and manually ran clientmrinit.exe and the log indicated it had converted.  Now the connection cache reg key has been changed to 20512 as expected.  I also see Router logs on MainServer indicating that RelayServer is relaying messages for the other two servers there.  The only thing that doesn't appear correct now is that the ReportData.xml file still shows 'RMS router type' as endpoint.

    I think I have enough now to build the second update/relay server at a remote site and if it proceeds smoothly I may rebuild this one from scratch.

    :56287
Reply
  • 0

    Well I got to 3/4 configured.  Looks like having 'Allow Location Roaming' turned on in the update policy was preventing RelayServer from converting to a relay.  I turned that off and manually ran clientmrinit.exe and the log indicated it had converted.  Now the connection cache reg key has been changed to 20512 as expected.  I also see Router logs on MainServer indicating that RelayServer is relaying messages for the other two servers there.  The only thing that doesn't appear correct now is that the ReportData.xml file still shows 'RMS router type' as endpoint.

    I think I have enough now to build the second update/relay server at a remote site and if it proceeds smoothly I may rebuild this one from scratch.

    :56287
Children
No Data
Unfiltered HTML