Quest Migration Manager for AD Limits/Concurrent Migrations

For large, geographically distributed projects, it is recommended to setup separate Resource Update Manager consoles (with their own AD LDS replica) in each location containing workstations.  This localizes the deployment traffic as well as the communications back to console from the deployed agents (the communications are not continuous unless you ask for real time stats - which I stay away from).  The agents operate independently and in parallel when performing their processing work so there's no limit to how many you can deploy and run.  I recall that when you do a mass agent deployment, the service will rollout five agents at a time (I could be off on that number) and queue the rest...deploying in batches of five.  I'm not sure if there is parameter somewhere you can modify to change this behavior (perhaps someone else will chime in).

There is a nice set of Powershell cmdlets shipped with QMM known as PowerRUM that can greatly streamline a large scale project.  Definitely worth a look.

Thanks for the reply!

Are there specific documents or documentation around this? From what you say, 20-30 at one time would be a piece of cake with no real restrictions barring the actual push of the agent itself. That is good news but if there is any hard data on limitations or similar, I would like to have it handy. I did search but was not able to find anything on this.

Thanks for the reply!

Are there specific documents or documentation around this? From what you say, 20-30 at one time would be a piece of cake with no real restrictions barring the actual push of the agent itself. That is good news but if there is any hard data on limitations or similar, I would like to have it handy. I did search but was not able to find anything on this.

I'm not aware of any documentation of this nature.   I would recommend that you have a look through the Quest Support Knowledge Base.  There's a tremendous amount of anecdotal knowledge out there in the highly specialized consulting community around the product.  If your organization is of any size, you would be well advised to find yourself a certified consultant to at least help you lay the ground work for your project.  It could save you a lot of frustration.  And yes, there are integrators out there who do this stuff - you don't HAVE to hire Quest's PS.  Just make sure whomever you engage with is certified on the product.

1000s are a piece of cake. Here is a link to the resource processing guide and the RUM (Resouce update manager) section. https://support.quest.com/technical-documents/migration-manager-for-ad/8.15/resource-processing-guide/2