Configure message relay in ver 5.2.2

I was watching the movie again at that link I provided above and I realized there is something I did not do that may be relevant.  The machine I am trying to turn into a relay (I will call it RelayServer) was already an update manager.  So it already had a distribution point on it.  I did not create a new one.  At around the 5 minute point on the video they are adding the remote server as a distribution point for the main server.  I did not do this since RelayServer already had a distribution point.  If I try and do this now it won’’’’t let me because the distribution point on RelayServer is called SophosUpdate so when I try and add the folder \\RelayServer\SophosUpdate as a distribution point on the main Server I get :

The location ‘‘‘‘\\RelayServer\SophosUpdate’’’’ ends with the reserved folder name ‘‘‘‘SophosUpdate’’’’.  Please choose another location.

Unless I am mistaken, the distribution point on RelayServer that was created in the process of making it an update manager should be getting updated from the main server anyway.   But if I look at the distribution tab for the main server the only distribution point listed is \\MainServer\SophosUpdate.  So maybe this is my problem?

I used the instructions from the Sophos Enterprise Console Advanced Startup Guide for ver 5.2.  Basically I installed an additional console on RelayServer then rebooted and ran \\MainServer\SUMInstallSet\Setup.exe on RelayServer.  This installed update manager on RelayServer and created the distribution point \\RelayServer\SophosUpdate. 

Then I followed all of the other instructions as in the video: modified the mrinit file, copied it to the rms subdirectory, ran ConfigCID.exe on the main server while indicating the appropriate directory on RelayServer,  and then used various methods to push the protection to RelayServer to try and trigger it to turn into a message relay.  I also did not have to create a group or an update policy for RelayServer since they already existed.

I was watching the movie again at that link I provided above and I realized there is something I did not do that may be relevant.  The machine I am trying to turn into a relay (I will call it RelayServer) was already an update manager.  So it already had a distribution point on it.  I did not create a new one.  At around the 5 minute point on the video they are adding the remote server as a distribution point for the main server.  I did not do this since RelayServer already had a distribution point.  If I try and do this now it won’’’’t let me because the distribution point on RelayServer is called SophosUpdate so when I try and add the folder \\RelayServer\SophosUpdate as a distribution point on the main Server I get :

The location ‘‘‘‘\\RelayServer\SophosUpdate’’’’ ends with the reserved folder name ‘‘‘‘SophosUpdate’’’’.  Please choose another location.

Unless I am mistaken, the distribution point on RelayServer that was created in the process of making it an update manager should be getting updated from the main server anyway.   But if I look at the distribution tab for the main server the only distribution point listed is \\MainServer\SophosUpdate.  So maybe this is my problem?

I used the instructions from the Sophos Enterprise Console Advanced Startup Guide for ver 5.2.  Basically I installed an additional console on RelayServer then rebooted and ran \\MainServer\SUMInstallSet\Setup.exe on RelayServer.  This installed update manager on RelayServer and created the distribution point \\RelayServer\SophosUpdate. 

Then I followed all of the other instructions as in the video: modified the mrinit file, copied it to the rms subdirectory, ran ConfigCID.exe on the main server while indicating the appropriate directory on RelayServer,  and then used various methods to push the protection to RelayServer to try and trigger it to turn into a message relay.  I also did not have to create a group or an update policy for RelayServer since they already existed.