Quest AD migration manager... 3

[blade1000]

Hello-

Has anyone here used the Quest AD Mig mgr tools for an interforest migration plan?

Just wondering at a high level if the tools provided:

-ease of use
-discover
-monitoring/reporting features.

I have read thru some of the white papers from the quest site, but they are consolidated, not too much information to be honest.

Any information on your experiences would be great and much appreciated.
thanks
blade

 

[blade1000]

Hi Santhosh,

Just had an additional inquiry as I gear up for my installation of the quest tools AD/Exchange..
I am very excited about this and thanks in advance for any additional information

I have roughly under 1000 AD accts/mailboxes to move from source to target.. the customer has bundled T1's and was looking to migrate roughly 90 users/mailboxes each evening for a span of 2 business weeks.. so that gives me 10 business days.. so what do you think sir? am I shooting too high in the number of users per day to migrate?

If I start towards the end of the work day between 3pm to 6pm would it be ok in your experience whether I can migrate 90 or so users per evening (AD and mailbox)..

Just trying to get a feel for how much latitude I have using Quest..

Also I have been reading about DSA (agents) and am not clear on one thing.. if I am migrating file servers/ file and print servers from source to target .. do I need to individually install DSA agents on each individual source server before I can migrate them to the target domain? I am not sure about this but thought I can do everything from the console where I plan to install the Quest migration management tools and that would be that.

please let me know if you can any information and what I am missing if anything.


Thanks very much and appreciate your feedback

blade

 

[58sniper]

Weighing in on it from an Exchange perspective, how much mail are we dealing with? You have to determine how much mail you can move over those pipes in a reasonable amount of time, and that may impact your expected migration velocity.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[SanthoshSivarajan]

You can easily move 90 users/mailboxes per night BUT it s all depends on your configuration. As I mentioned in my previous reply, you need to add all these mailboxes into a “Sync” collection before the migration (maybe a week prior to the migration day). That way you can ensure that all mailboxes are in-sync before you move them into the “switch” collection. You can use the QMM Static Portal to verify the Sync status or you can use a PowerShell command to compare the source and the target mailboxes.

Also, you have a few options to control the bandwidth inside QMM:
• Enable Compression
• Change the QMM PST file size
• Change QMM mail sync schedule

You will see all these configurations inside the QMM Mail Source Agent (MSA) properties page.

How big are these mailboxes? Do you have any Public Folders? Are you planning to migrate them?

DSA – is a directory synchronization agent. It is responsible for directory sync. I think you are confused with the RUM agent (Vmover). The RUM agent (Vmover) is responsible for workstation, file and printer server migration. You need to install the RUM agent on all workstations, file and printer servers. You can use a single DSA for the entire migration. But in general, it is a best practice to use one DSA for dirsync and one for migration.

You can perform all these actions from the QMM console. If needed, you can install multiple RUM consoles for the workstation, file and printer server migrations.



Santhosh Sivarajan

http://blogs.sivarajan.com

http://www.sivarajan.com

 

[blade1000]

Hi Santhosh,

Some answers to your questions to help better answer my overall questions

How big are these mailboxes?
I should have a proper number in size this evening.. I am not administering that environment currently but will gain more control by early next week to determine these numbers.

Do you have any Public Folders? Are you planning to migrate them? yes, there are and plan to migrate them, need to find out size etc. will have info soon


So I can install these RUM agents entirely from the QMM console -I have over 25 file and printer servers and probably over 900 workstations to migrate too.. I worry that if I need to do this manually somehow -I won't have enough time.. I assume once I sync everything I will "see" my source domain assets (workstations, servers etc) and I can "push" the rum agent to these assets? please let me know if I am entirely off base here though.

Otherwise,

There is a T3 between the source and target so we should be in good standing to migrate about 95 users/workstations/mailboxes per evening? your thoughts on this?

Thanks again for all the information you've provided.

blade

 

[blade1000]

Hi santhosh,

I retrieved the mailbox data size and it is roughly 370Gb for approximately 960 users and the public folder data size it about 185Gb... not that much in either data size.

So the 90 or so users per day should be ok...

hey, if I did choose this number of users per day (90 or so) -what is the proper sequence if any to migrate first priority.. would it be:

Migrate the file and print servers first? then computers then user then mailbox? or does this not matter to some degree.

I appreciate any feedback on this Santhosh
blade

 

[SanthoshSivarajan]

If you are planning to migrate PF data, enable the PF sync before the mailbox migration. PF data migration will take longer.

You can see a migration flowchart on my following blog:

http://portal.sivarajan.com/2010/02/active-directory-migration-high-level.html

My recommendation is to migrate File & Printer servers after the user, computer and mailbox migration. After the user migration, users will be able to access the file & print servers using SIDHistory. Before the file and print server migration, make sure to perform “resounce updating” (re-acl) on these servers.

Please let me know if you need more info.


Santhosh Sivarajan

http://blogs.sivarajan.com

http://www.sivarajan.com

 

[kmcferrin]

Just so you know, there are some Exchange 2010 tips that are not included in the QMM for Exchange documentation. We ran into a few odd questions regarding DAG behavior that wasn't covered in the docs and got the supplementary information from one of my Quest contacts. The doc in question is called "MigrationManager_8.6_MigratingToExchange2010.pdf" and should be available from the same site where you downloaded the demo software.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator

 

[blade1000]

thanks

blade