• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 19 subscribers
  • Views 2533 views
  • Users 0 members are here
Options
Related
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

Resource Update Manager distribution criteria

francesco difabio
over 6 years ago

Hello everybody,

we have to perform an intraforest migration of clients and servers (users and groups have already been migrated to target forest).

It has been decided to implement a distributed topology of RUM, therefore we have to install several RUM servers.

We have to define how many RUM servers to install and where.

What are the criteria that must be used to define RUM servers sizing (ie. bandwidth, number of computers etc.)?

What are the hardware requirements for RUM servers?

Unfortunately these information are not specified on QMM for AD documentation.

Thank you in advance

Francesco

Parents
  • 0 over 6 years ago

    The server and workstation side RUM agents want to send status updates back to the RUM.  This doesn't necessarily use a lot of bandwidth but if you have only one RUM console in a large distributed environment and are crossing a WAN to many locations, you might find that the status information in the console is a bit slow to refresh.

    It's hard to say what the "sweet spot" is on the number of computers in a remote location.  For example, if there are only 10 computers but they are all "VIP" users, you might want to put a RUM out there.

    I would use 50 as a good baseline - if you have 50 machines in a location and the bandwidth to that location is heavily utilized, put a remote RUM console out there.  You will of course want to deploy an AD LDS replica instance out there with it.

Reply
  • 0 over 6 years ago

    The server and workstation side RUM agents want to send status updates back to the RUM.  This doesn't necessarily use a lot of bandwidth but if you have only one RUM console in a large distributed environment and are crossing a WAN to many locations, you might find that the status information in the console is a bit slow to refresh.

    It's hard to say what the "sweet spot" is on the number of computers in a remote location.  For example, if there are only 10 computers but they are all "VIP" users, you might want to put a RUM out there.

    I would use 50 as a good baseline - if you have 50 machines in a location and the bandwidth to that location is heavily utilized, put a remote RUM console out there.  You will of course want to deploy an AD LDS replica instance out there with it.

Children
No Data