Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 18 replies
  • Subscribers 1 subscriber
  • Views 51596 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 built a second update/relay server in another remote site and I basically have the same problem.  It won't convert itself to a relay.  I am sure I can run clientmrinit.exe manually and do it but that doesn't seem to be doing everything it should since the ReportData.xml file doesn't indicate that it is a relay.

    The only thing I have done differently on this machine then the instructions to create the relay is that I actually installed the offical Setup.exe to make it a SUM first.  I even created a seperate distribution point and everything and it still will not convert to a relay.

    I am going to reinstall from scratch and follow the directions exactly (without installing the SUM).  Also yes the instructions actually say "Note: If you are using "Sophos" as Secondary update location it is recommended to enable the option "Allow location roaming" to prevent the client from changing the Message Relay configuration as long as it is getting updates from Sophos."

    I am using Sophos as the secondary.  But I also have laptops in the site and was planning to use the same update policy for everything although at this point I have already created multiple update policies for each site to try and get the relay server to not have that enabled.

    :56317
Reply
  • 0

    Well I built a second update/relay server in another remote site and I basically have the same problem.  It won't convert itself to a relay.  I am sure I can run clientmrinit.exe manually and do it but that doesn't seem to be doing everything it should since the ReportData.xml file doesn't indicate that it is a relay.

    The only thing I have done differently on this machine then the instructions to create the relay is that I actually installed the offical Setup.exe to make it a SUM first.  I even created a seperate distribution point and everything and it still will not convert to a relay.

    I am going to reinstall from scratch and follow the directions exactly (without installing the SUM).  Also yes the instructions actually say "Note: If you are using "Sophos" as Secondary update location it is recommended to enable the option "Allow location roaming" to prevent the client from changing the Message Relay configuration as long as it is getting updates from Sophos."

    I am using Sophos as the secondary.  But I also have laptops in the site and was planning to use the same update policy for everything although at this point I have already created multiple update policies for each site to try and get the relay server to not have that enabled.

    :56317
Children
No Data
Unfiltered HTML