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

    jak - thank you for the detailed response.

    I think I'm missing one point - the directions all seem to put the CID/Distribution point on Server 1. I want mine on Server2, with the relay.

    I updated the CID on server1 and now when I point to it from the update policy those endpoints are successfully using server2 as a relay.  

    But, I want that CID on server2.  I have a subscription for the update manager on server2, and that CID is being created there.  Ihad assumed that it would be copied from server1 (which is its source in the update manager  config) but that doesn't seem to work that way.

    Would I need to update the mrinit.conf on server2 and then run configcid there?  Would that CID get overwritten if the same CID on server1 gets updated?  OR do these CIDs on different servers just share the same CID number, but are really unique?

    (As a side note, a feature request would be to put this message relay stuff in the interface so we don't have to deal with it.)

    thanks for your help!

    :39581
Reply
  • 0

    jak - thank you for the detailed response.

    I think I'm missing one point - the directions all seem to put the CID/Distribution point on Server 1. I want mine on Server2, with the relay.

    I updated the CID on server1 and now when I point to it from the update policy those endpoints are successfully using server2 as a relay.  

    But, I want that CID on server2.  I have a subscription for the update manager on server2, and that CID is being created there.  Ihad assumed that it would be copied from server1 (which is its source in the update manager  config) but that doesn't seem to work that way.

    Would I need to update the mrinit.conf on server2 and then run configcid there?  Would that CID get overwritten if the same CID on server1 gets updated?  OR do these CIDs on different servers just share the same CID number, but are really unique?

    (As a side note, a feature request would be to put this message relay stuff in the interface so we don't have to deal with it.)

    thanks for your help!

    :39581
Children
No Data